diff options
| author | Hiroki Sato <hrs@FreeBSD.org> | 2012-05-17 02:51:08 +0000 |
|---|---|---|
| committer | Hiroki Sato <hrs@FreeBSD.org> | 2012-05-17 02:51:08 +0000 |
| commit | 282a032540622ef194d646326406f3349c379554 (patch) | |
| tree | feaefb45542a569175c58ea7016463938c1e9e9e /en_US.ISO8859-1/htdocs/news | |
| parent | 2519deaad71bcaff33737e23ebcbd2824782ad0d (diff) | |
| parent | 84d6e5fb459d9143f8b529749d8cde9face5b5e7 (diff) | |
| download | doc-282a032540622ef194d646326406f3349c379554.tar.gz doc-282a032540622ef194d646326406f3349c379554.zip | |
Notes
Diffstat (limited to 'en_US.ISO8859-1/htdocs/news')
107 files changed, 87681 insertions, 0 deletions
diff --git a/en_US.ISO8859-1/htdocs/news/1993/Makefile b/en_US.ISO8859-1/htdocs/news/1993/Makefile new file mode 100644 index 0000000000..022ef33fbf --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/1993/Makefile @@ -0,0 +1,12 @@ +# $FreeBSD$ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +DOCS= freebsd-coined.sgml + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/news/1993/freebsd-coined.sgml b/en_US.ISO8859-1/htdocs/news/1993/freebsd-coined.sgml new file mode 100644 index 0000000000..ddd5b88ae4 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/1993/freebsd-coined.sgml @@ -0,0 +1,40 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA "../.."> +<!ENTITY date "$FreeBSD: www/en/news/1993/freebsd-coined.sgml,v 1.2 2005/10/04 06:22:24 murray Exp $"> +<!ENTITY title "FreeBSD Archives"> +<!ENTITY % navinclude.about "INCLUDE"> +]> +<html> +&header; + +<p><b>To:</b> interim@bsd.coe.montana.edu (Interim 0.1.5)<br> +<b>Subject:</b> Re: "386BSD" trademark (fwd)<br> +<b>From:</b> David Greenman <davidg@implode.rain.com><br> +<b>Date:</b> Sat, 19 Jun 93 17:26:02 -0700<br></p> + +<pre> +> Okay folks.. taking new name suggestions.. we have: +> +> BSDFree86 - Rod, who is going with Jordans improved NON BSDI name.. +> Free86BSD - Jordan, Rod likes this one two... +> - (F86BSD for short) +> +> vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv +> v v +> v This is the hat to drop yours in! v +> v v +> vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv + + + How about just simply "FreeBSD"? No confusion, no fuss, seems like a good + compromise to me. :-) + + --- + + -DG +</pre> + +&footer; + +</body> +</html> diff --git a/en_US.ISO8859-1/htdocs/news/1996/Makefile b/en_US.ISO8859-1/htdocs/news/1996/Makefile new file mode 100644 index 0000000000..2d006f467a --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/1996/Makefile @@ -0,0 +1,12 @@ +# $FreeBSD: www/en/news/1996/Makefile,v 1.2 2000/03/22 16:22:43 phantom Exp $ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +DOCS= index.sgml + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/news/1996/index.sgml b/en_US.ISO8859-1/htdocs/news/1996/index.sgml new file mode 100644 index 0000000000..50001fb0d8 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/1996/index.sgml @@ -0,0 +1,52 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA "../.."> +<!ENTITY date "$FreeBSD: www/en/news/1996/index.sgml,v 1.10 2005/10/04 19:43:48 hrs Exp $"> +<!ENTITY title "FreeBSD News Flash! (1996)"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<html> + &header; + + <h2>December 1996</h2> + + <ul> + <li> + <p><b>24-Dec-1996</b> FreeBSD <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/2.2-BETA">2.2-BETA</a> has + been released. Please see the <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/2.2-BETA/RELNOTES.TXT"> + Release Notes</a> for more information.</p></li> + + <li> + <p><b>13-Dec-1996</b> FreeBSD 2.2-RELEASE will not support + installation on machines with less than 5MB of RAM or 1.2MB floppy + drives. Please see the original <a + href="&base;/releases/2.2R/install-media.html">announcement</a> for + more information.</p> + </li> + </ul> + + <h2>November 1996</h2> + + <ul> + <li> + <p><b>15-Nov-1996</b> FreeBSD <a + href="&base;/releases/2.1.6R/security.html">2.1.6-RELEASE</a> is + out. Please see the <a + href="&base;/releases/2.1.6R/security.html">release notes</a> for + more information.</p> + </li> + + <li> + <p><b>4-Nov-1996</b> The FreeBSD <a + href="http://cvsweb.FreeBSD.org/">CVS</a> development + tree has branched again. <a href="&base;/releases/index.html">See here</a> for + more information.</p> + </li> + </ul> + + <a href="../news.html">News Home</a> + &footer; + </body> +</html> diff --git a/en_US.ISO8859-1/htdocs/news/1997/Makefile b/en_US.ISO8859-1/htdocs/news/1997/Makefile new file mode 100644 index 0000000000..0311987239 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/1997/Makefile @@ -0,0 +1,12 @@ +# $FreeBSD: www/en/news/1997/Makefile,v 1.3 2000/11/07 04:05:20 kuriyama Exp $ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +DOCS= index.sgml + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/news/1997/index.sgml b/en_US.ISO8859-1/htdocs/news/1997/index.sgml new file mode 100644 index 0000000000..3ab2fbb323 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/1997/index.sgml @@ -0,0 +1,270 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA "../.."> +<!ENTITY date "$FreeBSD: www/en/news/1997/index.sgml,v 1.8 2005/10/04 19:43:48 hrs Exp $"> +<!ENTITY title "FreeBSD News Flash! (1997)"> +<!ENTITY % navinclude.about "INCLUDE"> +<!ENTITY ftp "ftp://ftp.FreeBSD.org/pub/FreeBSD"> +]> + +<html> + &header; + + <h2>December 1997</h2> + + <ul> + <li> + <p><b>26-Dec-97</b> A convenient front-end tool for installing and + configuring the <a href="../doc/en_US.ISO8859-1/books/handbook/synching.html#CVSUP">CVSup</a> + utility is now available. To use it, simply login or su to root and + run: <tt><b>pkg_add</b> &ftp;/development/CVSup/cvsupit.tgz</tt></p> + </li> + + <li> + <p><b>2-Dec-97</b> The "FOOF" bug has now been fixed in our + 3.0-current and 2.2-stable branches and can either be incorporated + by using the <a href="../doc/en_US.ISO8859-1/books/handbook/synching.html#CVSUP">CVSup</a> + utility, as described below for the LAND attack fix, or by applying + <a + href="&ftp;/2.2.5-RELEASE/updates/f00f.diff.2.2">these + patches</a>.</p> + </li> + + <li> + <p><b>1-Dec-97</b> The "LAND attack" bug in TCP/IP has now been fixed + in all relevant branches and can be incorporated by using the <a + href="../doc/en_US.ISO8859-1/books/handbook/synching.html#CVSUP">CVSup</a> utility to track + the latest 2.2 or 3.0 sources.</p> + </li> + + <li> + <p><b>1-Dec-97</b> Team FreeBSD is a group of FreeBSD users and + supporters contributing CPU idle time in an effort to crack RSA's + 64-bit encryption code. For more information, visit <a + href="http://www.circle.net/team-freebsd/">Team FreeBSD's WWW + site</a>.</p> + </li> + </ul> + + <h2>November 1997</h2> + + <ul> + <li> + <p><b>21-Nov-97</b> <em>Pentium bug</em> -- We are aware of the "F00F" + Pentium halting bug and are working with Intel on a fix. When we + have a fix ready for public consumption it will be announced here, + on the mailing list announce@FreeBSD.org and to the Usenet newsgroup + <a + href="news:comp.unix.bsd.freebsd.announce">comp.unix.bsd.freebsd.announce</a>. Your patience is appreciated.</p> + </li> + + <li> + <p><b>09-Nov-97</b> FreeBSD 2.2.5-RELEASE CDROMS are now in stock and + shipping to customers worldwide. More information is available at + <a + href="http://www.wccdrom.com/titles/os/fbsd25.htm">http://www.wccdrom.com/titles/os/fbsd25.htm</a>.</p> + </li> + </ul> + + <h2>October 1997</h2> + + <ul> + <li> + <p><b>22-Oct-97</b> FreeBSD 2.2.5 has been released. See the <a + href="&base;/releases/index.html">Release Information</a> page for + details. Also be sure to check the <a + href="&ftp;/2.2.5-RELEASE/ERRATA.TXT"> release errata</a> after + installation for any late-breaking issues with 2.2.5 that you should + know about.</p> + </li> + </ul> + + <h2>September 1997</h2> + + <ul> + <li> + <p><b>01-Sep-97</b> FreeBSD performed well in an Internet Week <a + href="http://techweb.cmp.com/internetwk/reviews/rev0901.htm">review</a> of WWW server platforms.</p> + </li> + </ul> + + <h2>August 1997</h2> + + <ul> + <li> + <p><b>11-Aug-97</b> Researchers in Duke University's <a + href="http://www.cs.duke.edu/ari/index.html">Trapeze Project</a> + have developed a high-speed Myrinet driver for FreeBSD. More + information about the driver, Trapeze Project, and its parent + project, the Collaborative Cluster Computing Iniative, including the + code for the Myrinet driver, are available from the CCCI's <a + href="http://www.cs.duke.edu/ari/index.html">WWW page</a>.</p> + </li> + + <li> + <p><b>03-Aug-97</b> Netscape Communications has released a beta + version of Netscape Communicator v4.0 for FreeBSD. It can be + obtained via FTP from <a + href="ftp://ftp.netscape.com/pub/communicator/4.03/4.03b8/english/unix/freebsd/base_install/">ftp.netscape.com</a> or its mirrors.</p> + </li> + </ul> + + + <h2>July 1997</h2> + + <ul> + <li> + <p><b>22-Jul-97</b> MacIP, an AppleTalk-to-IP gateway program for + FreeBSD, is in beta testing. To get the latest version, see <a + href="http://www.promo.de/pub/people/stefan/netatalk/">http://www.promo.de/pub/people/stefan/netatalk/</a> or <a href="ftp://ftp.promo.de/pub/people/stefan/netatalk/">ftp://ftp.promo.de/pub/people/stefan/netatalk/</a>.</p> + </li> + + <li> + <p><b>17-Jul-97</b> The first issue of the FreeBSD Newsletter is now + available in <a href="&ftp;/doc/newsletter/issue1.pdf">Adobe PDF + format</a> (also by <a + href="&ftp;/doc/newsletter/issue1.pdf">FTP</a>). A <a + href="&ftp;/doc/newsletter/README.TXT">help file</a> is available + to assist you in selecting and using a PDF viewer. Article + submissions, advertisements, and letters to the editor should be + sent to <a + href="mailto:newsletter@FreeBSD.org">newsletter@FreeBSD.org</a>.</p> + </li> + </ul> + + <h2>June 1997</h2> + + <ul> + <li> + <p><b>17-Jun-97</b> FreeBSD <a + href="&ftp;/2.2.2-RELEASE/">2.2.2-RELEASE</a> CD-ROM discs are now + in stock; subscription customers should receive them shortly.</p> + </li> + </ul> + + <h2>May 1997</h2> + + <ul> + <li> + <p><b>16-May-97</b> FreeBSD <a + href="&ftp;/2.2.2-RELEASE/">2.2.2-RELEASE</a> has been released. + The <a href="&ftp;/2.2.2-RELEASE/RELNOTES.TXT">Release Notes</a> and + <a href="&ftp;/FreeBSD2.2.2-RELEASE/ERRATA.TXT">Errata List</a> can + provide more information.</p> + </li> + + <li> + <p><b>12-May-97</b> A 3.0-Current SNAP-of-the-day server has been + established at <a + href="ftp://current.FreeBSD.org/pub/FreeBSD/">ftp://current.FreeBSD.org/pub/FreeBSD/</a>. + A 3.0-SNAPshot will be generated daily, and old SNAPshots will be + kept for a minimum of one week.</p> + </li> + </ul> + + <h2>April 1997</h2> + + <ul> + <li><p><b>28-Apr-97</b> The 3.0-current src tree now contains support + for building Symmetric MultiProcessor kernels. For details go to + the <a href="http://www.FreeBSD.org/~fsmp/SMP/SMP.html">SMP</a> + page. + </p> + </li> + + <li><p><b>22-Apr-97</b> A RELENG_2.2 snap-of-the-day server has been + established at <a + href="ftp://releng22.FreeBSD.org/pub/FreeBSD/">ftp://releng22.FreeBSD.org/pub/FreeBSD</a>. + The <a + href="ftp://releng22.FreeBSD.org/pub/FreeBSD/README.TXT">README.TXT</a> has more information.</p> + </li> + + <li> + <p><b>15-Apr-97</b> FreeBSD 2.2.1-RELEASE CDs are shipping. Please + see <a + href="http://www.wccdrom.com/titles/os/fbsd22.htm">http://www.wccdrom.com/titles/os/fbsd22.htm</a> for more information.</p> + </li> + </ul> + + <h2>March 1997</h2> + + <ul> + <li><p><b>28-Mar-97</b> Sony Computer Science Laboratory, Inc. has + released an alpha version of ALTQ/CBQ, an alternative queuing + framework for BSD Unix. <a + href="http://www.csl.sony.co.jp/person/kjc/programs.html">More + information</a> and the <a + href="ftp://ftp.csl.sony.co.jp/pub/kjc/altq.tar.gz">source + code</a> is available.</p> + </li> + + <li> + <p><b>25-Mar-97</b> <a href="&ftp;/2.2.1-RELEASE/">FreeBSD + 2.2.1-RELEASE</a> is now available, replacing 2.2-RELEASE. Read + the <a href="&ftp;/2.2.1-RELEASE/README.TXT">README.TXT</a> file or + the <a href="&base;/releases/2.2.1R/notes.html">Release Notes</a> + for more information.</p> + </li> + + <li> + <p><b>16-Mar-97</b> <a href="&ftp;/2.2-RELEASE/">FreeBSD + 2.2-RELEASE</a> is now available. Read the <a + href="&ftp;/2.2-RELEASE/README.TXT">README.TXT</a> file or the <a + href="&base;/releases/2.2R/notes.html">Release Notes</a> for + more information.</p> + </li> + </ul> + + <h2>February 1997</h2> + + <ul> + <li> + <p><b>20-Feb-1997</b> FreeBSD 2.1.7-RELEASE is now available. Read the + README.TXT file or the <a href="&base;/releases/2.1.7R/notes.html"> + Release Notes</a> for more information.</p> + </li> + + <li> + <p><b>10-Feb-1997</b> FreeBSD 3.0-970209-SNAP has been released. Read + the README.TXT file for more information about this + release.</p> + </li> + + <li> + <p><b>06-Feb-1997</b> A serious security problem affecting FreeBSD + 2.1.6 and earlier systems was found. The problem has been corrected + within the -stable, -current, and RELENG_2_2 source trees. As an + additional precaution, FreeBSD 2.1.6 is no longer available from the + FTP distribution sites. You can read more about the problem and + solution from the <a + href="&ftp;/CERT/advisories/FreeBSD-SA-97:01.setlocale">FreeBSD-SA-97:01.setlocale</a> security announcement.</p> + </li> + + <li> + <p><b>06-Feb-1997</b> The final pre-release version of FreeBSD + 2.2-GAMMA, is now available. The README.TXT file has more + information.</p> + </li> + + <li> + <p><b>02-Feb-1997</b> A snap-of-the-day server has been set up for the + most current <A HREF="../releases/snapshots.html">snapshot</a> + release of FreeBSD 2.2. Read the <A + HREF="ftp://22gamma.FreeBSD.org/pub/FreeBSD/README.TXT">README.TXT</A> file for more information.</p> + </li> + </ul> + + <h2>January 1997</h2> + + <ul> + <li> + <p><b>25-Jan-1997</b> FreeBSD <A HREF="&ftp;/3.0-970124-SNAP/"> + 3.0-970124-SNAP</A> has been released. Please see the <a + href="&ftp;/3.0-970124-SNAP/RELNOTES.TXT"> Release Notes</a> for + more information.</p> + </li> + </ul> + + <a href="../news.html">News Home</a> + &footer; + </body> +</html> diff --git a/en_US.ISO8859-1/htdocs/news/1998/Makefile b/en_US.ISO8859-1/htdocs/news/1998/Makefile new file mode 100644 index 0000000000..a979585697 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/1998/Makefile @@ -0,0 +1,15 @@ +# $FreeBSD: www/en/news/1998/Makefile,v 1.4 2005/09/18 04:33:45 hrs Exp $ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +DOCS= index.sgml + +XMLDOCS+= press:${XSL_NEWS_PRESS_OLD}:: +DEPENDSET.press=transtable press + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/news/1998/index.sgml b/en_US.ISO8859-1/htdocs/news/1998/index.sgml new file mode 100644 index 0000000000..1cd039969e --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/1998/index.sgml @@ -0,0 +1,240 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA "../.."> +<!ENTITY date "$FreeBSD: www/en/news/1998/index.sgml,v 1.9 2005/10/04 19:43:48 hrs Exp $"> +<!ENTITY title "FreeBSD News Flash! (1998)"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<html> + &header; + + <h2>December 1998</h2> + + <ul> + <li><p><b>28-Dec-98</b> + Unless circumstances dictate otherwise, FreeBSD 3.0 will depart + the -CURRENT branch late in the day on 15 January 1999. The 3.1 + release will follow 30 days later, on 15 February 1999. + Developers should consider this as ADVANCE NOTICE of these + events.</p></li> + + <li><p><b>13-Dec-98</b> + Walnut Creek CDROM has opened the <a + href="http://www.freebsdmall.com/">FreeBSD Mall</a>, a site + devoted to the commercial aspects of FreeBSD, including add-ons, + hardware, and commercial tech-support. To advertise or sell your + products or services at the FreeBSD Mall, contact BSDi.</p></li> + </ul> + + <h2>November 1998</h2> + + <ul> + <li><p><b>30-Nov-98</b> + <a href="&base;/releases/2.2.8R/announce.html">FreeBSD 2.2.8</a> + has been released. Please see the <a + href="&base;/releases/index.html">Release Information</a> page for + more details. Also be sure to check the <a + href="&base;/releases/2.2.8R/errata.html">release errata</a> after + installation for any late-breaking issues with 2.2.8 that you + might need to be aware of.</p></li> + + <li><p><b>26-Nov-98</b> + <a href="http://www.freebsdrocks.com/">FreeBSD Rocks</a> is an + initiative designed to provide the FreeBSD community with the + latest FreeBSD news, software and resources. All areas include + search facilities, making keyword searching of historical posts + a breeze. The pages are updated daily and everyone is invited to + sign up an post an article. If it happened today, you'll see it + on FreeBSDRocks.</p></li> + </ul> + + <h2>October 1998</h2> + + <ul> + <li><p><b>15-Oct-98</b> + <a href="&base;/releases/3.0R/announce.html">FreeBSD 3.0</a> has + been released. See the <a + href="&base;/releases/index.html">Release Information</a> page for + details. Also be sure to check the <a + href="&base;/releases/3.0R/errata.html">release errata</a> after + installation for any late-breaking issues with 3.0 that you might + need to be aware of.</p></li> + </ul> + + <h2>September 1998</h2> + + <ul> + <li><p><b>15-Sep-98</b> + September 15th is the scheduled date for entering BETA with the + 3.0-CURRENT tree. As all of you already (should) know, 3.0 is + scheduled for release on October 15th so this gives us a nice 30 + day BETA period. During this time, I don't expect anyone to drop + in significant new work or otherwise perturb the 3.0-CURRENT tree + in such a way that violates the general idea of a BETA (you're + supposed to test what you have, not move the goalposts every + couple of days :).</p></li> + + <li><p><b>13-Sep-98</b> + After more than a year of development, the Common Access Method + SCSI layer for FreeBSD will be integrated into 3.0-CURRENT on + Sunday, September 13th. The CAM development team is currently + busy ensuring that the integration process goes as smoothly as + possible, so please understand that we may be slow to respond to + questions about CAM during that time.</p></li> + + <li><p><b>09-Sep-98</b> + Perl5 is now imported into the 3.0-CURRENT source + tree.</p></li> + + <li><p><b>05-Sep-98</b> + <a name="giveaway" href="http://visar.csustan.edu/">The BSD CD + Giveaway List</a>. If somebody has a CD to give away (recipient + pays for shipping) or to lend locally, they can put their email + address on the list. Hardware and literature can also be given + away. We encourage people to donate CDs to local libraries and + put them on the list as well.</p></li> + + <li><p><b>01-Sep-98</b> + First issue of Daemon News arrives day earlier. This ezine is + by the BSD community for the BSD community. See <a + href="http://www.daemonnews.org/">http://www.daemonnews.org/</a></p></li> + </ul> + + <h2>August 1998</h2> + + <ul> + <li><p><b>31-Aug-98</b> + FreeBSD -CURRENT branch (the future 3.0-RELEASE) has switched to + ELF from a.out format. People involved did a great job; + transition went smooth. Check the <a + href="http://www.FreeBSD.org/search/search.html">freebsd-current@FreeBSD.org</a> + mail archive for more information on the transition to + ELF.</p></li> + + <li><p><b>23-Aug-98</b> + Suidcontrol-0.1 utility has been released. The suidcontrol is an + experimental utility for managing suid/sgid policy under FreeBSD. + You can get more information at <a + href="http://www.watson.org/fbsd-hardening/suidcontrol.html">http://www.watson.org/fbsd-hardening/suidcontrol.html</a></p></li> + + <li><p><b>09-Aug-98</b> + FreeBSD Security How-To has been published. This work is + currently in beta and can be found at <a + href="http://www.best.com/~jkb/howto.txt">http://www.best.com/~jkb/howto.txt</a></p></li> + </ul> + + <h2>July 1998</h2> + + <ul> + <li><p><b>22-Jul-98</b> + FreeBSD 2.2.7 has been released. See the <a + href="&base;/releases/index.html">Release Information</a> page for + details. Also be sure to check the <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/2.2.7-RELEASE/ERRATA.TXT">release errata</a> + after installation for any late-breaking issues with 2.2.7 that you + should know about.</p></li> + + <li><p><b>16-Jul-98</b> + A ``FreeBSD for Linux users'' documentation effort has + started. Please see the <a href="&base;/docproj/current.html">list of + current documentation projects</a> for more + information.</p></li> + + <li><p><b>13-Jul-98</b> + <a href="mailto:jkh@FreeBSD.org">Jordan Hubbard</a> writes an <a + href="http://editorials.freshmeat.net/jordan980713/">editorial</a> + on the past and future of the Unix community.</p></li> + + <li><p><b>09-Jul-98</b> + A <a href="http://www.es.FreeBSD.org/es/FAQ/FAQ.html">Spanish + translation</a> of the <a href="&base;/doc/en_US.ISO8859-1/books/faq/index.html">FAQ</a> has been + completed by the <a href="http://www.es.FreeBSD.org/es/">Spanish + Documentation Project</a>. More information can be found at the <a + href="&base;/docproj/translations.html">translations + page</a>.</p></li> + </ul> + + <h2>May 1998</h2> + + <ul> + <li><p><b>30-May-98</b> + FreeBSD and Apache are used in <a + href="http://www.WebTechniques.com/features/1998/05/engelschall/engelschall.shtml">this + very useful article</a> on implementing a web farm using round-robin + DNS in <a + href="http://www.WebTechniques.com/">WEBTechniques.com</a>.</p></li> + + <li><p><b>23-May-98</b> + The second issue of the FreeBSD Newsletter is now available in <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/newsletter/issue2.pdf">Adobe + PDF format</a> (also by <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/newsletter/issue2.pdf">FTP</a>). + A <a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/newsletter/README.TXT">help + file</a> is available to assist you in selecting and using a PDF + viewer. Article submissions, advertisements, and letters to the + editor should be sent to <a + href="mailto:newsletter@FreeBSD.org">newsletter@FreeBSD.org</a>.</p></li> + + <li><p><b>01-May-98</b> + The FreeBSD Project set up <a name="anoncvs" + href="&base;/doc/en_US.ISO8859-1/books/handbook/synching.html#ANONCVS">Anonymous CVS</a> for the + <a href="http://cvsweb.FreeBSD.org/">FreeBSD CVS + tree</a>. Among other things, it allows users of FreeBSD to + perform, with no special privileges, read-only CVS operations + against one of the FreeBSD project's official anoncvs + servers.</p></li> + </ul> + + <h2>April 1998</h2> + + <ul> + <li><p><b>16-Apr-98</b> + The new 4 CD set of FreeBSD 2.2.6 is now in stock and should start + shipping to subscription and back-order customers tomorrow. More + information on the CD contents are available from <a + href="http://www.wccdrom.com/">http://www.wccdrom.com/</a>.</p></li> + + <li><p><b>11-Apr-98</b> + The new FreeBSD project FreeBSD + Mozilla Group is created. The FreeBSD Mozilla Group supports + and improves the free available Netscape web browser, otherwise + known as <a href="http://www.mozilla.org/">Mozilla</a>.</p></li> + </ul> + + <h2>March 1998</h2> + + <ul> + <li><p><b>25-Mar-98</b> + FreeBSD 2.2.6 has been released. See the <a + href="&base;/releases/index.html">Release Information</a> page for + details. Also be sure to check the <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/2.2.6-RELEASE/ERRATA.TXT">release + errata</a> after installation for any late-breaking issues with + 2.2.6 that you should know about.</p></li> + </ul> + + <h2>February 1998</h2> + + <ul> + <li><p><b>08-Feb-98</b> + A page detailing the <a href="&base;/y2kbug.html">FreeBSD Year 2000 + compliance statement</a> is now available, linked through the <a + href="&base;/docs.html">Documentation</a> page.</p></li> + </ul> + + <h2>January 1998</h2> + + <ul> + <li><p><b>08-Jan-98</b> + Improved support for Plug-n-Play cards has now been integrated + into both 3.0-CURRENT and 2.2-STABLE branches now. This is + available in source form via the <a + href="&base;/doc/en_US.ISO8859-1/books/handbook/synching.html#CVSUP">CVSup</a> utility or in + binary release snapshots from <a + href="ftp://current.FreeBSD.org/pub/FreeBSD">current.FreeBSD.org</a></p></li> + </ul> + + <a href="../news.html">News Home</a> + &footer; + </body> +</html> diff --git a/en_US.ISO8859-1/htdocs/news/1998/press.xml b/en_US.ISO8859-1/htdocs/news/1998/press.xml new file mode 100644 index 0000000000..94d1b3862d --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/1998/press.xml @@ -0,0 +1,449 @@ +<press> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD$ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>1998</name> + + <month> + <name>12</name> + + <story> + <name>The story on FreeBSD</name> + + <url>http://www.linuxworld.com/linuxworld/lw-1998-12/lw-12-freebsd.html</url> + <site-name>LinuxWorld</site-name> + <site-url>http://www.linuxworld.com/</site-url> + <date>December 1998</date> + <author>Cameron Laird and Kathryn Soraiz</author> + + <p>This issue has a good article on FreeBSD and why it's worth a look + by Linux folks.</p> + </story> + </month> + + <month> + <name>11</name> + + <story> + <name>The Open-Source Revolution</name> + + <url>http://www.edventure.com/release1/1198.html</url> + <site-name>RELEASE 1.0</site-name> + <site-url>http://www.edventure.com/release1/</site-url> + <date>November 1998</date> + <author>Tim O'Reilly, with an introduction by Esther Dyson</author> + + <p>A brief, business oriented introduction to the open source + community.</p> + </story> + + <story> + <name>Report from Comdex--Walnut Creek CDROM, FreeBSD and + Slackware</name> + + <url>http://www.linuxtoday.com/stories/1005.html</url> + <site-name>Linux Today</site-name> + <site-url>http://www.linuxtoday.com/</site-url> + <date>20 November 1998</date> + <author>Dwight Johnson</author> + + <p>There is a good report on the Walnut Creek booth and FreeBSD at + the Linux Today website. The first half of the report is on + Slackware Linux, the second half is on FreeBSD.</p> + </story> + + <story> + <name>Ellison plans hardware, bashes Bill</name> + + <url>http://www.news.com/News/Item/0,4,28816,00.html</url> + <site-name>CNET News.com</site-name> + <site-url>http://www.news.com/</site-url> + <date>16 November 1998</date> + <author>Tim Clark</author> + + <p>Larry Ellison talking about their new dedicated Oracle servers, + mentions FreeBSD as one of a list of candidate OSes for the + platform.</p> + </story> + </month> + + <month> + <name>10</name> + + <story> + <name>Linux/etc, The other free Unixes, part 2 of 2</name> + + <url>http://www.computerbits.com/archive/19981000/lnx9810.htm</url> + <site-name>Computer Bits</site-name> + <site-url>http://www.computerbits.com/</site-url> + <date>October 1998</date> + <author>Terry Griffin</author> + + <p>Continuation of an earlier column reviewing freely available + Unix like operating systems.</p> + </story> + + <story> + <name>What Is FreeBSD?</name> + + <url>http://www.performance-computing.com/features/9810of1.shtml</url> + <site-name>Performance Computing</site-name> + <site-url>http://www.performance-computing.com/</site-url> + <date>October 1998</date> + <author>Jordan K. Hubbard</author> + + <p>An introduction to FreeBSD, and where it stands with respect to + the other free OSes.</p> + </story> + + <story> + <name>Unix back in the fight with NT</name> + + <url>http://www.mercurycenter.com/business/center/unix102798.htm</url> + <site-name>Mercury Center</site-name> + <site-url>http://www.mercurycenter.com/</site-url> + <date>26 October 1998</date> + <author>Miguel Helft</author> + + <p>An article touting the stability and power of the Unix platform + over NT.</p> + </story> + + <story> + <name>A No-Cost NOS</name> + + <url>http://www.zdnet.com/pcmag/pclabs/nettools/1718/bench1.html</url> + <site-name>ZDNet</site-name> + <site-url>http://www.zdnet.com/</site-url> + <date>20 October 1998</date> + <author>Ryan Snedegar</author> + + <p>Ryan Snedegar reviews FreeBSD 2.2.7 and finds its web-serving + performance to be better than Windows NT.</p> + </story> + + <story> + <name>Open Code Frees Up The Net</name> + + <url>http://www.zdnet.com/intweek/stories/prtarchivestory/0,4356,361668,00.HTML</url> + <site-name>Inter@ctive Week</site-name> + <site-url>http://www.zdnet.com/intweek/</site-url> + <date>19 October 1998</date> + <author>Charles Babcock</author> + + <p>About why customers prefer open source software like Linux, FreeBSD, + Perl and TCL to proprietary alternatives.</p> + </story> + + <story> + <name>It's only free Unix - but I like it</name> + + <url>http://www.ireland.com/newspaper/computimes/1998/1012/cmp2.htm</url> + <site-name>The Irish Times</site-name> + <site-url>http://www.irish-times.com/</site-url> + <date>12 October 1998</date> + <author>David Malone</author> + </story> + </month> + + <month> + <name>9</name> + + <story> + <name>Linux/etc, The other free Unixes, part 1 of 2</name> + + <url>http://www.computerbits.com/archive/19980900/lnx9809.htm</url> + <site-name>Computer Bits</site-name> + <site-url>http://www.computerbits.com/</site-url> + <date>September 1998</date> + <author>Terry Griffin</author> + + <p>Briefly reviews the BSD Unix heritage.</p> + </story> + + <story> + <name>Communications & Networking: Asynchronous Communications + Using select and poll</name> + + <url>http://www.ddj.com/articles/1998/9809/9809e/9809e.htm</url> + <site-name>Dr. Dobb's Journal</site-name> + <site-url>http://www.ddj.com/</site-url> + <date>September 1998</date> + <author>Sean Eric Fagan</author> + + <p>On how to use FreeBSD's + <tt><a href="http://www.FreeBSD.org/cgi/man.cgi?select">select(2)</a></tt> + and + <tt><a href="http://www.FreeBSD.org/cgi/man.cgi?poll">poll(2)</a></tt> + system calls.</p> + </story> + + <story> + <name>Quality Unix for FREE</name> + + <url>http://www.zdnet.com/sr/stories/issue/0,4537,349576,00.html</url> + <site-name>Sm@rt Reseller Online</site-name> + <site-url>http://www.zdnet.com/sr/</site-url> + <date>07 September 1998</date> + <author>Brett Glass</author> + + <p>A short introduction to FreeBSD 2.2.7.</p> + </story> + </month> + + <month> + <name>8</name> + + <story> + <name>Hack raises flags about small ISPs</name> + + <url>http://www.news.com/News/Item/0,4,25526,00.html</url> + <site-name>News.com: Tech News First</site-name> + <site-url>http://www.news.com/</site-url> + <date>21 August 1998</date> + <author>Jim Hu, Staff Writer, CNET NEWS.COM</author> + + <p>Desire for better security has led some ISPs to deploy FreeBSD on + their servers.</p> + </story> + </month> + + <month> + <name>7</name> + + <story> + <name>Walnut Creek CDROM, One of the Largest Public FTP Archives in + the World, Sets Traffic Record Using FreeBSD and Colocating on CRL's + High-Speed Internet Network</name> + + <url>http://www.crl.com/wccdromrcd.html</url> + <site-name>CRL Network Services</site-name> + <site-url>http://www.crl.com/</site-url> + <date>30 July 1998</date> + <author>CRL Press Release</author> + </story> + + <story> + <name>Pulling on one end of the rope</name> + + <url></url> + <site-name>( freshmeat )</site-name> + <site-url>http://www.freshmeat.net/</site-url> + <date>13 July 1998</date> + <author>Jordan K. Hubbard</author> + + <p>Jordan compares the past of Unix with the future of Linux, outlining + possible similarities and describing faults that could be + prevented.</p> + </story> + </month> + + <month> + <name>6</name> + + <story> + <name>Nader urges Windows probe</name> + + <url>http://www.news.com/News/Item/0,4,23145,00.html</url> + <site-name>CNET News.com</site-name> + <site-url>http://www.news.com/</site-url> + <date>14 June 1998</date> + <author>Jeff Pelline</author> + + <p>Consumer-rights advocate Ralph Nader mentions FreeBSD by name.</p> + </story> + + <story> + <name>Stone's Throw, Issue Fourteen: Home of the Brave, Land of the + FreeBSD</name> + + <url>http://RhapsodyOS.com/editorial/stone/ST00014.html</url> + <site-name>RhapsodyOS</site-name> + <site-url>http://RhapsodyOS.com/</site-url> + <date>10 June 1998</date> + <author>Andrew Stone</author> + </story> + </month> + + <month> + <name>5</name> + + <story> + <name>Load Balancing Your Web Site</name> + + <url>http://www.WebTechniques.com/features/1998/05/engelschall/engelschall.shtml</url> + <site-name>Web Techniques Magazine</site-name> + <site-url>http://www.WebTechniques.com/</site-url> + <date>May 1998</date> + <author>Ralf S.Engelschall</author> + + <p>Practical approaches to distributing HTTP traffic at your site. + Includes a section on performance tuning Apache under FreeBSD.</p> + </story> + + <story> + <name>Is NT paranoid or is Unix out to get it?</name> + + <url>http://www.ncworldmag.com/ncworld/ncw-05-1998/ncw-05-nextten.html</url> + <site-name>NC World</site-name> + <site-url>http://www.ncworldmag.com/</site-url> + <date>May 1998</date> + <author>Nicholas Petreley</author> + </story> + + <story> + <name>Security Tools in FreeBSD</name> + + <url>http://www.samag.com/archive/0705/feature.shtml</url> + <site-name>SysAdmin</site-name> + <site-url>http://www.samag.com/</site-url> + <date>May 1998</date> + <author>Guy Helmer</author> + </story> + + <story> + <name>Free Unix: Do You Get What You Pay For?</name> + + <url>http://advisor.gartner.com/inbox/articles/ihl2_6398.html</url> + <site-name>GartnerGroup</site-name> + <site-url>http://www.gartner.com/</site-url> + <date>04 May 1998</date> + <author>G. Weiss</author> + </story> + </month> + + <month> + <name>4</name> + + <story> + <name>The new Unix alters NT's orbit</name> + + <url>http://www.ncworldmag.com/ncworld/ncw-04-1998/ncw-04-nextten.html</url> + <site-name>NC World</site-name> + <site-url>http://www.ncworldmag.com/</site-url> + <date>April 1998</date> + <author>Nicholas Petreley</author> + </story> + + <story> + <name>Who's Serving Who?</name> + + <url>http://www.dv.com/magazine/1998/0498/johnson0498.html</url> + <site-name>DV Live Magazine</site-name> + <site-url>http://www.dv.com/</site-url> + <date>April 98</date> + <author>Nels Johnson</author> + + <p>For smaller companies and web sites, a FreeBSD and Apache on an + Intel (PC) architecture machine is more than sufficient.</p> + </story> + </month> + + <month> + <name>3</name> + + <story> + <name>Searching for the next Windows NT</name> + <url>http://www.ncworldmag.com/ncworld/ncw-03-1998/ncw-03-nextten.html</url> + <site-name>NC World</site-name> + <site-url>http://www.ncworldmag.com/</site-url> + <date>March 1998</date> + <author>Nicholas Petreley</author> + </story> + + <story> + <name>Benchmarking and Software Testing: Tracing BSD System + Calls</name> + + <url>http://www.ddj.com/ddj/1998/1998_03/index.htm</url> + <site-name>Dr. Dobb's Journal</site-name> + <site-url>http://www.ddj.com/</site-url> + <date>March 1998</date> + <author>Sean Eric Fagan</author> + + <p><i>Note</i>: the article is not available online.</p> + </story> + + <story> + <name>Five alternative operating systems reviewed</name> + + <url>http://www.cnet.com/Content/Reviews/Compare/AltOS/</url> + <site-name>CNET</site-name> + <site-url>http://www.cnet.com/</site-url> + <date>25 March 1998</date> + <author>Cormac Foster</author> + </story> + </month> + + <month> + <name>2</name> + + <story> + <name>Source code for the masses</name> + + <url>http://www.news.com/SpecialFeatures/0,5,18652,00.html</url> + <site-name>News.com</site-name> + <site-url>http://www.news.com</site-url> + <date>02 February 1998</date> + <author>Alex Lash</author> + </story> + </month> + </year> + + <year> + <name>1997</name> + + <month> + <name>8</name> + + <story> + <name>The Network Community</name> + + <url>http://www.computerbits.com/archive/9708/lan9708.htm</url> + <site-name>Computer Bits Online</site-name> + <site-url>http://www.computerbits.com/</site-url> + <date>August 1997</date> + <author>Ted Mittelstaedt</author> + </story> + </month> + + <month> + <name>5</name> + + <story> + <name>The Politics of NC Computing According to Oracle</name> + + <url>http://www.ncworldmag.com/ncworld/ncw-05-1997/ncw-05-analysis.html</url> + <site-name>NC World</site-name> + <site-url>http://www.ncworldmag.com/</site-url> + <date>May 1997</date> + <author>Rawn Shaw</author> + </story> + </month> + </year> + + <year> + <name>1996</name> + + <month> + <name>11</name> + + <story> + <name>Assorted Security Tips for UNIX</name> + + <url>http://www.samag.com/documents/s=1211/sam9611d/</url> + <site-name>SysAdmin</site-name> + <site-url>http://www.samag.com/</site-url> + <date>November 1996</date> + <author>Arthur Donkers</author> + + <p>A collection of tips and tricks to secure your internal + network.</p> + </story> + </month> + </year> +</press> diff --git a/en_US.ISO8859-1/htdocs/news/1999/Makefile b/en_US.ISO8859-1/htdocs/news/1999/Makefile new file mode 100644 index 0000000000..2f9a63cf46 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/1999/Makefile @@ -0,0 +1,15 @@ +# $FreeBSD: www/en/news/1999/Makefile,v 1.4 2005/09/18 04:33:45 hrs Exp $ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +DOCS= index.sgml + +XMLDOCS+= press:${XSL_NEWS_PRESS_OLD}:: +DEPENDSET.press=transtable press + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/news/1999/index.sgml b/en_US.ISO8859-1/htdocs/news/1999/index.sgml new file mode 100644 index 0000000000..44c1e9a8ff --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/1999/index.sgml @@ -0,0 +1,368 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA "../.."> +<!ENTITY date "$FreeBSD: www/en/news/1999/index.sgml,v 1.6 2005/10/04 19:43:48 hrs Exp $"> +<!ENTITY title "FreeBSD News Flash! (1999)"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<html> + &header; + + <h2>December 1999</h2> + + <ul> + <li><p><b>30-Dec-1999</b> + A new committer: <a href="mailto:groudier@FreeBSD.org">Gerard + Roudier</a> (Symbios SCSI driver)</p></li> + + <li><p><b>20-Dec-1999</b> + <a href="&base;/releases/3.4R/announce.html">FreeBSD 3.4</a> has + been released. Please see the <a + href="&base;/releases/index.html">Release Information</a> page for + more details. Also be sure to check the <a + href="&base;/releases/3.4R/errata.html">release errata</a> after + installation for any late-breaking issues with 3.4 that + occur.</p></li> + + <li><p><b>18-Dec-1999</b> + A new committer: <a href="mailto:rwatson@FreeBSD.org">Robert + Watson</a> (Coda, POSIX.1e ACLs/Capabilities/Auditing/MAC, FFS + extended attributes, Jail code improvements/documentation, + IPFW/BPF cleanup)</p></li> + + <li><p><b>16-Dec-1999</b> + Remove a committer: James Raynard, <i>"I have decided to resign as + a committer as it's been a very long time since I last had the + time to work on FreeBSD and things have now got to the point where + not even "speed reading" can help me keep up with the commit + mail."</i> Our thanks to James for the time and effort he has + contributed to FreeBSD.</p> + + <p>A new committer: <a href="mailto:asmodai@FreeBSD.org">Jeroen + Ruigrok van der Werven</a> (Docs, in particular mdoc, low-level + interfaces, and other source tree related + documentation)</p></li> + + <li><p><b>15-Dec-1999</b> + A new committer: <a href="mailto:jedgar@FreeBSD.org">Chris D. + Faulhaber</a></p></li> + + <li><p><b>14-Dec-1999</b> + A new committer: <a href="mailto:nbm@FreeBSD.org">Neil + Blakey-Milner</a> (Docs)</p></li> + </ul> + + <h2>October 1999</h2> + + <ul> + <li><p><b>24-Oct-1999</b> + The <a href="http://www.freebsdcon.org/">FreeBSD Con</a> '99 event + this year was a big success! Over 350 people attended, and both + the vendors and attendees alike said they found the event to be + both entertaining and valuable. Many thanks to <a + href="http://www.wccdrom.com/">Walnut Creek CDROM</a> for producing + this event and to <a href="http://www.mckusick.com/"> Dr. Marshall + Kirk McKusick</a> for teaching two kernel internals tutorials and + giving his <a + href="http://www.mckusick.com/history/index.html">History of + BSD</a> talk at the conference.</p></li> + + <li><p><b>10-Oct-1999</b> + A new committer: <a href="mailto:joe@FreeBSD.org">Josef + Karthauser</a></p></li> + </ul> + + <h2>September 1999</h2> + + <ul> + <li><p><b>27-Sep-1999</b> + A new committer: <a href="mailto:nakai@FreeBSD.org">Yukihiro + Nakai</a> (Ports)</p></li> + + <li><p><b>26-Sep-1999</b> + A new committer: <a href="mailto:dan@FreeBSD.org">Dan Moschuk</a> + (Ports)</p></li> + + <li><p><b>17-Sep-1999</b> + <a href="&base;/releases/3.3R/announce.html">FreeBSD 3.3</a> has + been released. Please see the <a + href="&base;/releases/index.html">Release Information</a> page for + more details. Also be sure to check the <a + href="&base;/releases/3.3R/errata.html">release errata</a> after + installation for any late-breaking issues with 3.3 that + occur.</p></li> + + <li><p><b>08-Sep-1999</b> + New committers: <a href="mailto:bp@FreeBSD.org">Boris Popov</a> + (Netware) and <a href="mailto:wsanchez@FreeBSD.org">Wilfredo + Sanchez</a> (FreeBSD/Apple Darwin collaboration)</p></li> + + <li><p><b>05-Sep-1999</b> + A new committer: <a href="mailto:jmas@FreeBSD.org">Jose M. + Alcaide</a> (Docs/Spanish translation)</p></li> + + <li><p><b>03-Sep-1999</b> + New committers: <a href="mailto:imura@FreeBSD.org">R. Imura</a> + (Ports/KDE), <a href="mailto:andy@FreeBSD.org">Andrey + Zakhvatov</a> (Docs/Russian translation) and <a + href="mailto:gioria@FreeBSD.org">Sebastien Gioria</a> (Docs/French + translation)</p></li> + + <li><p><b>02-Sep-1999</b> + A new committer: <a href="mailto:phantom@FreeBSD.org">Alexey + Zelkin</a> (Localization/Docs/Russian translation)</p></li> + </ul> + + <h2>August 1999</h2> + + <ul> + <li><p><b>23-Aug-1999</b> + A new committer: <a href="mailto:jhb@FreeBSD.org">John Baldwin</a> + (Docs)</p></li> + + <li><p><b>11-Aug-1999</b> New committers: <a + href="mailto:alfred@FreeBSD.org">Alfred Perlstein</a> (SMP) and + <a href="mailto:jim@FreeBSD.org">Jim Mock</a> (Docs)</p></li> + + <li><p><b>10-Aug-1999</b> + <a href="http://www.codeforge.com/">C-Forge</a>, an Integrated + Development Environment, has been released (beta) for FreeBSD, + supporting C, C++, Perl, Tcl, and many other + languages.</p></li> + + <li><p><b>06-Aug-1999</b> + A new committer: <a href="mailto:chris@FreeBSD.org">Chris + Costello</a> (Docs)</p></li> + + <li><p><b>04-Aug-1999</b> + A new committer: <a href="mailto:pho@FreeBSD.org">Peter Holm</a> + (Docs)</p></li> + </ul> + + <h2>July 1999</h2> + + <ul> + <li><p><b>29-Jul-1999</b> + New committers: <a href="mailto:shin@FreeBSD.org">Yoshinobu + Inoue</a> and <a href="mailto:sumikawa@FreeBSD.org">Munechika + Sumikawa</a> (KAME/IPv6)</p></li> + + <li><p><b>27-Jul-1999</b> + A new committer: <a href="mailto:mdodd@FreeBSD.org">Matthew N. + Dodd</a> (EISA/PCI/newbus)</p></li> + + <li><p><b>14-Jul-1999</b> + A new committer: <a href="mailto:tanimura@FreeBSD.org">Seigo + Tanimura</a> (MIDI)</p></li> + + <li><p><b>07-Jul-1999</b> + A new committer: <a href="mailto:cg@FreeBSD.org">Cameron Grant</a> + (PCM)</p></li> + + <li><p><b>03-Jul-1999</b> + A new committer: <a href="mailto:marcel@FreeBSD.org">Marcel + Moolenaar</a> (Linux compat)</p></li> + + <li><p><b>01-Jul-1999</b> + New committers: <a href="mailto:nyan@FreeBSD.org">Takahashi + Yoshihiro</a> (PC98) and <a + href="mailto:gehenna@FreeBSD.org">Masahide MAEKAWA</a></p></li> + </ul> + + <h2>June 1999</h2> + + <ul> + <li><p><b>30-Jun-1999</b> + New committers: <a href="mailto:lile@FreeBSD.org">Larry Lile</a> + (Token Ring), <a href="mailto:dbaker@FreeBSD.org">Daniel Baker</a> + (Ports), and <a href="mailto:deischen@FreeBSD.org">Daniel + Eischen</a></p></li> + + <li><p><b>19-Jun-1999</b> + A new committer: <a href="mailto:cpiazza@FreeBSD.org">Chris + Piazza</a></p></li> + + <li><p><b>18-Jun-1999</b> + A new committer: <a href="mailto:iwasaki@FreeBSD.org">Mitsuru + IWASAKI</a></p></li> + + <li><p><b>17-Jun-1999</b> + A new committer: <a href="mailto:green@FreeBSD.org">Brian + Feldman</a></p></li> + + <li><p><b>14-Jun-1999</b> + A new committer: <a href="mailto:sheldonh@FreeBSD.org">Sheldon + Hearn</a></p></li> + + <li><p><b>10-Jun-1999</b> + FreeBSD 3.2-RELEASE CDs are shipping. Subscribers who did not + make any special shipping arrangements should be receiving their + CDs soon. Anyone who wishes to order 3.2-RELEASE or to subscribe + may do so via <a href="http://www.freebsdmall.com/">The FreeBSD + Mall</a>.</p></li> + + <li><p><b>08-Jun-1999</b> + A new <a href="http://freebsd.itworks.com.au/">Australian FreeBSD + Web Mirror</a> now exists. Thanks to <a + href="http://www.itworks.com.au/">ITworks Consulting</a> for + providing the host.</p></li> + </ul> + + <h2>May 1999</h2> + + <ul> + <li><p><b>28-May-1999</b> + A new committer: <a href="mailto:kevlo@FreeBSD.org">Kevin + Lo</a></p></li> + + <li><p><b>27-May-1999</b> + A new committer: <a href="mailto:ru@FreeBSD.org">Ruslan + Ermilov</a></p></li> + + <li><p><b>26-May-1999</b> + A new committer: <a href="mailto:mtaylor@FreeBSD.org">Mark J. + Taylor</a></p></li> + + <li><p><b>18-May-1999</b> + <a href="&base;/releases/3.2R/announce.html">FreeBSD 3.2</a> has + been released. Please see the <a + href="&base;/releases/index.html">Release Information</a> page for + more details. Also be sure to check the <a + href="&base;/releases/3.2R/errata.html">release errata</a> after + installation for any late-breaking issues with 3.2 that you might + need to be aware of.</p></li> + </ul> + + <h2>April 1999</h2> + + <ul> + <li><p><b>30-Apr-1999</b> + A new committer: <a href="mailto:tom@FreeBSD.org">Tom Hukins</a> + (Docs)</p></li> + + <li><p><b>22-Apr-1999</b> + The <a href="&base;/tutorials/docproj-primer/">FreeBSD Documentation + Project Primer</a> is now available (in the <a + href="&base;/tutorials/index.html">tutorials section</a>) for people who want to + learn the technical details of the <a + href="&base;/docproj/docproj.html">Documentation + Project</a>.</p></li> + + <li><p><b>15-Apr-1999</b> + A new committer: <a href="mailto:dick@FreeBSD.org">Richard + Seaman</a></p></li> + + <li><p><b>13-Apr-1999</b> + A new committer: <a href="mailto:mharo@FreeBSD.org">Michael + Haro</a></p></li> + </ul> + + <h2>March 1999</h2> + + <ul> + <li><p><b>30-Mar-1999</b> + A new committer: <a href="mailto:nsayer@FreeBSD.org">Nick + Sayer</a></p></li> + + <li><p><b>10-Mar-1999</b> + A new committer: <a href="mailto:jasone@FreeBSD.org">Jason + Evans</a></p></li> + + <li><p><b>05-Mar-1999</b> + The <a href="http://www.usenix.org/">USENIX Association</a> has + announced the <a + href="http://www.usenix.org/events/usenix99/">1999 USENIX Annual + Technical Conference</a>, scheduled for 06-11 June 1999 in + Monterey, CA, USA. Our own Jordan Hubbard is chairing the FREENIX + Track, devoted to open source software's latest developments and + interesting applications.</p></li> + + <li><p><b>02-Mar-1999</b> + A new committer: <a href="mailto:taoka@FreeBSD.org">Satoshi + TAOKA</a> (Ports)</p></li> + + <li><p><b>01-Mar-1999</b> + A secure server has been set up to accept monetary donations to + the FreeBSD Project. For more information, see: <a + href="http://www.freebsdmall.com/donate/">http://www.freebsdmall.com/donate/</a>.</p></li> + + <li><p><b>01-Mar-1999</b> + FreeBSD 3.1-RELEASE CDs are now shipping. Subscribers should + receive their CDs soon. See <a + href="http://www.wccdrom.com/">http://www.wccdrom.com/</a> to + order.</p></li> + </ul> + + <h2>February 1999</h2> + + <ul> + <li><p><b>25-Feb-1999</b> + A new committer: <a href="mailto:shige@FreeBSD.org">Shigeyuki + FUKUSHIMA</a></p></li> + + <li><p><b>23-Feb-1999</b> + A new committer: <a href="mailto:alc@FreeBSD.org">Alan Cox</a> + (VM)</p></li> + + <li><p><b>19-Feb-1999</b> + A new committer: <a href="mailto:kris@FreeBSD.org">Kris + Kennaway</a></p></li> + + <li><p><b>17-Feb-1999</b> + The Gartner Group has released a report, <i>Divorcing Thin Server + Software from the Hardware</i>, examining the trend in the OEM + market of using software and hardware from different + vendors.</p></li> + + <li><p><b>15-Feb-1999</b> + <a href="&base;/releases/3.1R/announce.html">FreeBSD 3.1</a> has + been released. Please see the <a + href="&base;/releases/index.html">Release Information</a> page for + more details. Also be sure to check the <a + href="&base;/releases/3.1R/errata.html">release errata</a> after + installation for any late-breaking issues with 3.1 that you might + need to be aware of.</p></li> + + <li><p><b>04-Feb-1999</b> + The <a href="http://www.freebsddiary.org/">FreeBSD Diary</a>, a + collection of how-to entries aimed at Unix novices, is now + available.</p></li> + + <li><p><b>03-Feb-1999</b> + A new committer: <a href="mailto:dcs@FreeBSD.org">Daniel + Sobral</a> (Bootloader)</p></li> + </ul> + + <h2>January 1999</h2> + + <ul> + <li><p><b>21-Jan-1999</b> + A new committer: <a href="mailto:roger@FreeBSD.org">Roger + Hardiman</a> (bt8x8 driver)</p></li> + + <li><p><b>20-Jan-1999</b> 3.0-STABLE has now departed the -CURRENT + branch. The next release on this branch will be 3.1-RELEASE, + in mid-February 1999.</p></li> + + <li><p><b>15-Jan-1999</b> + A new committer: <a href="mailto:gallatin@FreeBSD.org">Andrew + Gallatin</a> (Alpha)</p></li> + + <li><p><b>13-Jan-1999</b> + The <a href="http://www.freebsdzine.org/">FreeBSD ezine</a> is a + monthly collection of easy to read (we hope) articles written by + FreeBSD users and administrators just like you.</p></li> + + <li><p><b>10-Jan-99</b> + Jordan Hubbard's "<a href="../sou1999.html">State of the Union</a>", + a look back at 1998, and a look forward to the future.</p></li> + + <li><p><b>02-Jan-1999</b> + A new committer: <a href="mailto:simokawa@FreeBSD.org">Hidetoshi + Shimokawa</a> (Alpha/Ports)</p></li> + </ul> + + <a href="../news.html">News Home</a> + &footer; + </body> +</html> diff --git a/en_US.ISO8859-1/htdocs/news/1999/press.xml b/en_US.ISO8859-1/htdocs/news/1999/press.xml new file mode 100644 index 0000000000..cce85327c0 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/1999/press.xml @@ -0,0 +1,896 @@ +<press> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD$ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>1999</name> + + <month> + <name>12</name> + + <story> + <name>Freei.Net Doubles Service Speed With Intel(R) Server + Platforms</name> + + <url>http://biz.yahoo.com/prnews/991215/wa_freei_d_1.html</url> + <site-name>Freei.Net</site-name> + <site-url>http://www.freei.net</site-url> + <date>15 December 1999</date> + <author>Freei.Net Press Release</author> + + <p>Freei.Net is purchasing hundreds of Intel's LB440GX 2U Rack Server + Platforms as the Internet service provider continues to experience + explosive growth in its subscriber base. ``The LB440GX flawlessly + supports our FreeBSD operating system,'' said Steve Bourg, + Freei.Net's Chief Technical Officer.</p> + </story> + + <story> + <name>FreeBSD 3.3. Robust OS well suited for Internet/Intranet + Deployment</name> + + <url>http://www.data.com/features/1206a.html</url> + <site-name>Data Communications Online</site-name> + <site-url>http://www.data.com/</site-url> + <date>December 1999</date> + + <author>Juha Saarinen</author> + + <p>Linux administrator turns to FreeBSD and finds it impressive.</p> + </story> + </month> + + <month> + <name>11</name> + + <story> + <name>FreeBSD at COMDEX</name> + + <url>http://slashdot.org/article.pl?sid=99/11/21/1430208&mode=nocomment</url> + <site-name>Slashdot</site-name> + <site-url>http://slashdot.org/</site-url> + <date>21 November 1999</date> + <author>Brett Glass</author> + + <p>Brett Glass sent this message + to the FreeBSD -chat mailing list, about his experiences and + perceptions at COMDEX. Of particular interest are the problems he + had trying to get vendors to support the BSDs and Linux.</p> + </story> + + <story> + <name>Who controls free software?</name> + + <url>http://www.salon.com/tech/feature/1999/11/18/red_hat/index.html</url> + <site-name>Salon Magazine</site-name> + <site-url>http://www.salon.com/</site-url> + <date>18 November 1999</date> + <author>Andrew Leonard</author> + + <p>Discusses <a href="http://www.redhat.com/">RedHat</a>'s acquisition + of <a href="http://www.cygnus.com/">Cygnus</a>, quotes + <a href="mailto:jkh@FreeBSD.org">Jordan Hubbard</a> at length, and + mentions FreeBSD.</p> + </story> + + <story> + <name>The Darwinist: Darwin for x86?</name> + + <url>http://macweek.zdnet.com/1999/11/14/darwinist.html</url> + <site-name>MacWeek</site-name> + <site-url>http://macweek.zdnet.com/</site-url> + <date>15 November 1999</date> + <author>Stephan Somogyi</author> + + <p>A report on Wilfredo Sanchez's session on FreeBSD and the Apple + Darwin project at the first FreeBSDCon.</p> + </story> + + <story> + <name>Bob Frankenberg's breaking Windows</name> + + <url>http://cbs.marketwatch.com/archive/19991108/news/current/soapbox.htx?source=blq/yhoo&dist=yhoo</url> + <site-name>CBS MarketWatch</site-name> + <site-url>http://cbs.marketwatch.com/</site-url> + <date>08 November 1999</date> + <author>Michael Tarsala</author> + + <p>In an interview with CBS MarketWatch, Bob Frankenberg, ex-CEO of + <a href="http://www.novell.com/">Novell</a>, praises + FreeBSD for doing ``an exceptionally good job''. FreeBSD is + used in his current company, + <a href="http://www.encanto.com/">Encanto</a>.</p> + </story> + + <story> + <name>Applix and Walnut Creek Partner to Provide Applixware Office for + the FreeBSD Operating System</name> + + <url>http://www.applix.com/releases/99-11-03_applixware_office_for_freebsd_os.cfm</url> + <site-name>Applix Inc.</site-name> + <site-url>http://www.applix.com/</site-url> + <date>03 November 1999</date> + <author>Applix Inc. press release</author> + + <p>Walnut Creek will distribute Applixware Office v4.4.2 in their + FreeBSD 3.3 Power Desktop product. In addition, Walnut Creek will + bundle <a href="http://www.applixware.org/">Applix'SHELF</a>, a + visual open-source application development toolset and runtime + environment with FreeBSD.</p> + </story> + + <story> + <name>LinuxWorld report on FreeBSDCon 99</name> + + <url>http://www.linuxworld.com/linuxworld/lw-1999-10/lw-10-bsd_p.html</url> + <site-name>LinuxWorld</site-name> + <site-url>http://www.linuxworld.com/</site-url> + <date>01 November 1999</date> + <author>Vicki Brown</author> + + <p>October 17, 1999 marked a milestone in the history of FreeBSD -- the + first FreeBSD conference was held in the city where it all began.</p> + </story> + + <story> + <name>FreeBSDCon'99: Fans of Linux's lesser-known sibling gather for + the first time</name> + + <url>http://cnn.com/TECH/computing/9911/01/freebsd.con99.idg/index.html</url> + <site-name>CNN</site-name> + <site-url>http://cnn.com/</site-url> + <date>01 November 1999</date> + <author>Vicki Brown</author> + + <p>Repost of IDG article about FreeBSDCon '99.</p> + </story> + </month> + + <month> + <name>10</name> + + <story> + <name>ServerWatch's Review of FreeBSD</name> + + <url>http://serverwatch.internet.com/reviews/platform-freebsd.html</url> + <site-name>ServerWatch</site-name> + <site-url>http://serverwatch.internet.com/</site-url> + <date>25 October 1999</date> + <author>Kevin Reichard</author> + + <p>FreeBSD v3.2 is as close to the perfect Internet server operating + system as it comes.</p> + </story> + + <story> + <name>Grass Roots Daemocracy</name> + + <url>http://www.upside.com/texis/mvm/story?id=380d3cf90&src=yahoo</url> + <site-name>Upside</site-name> + <site-url>http://www.upside.com/</site-url> + <date>20 October 1999</date> + <author>Sam Williams</author> + + <p>A report from the first annual FreeBSDCon held in Berkeley, + California.</p> + </story> + + <story> + <name>ENTERA DELIVERS FreeBSD STREAMING SERVER SUPPORTING + QUICKTIME</name> + + <url>http://www.entera.com/news/pressreleases/1004elsabsd.html</url> + <site-name>Entera</site-name> + <site-url>http://www.entera.com/</site-url> + <date>04 October 1999</date> + <author>Entera Press Release</author> + + <p>Entera announces a <a href="http://www.streamingserver.org/">free, + standards-based RTSP/RTP server</a> to stream QuickTime from a + FreeBSD platform.</p> + </story> + + <story> + <name>Open Source Software Development as a Special Type of Academic + Research</name> + + <url>http://www.firstmonday.dk/issues/issue4_10/bezroukov/index.html</url> + <site-name>First Monday</site-name> + <site-url>http://www.firstmonday.dk/</site-url> + <date>October 1999</date> + <author>Nikolai Bezroukov</author> + + <p>This paper tries to explore links between open source software + development and academic research as a better paradigm for OSS + development.</p> + </story> + </month> + + <month> + <name>9</name> + + <story> + <name></name> + <url></url> + <site-name>The Boston Globe</site-name> + <site-url>http://www.boston.com/</site-url> + <date>16 September 1999</date> + <p>Claims that the operating systems based on BSD are more reliable + and secure. <i>(requires registration with The Boston Globe prior to + viewing)</i></p> + </story> + + <story> + <name>Beyond Linux, Free Systems Help Build The Web</name> + + <url>http://dowjones.wsj.com/n/SB936961814325017645-d-main-c1.html</url> + <site-name>Wall Street Journal</site-name> + <site-url>http://dowjones.wsj.com/</site-url> + <date>10 September 1999</date> + <author>Lee Gomes</author> + + <p>An introduction to the BSD family of free operating systems.</p> + </story> + + <story> + <name>Maintaining Patch Levels with Open Source BSDs</name> + + <url>http://www.samag.com/archive/0809/feature.shtml</url> + <site-name>SysAdmin</site-name> + <site-url>http://www.samag.com/</site-url> + <date>September 1999</date> + <author>Michael Lucas</author> + + <p>Focusses on the BSD development model and the ease of keeping + upto-date with tools like sup and CVSup.</p> + </story> + </month> + + <month> + <name>8</name> + + <story> + <name>Out of Linux limelight, devil gets its due</name> + + <url>http://web.boston.com/technology/packages/opensource/linux_limelight.shtml</url> + <site-name>Boston Globe</site-name> + <site-url>http://web.boston.com/</site-url> + <date>12 August 1999</date> + <author>Hiawatha Bray</author> + + <p>A short (but not very accurate) introduction to FreeBSD for people + who have heard about Linux.</p> + </story> + + <story> + <name>Reporter's notebook: Hackers on holiday</name> + + <url>http://www.cnn.com/TECH/computing/9908/11/hacker.hols.idg/index.html</url> + <site-name>CNN</site-name> + <site-url>http://www.cnn.com/</site-url> + <date>11 August 1999</date> + <author>Ann Harrison</author> + + <p>CNN reports that the winner during the "Linux Death + Match" at the Chaos Computer Camp in Germany used FreeBSD tools + to win out over Linux attackers. More details are available at + <a href="http://www.42.org/~sec/Berichte/199908Camp/index.en.html#match">http://www.42.org/~sec/Berichte/199908Camp/index.en.html#match</a>.</p> + </story> + + <story> + <name>More FreeBSD Comics</name> + + <url>http://www.userfriendly.org/cartoons/archives/99aug/19990803.html</url> + <site-name>User Friendly the + Comic Strip</site-name> + <site-url>http://www.userfriendly.org/</site-url> + <date>03 August 1999</date> + <author>Illiad</author> + + <p>See also the comics for the + <a href="http://www.userfriendly.org/cartoons/archives/99aug/19990804.html"> + 4th</a> and the + <a href="http://www.userfriendly.org/cartoons/archives/99aug/19990805.html"> + 5th</a>.</p> + </story> + + <story> + <name>World's Biggest Internet Search Engine Goes Online</name> + + <url>http://www.fast.no/company/press/twbs02081999.html</url> + <site-name>Fast Search & Transfer</site-name> + <site-url>http://web.fast.no/</site-url> + <date>02 August 1999</date> + <author>FAST Press Release</author> + + <p>Said to be the largest search engine on the Internet, + <a href="http://www.alltheweb.com/">FAST Web Search</a> + <a href="http://www-new.fast.no/faq/faqfastwebsearch.html#Hardware"> + uses the FreeBSD operating system</a>.</p> + </story> + + <story> + <name>Duke Computer Scientists Exceed "Gigabit" Data + Processing Speeds With Internet Software</name> + + <url>http://www.sciencedaily.com/releases/1999/08/990802072727.htm</url> + <site-name>Science Daily Magazine</site-name> + <site-url>http://www.sciencedaily.com/</site-url> + <date>02 August 1999</date> + <author>Duke University press release</author> + + <p>Using FreeBSD, Duke University computer science researchers have + developed a system for communication at speeds higher than one + billion bits per second in a local area network of personal + computers. More details can be found at the + <a href="http://www.cs.duke.edu/ari/trapeze">Trapeze project</a> web + site.</p> + </story> + </month> + + <month> + <name>7</name> + + <story> + <name>WORLDS LARGEST INDEPENDENT IPP HITS NEW MILESTONE</name> + + <url>http://www.pair.com/pair/press/19990727.html</url> + <site-name>Pair Networks</site-name> + <site-url>http://www.pair.com/</site-url> + <date>27 July 1999</date> + <author>pair Networks press release</author> + + <p>pair Networks, Inc., the World's largest independently owned and + operated paid hosting service, today announced that it has surpassed + the 60,000 Web site milestone. Their web servers in their + state-of-the-art data center house more than 2 Terabytes of storage, + and deliver up to 100 million hits per day to site visitors. pair + uses FreeBSD in order to ensure maximum uptime and reliability.</p> + </story> + + <story> + <name>Free OS? It' s as easy as BSD</name> + + <url>http://www.techwebuk.com/story/TUK19990726S0029</url> + <site-name>TechWeb UK</site-name> + <site-url>http://www.techwebuk.com/</site-url> + <date>26 July 1999</date> + <author>Peter McGarvey</author> + + <p>Network manager Peter McGarvey writes about his experience with + a number of varieties of Unix. He sums up: <i>FreeBSD is the + greatest</i>.</p> + </story> + + <story> + <name>BSD a better OS than Linux?</name> + + <url>http://www.zdnet.com/zdnn/stories/news/0,4586,2299366,00.html</url> + <site-name>ZD Net News</site-name> + <site-url>http://www.zdnet.com/</site-url> + <date>22 July 1999</date> + <author>Bob Sullivan</author> + + <p>BSD is the software behind the world's most popular Web site and the + world's most popular FTP site.</p> + </story> + + <story> + <name>The Net's stealth operating system</name> + + <url>http://www.msnbc.com/news/292376.asp</url> + <site-name>MSNBC</site-name> + <site-url>http://www.msnbc.com/</site-url> + <date>21 July 1999</date> + <author>Bob Sullivan</author> + + <p>BSD powers some of the biggest sites, and its users are among + the most jealous of Linux.</p> + </story> + + <story> + <name>Embed Together: The Case For BSD In Network Appliances</name> + + <url>http://www.performancecomputing.com/features/9906of2.shtml</url> + <site-name>Performance Computing</site-name> + <site-url>http://www.performancecomputing.com/</site-url> + <date>02 July 1999</date> + <author>Kevin Rose and Charles Davidson</author> + + <p>Underlines the advantages of BSD for the embedded device market. + Mentions <a href="http://www.FreeBSD.org/~picobsd/">picoBSD</a>.</p> + </story> + </month> + + <month> + <name>6</name> + + <story> + <name>Radio interview: Linux and FreeBSD</name> + <url>http://ebs.tamu.edu/kamu-fm/gig-24jun99.ram</url> + <site-name>GigABytes Radio Talk Show</site-name> + <site-url>http://cis.tamu.edu/news/gigabytes/index.html</site-url> + <date>June 1999</date> + <author>Chris DiBona and Jordan Hubbard</author> + + <p>Chris DiBona of VA Research and Jordan Hubbard of the FreeBSD + Project give their views on Linux and FreeBSD.</p> + </story> + + <story> + <name>Thin Servers</name> + + <url>http://www.ntsystems.com/db_area/archive/1999/9906/306r1.shtml</url> + <site-name>Windows NT Systems</site-name> + <site-url>http://www.ntsystems.com/</site-url> + <date>June 1999</date> + <author>Ted Drude</author> + + <p>A survey of thin servers, featuring products using FreeBSD as + their internal operating system.</p> + </story> + + <story> + <name>Information Technology and the Internet in Co-operation + Ireland</name> + + <url>http://www.pcc.ie/net/ci.html</url> + <site-name>Public Communications Centre, + Ireland</site-name> + <site-url>http://www.pcc.ie/</site-url> + <date>June 1999</date> + <author>Interview with Michael Doyle</author> + + <p>Michael Doyle, system administrator for + <a href="http://www.co-operation-ireland.ie">Co-operation + Ireland</a> roots for FreeBSD in this interview. Michael is using + FreeBSD and <a href="http://www.postgresql.org">PostgreSQL</a> as + a cost-effective and ultra-reliable solution for his + organization's I.T. needs.</p> + </story> + + <story> + <name>GPL and BSD: explication and comparison</name> + + <url>http://www.32bitsonline.com/article.php3?file=issues/199906/gplbsd&page=1</url> + <site-name>32BitsOnline</site-name> + <site-url>http://www.32bitsonline.com/</site-url> + <date>June 1999</date> + <author>Rob Bos</author> + + <p>An article comparing BSD and GPL style licenses.</p> + </story> + + <story> + <name>CmdrTaco on Slashdot Sale</name> + <url>http://www.wired.com/news/news/business/story/20483.html</url> + <site-name>Wired Business News</site-name> + <site-url>http://www.wired.com/</site-url> + <date>29 June 1999</date> + <author>Leander Kahney</author> + + <p>In an interview with Wired News, Rob Malda, founder of + <a href="http://slashdot.org/">Slashdot</a>, says that he would now + like to spend some more time reporting on FreeBSD.</p> + </story> + + <story> + <name>Server Platforms - FreeBSD Review</name> + + <url>http://serverwatch.internet.com/reviews/platform-freebsd.html</url> + <site-name>ServerWatch</site-name> + <site-url>http://serverwatch.internet.com/</site-url> + <date>17 June 1999</date> + <author>Kevin Reichard</author> + + <p>FreeBSD: Is it the perfect Internet server operating system? As + close as it comes.</p> + </story> + + <story> + <name>Yes! There is intelligent life beyond Linux</name> + + <url>http://www.networkweek.com/openwindow/story/NWW19990611S0005</url> + <site-name>Network Week Online</site-name> + <site-url>http://www.networkweek.com/</site-url> + <date>16 June 1999</date> + <author>David Cartwright</author> + + <p>It looks like Unix, it tastes like Unix but it isn't Unix. It's + FreeBSD!</p> + </story> + </month> + + <month> + <name>5</name> + + <story> + <name>Silicon Carny: Why I run FreeBSD</name> + + <url>http://www.sunworld.com/sunworldonline/swol-05-1999/swol-05-silicon.html</url> + <site-name>SunWorld</site-name> + <site-url>http://www.sunworld.com/</site-url> + <date>May 1999</date> + <author>Rich Morin</author> + + <p>Rich Morin explains why FreeBSD is the superior OS for him.</p> + </story> + + <story> + <name>INTERNET'S BUSIEST SOFTWARE ARCHIVE REACHES NEW DOWNLOAD + MILESTONE</name> + + <url>http://www.wccdrom.com/press/wcarchive_milestone.phtml</url> + <site-name>Walnut Creek CDROM</site-name> + <site-url>http://www.wccdrom.com/</site-url> + <date>26 May 1999</date> + <author>David Greenman</author> + + <p>Walnut Creek CDROM, Inc. announces that their popular software + archive at ftp://ftp.cdrom.com has surpassed the one trillion bytes + (one terabyte) milestone of files downloaded per day from a single + server machine.</p> + </story> + + <story> + <name>Bye-Bye, Windows</name> + + <url>http://home.cnet.com/category/0-3709-7-284910.html</url> + <site-name>CNet</site-name> + <site-url>http://home.cnet.com</site-url> + <date>24 May 1999</date> + <author>Christopher Lindquist</author> + + <p>Reviews alternative PC operating systems. Includes a + <a href="http://home.cnet.com/category/topic/0,10000,0-3709-7-285083,00.html">review of FreeBSD 3.2</a>.</p> + </story> + + <story> + <name>Gnome is no Windows dwarf</name> + + <url>http://news.bbc.co.uk/hi/english/sci/tech/newsid_321000/321433.stm</url> + <site-name>BBC</site-name> + <site-url>http://bbc.co.uk/</site-url> + <date>20 May 1999</date> + <author>Chris Nuttall</author> + + <p>Article on Gnome and the Open Source movement. Mentions + FreeBSD.</p> + </story> + + <story> + <name>OS Also-Rans</name> + + <url>http://www.pioneerplanet.com/reprints/051799tech.htm</url> + <site-name>Pioneer Planet</site-name> + <site-url>http://www.pioneerplanet.com</site-url> + <date>17 May 1999</date> + <author>JULIO OJEDA-ZAPATA</author> + + <p>A short article introducing a few alternative OSes, including + FreeBSD and OpenBSD. Aimed at the general public.</p> + </story> + + <story> + <name>Micron Electronics NetFRAME chosen for Internet's busiest + site</name> + + <url>http://www.wccdrom.com/press/micron.phtml</url> + <site-name>Walnut Creek CDROM</site-name> + <site-url>http://www.wccdrom.com/</site-url> + <date>04 May 1999</date> + <author>David Greenman</author> + + <p>During its first full day of operation, the new NetFRAME 9201 server + set a new all-time one day download record of 969GB + of files, surpassing the previous record set last year of + 873GB/day.</p> + </story> + + <story> + <name>The other open-source OS: FreeBSD</name> + + <url>http://www.zdnet.com/pcweek/stories/news/0,4153,400844,00.html</url> + <site-name>ZD Net</site-name> + <site-url>http://www.zdnet.com/</site-url> + <date>03 May 1999</date> + <author>Anne Chen</author> + + <p>Examples of FreeBSD deployment in the real world and why some + technology officers find it attractive.</p> + </story> + </month> + + <month> + <name>4</name> + + <story> + <name>Open-Source Software: Power to the People</name> + + <url>http://www.data.com/issue/990407/open.html</url> + <site-name>Data Communications</site-name> + <site-url>http://www.data.com</site-url> + <date>April 1999</date> + <author>Lee Bruno</author> + + <p>Linux and BSD Unix are starting to show up on more and more + corporate servers, running alongside or even replacing Netware + and Windows NT.</p> + </story> + + <story> + <name>XML: Complete XML Development System Integrated with + FreeBSD</name> + <url>http://advocacy.FreeBSD.org/stories/pr_xml.html</url> + <site-name>FreeBSD Advocacy</site-name> + <site-url>http://advocacy.FreeBSD.org/</site-url> + <date>29 April 1999</date> + <author>Jordan Hubbard</author> + + <p>Included with FreeBSD 3.1 is a complete, integrated SGML/XML + development system that installs with a simple, easy to use + command sequence.</p> + </story> + + <story> + <name>Inktomi Announces Traffic Server 3.0</name> + + <url>http://www.inktomi.com/new/press/ts3.html</url> + <site-name>Inktomi</site-name> + <site-url>http://www.inktomi.com</site-url> + <date>26 April 1999</date> + <author>Inktomi press release</author> + + <p>FreeBSD is a supported operating system for a new version of + Inktomi's carrier-class network cache platform.</p> + </story> + + <story> + <name>The Matrix: FreeBSD Used to Generate Special Effects</name> + + <url>http://advocacy.FreeBSD.org/stories/pr_matrix.html</url> + <site-name>FreeBSD Advocacy</site-name> + <site-url>http://advocacy.FreeBSD.org/</site-url> + <date>22 April 1999</date> + <author>Jordan Hubbard</author> + + <p>Dual-Processor FreeBSD systems were used to generate a large + number of special effects in the cutting edge Warner Brothers film, + <i>The Matrix</i>.</p> + </story> + + <story> + <name>Let's Get More Educated About FreeBSD</name> + + <url>http://www.osopinion.com/Opinions/PrestonWiley/PrestonWiley1.html</url> + <site-name>osOpinion</site-name> + <site-url>http://www.osopinion.com/</site-url> + <date>20 April 1999</date> + <author>Preston S. Wiley</author> + + <p>A system administrator shares his views on FreeBSD.</p> + </story> + + <story> + <name>The Oldest Free OS</name> + <url>http://www.zdnet.com/sr/stories/column/0,4712,398025,00.html</url> + <site-name>ZD Net</site-name> + <site-url>http://www.zdnet.com</site-url> + <date>15 April 1999</date> + <author>Steven J. Vaughan-Nichols</author> + + <p>What are the oldest free operating systems around? The answer is + the Berkeley Software Distribution (BSD) Unix variants.</p> + </story> + + <story> + <name>FreeBSD wants a place in the sun</name> + + <url>http://www.upside.com/texis/mvm/down_the_toilet?id=3714d4820</url> + <site-name>Upside</site-name> + <site-url>http://www.upside.com</site-url> + <date>13 April 1999</date> + <author>Sam Williams</author> + + <p>Introduces FreeBSD to Linux users.</p> + </story> + + <story> + <name>FreeBSD Offers a Sound Open Source Alternative</name> + + <url>http://www.internetworld.com/print/current/webdev/19990412-freebsd.html</url> + <site-name>Internet World</site-name> + <site-url>http://www.internetworld.com</site-url> + <date>12 April 1999</date> + <author>James C. Luh</author> + + <p>Outside technical circles, many remain unaware of viable choices + for internet servers---like the FreeBSD operating system that drives + Web servers for such high-profile names as Yahoo and Best Internet + Communications (now part of Verio).</p> + </story> + + <story> + <name>Serious FTP: Behind the scenes of Walnut Creek CDROM</name> + + <url>http://cnn.com/TECH/computing/9904/08/cdrom.idg/index.html</url> + <site-name>CNN</site-name> + <site-url>http://cnn.com</site-url> + <date>08 April 1999</date> + <author>Rich Morin</author> + + <p>A description of the Walnut Creek CDROM setup. + The article is also available from + <a href="http://www.sunworld.com/swol-04-1999/swol-04-silicon.html"> + SunWorld</a>.</p> + </story> + + <story> + <name>Thin Servers: Off-the-Shelf Internet Help</name> + + <url>http://www.techweb.com/se/directlink.cgi?DAT19990407S0024</url> + <site-name>TechWeb</site-name> + <site-url>http://www.techweb.com/</site-url> + <date>07 April 1999</date> + <author>Christine Zimmerman</author> + + <p>Discusses thin-servers, including six built using an embedded + FreeBSD kernel.</p> + </story> + </month> + + <month> + <name>3</name> + + <story> + <name>A FreeBSD Comic Strip</name> + + <url>http://www.userfriendly.org/cartoons/archives/99mar/19990320.html</url> + <site-name>User Friendly the Comic Strip</site-name> + <site-url>http://www.userfriendly.org/</site-url> + <date>20 March 1999</date> + <author>Illiad</author> + + <p>See also the serial from the + <a href="http://www.userfriendly.org/cartoons/archives/99mar/19990322.html">22nd</a>, + <a href="http://www.userfriendly.org/cartoons/archives/99mar/19990323.html">23rd</a>, + <a href="http://www.userfriendly.org/cartoons/archives/99mar/19990324.html">24th</a>, + <a href="http://www.userfriendly.org/cartoons/archives/99mar/19990325.html">25th</a>, + <a href="http://www.userfriendly.org/cartoons/archives/99mar/19990326.html">26th</a>, and + <a href="http://www.userfriendly.org/cartoons/archives/99mar/19990327.html">27th</a> of March, 1999.</p> + </story> + + <story> + <name>Rising support for BSD</name> + + <url>http://www.it.fairfax.com.au/990316/openline1.html</url> + <site-name>Fairfax IT News</site-name> + <site-url>http://www.it.fairfax.com.au</site-url> + <date>16 March 1999</date> + <author>Nathan Cochrane</author> + + <p>Columnist Nathan Cochrane talks about the BSD family of open + source operating systems.</p> + </story> + + <story> + <name>Whence the Source: Untangling the Open Source/Free Software + Debate</name> + + <url>http://opensource.oreilly.com/news/scoville_0399.html</url> + <site-name>O'Reilly Open Source</site-name> + <site-url>http://opensource.oreilly.com</site-url> + <date>05 March 1999</date> + <author>Thomas Scoville</author> + + <p>An article on the open-source / free-software debate. Mentions + Berkeley Unix as one of the early successes of shared source code + collaboration.</p> + </story> + </month> + + <month> + <name>2</name> + + <story> + <name>LWN interviews Alan Cox</name> + + <url>http://lwn.net/1999/features/ACInterview/</url> + <site-name>Linux Weekly News</site-name> + <site-url>http://lwn.net/</site-url> + <date>February 1999</date> + + <p>There is a small but interesting FreeBSD mention in LWN in an + interview with Linux's Alan Cox.</p> + </story> + + <story> + <site-name>The Economist</site-name> + <site-url>http://www.economist.com</site-url> + + <date>20 February 1999</date> + + <p>Software that has been developed by thousands of volunteers and is + given away is often better than the stuff for sale. <i>Note</i>: The + article is no longer available online without registration.</p> + </story> + </month> + + <month> + <name>1</name> + + <story> + <name>Twenty Years of Berkeley Unix</name> + + <url>http://www.oreilly.com/catalog/opensources/book/kirkmck.html</url> + <site-name>O'Reilly and Associates</site-name> + <site-url>http://www.oreilly.com</site-url> + <date>January 1999</date> + <author>Marshall Kirk McKusick</author> + + <p>A short history of Berkeley Unix.</p> + </story> + + <story> + <name>WWWsmith: Installation and Configuration of FreeBSD</name> + + <url>http://www.linuxjournal.com/issue57/2515.html</url> + <site-name>LINUX JOURNAL</site-name> + <site-url>http://www.linuxjournal.com/</site-url> + <date>January 1999</date> + <author>Sean Eric Fagan</author> + + <p>Here is how to set up a web server using another freely available + operating system, FreeBSD, a high performance, mature, Unix-like + system.</p> + </story> + + <story> + <name>The return of BSD - What are the BSD flavors and why might you + use them?</name> + + <url>http://www.sunworld.com/swol-01-1999/swol-01-bsd.html</url> + <site-name>SunWorld</site-name> + <site-url>http://www.sunworld.com/</site-url> + <date>January 1999</date> + <author>Greg Lehey</author> + + <p>Introduces the modern BSD OSes to the general public.</p> + </story> + + <story> + <site-name>GartnerGroup</site-name> + <site-url>http://www.gartner.com/</site-url> + <date>18 January 1999</date> + + <p>While finished thin servers should be optimized in both hardware + and software for the task at hand, who says the software and hardware + must come from the same developer? This Perspective examines the + emerging trend in the OEM market of divorcing the software layer from + the hardware layer. Many operating systems are vying to be the OS of + choice for thin servers. This document examines this issue in detail, + particularly the differences between Linux and FreeBSD, the current + de facto leaders in the market. <i>Note</i>: The article is no + longer available online without registration.</p> + </story> + + <story> + <name>Nature Web Matters: Internet tomography</name> + + <url>http://helix.nature.com/webmatters/tomog/tomog.html</url> + <site-name>Nature</site-name> + <site-url>http://www.nature.com/</site-url> + <date>07 January 1999</date> + <author>K.C. Claffy, Tracie Monk & Daniel McRobb, UCSD/CAIDA, + USA.</author> + + <p>The article describes a network management tool built on FreeBSD + that has even used network connections to www.FreeBSD.org for + performing network research.</p> + </story> + </month> + </year> +</press> diff --git a/en_US.ISO8859-1/htdocs/news/2000/Makefile b/en_US.ISO8859-1/htdocs/news/2000/Makefile new file mode 100644 index 0000000000..b3285af56a --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2000/Makefile @@ -0,0 +1,15 @@ +# $FreeBSD: www/en/news/2000/Makefile,v 1.4 2005/09/18 04:33:45 hrs Exp $ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +DOCS= index.sgml + +XMLDOCS+= press:${XSL_NEWS_PRESS_OLD}:: +DEPENDSET.press=transtable press + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/news/2000/index.sgml b/en_US.ISO8859-1/htdocs/news/2000/index.sgml new file mode 100644 index 0000000000..9a63665d29 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2000/index.sgml @@ -0,0 +1,454 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA "../.."> +<!ENTITY date "$FreeBSD: www/en/news/2000/index.sgml,v 1.12 2005/10/04 19:43:48 hrs Exp $"> +<!ENTITY title "FreeBSD News Flash! (2000)"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<html> + &header; + + <h2>December 2000</h2> + + <ul> + <li><p><b>28-Dec-2000</b> + New committer: <a href="mailto:sf@FreeBSD.org">FUJISHIMA Satsuki</a> + (ports)</p></li> + + <li><p><b>06-Dec-2000</b> + New committer: <a href="mailto:clive@FreeBSD.org">Clive T. + Lin</a></p></li> + + <li><p><b>04-Dec-2000</b> + New committers: <a href="mailto:chm@FreeBSD.org">Christoph + Herrmann</a> and <a href="mailto:tomsoft@FreeBSD.org">Thomas-Henning + von Kamptz</a> (growfs)</p></li> + + <li><p><b>01-Dec-2000</b> + New committer: <a href="mailto:iedowse@FreeBSD.org">Ian + Dowse</a></p></li> + </ul> + + <h2>November 2000</h2> + + <ul> + <li><p><b>30-Nov-2000</b> + Individual porting efforts were moved into the <a + href="&base;/platforms/index.html">platforms</a> directory. Separate + pages for the Alpha, IA-64, PowerPC, and SPARC porting projects + can be found there.</p></li> + + <li><p><b>22-Nov-2000</b> + <a href="&base;/releases/4.2R/announce.html">FreeBSD 4.2</a> has + been released. Please see the <a + href="&base;/releases/index.html">Release Information</a> page for + more details. Also be sure to check the <a + href="&base;/releases/4.2R/errata.html">release errata</a> after + installation for any late-breaking issues with 4.2 that + occur.</p></li> + + <li><p><b>22-Nov-2000</b> + And yet another new committer: <a + href="mailto:roam@FreeBSD.org">Peter Pentchev</a> (ports)</p></li> + + <li><p><b>13-Nov-2000</b> + Yet another new committer: <a + href="mailto:okazaki@FreeBSD.org">OKAZAKI Tetsurou</a> + (ports)</p></li> + + <li><p><b>13-Nov-2000</b> + Another new committer: <a href="mailto:kiri@FreeBSD.org">Kazuhiko + Kiriyama</a> (ports)</p></li> + + <li><p><b>13-Nov-2000</b> + New committer: <a href="mailto:demon@FreeBSD.org">Dmitry + Sivachenko</a> (Mainly ports)</p></li> + + <li><p><b>12-Nov-2000</b> + Another new committer: <a href="mailto:issei@FreeBSD.org">Issei + Suzuki</a> (Ports)</p></li> + + <li><p><b>06-Nov-2000</b> + Another new committer: <a + href="mailto:keith@FreeBSD.org">Jing-Tang Keith Jang</a> (ports, + mostly in the chinese category)</p></li> + + <li><p><b>02-Nov-2000</b> + Another new committer: <a href="mailto:benno@FreeBSD.org">Benno + Rice</a> (PowerPC port and OpenFirmware /boot/loader)</p></li> + </ul> + + <h2>October 2000</h2> + + <ul> + <li><p><b>26-Oct-2000</b> + Yet another new committer: <a + href="mailto:DougB@FreeBSD.org">Doug Barton</a> (mergemaster, + and whatever other trouble I can get into)</p></li> + + <li><p><b>26-Oct-2000</b> + A new committer: <a href="mailto:gad@FreeBSD.org">Garance A + Drosehn</a> (lpr and friends)</p></li> + + <li><p><b>18-Oct-2000</b> + <b>New FreeBSD Core Team Elected!</b> Read the official + <a href="&base;/news/press-rel-5.html">press release</a> for + more information.</p></li> + + <li><p><b>16-Oct-2000</b> + A new committer: <a href="mailto:jon@FreeBSD.org">Jonathan + Chen</a> (newcard cardbus)</p></li> + + <li><p><b>03-Oct-2000</b> + The complete track <a + href="http://www.bsdcon.com/schedule.php3">schedule</a> for <a + href="http://www.bsdcon.com">BSDCon</a> has been released. + BSDCon is the premiere annual technical conference for BSD + users and will be held from October 14-20 in Monterey, + CA.</p></li> + + <li><p><b>02-Oct-2000</b> <a href="mailto:dfr@FreeBSD.org">Doug + Rabson</a> has made a series of commits to -CURRENT with early + IA64 support. The kernel will now reach the mountroot prompt. + Please follow the ia64 mailing list for more + information.</p></li> + + <li><p><b>01-Oct-2000</b> + A new committer: <a href="mailto:trevor@FreeBSD.org">Trevor + Johnson</a> (sundry ports, mostly in the audio category)</p></li> + + <li><p><b>01-Oct-2000</b> + A new committer: <a href="mailto:jeh@FreeBSD.org">James + Housley</a> (ports, especially RTEMS. Side interest in + IPv6)</p></li> + + <li><p><b>01-Oct-2000</b> + A new committer: <a href="mailto:lioux@FreeBSD.org">Mário + Sérgio Fujikawa Ferreira</a></p></li> + </ul> + + <h2>September 2000</h2> + + <ul> + <li><p><b>29-Sep-2000</b> + <a href="http://www.terasolutions.com/">TeraSolutions, Inc.</a> + and Lightning Internet Services <a + href="http://www.terasolutions.com/pr092900.html">announced</a> + today that a popular OpenSource software archive at + <a href="ftp://ftp.freesoftware.com/"> ftp.freesoftware.com</a> + (also known as <a + href="ftp://ftp.FreeBSD.org/">ftp.FreeBSD.org</a>) has surpassed + the two trillion bytes (<b>two terabytes</b>) milestone of files + downloaded per day from a single server machine.</p></li> + + <li><p><b>27-Sep-2000</b> + <a href="&base;/releases/4.1.1R/announce.html">FreeBSD 4.1.1</a> has + been released. Please see the <a + href="&base;/releases/index.html">Release Information</a> page for + more details. Also be sure to check the <a + href="&base;/releases/4.1.1R/errata.html">release errata</a> after + installation for any late-breaking issues with 4.1.1 that + occur.</p></li> + + <li><p><b>21-Sep-2000</b> + A new committer: <a href="mailto:bmilekic@FreeBSD.org">Bosko + Milekic</a></p></li> + </ul> + + <h2>August 2000</h2> + + <ul> + <li><p><b>22-Aug-2000</b> + A new committer: <a href="mailto:bmah@FreeBSD.org">Bruce A. + Mah</a> (docs, pkg_version, assorted ports)</p></li> + + <li><p><b>15-Aug-2000</b> + A new committer: <a href="mailto:rv@FreeBSD.org">Rajesh + Vaidheeswarran</a> (ports/devel/cons)</p></li> + + <li><p><b>05-Aug-2000</b> + A new committer: <a href="mailto:onoe@FreeBSD.org">Atsushi + Onoe</a> (awi driver)</p></li> + </ul> + + <h2>July 2000</h2> + + <ul> + <li><p><b>27-July-2000</b> + <a href="&base;/releases/4.1R/announce.html">FreeBSD 4.1</a> has + been released. Please see the <a + href="&base;/releases/index.html">Release Information</a> page for + more details. Also be sure to check the <a + href="&base;/releases/4.1R/errata.html">release errata</a> after + installation for any late-breaking issues with 4.1 that + occur.</p></li> + + <li><p><b>12-July-2000</b> + A new committer: <a href="mailto:marko@FreeBSD.org">Mark + Ovens</a></p></li> + + <li><p><b>11-July-2000</b> + A new committer: <a href="mailto:kbyanc@FreeBSD.org">Kelly + Yancey</a></p></li> + + <li><p><b>11-July-2000</b> + A new committer: <a href="mailto:dwmalone@FreeBSD.org">David + Malone</a></p></li> + + <li><p><b>11-July-2000</b> + A new committer: <a href="mailto:non@FreeBSD.org">Noriaki + Mitsunaga</a> (PC-Card)</p></li> + + <li><p><b>10-July-2000</b> + A new committer: <a href="mailto:ben@FreeBSD.org">Ben + Smithurst</a> (Docs)</p></li> + + <li><p><b>08-July-2000</b> + A new committer: <a href="mailto:dannyboy@FreeBSD.org">Daniel + Harris</a> (Docs)</p></li> + + <li><p><b>07-July-2000</b> + A new committer: <a href="mailto:takawata@FreeBSD.org">Takanori + Watanabe</a> (ACPI)</p></li> + + <li><p><b>06-July-2000</b> + A new committer: <a href="mailto:hrs@FreeBSD.org">Hiroki + Sato</a> (Japanese Docs)</p></li> + + <li><p><b>05-July-2000</b> + A new committer: <a href="mailto:horikawa@FreeBSD.org">Kazuo + Horikawa (Japanese Online Manuals)</a></p></li> + + <li><p><b>03-July-2000</b> + A new committer: <a href="mailto:adrian@FreeBSD.org">Adrian + Chadd</a></p></li> + </ul> + + <h2>June 2000</h2> + + <ul> + <li><p><b>30-June-2000</b> + <a href="http://freshports.org/">http://freshports.org/</a> has + been upgraded to FreshPorts 1.1. The FreshPorts website contains + the latest details of which ports have been create/updated/removed. + This upgrade, the first since FreshPorts was release in early May, + gives you an improved home page, which together with a commit + history means you can find out about your ports faster and + easier.</p></li> + + <li><p><b>29-June-2000</b> + <a href="http://www.tucows.com/">Tucows</a> has added a + <a href="http://bsd.tucows.com/">BSD section</a>.</p></li> + + <li><p><b>26-June-2000</b> + A new committer: <a href="mailto:akiyama@FreeBSD.org">Shunsuke + Akiyama</a> (Optical disk driver)</p></li> + + <li><p><b>24-June-2000</b> + <a href="&base;/releases/3.5R/announce.html">FreeBSD 3.5</a> has + been released. Please see the <a + href="&base;/releases/index.html">Release Information</a> page for + more details. Also be sure to check the <a + href="&base;/releases/3.5R/errata.html">release errata</a> after + installation for any late-breaking issues with 3.5 that + occur.</p></li> + + <li><p><b>20-June-2000</b> + A new committer: <a href="mailto:sanpei@FreeBSD.org">MIHIRA + Sanpei Yoshiro</a> (PC-Card)</p> + + <p>A new committer: <a href="mailto:cokane@FreeBSD.org">Coleman + Kane</a> (3dfx voodoo for glide/Mesa)</p></li> + + <li><p><b>19-June-2000</b> + A new committer: <a href="mailto:cjh@FreeBSD.org">CHOI + Junho</a> (Ports)</p></li> + + <li><p><b>08-June-2000</b> + Jordan Hubbard and Warner Losh will be in Japan during the first + part of June 2000. They will be giving talks at: the BSD BOF at + Networld+Interop 2000 Tokyo (8th), the JUS seminor at Tokyo (9th), + the NBUG event at Nagoya (10th), and, the K*BUG seminor at Osaka + (10th). Please see <a + href="http://www.jp.FreeBSD.org/">http://www.jp.FreeBSD.org/</a>.</p> + + <p>A new article is available, explaining how to <a + href="&base;/tutorials/dialup-firewall/index.html">use PPP, natd, + and ipfw</a> to implement a firewall with a PPP dialup + connection.</p> + + <p>A new committer: <a href="mailto:alex@FreeBSD.org">Alexander + Langer</a> (Ports, Docs)</p></li> + + <li><p><b>06-Jun-2000</b> + The first <a href="&base;/conspectus/index.html">FreeBSD + Conspectus</a> has been added, providing a summary of events on + the <tt>-stable</tt> mailing list over the past week.</p></li> + </ul> + + <h2>May 2000</h2> + + <ul> + <li><p><b>19-May-2000</b> + A new committer: <a href="mailto:cp@FreeBSD.org">Chuck + Paterson</a> (SMP)</p></li> + + <li><p><b>18-May-2000</b> + A hardcopy version of the <a href="&base;/doc/en_US.ISO8859-1/books/handbook/index.html">FreeBSD + Handbook</a> is now available. If you would like to order a + copy, please visit the <a + href="http://www.freebsdmall.com/">FreeBSDMall</a>, or <a + href="http://www.osd.bsdi.com/">BSDi's web site</a>.</p></li> + + <li><p><b>15-May-2000</b> + A new committer: <a href="mailto:jake@FreeBSD.org">Jake + Burkholder</a> (legacy drivers)</p></li> + + <li><p><b>14-May-2000</b> + Issue #04 of <a href="http://www.freebsdzine.org/">The FreeBSD + 'zine</a> is now available.</p></li> + + <li><p><b>09-May-2000</b> + <a href="http://freshports.org/">Freshports</a>: Similar in + nature to <a href="http://freshmeat.net/">Freshmeat</a>, this site + deals exclusively with FreeBSD ports, and allows you to create + your own ``watch lists'' for your favorite ports.</p></li> + </ul> + + <h2>April 2000</h2> + + <ul> + <li><p><b>16-Apr-2000</b> + New mailing lists available: <strong>freebsd-i18n</strong> + (FreeBSD Internationalization) and <strong>freebsd-ppc</strong> + (Porting FreeBSD to the PowerPC)</p></li> + + <li><p><b>04-Apr-2000</b> + A new committer: <a href="mailto:murray@FreeBSD.org">Murray + Stokely</a> (sysinstall)</p></li> + </ul> + + <h2>March 2000</h2> + + <ul> + <li><p><b>22-Mar-2000</b> + A new committer: <a href="mailto:knu@FreeBSD.org">Akinori + MUSHA</a> (Ports)</p></li> + + <li><p><b>21-Mar-2000</b> + <a href="mailto:unfurl@FreeBSD.org">Bill Swingle</a> has written + an <a href="http://www.32bitsonline.com/article.php3?file=issues/200003/bsdports&page=1"> + article on the Ports and Packages System</a> for <a + href="http://www.32bitsonline.com/">32bitsonline.com</a></p></li> + + <li><p><b>20-Mar-2000</b> + A new committer: <a href="mailto:will@FreeBSD.org">Will + Andrews</a> (Ports)</p></li> + + <li><p><b>15-Mar-2000</b> + Issue #2 of <a href="http://www.freebsdzine.org/">The FreeBSD + 'zine</a> is now available.</p></li> + + <li><p><b>13-Mar-2000</b> + <a href="&base;/releases/4.0R/announce.html">FreeBSD 4.0</a> has + been released. Please see the <a + href="&base;/releases/index.html">Release Information</a> page for + more details. Also be sure to check the <a + href="&base;/releases/4.0R/errata.html">release errata</a> after + installation for any late-breaking issues with 4.0 that + occur.</p></li> + + <li><p><b>09-Mar-2000</b> + <a href="http://www.wccdrom.com/">Walnut Creek CDROM</a> and <a + href="http://www.BSDI.com/">BSDI</a> merge! Read the official + <a href="&base;/news/press-rel-4.html">press release</a> for more + information.</p></li> + </ul> + + <h2>February 2000</h2> + + <ul> + <li><p><b>26-Feb-2000</b> + A new committer: <a href="mailto:ume@FreeBSD.org">Hajimu + UMEMOTO</a> (IPv6)</p></li> + + <li><p><b>23-Feb-2000</b> + A new committer: <a href="mailto:ps@FreeBSD.org">Paul + Saab</a></p></li> + + <li><p><b>22-Feb-2000</b> + <a href="http://www.32bitsonline.com/">32BitsOnline.com</a> has a + <a href="http://www.32bitsonline.com/article.php3?file=issues/200002/fbsd34&page=1">review</a> + of FreeBSD 3.4 by <a href="mailto:csmith@medullas.com">Clifford + Smith</a> available on their web site. All in all, a good + review.</p></li> + + <li><p><b>18-Feb-2000</b> + A new committer: <a href="mailto:bsd@FreeBSD.org">Brian S Dean</a> + (Kernel support for IA32 hardware debug registers, misc + fixes/feature enhancements in other areas)</p></li> + + <li><p><b>17-Feb-2000</b> + A new issue of <a href="http://www.freebsdzine.org/">The FreeBSD + 'zine</a> came out on the 15th. This is the first issue of the + 'zine in 7 months; lots of changes have been made, and many new + features have been added. Be sure to check it out.</p></li> + + <li><p><b>10-Feb-2000</b> + <a href="mailto:mwlucas@blackhelicopters.org">Michael Lucas</a> + has written an excellent <a + href="http://www.linux.com/featured_articles/20000210/282/"> + article</a> on the differences between the BSD license and the + GPL. This article is definitely worth reading.</p> + + <p>New committers: <a href="mailto:gsutter@FreeBSD.org">Greg + Sutter</a> and <a href="mailto:unfurl@FreeBSD.org">Bill + Swingle</a> (Docs)</p></li> + </ul> + + <h2>January 2000</h2> + + <ul> + <li><p><b>22-Jan-2000</b> + The <a href="http://www.freebsddiary.org/">FreeBSD Diary</a>, a + chronicle of what one guy is doing with FreeBSD, has been around + for almost two years. Until today, it was tucked away in a corner + of his site. Following significant growth, a new-look site was + launched today. The site contains a huge number of how-to guides + and the readership includes NetBSD, OpenBSD, and Linux + users.</p></li> + + <li><p><b>13-Jan-2000</b> + A new committer: <a href="mailto:wilko@FreeBSD.org">Wilko + Bulte</a></p></li> + + <li><p><b>04-Jan-2000</b> + The <a href="http://www.testdrive.compaq.com/">Compaq Testdrive + program</a> is now making testdrives available of the latest + FreeBSD 4.0-20000101-CURRENT release running on an Alpha XP1000 + EV6.7. running at 667MHz and loaded with two gigs of ram. To get + a free shell account as a participant in the testdrive program, + all you need to do is register at the site. These accounts aren't + for playing, the goal of the program is to make brand new systems + available to developers so they can test, build and port their + apps to the world's fastest computer. The testdrive program also + offers other systems running FreeBSD, including a Proliant 5500 + dual Xeon 450MHz and a DPW500a.</p></li> + + <li><p><b>03-Jan-2000</b> + A new committer: <a href="mailto:patrick@FreeBSD.org">Patrick + Gardella</a> (JDK/WWW)</p></li> + + <li><p><b>02-Jan-2000</b> + A new committer: <a href="mailto:ade@FreeBSD.org">Ade Lovett</a> + (Ports)</p></li> + + <li><p><b>01-Jan-2000</b> + A new committer: <a href="mailto:reg@FreeBSD.org">Jeremy Lea</a> + (Ports)</p></li> + </ul> + + <a href="../news.html">News Home</a> + &footer; + </body> +</html> diff --git a/en_US.ISO8859-1/htdocs/news/2000/press.xml b/en_US.ISO8859-1/htdocs/news/2000/press.xml new file mode 100644 index 0000000000..04eaf59594 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2000/press.xml @@ -0,0 +1,610 @@ +<press> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD: www/en/news/2000/press.xml,v 1.1 2004/04/07 11:35:09 phantom Exp $ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2000</name> + + <month> + <name>12</name> + + <story> + <name>BSD Ports Collection Basics</name> + <url>http://www.onlamp.com/pub/a/bsd/2000/12/21/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>21 December 2000</date> + <author>Michael Lucas</author> + <p>How the FreeBSD Ports collection works.</p> + </story> + + + <story> + <name>BSD Tricks: Unprepared Disaster Recovery</name> + <url>http://www.onlamp.com/pub/a/bsd/2000/12/07/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>07 December 2000</date> + <author>Michael Lucas</author> + <p>How to recover files off of FreeBSD system.</p> + </story> + + </month> + + <month> + <name>11</name> + + <story> + <name>Open-sourcing the Apple</name> + + <url>http://www.salon.com/tech/review/2000/11/17/hubbard_osx/index.html</url> + <site-name>Salon Magazine</site-name> + <site-url>http://www.salon.com/</site-url> + <date>17 November 2000</date> + <author>Jordan Hubbard</author> + + <p>A geek's appraisal of the Apple OS X from Jordan Hubbard, one + of the lead developers on the FreeBSD project.</p> + </story> + + <story> + <name>BSD Tricks: Linux Compatibility, the Hard Way</name> + <url>http://www.onlamp.com/pub/a/bsd/2000/11/16/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>16 November 2000</date> + <author>Michael Lucas</author> + <p>Using a Linux install under FreeBSD's Linux compatibility mode.</p> + </story> + + + <story> + <name>Laptops, PC Cards and FreeBSD</name> + <url>http://www.onlamp.com/pub/a/bsd/2000/11/02/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>02 November 2000</date> + <author>Michael Lucas</author> + <p>Using FreeBSD on a laptop.</p> + </story> + + </month> + + <month> + <name>10</name> + + <story> + <name>BSD Tricks: Introductory Revision Control</name> + <url>http://www.onlamp.com/pub/a/bsd/2000/10/19/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>19 October 2000</date> + <author>Michael Lucas</author> + <p>Using RCS for file revision control.</p> + </story> + + <story> + <name>BSD OSs Offer Unix Alternatives to Linux</name> + <url>http://www.byte.com/documents/BYT20000927S0001/</url> + <site-name>BYTE</site-name> + <site-url>http://www.byte.com/</site-url> + <date>02 October 2000</date> + <author>Bill Nicholls</author> + + <p>This column gives an overview of the different versions of BSD, + with links for more information.</p> + </story> + </month> + + <month> + <name>9</name> + + <story> + <name>INTERNET'S BUSIEST OPENSOURCE SOFTWARE ARCHIVE SETS NEW DOWNLOAD + RECORD</name> + + <url>http://www.terasolutions.com/pr092900.html</url> + <site-name>TeraSolutions</site-name> + <site-url>http://www.terasolutions.com/</site-url> + <date>29 September 2000</date> + <author>TeraSolutions Press Release</author> + + <p>TeraSolutions, Inc. and Lightning Internet Services announce that + the OpenSource archive at <a href="ftp://ftp.freesoftware.com/"> + ftp.freesoftware.com</a> has surpassed the download milestone of + two trillion bytes per day from a single server machine.</p> + </story> + + <story> + <name>BSD Tricks: MFS</name> + + <url>http://www.onlamp.com/pub/a/bsd/2000/09/07/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>07 September 2000</date> + <author>Michael Lucas</author> + + <p>A short article on using the FreeBSD Memory Filesystem.</p> + </story> + + <story> + <name>TRUSTING BSD - Ultra-High Security for FreeBSD</name> + + <url>http://www.ispworld.com/bw/sep/Unix_Flavor.htm</url> + <site-name>ISPworld</site-name> + <site-url>http://www.ispworld.com/</site-url> + <date>September 2000</date> + <author>Jeffrey Carl</author> + + <p>An interview with Robert Watson, one of the lead developers in the + <a href="http://www.trustedbsd.org/">TrustedBSD</a> project.</p> + </story> + </month> + + <month> + <name>8</name> + + <story> + <name>More FreeBSD Comics</name> + + <url>http://ars.userfriendly.org/cartoons/?id=20000807&mode=classic</url> + <site-name>User Friendly the Comic Strip</site-name> + <site-url>http://www.userfriendly.org/</site-url> + <date>07 August 2000</date> + <author>Illiad</author> + + <p>See also the comics for the + <a href="http://ars.userfriendly.org/cartoons/?id=20000808&mode=classic">8th</a>, + <a href="http://ars.userfriendly.org/cartoons/?id=20000809&mode=classic">9th</a>, + <a href="http://ars.userfriendly.org/cartoons/?id=20000810&mode=classic">10th</a>, + <a href="http://ars.userfriendly.org/cartoons/?id=20000811&mode=classic">11th</a>, + and <a href="http://ars.userfriendly.org/cartoons/?id=20000812&mode=classic">12th</a>.</p> + </story> + </month> + + <month> + <name>7</name> + + <story> + <name>Experiments in SMB</name> + <url>http://www.onlamp.com/pub/a/bsd/2000/07/13/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>13 July 2000</date> + <author>Michael Lucas</author> + <p>An early review of FreeBSD's SMB support.</p> + </story> + + </month> + + <month> + <name>6</name> + + <story> + <name>Installing OCSweb on FreeBSD</name> + <url>http://www.onlamp.com/pub/a/bsd/2000/06/15/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>15 June 2000</date> + <author>Michael Lucas</author> + <p>An article on a developers experience porting software from + Linux to FreeBSD.</p> + </story> + + <story> + <name>The State of the Daemon</name> + + <url>http://www.unixreview.com/documents/s=1247/urm0006c/</url> + <site-name>Unix Review</site-name> + <site-url>http://www.unixreview.com/</site-url> + <date>07 June 2000</date> + <author>Michael Lucas</author> + + <p>An informative article on BSD, and where it is going.</p> + </story> + + <story> + <name>Server Goliaths Turn to Appliance Servers</name> + + <url>http://sw.expert.com/news/SE.N1.JUN.00.pdf</url> + <site-name>Server/Workstation Expert</site-name> + <site-url>http://sw.expert.com/</site-url> + <date>June 2000</date> + <author>Adam Darby</author> + + <p>An article evaluating various commercial OSes that contains a + blurb about BSDI and FreeBSD.</p> + </story> + + <story> + <name>FreeBSD: Serving the World</name> + + <url>http://www.osopinion.com/Opinions/JamesHoward/JamesHoward1.html</url> + <site-name>osOpinion</site-name> + <site-url>http://www.osopinion.com/</site-url> + <date>June 2000</date> + <author>James Howard</author> + + <p>With the recent hype surrounding open source software, an + important project has gone unnoticed in the media. This project, + FreeBSD, aims to create a rock-solid UNIX clone based on the 4BSD + work from the University of California at Berkeley.</p> + </story> + </month> + + <month> + <name>5</name> + + <story> + <name>Riding the Web Wave</name> + + <url>http://www.sfgate.com/cgi-bin/article.cgi?file=/chronicle/archive/2000/05/29/BU20648.DTL</url> + <site-name>SFGate</site-name> + <site-url>http://www.sfgate.com/</site-url> + <date>29 May 2000</date> + <author>Henry Norr</author> + + <p>FreeBSD, a relatively unknown operating system is playing a big + role on the Internet.</p> + </story> + + <story> + <name>BSD Unix: Power to the people, from the code</name> + + <url>http://www.salon.com/tech/fsp/2000/05/16/chapter_2_part_one/index.html</url> + <site-name>Salon</site-name> + <site-url>http://www.salon.com/</site-url> + <date>16 May 2000</date> + <author>Andrew Leonard</author> + + <p>How Berkeley hackers built the Net's most fabled free operating + system on the ashes of the '60s---and then lost the lead to + Linux.</p> + </story> + + <story> + <name>Install FreeBSD 4.0 in seven easy steps</name> + + <url>http://www.techrepublic.com/article.jhtml?id=r00220000516eje01.htm</url> + <site-name>TechRepublic</site-name> + <site-url>http://www.techrepublic.com/</site-url> + <date>16 May 2000</date> + <author>Dru Lavigne</author> + + <p>A short guide to installing FreeBSD 4.0.</p> + </story> + + <story> + <name>Partial Reunification May Give BSD New Visibility</name> + + <url>http://www.computerworld.com/home/print.nsf/all/000508DC8A</url> + <site-name>ComputerWorld</site-name> + <site-url>http://www.computerworld.com/</site-url> + <date>08 May 2000</date> + <author>Dominique Deckmyn</author> + + <p>Compares the merged Walnut Creek/BSDI OS offering to Linux.</p> + </story> + + <story> + <name>Developers using open-source software behind bosses' + backs</name> + + <url>http://www.cnn.com/2000/TECH/computing/05/05/open.source.smugglers.idg/index.html</url> + <site-name>CNN</site-name> + <site-url>http://www.cnn.com/</site-url> + <date>05 May 2000</date> + <author>Peter Wayner</author> + + <p>Open-source software sometimes provides a better solution than + expensive commercial, closed software.</p> + </story> + + <story> + <name>FreeBSD 4.0 Now Includes PolyServe's High Availability + Clustering & Load Balancing Software</name> + + <url>http://biz.yahoo.com/bw/000501/ca_polyser_1.html</url> + <site-name>PolyServe</site-name> + <site-url>http://www.polyserve.com/</site-url> + <date>01 May 2000</date> + <author>PolyServe Press Release</author> + + <p>PolyServe, a provider of software-based, distributed server + clustering technology, announced co-marketing agreement with FreeBSD, + Inc. to ship PolyServe's Understudy (TM) software program with all + new versions of FreeBSD 4.0 operating system software.</p> + </story> + + <story> + <name>BSDI Getting the Word Out</name> + + <url>http://webserver.expert.com/news/5.5/n5.shtml</url> + <site-name>WebServer Online</site-name> + <site-url>http://webserver.expert.com/</site-url> + <date>May 2000</date> + <author>Alexandra Barrett</author> + + <p>Talks of the lack of awareness in the market of the strengths of + the BSD operating system and of the plans afoot to change this.</p> + </story> + </month> + + <month> + <name>4</name> + + <story> + <name>The New BSDI to Offer Technical Support for the FreeBSD + Operating System</name> + + <url>http://www.bsdi.com/press/20000418.mhtml</url> + <site-name>BSDi</site-name> + <site-url>http://www.bsdi.com/</site-url> + <date>18 April 2000</date> + <author>BSDi Press Release</author> + + <p>BSDi will be offering technical support contracts for FreeBSD + beginning in May 2000.</p> + </story> + + <story> + <name>Commentary: BSD sleight of hand</name> + + <url>http://www.zdnet.com/zdnn/stories/news/0,4586,2507538,00.html</url> + <site-name>ZD Net News</site-name> + <site-url>http://www.zdnet.com/</site-url> + <date>04 April 2000</date> + <author>Stephan Somogyi</author> + + <p>Commentary on the BSDI/FreeBSD merger.</p> + </story> + + <story> + <name>FreeBSD 3.4 Review, Part 2: Adopting the Daemon</name> + + <url>http://www.32bitsonline.com/article.php3?file=issues/200004/freebsd2e&page=1</url> + <site-name>32BitsOnline.com</site-name> + <site-url>http://www.32bitsonline.com/</site-url> + <date>April 2000</date> + <author>Clifford Smith</author> + + <p>The second part of a review of FreeBSD v3.4.</p> + </story> + </month> + + <month> + <name>3</name> + + <story> + <name>The legend of BSD</name> + + <url>http://www.sfbg.com/SFLife/34/26/tech.html</url> + <site-name>sf life</site-name> + <site-url>http://www.sfbg.com/</site-url> + <date>29 March 2000</date> + <author>Annalee Newitz</author> + + <p>An interview with three BSD veterans on the past and future of + BSD.</p> + </story> + + <story> + <name>Bostic on the BSD tradition</name> + + <url>http://www.oreillynet.com/pub/a/bsd/2000/03/24/bostic.html</url> + <site-name>O'Reilly Network</site-name> + <site-url>http://www.oreillynet.com/</site-url> + <date>24 March 2000</date> + <author>Dale Dougherty</author> + + <p>An interview with BSD veteran Keith Bostic on the BSDI/FreeBSD + merger. ``BSD has always had the best technology'', says Keith.</p> + </story> + + <story> + <name>Customizing the FreeBSD Kernel</name> + + <url>http://www.linuxworld.com/linuxworld/lw-2000-03/lw-03-freebsd_p.html</url> + <site-name>LinuxWorld</site-name> + <site-url>http://www.linuxworld.com/</site-url> + <date>March 2000</date> + <author>Michael Lucas</author> + + <p>Michael Lucas presents a guide to customizing the FreeBSD kernel, + written for the Linux oriented.</p> + </story> + + <story> + <name>FreeBSD for the SVR4/Linux Administrator</name> + + <url>http://www.samag.com/archive/0903/feature.shtml</url> + <site-name>SysAdmin</site-name> + <site-url>http://www.samag.com/</site-url> + <date>March 2000</date> + <author>Michael Lucas</author> + + <p>This article attempts to give a System V or Linux administrator + a basic grounding in FreeBSD configuration and usage.</p> + </story> + + <story> + <name>FreeBSD Ports and Packages System Explained</name> + + <url>http://www.32bitsonline.com/article.php3?file=issues/200003/bsdports&page=1</url> + <site-name>32BitsOnline</site-name> + <site-url>http://www.32bitsonline.com/</site-url> + <date>March 2000</date> + <author>Bill Swingle</author> + + <p>A good description of the FreeBSD Ports collection.</p> + </story> + </month> + + <month> + <name>2</name> + + <story> + <name>Business Lessons From Online Porn</name> + + <url>http://www.upside.com/texis/mvm/print-it?id=38adbbff0&t=/texis/mvm/news/news</url> + <site-name>Upside</site-name> + <site-url>http://www.upside.com/</site-url> + <date>21 February 2000</date> + <author>Richard A. Glidewell</author> + + <p>Praise for FreeBSD from this article: ``FreeBSD is the system of + choice because it is fast, stable, and can handle large volumes of + traffic.''</p> + </story> + + <story> + <name>Crazed Ferrets in a Berkeley Shower</name> + + <url>http://www.linux.com/articles.phtml?aid=7125</url> + <site-name>Linux.com</site-name> + <site-url>http://www.linux.com/</site-url> + <date>10 February 2000</date> + <author>Michael Lucas</author> + + <p>An article on the BSD License.</p> + </story> + + <story> + <name>Three Unixlike systems may be better than Linux</name> + + <url>http://www.computerworld.com/cwi/story/0,1199,NAV47_STO41147,00.html</url> + <site-name>ComputerWorld</site-name> + <site-url>http://www.computerworld.com/</site-url> + <date>07 February 2000</date> + <author>Simson L. Garfinkel</author> + + <p>Promotes the BSD OSes as better alternatives to Linux + in the areas of performance, reliability and security.</p> + </story> + + <story> + <name>Buddying up to BSD: Part Five - FreeBSD Continued</name> + + <url>http://www.linux.com/featured_articles/20000208/275/</url> + <site-name>Linux.com</site-name> + <site-url>http://www.linux.com/</site-url> + <date>08 February 2000</date> + <author>Matt Michie</author> + + <p>A Linux user writes about his experiences with the FreeBSD ports + system.</p> + </story> + + <story> + <name>Review of FreeBSD 3.4</name> + + <url>http://www.32bitsonline.com/article.php3?file=issues/200002/fbsd34&page=1</url> + <site-name>32BitsOnline.com</site-name> + <site-url>http://www.32bitsonline.com/</site-url> + <date>February 2000</date> + <author>Clifford Smith</author> + + <p>A review of FreeBSD 3.4.</p> + </story> + + <story> + <name>FreeBSD 4.0 And Beyond</name> + + <url>http://www.boardwatch.com/mag/2000/feb/bwm79.html</url> + <site-name>Boardwatch</site-name> + <site-url>http://www.boardwatch.com/</site-url> + <date>February 2000</date> + <author>Jeffrey Carl</author> + + <p>A Jordan Hubbard Interview on Improvements, New Platforms and + What's to Come.</p> + </story> + </month> + + <month> + <name>1</name> + + <story> + <name>Buddying up to BSD: Part Four - FreeBSD</name> + + <url>http://www.linux.com/featured_articles/20000126/270/</url> + <site-name>Linux.com</site-name> + <site-url>http://www.linux.com/</site-url> + <date>26 January 2000</date> + <author>Matt Michie</author> + + <p>A Linux user writes about his experiences with FreeBSD.</p> + </story> + + <story> + <name>Debunking Open-Source Myths: Origins and Players</name> + + <url>http://www.gartnerweb.com/public/static/hotc/hc00085832.html</url> + <site-name>Gartner Group</site-name> + <site-url>http://www.gartnerweb.com/</site-url> + <date>18 January 2000</date> + <author>N. Drakos and M. Driver</author> + + <p>A report that looks at and debunks some of the myths associated with + Open Source development.</p> + </story> + + <story> + <name>Linux Scales Enterprise Wall</name> + + <url>http://www.techweb.com/wire/story/TWB20000114S0013</url> + <site-name>TechWeb</site-name> + <site-url>http://www.techweb.com/</site-url> + <date>14 January 2000</date> + <author>Mitch Wagner</author> + + <p>About 17 percent of enterprises plan to deploy FreeBSD or Linux + as a primary platform for e-commerce within two years.</p> + </story> + + <story> + <name>Jobs announces new MacOS, becomes 'iCEO'</name> + + <url>http://cnn.com/2000/TECH/computing/01/05/macworld.keynote/index.html</url> + <site-name>CNN</site-name> + <site-url>http://cnn.com/</site-url> + <date>05 January 2000</date> + <author>CNN news article</author> + + <p>Steve Jobs' Macworld Expo keynote speech mentions FreeBSD as one of + the components in the new Darwin OS from Apple.</p> + </story> + + <story> + <name>Mac OS X</name> + + <url>http://www.apple.com/macosx/inside.html</url> + <site-name>Apple Inc.</site-name> + <site-url>http://www.apple.com/</site-url> + <date>January 2000</date> + <author>Apple communication</author> + + <p>In an article on the next generation Darwin OS, Apple Inc., refers + to FreeBSD as one of the ``most acclaimed OS projects of the modern + era.''</p> + </story> + + <story> + <name>Linux under FreeBSD</name> + + <url>http://www.samag.com/documents/s=1169/sam0001b/</url> + <site-name>SysAdmin</site-name> + <site-url>http://www.samag.com/</site-url> + <date>January 2000</date> + <author>Michael Lucas</author> + + <p>FreeBSD has several options for using software from other platforms + such as Linux. This article examines Linux emulation under + FreeBSD.</p> + </story> + </month> + </year> +</press> diff --git a/en_US.ISO8859-1/htdocs/news/2001/Makefile b/en_US.ISO8859-1/htdocs/news/2001/Makefile new file mode 100644 index 0000000000..bd9a14671b --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2001/Makefile @@ -0,0 +1,16 @@ +# $FreeBSD: www/en/news/2001/Makefile,v 1.6 2005/09/20 21:18:25 hrs Exp $ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +XMLDOCS+= index:${XSL_NEWS_NEWSFLASH_OLD}:news.xml: +DEPENDSET.index=transtable news + +XMLDOCS+= press:${XSL_NEWS_PRESS_OLD}:: +DEPENDSET.press=transtable press + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/news/2001/news.xml b/en_US.ISO8859-1/htdocs/news/2001/news.xml new file mode 100644 index 0000000000..1d88685ab7 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2001/news.xml @@ -0,0 +1,966 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE news PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for News//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/news.dtd"> + +<!-- Simple schema for FreeBSD Project news. + + Divide time in to <year>, <month>, and <day> elements, each of which + has a <name>. + + each <day> element contains one or more <event> elements. + + Each <event> contains an optional <title>, and then a <p>. <p> elements + can contain <a> anchors. + + Use the <title> element if the <p> content is lengthy. When generating + synopses of this information (e.g., for syndication using RDF files), + the contents of <title> will be preferred over <p>. +--> + +<news> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD: www/en/news/2001/news.xml,v 1.65 2006/08/19 21:20:39 hrs Exp $ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2001</name> + + <month> + <name>12</name> + + <day> + <name>31</name> + + <event> + <title><a href="http://www.usenix.org/events/bsdcon02/">BSDCon + 2002</a> - February 11-14, San Francisco</title> + + <p><a + href="http://www.usenix.org/events/bsdcon02/">BSDCon</a> + will be hosted by the <a href="http://www.usenix.org">Usenix + Association</a> this year. The conference will run from + February 11-14 in San Francisco. The FreeBSD Project will + have a broad presence at this conference, and anyone + interested in learning more about specific technologies + or the FreeBSD Project in general is encouraged to attend.</p> + </event> + </day> + + <day> + <name>28</name> + + <event> + <p>New committer: <a + href="mailto:ambrisko@FreeBSD.org">Doug Ambrisko</a> + (Aironet)</p> + </event> + + </day> + + <day> + <name>27</name> + + <event> + <p>New committer: <a + href="mailto:skv@FreeBSD.org">Sergey Skvortsov</a> + (Ports)</p> + </event> + + </day> + + <day> + <name>21</name> + + <event> + <title>FreeBSD-stable tree frozen in preparation for 4.5</title> + + <p>The FreeBSD-stable branch of the source tree has now been + frozen in preparation for the release of FreeBSD 4.5. This means + that any new commits to the -stable source tree must be approved + by the release engineering team first. Our expected "ship" date + for 4.5 is January 20th, 2002.</p> + </event> + + <event> + <title>November 2001 Status Report</title> + + <p>The November 2001 status report is now available; see the + <a href="&base;/news/status/status.html">status reports Web page</a> for + more information.</p> + </event> + + <event> + <title>"Backports" site, with patches for older FreeBSD + releases</title> + + <p><a href="http://www.visi.com/~hawkeyd/freebsd-backports.html">The + FreeBSD Backports Collection</a> is a new site created by + D J Hawkey Jr. It contains patches that appeared in + FreeBSD-stable that have not yet been merged in to older + releases. Wider testing of these patches makes it more likely + that they will be committed to earlier FreeBSD releases. So if + your site relies on earlier releases of FreeBSD, and, for whatever + reason, you do not wish to update to the most recent release, + you are encouraged to visit this site frequently.</p> + </event> + </day> + + <day> + <name>20</name> + + <event> + <p>New committer: <a + href="mailto:mbr@FreeBSD.org">Martin Blapp</a> + (Ports)</p> + </event> + </day> + + <day> + <name>7</name> + + <event> + <title>New BSD-related journal : <a + href="http://bsdfreak.org">BSDFreak</a></title> + + <p><a href="http://bsdfreak.org">BSDFreak</a> is a new site + that provides tutorials, articles, and journals covering + BSD operating systems from a user's perspective.</p> + + </event> + </day> + </month> + + <month> + <name>11</name> + + <day> + <name>30</name> + + <event> + <p>New committer: <a + href="mailto:mwlucas@FreeBSD.org">Michael Lucas</a> + (Documentation Project)</p> + </event> + </day> + + <day> + <name>28</name> + + <event> + <p>New committer: <a href="mailto:pdeuskar@FreeBSD.org">Prafulla + Deuskar</a> (Intel gigabit device driver)</p> + </event> + </day> + + <day> + <name>25</name> + + <event> + <p>New committer: <a href="mailto:yoichi@FreeBSD.org">Yoichi + NAKAYAMA</a> (Ports)</p> + </event> + </day> + + <day> + <name>23</name> + + <event> + <title>Writing FreeBSD Problem Reports</title> + + <p><a href="mailto:des@FreeBSD.org">Dag-Erling Smørgrav</a> + has written an article about <a + href="&base;/doc/en_US.ISO8859-1/articles/problem-reports/article.html"> + writing FreeBSD problem reports</a>.</p> + </event> + </day> + + <day> + <name>20</name> + + <event> + <p>New committer: <a href="mailto:znerd@FreeBSD.org">Ernst + de Haan</a> (Ports)</p> + </event> + + <event> + <title>Core Appoints Bugmeister</title> + + <p>The FreeBSD Core Team has appointed <a + href="mailto:des@FreeBSD.org">Dag-Erling Smørgrav</a> as + Bugmeister.</p> + </event> + </day> + + <day> + <name>14</name> + + <event> + <p>New committer: <a href="mailto:pat@FreeBSD.org">Patrick + Li</a> (Ports)</p> + </event> + </day> + + <day> + <name>13</name> + + <event> + <p>New committer: <a href="mailto:cy@FreeBSD.org">Cy + Schubert</a> (Ports)</p> + </event> + </day> + + <day> + <name>6</name> + + <event> + <p>New committer: <a href="mailto:anders@FreeBSD.org">Anders + Nordby</a> (Ports)</p> + </event> + </day> + + <day> + <name>3</name> + + <event> + <p>New committer: <a href="mailto:naddy@FreeBSD.org">Christian + Weisgerber</a> (Ports)</p> + </event> + + <event> + <title>ATA 48-bit addressing code tested and found to be + working and stable</title> + + <p>Soren Schmidt, author of the ATA driver, tested a + new 160 GB ATA harddisk provided kindly by + <a href="http://www.maxtor.com">Maxtor Corporation</a> + with the new ATA specification's 48-bit addressing mode + support in FreeBSD 5.0-CURRENT. The results show that the + code is stable and functions as it should and will be + backported to STABLE.</p> + </event> + </day> + + <day> + <name>2</name> + + <event> + <p>New committer: <a href="mailto:nobutaka@FreeBSD.org">MANTANI + Nobutaka</a> (Ports)</p> + </event> + + <event> + <p>New committer: <a href="mailto:arr@FreeBSD.org">Andrew R. + Reiter</a> (SMPng, TrustedBSD)</p> + </event> + </day> + </month> + + <month> + <name>10</name> + + <day> + <name>30</name> + + <event> + <title>FreeBSD Handbook, 2nd Edition now available!</title> + + <p>"The FreeBSD Handbook, 2nd Edition" is now available in + printed form! This is the primary source of documentation + produced by the <a + href="http://www.FreeBSD.org/docproj/">FreeBSD + Documentation Project</a> and is available now from, + amongst other places, <a + href="http://www.freebsdmall.com">The FreeBSD Mall</a>. + For a complete list of changes in this edition, see the <a + href="http://docs.FreeBSD.org/cgi/getmsg.cgi?fetch=0+0+archive/2001/freebsd-announce/20011028.freebsd-announce">announce</a> + message from the editors. The ISBN for this book is + 1571763031. 653 pages.</p> + + </event> + </day> + + <day> + <name>26</name> + + <event> + <p>New committer: <a href="mailto:matusita@FreeBSD.org">Makoto + Matsushita</a> (release building)</p> + </event> + </day> + + <day> + <name>23</name> + + <event> + <title>Bootstrapping Vinum: A Foundation for Reliable Servers</title> + <p><a href="mailto:Bob@BGPBook.Com">Bob Van Valzah</a> has submitted + an article introducing <a + href="&base;/doc/en_US.ISO8859-1/articles/vinum/index.html"> + failure-resilient servers and step-by-step instructions + for building one with Vinum</a>.</p> + </event> + + <event> + <title>FreeBSD/ia64 port boots unattended to multi-user mode</title> + <p><a href="mailto:dfr@FreeBSD.org">Doug Rabson</a> and + <a href="mailto:peter@FreeBSD.org">Peter Wemm</a> have been + working non-stop on the FreeBSD/ia64 port in the past few + weeks and said today that it boots into multi-user mode + without any operator attendance. This is indeed a major + milestone in continued FreeBSD porting efforts. Right now + most work is concentrating on fixing any problems in the + sourcetree which become exposed by this platform's porting + effort.</p> + </event> + </day> + + <day> + <name>19</name> + + <event> + <title>FreeBSD/sparc64 port boots to single user mode</title> + <p><a href="mailto:jake@FreeBSD.org">Jake Burkholder</a> and + <a href="mailto:tmm@FreeBSD.org">Thomas Moestl</a> have been + porting FreeBSD to the ultra sparc for the past few months + and first booted a machine into single user mode on the 18th + of October. The log from the serial console can be found at + <a href="http://people.FreeBSD.org/~jake/tip.single_user"> + http://people.FreeBSD.org/~jake/tip.single_user</a>.</p> + </event> + </day> + + <day> + <name>17</name> + + <event> + <p>New committer: <a href="mailto:amorita@FreeBSD.org">Akio + Morita</a> (PC98)</p> + </event> + </day> + + <day> + <name>7</name> + + <event> + <title>FreeBSD/ppc port now boots and executes kernel</title> + <p><a href="mailto:benno@FreeBSD.org">Benno Rice</a> has committed + a mega-patch which added support for OpenFirmware to the FreeBSD + loader. The loader can now load a kernel over the network and + execute it on an Apple iMac.</p> + </event> + </day> + + <day> + <name>5</name> + + <event> + <title>FreeBSD/ia64 port now boots on real hardware</title> + <p>After a few months of development <a href="mailto:dfr@FreeBSD.org"> + Doug Rabson</a> and <a href="mailto:peter@FreeBSD.org">Peter + Wemm</a> have committed patches which extends the FreeBSD/ia64 + port's functionality and adds the possibility to boot on real + hardware.</p> + </event> + + <event> + <p>New committer: + <a href="mailto:keramida@FreeBSD.org">Giorgos Keramidas</a> + (Docs)</p> + </event> + </day> + </month> + + <month> + <name>9</name> + + <day> + <name>18</name> + + <event> + <title>August 2001 Status Report</title> + + <p>The August 2001 Status Report is now available; see the + <a href="&base;/news/status/status.html">Status Reports Web Page</a>.</p> + </event> + </day> + + <day> + <name>10</name> + + <event> + <title>Comprehensive Project List available for 5.0</title> + + <p>Many people, upon hearing of 5.0's untimely delay for a + full year, have asked what they can do to help 5.0 get + back on track. <a + href="http://docs.FreeBSD.org/cgi/getmsg.cgi?fetch=4914+0+archive/2001/freebsd-announce/20010916.freebsd-announce"> + This email</a> gives a list of outstanding projects for 5.0 and + as much information as possible about how to get + involved.</p> + </event> + </day> + </month> + + <month> + <name>8</name> + <day> + <name>30</name> + + <event> + <title>FreeBSD 5.0 delayed until November 2002</title> + + <p>FreeBSD 5.0 has been delayed until November 2002. The + complete announcement from Jordan is available <a + href="http://docs.FreeBSD.org/cgi/getmsg.cgi?fetch=34983+0+archive/2001/freebsd-announce/20010902.freebsd-announce">here</a>.</p> + </event> + </day> + + <day> + <name>28</name> + + <event> + <p>New committer: <a href="mailto:robert@FreeBSD.org">Robert + Drehmel</a></p> + </event> + </day> + + <day> + <name>22</name> + + <event> + <p>New committer: <a href="mailto:petef@FreeBSD.org">Pete + Fritchman</a> (Ports)</p> + </event> + </day> + + <day> + <name>17</name> + + <event> + <title>New-user focused FreeBSD book available</title> + + <p>Annelise Anderson, a frequent contributor to the FreeBSD mailing + lists, has written "FreeBSD: An Open-Source Operating System + for Your PC", an introduction to FreeBSD aimed at the new user. + Published by The Bit Tree Press, the ISBN is 0971204500, and it + can be ordered from, amongst other places, the + <a href="http://mall.daemonnews.org">DaemonNews Mall</a>.</p> + </event> + </day> + + <day> + <name>16</name> + + <event> + <title>Installation documentation substantially improved</title> + + <p>The + <a href="&base;/doc/en_US.ISO8859-1/books/handbook/install.html">Installing FreeBSD</a> + section of the + <a href="&base;/doc/en_US.ISO8859-1/books/handbook/index.html">Handbook</a> + has been substantially improved and updated. The new + documentation features "screenshots" of almost every stage of the + installation process, and expanded text detailing what each stage + of the install covers. The bulk of the work was carried out by + Randy Pratt.</p> + </event> + </day> + + <day> + <name>14</name> + + <event> + <p>New committer: <a href="mailto:fjoe@FreeBSD.org">Max Khon</a></p> + </event> + </day> + + <day> + <name>9</name> + + <event> + <p>New committer: <a href="mailto:rpratt@FreeBSD.org">Randy + Pratt</a> (Docs)</p> + </event> + + <event> + <title>July 2001 Status Report</title> + + <p>The July 2001 status report is now available; see the + <a href="&base;/news/status/status.html">Status Reports Web + page</a>.</p> + </event> + </day> + + <day> + <name>8</name> + + <event> + <title>FreeBSD RDF news headline file now available</title> + + <p>An RDF file of the last 10 news headlines on the FreeBSD site + is now available. The URL is <a href="http://www.FreeBSD.org/news/news.rdf">http://www.FreeBSD.org/news/news.rdf</a>. You can use this file + to <i>syndicate</i> FreeBSD news headlines on to your own web + site (as <a href="http://daily.daemonnews.org/">Daily + DaemonNews</a> and the + <a href="http://www.freebsddiary.org/newsfeeds.php">FreeBSD + Diary</a> do), or on to your desktop, using applications such as + <a href="http://apps.kde.com/na/2/info/id/999">KNewsTicker</a>.</p> + </event> + </day> + + <day> + <name>7</name> + + <event> + <title>Pandaemonium User Group</title> + + <p><a href="http://pandaemonium.newmillennium.net.au/">Pandaemonium</a>, + the BSD Users Group of Western Australia, has been + added to the <a href="&base;/support.html">Support</a> page.</p> + </event> + </day> + + <day> + <name>6</name> + + <event> + <p>New committer: <a href="mailto:logo@FreeBSD.org">Valentino + Vaschetto</a> (Docs)</p> + </event> + </day> + </month> + + <month> + <name>7</name> + + <day> + <name>30</name> + + <event> + <title>FreeBSD Handbook task list now available</title> + + <p>A second edition of <a href="&base;/handbook">The FreeBSD + Handbook</a> will be in production shortly. A + <a href="&base;/docproj/handbook.html">task list</a> has been + published for anyone who wants to help contribute to the state of + available printed documentation about FreeBSD.</p> + </event> + </day> + + <day> + <name>26</name> + + <event> + <p>New committer: <a href="mailto:mp@FreeBSD.org">Mark Peek</a></p> + </event> + </day> + + <day> + <name>16</name> + + <event> + <p>New committer: <a href="mailto:bbraun@FreeBSD.org">Rob + Braun</a></p> + </event> + + <event> + <p>New committer: <a href="mailto:zarzycki@FreeBSD.org">Dave + Zarzycki</a></p> + </event> + + <event> + <p>New committer: <a href="mailto:mike@FreeBSD.org">Mike Barcroft</a></p> + </event> + </day> + + <day> + <name>13</name> + + <event> + <p>New committer: <a href="mailto:chern@FreeBSD.org">Chern Lee</a> + (Docs)</p> + </event> + </day> + </month> + + <month> + <name>6</name> + + <day> + <name>21</name> + + <event> + <p>New committer: <a href="mailto:brooks@FreeBSD.org">Brooks + Davis</a> (Networking, Mobile Computing)</p> + </event> + </day> + + <day> + <name>20</name> + + <event> + <title>Using FreeBSD with Solid State Media</title> + + <p><a href="mailto:john@kozubik.com">John Kozubik</a> has submitted + an article explaining + <a href="&base;/doc/en_US.ISO8859-1/articles/solid-state/index.html">How + to use FreeBSD with solid state media</a>.</p> + </event> + </day> + + <day> + <name>17</name> + + <event> + <title>FreeBSD boots on PowerPC</title> + + <p><a href="mailto:benno@FreeBSD.org">Benno Rice</a> has completed + enough work to allow FreeBSD to reach the mountroot prompt on the + PowerPC processor. Please see the PowerPC platform <a + href="&base;/platforms/ppc.html">page</a> and mailing list for more + information.</p> + </event> + </day> + + <day> + <name>15</name> + + <event> + <p>New committer: <a href="mailto:silby@FreeBSD.org">Mike + Silbersack</a> (Networking)</p> + </event> + </day> + + <day> + <name>14</name> + + <event> + <p>New committer: <a href="mailto:wjv@FreeBSD.org">Johann Visagie</a> + (Ports)</p> + </event> + </day> + + <day> + <name>13</name> + + <event> + <title>FreeBSD Status Report Available</title> + + <p><a href="mailto:rwatson@FreeBSD.org">Robert Watson</a> has + compiled a + <a href="http://docs.FreeBSD.org/cgi/getmsg.cgi?fetch=481962+0+archive/2001/freebsd-hackers/20010617.freebsd-hackers">status report</a> for the FreeBSD Project. These reports are scheduled to continue on a monthly basis.</p> + </event> + </day> + + <day> + <name>11</name> + + <event> + <p>New committer: <a href="mailto:tobez@FreeBSD.org">Anton + Berezin</a> (all things Perl)</p> + </event> + </day> + + <day> + <name>6</name> + + <event> + <p>New committer: <a href="mailto:dwcjr@FreeBSD.org">David + W. Chapman Jr.</a>(Ports)</p> + </event> + + <event> + <p>New committer: <a href="mailto:markp@FreeBSD.org">Mark Pulford</a> + (Ports)</p> + </event> + </day> + + <day> + <name>1</name> + + <event> + <p>New committer: <a href="mailto:cjc@FreeBSD.org">Crist J. Clark</a> + (Networking, security)</p> + </event> + </day> + </month> + + <month> + <name>5</name> + + <day> + <name>24</name> + + <event> + <title>ftp.FreeBSD.org back up</title> + + <p>The famous ftp site, + <a href="ftp://ftp.FreeBSD.org/">ftp.FreeBSD.org</a>, is now back + in full operation. Many thanks to <a + href="http://www.teledanmark.com/english/menu/start.htm">Tele + Danmark</a>, who are supplying the machine as well as the network + connection.</p> + </event> + </day> + + <day> + <name>16</name> + + <event> + <p>New committer: <a href="mailto:pirzyk@FreeBSD.org">Jim + Pirzyk</a></p> + </event> + </day> + + <day> + <name>2</name> + + <event> + <title>New FreeBSD 'zine issue out</title> + + <p>The first May 2001 issue of the + <a href="http://www.freebsdzine.org/">FreeBSD 'zine</a> is now + available. Starting this month, there will be two issues + per month; one on the 1st, and one on the 15th.</p> + </event> + </day> + </month> + + <month> + <name>4</name> + + <day> + <name>27</name> + + <event> + <title>SMP Alpha now works</title> + + <p>FreeBSD now works with multiple processors on Alpha systems, + thanks to the efforts of <a href="mailto:jhb@FreeBSD.org">John + Baldwin</a>, <a href="mailto:gallatin@FreeBSD.org">Andrew + Gallatin</a>, and <a href="mailto:dfr@FreeBSD.org">Doug + Rabson</a>.</p> + </event> + </day> + + <day> + <name>25</name> + + <event> + <p>New committer: <a href="mailto:tshiozak@FreeBSD.org">Takuya + SHIOZAKI</a> (Internationalization)</p> + </event> + + <event> + <p>New committer: <a href="mailto:ue@FreeBSD.org">Udo Erdelhoff</a> + (Docs)</p> + </event> + </day> + + <day> + <name>18</name> + + <event> + <p>The + <a href="&base;/doc/en_US.ISO8859-1/books/developers-handbook/index.html">Developer's + Handbook</a> is now available on the web site. This is an + evolving resource for people wanting to develop software for + FreeBSD (and not just for the committers who are developing + FreeBSD). Don't forget that a <a + href="&base;/docs.html">complete list of documentation</a> + available from this site is also available.</p> + </event> + </day> + + <day> + <name>17</name> + + <event> + <p>Addison Wesley have allowed us to republish + <a href="&base;/doc/en_US.ISO8859-1/books/corp-net-guide/index.html">Chapter + 8</a> of the + <a href="http://cseng.aw.com/book/0,,0201704811,00.html">FreeBSD + Corporate Networker's Guide</a>. Chapter 8 provides an in-depth + look at providing printing services to Windows, NT, and Novell + clients using FreeBSD.</p> + </event> + </day> + + <day> + <name>16</name> + + <event> + <p>Yet another new committer: + <a href="mailto:schweikh@FreeBSD.org">Jens Schweikhardt</a> + (Standards compliance)</p> + </event> + </day> + + <day> + <name>12</name> + + <event> + <p>The April issue of <a href="http://www.freebsdzine.org/">The + FreeBSD 'zine</a> is now available.</p> + </event> + </day> + + <day> + <name>10</name> + + <event> + <p>The <a href="&base;/ports/index.html">Ports Collection</a> now + contains more than 5,000 individual entries!</p> + </event> + </day> + + <day> + <name>5</name> + + <event> + <p>New committer: <a href="mailto:greid@FreeBSD.org">George Reid</a> + (Sound support, ports)</p> + </event> + </day> + + <day> + <name>4</name> + + <event><p>Wind River to Acquire BSDi Software Assets. Please read the + <a href="http://www.windriver.com/press/html/bsdi.html">Wind River + Press Release</a>, the announcement from + <a href="http://www.FreeBSD.org/cgi/mid.cgi?20010404220529.E3AFE37B727">Jordan K. Hubbard</a>, and the <a + href="http://www.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1010405211037.46990E-100000">FreeBSD Core Team statement</a>.</p> + </event> + </day> + </month> + + <month> + <name>3</name> + + <day> + <name>25</name> + + <event> + <p>New committer: <a href="mailto:yar@FreeBSD.org">Yar Tikhiy</a> + (Networking)</p> + </event> + </day> + + <day> + <name>24</name> + + <event> + <p>New committer: <a href="mailto:eric@FreeBSD.org">Eric Melville</a> + (System tools)</p> + </event> + </day> + + <day> + <name>13</name> + + <event> + <p>The March issue of <a href="http://www.freebsdzine.org/">The + FreeBSD 'zine</a> is now available.</p> + </event> + </day> + + <day> + <name>9</name> + + <event> + <p>New committer: <a href="mailto:dd@FreeBSD.org">Dima Dorfman</a> + (Docs)</p> + </event> + </day> + + <day> + <name>7</name> + + <event> + <p>New committer: <a href="mailto:keichii@FreeBSD.org">Michael + C. Wu</a> (Internationalization, porting efforts)</p> + </event> + </day> + + <day> + <name>6</name> + + <event> + <p>New committer: <a href="mailto:tmm@FreeBSD.org">Thomas + M&ouml;stl</a> (POSIX.1e extensions)</p> + </event> + + <event> + <p>New committer: <a href="mailto:orion@FreeBSD.org">Orion Hodson</a> + (Sound support)</p> + </event> + </day> + </month> + + <month> + <name>2</name> + + <day> + <name>20</name> + + <event> + <p>New committer: <a href="mailto:jesper@FreeBSD.org">Jesper + Skriver</a></p> + </event> + </day> + + <day> + <name>16</name> + + <event> + <p>The February issue of <a href="http://www.freebsdzine.org/">The + FreeBSD 'zine</a> is now available.</p> + </event> + </day> + + <day> + <name>5</name> + + <event> + <p>New committer: <a href="mailto:mikeh@FreeBSD.org">Mike Heffner</a> + (Audit project)</p> + </event> + </day> + </month> + + <month> + <name>1</name> + + <day> + <name>24</name> + + <event> + <p>New committer: <a href="mailto:olgeni@FreeBSD.org">Jimmy + Olgeni</a> (Ports)</p> + </event> + </day> + + <day> + <name>23</name> + + <event> + <p>New committer: <a href="mailto:dinoex@FreeBSD.org">Dirk Meyer</a> + (Ports)</p> + </event> + </day> + + <day> + <name>20</name> + + <event> + <p>New committer: <a href="mailto:ijliao@FreeBSD.org">Ying-chieh + Liao</a> (Ports)</p> + </event> + </day> + </month> + </year> +</news> + diff --git a/en_US.ISO8859-1/htdocs/news/2001/press.xml b/en_US.ISO8859-1/htdocs/news/2001/press.xml new file mode 100644 index 0000000000..6c10299977 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2001/press.xml @@ -0,0 +1,485 @@ +<press> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD: www/en/news/2001/press.xml,v 1.1 2004/04/07 11:35:10 phantom Exp $ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2001</name> + + <month> + <name>12</name> + + <story> + <name>Microsoft Hotmail still runs on U**x</name> + <url>http://www.theregister.co.uk/content/28/23348.html</url> + <site-name>The Register</site-name> + <site-url>http://www.theregister.co.uk/</site-url> + <date>12 December 2001</date> + <author>Andrew Orlowski</author> + <p>Nearly four years after it was acquired by Microsoft, + and in spite of a well-publicized effort to migrate it to + Windows and IIS, <a href="http://hotmail.com/">Hotmail</a> + is still partly based on FreeBSD and Apache.</p> + </story> + + <story> + <name>Keeping Your Options Open: FreeBSD as a Workstation for UNIX Newbies</name> + + <url>http://www.osnews.com/printer.php?news_id=392</url> + <site-name>OS News</site-name> + <site-url>http://www.osnews.com/</site-url> + <date>12 December 2001</date> + <author>Eugenia Loli-Queru</author> + <p>An article discussing FreeBSD as an workstation OS for new Unix users.</p> + </story> + + </month> + + <month> + <name>11</name> + + <story> + <name>Cleaning Up Ports</name> + + <url>http://www.onlamp.com/pub/a/bsd/2001/11/29/Big_Scary_Daemons.html</url> + <site-name>OnLamp</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>29 November 2001</date> + <author>Michael Lucas</author> + <p>A brief introduction to <tt>portupgrade</tt>.</p> + </story> + + <story> + <name>Stable SMB</name> + + <url>http://www.onlamp.com/pub/a/bsd/2001/11/15/Big_Scary_Daemons.html</url> + <site-name>OnLamp</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>15 November 2001</date> + <author>Michael Lucas</author> + <p>A short article on accessing a Windows(R) share from a + FreeBSD workstation.</p> + </story> + + <story> + <name>FreeBSD Versus Linux Revisited</name> + + <url>http://www.byte.com/documents/s=1794/byt20011107s0001/1112_moshe.html</url> + <site-name>Byte</site-name> + <site-url>http://www.byte.com/</site-url> + <date>12 November 2001</date> + <author>Moshe Bar</author> + <p>Byte's Moshe Bar does a comparison, through informal + benchmarks, of FreeBSD 4.3 to Linux 2.4.10 running + sendmail, procmail, MySQL, and Apache. The emphasis of + the article is examination of the newly rewritten VM + system in Linux, so the tests are conducted with only + 512 MB of RAM. + </p> + </story> + </month> + + <month> + <name>10</name> + + <story> + <name>The Big *BSD Interview</name> + <url>http://www.osnews.com/printer.php?news_id=153</url> + <site-name>OS News</site-name> + <site-url>http://www.osnews.com/</site-url> + <date>08 October 2001</date> + <author>Eugenia Loli-Queru</author> + <p>An interview with Matt Dillon, a key developer in + FreeBSD on the upcoming features in FreeBSD 5.0.</p> + </story> + + </month> + + <month> + <name>9</name> + + <story> + <name>Running Windows applications on FreeBSD</name> + <url>http://www.onlamp.com/pub/a/bsd/2001/09/21/FreeBSD_Basics.html</url> + <site-name>OnLamp</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>21 September 2001</date> + <author>Dru Lavigne</author> + <p>A short article on running Windows(R) applications under WINE + in FreeBSD.</p> + </story> + + <story> + <name>Dealing with Full Disks</name> + <url>http://www.onlamp.com/pub/a/bsd/2001/09/27/Big_Scary_Daemons.html</url> + <site-name>OnLamp</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>27 September 2001</date> + <author>Michael Lucas</author> + <p>A short article on dealing with the all too common full + disk.</p> + </story> + + <story> + <name>Ripping MP3s</name> + <url>http://www.onlamp.com/pub/a/bsd/2001/09/13/Big_Scary_Daemons.html</url> + <site-name>OnLamp</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>13 September 2001</date> + <author>Michael Lucas</author> + <p>A short article on ripping CDs on FreeBSD.</p> + </story> + + </month> + + <month> + <name>8</name> + + <story> + <name>FreeBSD Anti-Virus Protection - A Commercial Alternative</name> + <url>http://bsdatwork.com/reviews.php?op=showcontent&id=1</url> + <site-name>BSDatwork.com</site-name> + <site-url>http://www.bsdatwork.com/</site-url> + <date>21 August 2001</date> + <author>Jeremiah Gowdy</author> + <p>This is a review of Kaspersky Anti-Virus for FreeBSD, a product which + can protect a network of Microsoft Windows hosts by scanning e-mail and + SMB file shares.</p> + </story> + + <story> + <name>CVS Mirror</name> + <url>http://www.onlamp.com/pub/a/bsd/2001/08/30/Big_Scary_Daemons.html</url> + <site-name>Onlamp</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>30 August 2001</date> + <author>Michael Lucas</author> + <p>How to mirror the FreeBSD CVS repository.</p> + </story> + + <story> + <name>CVSup Infrastructure</name> + <url>http://www.onlamp.com/pub/a/bsd/2001/08/16/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>16 August 2001</date> + <author>Michael Lucas</author> + <p>An article on FreeBSD's CVSup infrastructure used to distribute + its source code worldwide.</p> + </story> + + <story> + <name>An Interview with Jordan Hubbard</name> + + <url>http://www.workingmac.com/article/32.wm</url> + + <site-name>Working Mac</site-name> + <site-url>http://www.workingmac.com/</site-url> + + <date>16 August 2001</date> + + <author>pairNetworks</author> + + <p>An short interview with Jordan Hubbard, one of the founders of the + FreeBSD project.</p> + </story> + </month> + + <month> + <name>7</name> + + <story> + <name>Controlling Bandwidth</name> + <url>http://www.onlamp.com/pub/a/bsd/2001/07/26/Big_Scary_Daemons.html + </url> + <site-name>OnLamp</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>26 July 2001</date> + <author>Michael Lucas</author> + <p>Using <tt>DUMMYNET</tt> to control bandwidth allocation</p> + </story> + + <story> + <name>Which OS is Fastest for High-Performance Network + Applications?</name> + <url>http://www.samag.com/documents/s=1148/sam0107a/0107a.htm</url> + + <site-name>Sys Admin</site-name> + <site-url>http://www.samag.com</site-url> + + <date>July 2001</date> + <author>Jeffrey B. Rothman and John Buckman</author> + + <p>Linux, Solaris, FreeBSD and Windows 2000 are benchmarked + for network applications. This article has a <a + href="http://www.samag.com/documents/s=1147/sam0108q/0108q.htm"> + sequel</a> where the tests were redone after tuning + FreeBSD.</p> + + </story> + + <story> + <name>NAI Labs Announces DARPA-Funded FreeBSD Security + Initiative</name> + + <url>http://opensource.nailabs.com/news/20010709-cboss.html</url> + + <site-name>NAI Labs</site-name> + <site-url>http://www.nailabs.com/</site-url> + + <author>NAI Labs Press Release</author> + + <p>NAI Labs, a division of Network Associates, Inc., announced a $1.2 + million contract awarded by the U.S. Navy's Space and Warfare Systems + Command to develop security extensions to the Open Source FreeBSD + operating system.</p> + </story> + </month> + + <month> + <name>6</name> + + <story> + <name>Controlling User Logins</name> + <url>http://www.onlamp.com/pub/a/bsd/2001/06/28/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>28 June 2001</date> + <author>Michael Lucas</author> + <p>An article describing the ways to control user access to your + FreeBSD system.</p> + </story> + + <story> + <name>Rotating Log Files</name> + <url>http://www.onlamp.com/pub/a/bsd/2001/06/14/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>14 June 2001</date> + <author>Michael Lucas</author> + <p>Using the functionality of <tt>newsyslog</tt> in FreeBSD.</p> + </story> + + <story> + <name>Microsoft's FreeBSD Move Aimed At Next Generation Of + Developers</name> + + <url>http://www.crn.com/sections/BreakingNews/breakingnews.asp?ArticleID=27727</url> + + <site-name>CRN</site-name> + <site-url>http://www.crn.com/</site-url> + + <date>27 June 2001</date> + + <author>Paula Rooney</author> + + <p>A report on Microsoft's venture to port its C# programming language + to FreeBSD.</p> + </story> + + <story> + <name>BSD guru to guide Apple on Unix</name> + + <url>http://www.macworld.co.uk/news/main_news.cfm?NewsID=3092</url> + + <site-name>Mac World</site-name> + <site-url>http://www.macworld.co.uk/</site-url> + <date>26 June 2001</date> + <author>Macworld (UK) staff</author> + + <p>Apple (<a href="http://www.apple.com/">http://www.apple.com/</a>) + has recruited FreeBSD founder Jordan Hubbard to its team, in a bid + to steer its Mac OS X BSD (Berkeley Software Distribution) + efforts.</p> + </story> + + <story> + <name>Microsoft Uses Open-Source Code Despite Denying Use of Such + Software</name> + + <site-name>Wall Street Journal</site-name> + <site-url>http://www.wsj.com/</site-url> + <date>18 June 2001</date> + <author>Lee Gomes</author> + + <p>An article which states that open-source software connected with + the FreeBSD operating system is used in several places deep inside + several versions of Microsoft's Windows software, and on numerous + server computers that manage major functions at Microsoft's free + e-mail service, <a href="http://www.hotmail.com/">Hotmail</a>.</p> + </story> + + <story> + <name>In your face! MS open source attacks backfire</name> + <url>http://zdnet.com.com/2100-11-530056.html</url> + <site-name>ZDNet</site-name> + <site-url>http://www.zdnet.com/</site-url> + <date>14 June 2001</date> + <author>Lee Gomes</author> + + <p>A report on the backfiring of the Microsoft effort to vilify + open source software.</p> + </story> + + </month> + + <month> + <name>5</name> + + <story> + <name>System Logging</name> + <url>http://www.onlamp.com/pub/a/bsd/2001/05/17/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>17 May 2001</date> + <author>Michael Lucas</author> + <p>System logging in FreeBSD using <tt>syslogd</tt>.</p> + </story> + + <story> + <name>BSD Tricks: CVS</name> + <url>http://www.onlamp.com/pub/a/bsd/2001/05/03/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>03 May 2001</date> + <author>Michael Lucas</author> + <p>Using CVS in client-mode.</p> + </story> + + </month> + + <month> + <name>4</name> + <story> + <name>Setting up Wireless Cards on FreeBSD</name> + <url>http://www.onlamp.com/pub/a/bsd/2001/04/19/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>19 April 2001</date> + <author>Michael Lucas</author> + <p>Configuring FreeBSD for wireless operation.</p> + </story> + + </month> + + <month> + <name>3</name> + + <story> + <name>FreeBSD Gaming</name> + <url>http://www.onlamp.com/pub/a/bsd/2001/03/22/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>22 March 2001</date> + <author>Michael Lucas</author> + <p>A survey of the games available in the FreeBSD ports + collection.</p> + </story> + + <story> + <name>Submitting Changes</name> + <url>http://www.onlamp.com/pub/a/bsd/2001/03/08/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>08 March 2001</date> + <author>Michael Lucas</author> + <p>Submitting change requests to the FreeBSD project using + <tt>send-pr</tt>.</p> + </story> + + </month> + + <month> + <name>2</name> + + <story> + <name>Changing FreeBSD Documentation</name> + <url>http://www.onlamp.com/pub/a/bsd/2001/02/22/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>22 February 2001</date> + <author>Michael Lucas</author> + <p>A mini tutorial on DocBook and its use by the FreeBSD + Documentation Project.</p> + </story> + + <story> + <name>The FreeBSD Documentation Project</name> + <url>http://www.onlamp.com/pub/a/bsd/2001/02/08/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>08 February 2001</date> + <author>Michael Lucas</author> + <p>An introduction to the FreeBSD project.</p> + </story> + + <story> + <name>For Servers: Linux 2.4 vs. FreeBSD 4.1.1</name> + + <url>http://www.byte.com/documents/s=558/BYT20010130S0010/</url> + <site-name>Byte</site-name> + <site-url>http://www.byte.com/</site-url> + <date>05 February 2001</date> + <author>Moshe Bar</author> + + <p>BYTE's Linux guru finds himself wondering why he isn't running + FreeBSD --- a comparison (with informal benchmarks) of FreeBSD + 4.1.1 and a Linux based distribution running the v2.4.0 Linux + kernel.</p> + </story> + </month> + + <month> + <name>1</name> + + <story> + <name>Modifying a Port</name> + <url>http://www.onlamp.com/pub/a/bsd/2001/01/25/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>25 January 2001</date> + <author>Michael Lucas</author> + <p>Howto modify a FreeBSD port.</p> + </story> + + <story> + <name>Fine Control of Ports</name> + <url>http://www.onlamp.com/pub/a/bsd/2001/01/04/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>04 January 2001</date> + <author>Michael Lucas</author> + <p>A system administrator's view of the Ports system.</p> + </story> + + <story> + <name>Is FreeBSD a Superior Server Platform to Linux?</name> + + <url>http://www.webtechniques.com/archives/2001/01/infrrevu/</url> + <site-name>Web Techniques</site-name> + <site-url>http://www.webtechniques.com/</site-url> + <date>January 2001</date> + <author>Nathan Boeger</author> + + <p>A reviewer finds FreeBSD 4.1 to be better suited for web + serving than a Red Hat Linux distribution.</p> + </story> + + <story> + <name>A Roundtable on BSD, Security, and Quality</name> + + <url>http://www.ddj.com/documents/s=865/ddj0165a/</url> + <site-name>Dr Dobbs Journal</site-name> + <site-url>http://www.ddj.com/</site-url> + <date>January 2001</date> + <author>Jack J. Woehr</author> + + <p>A report from a roundtable at the recent USENIX Security + Symposium 2000, involving several prominent developers in the + BSD world.</p> + </story> + </month> + </year> +</press> diff --git a/en_US.ISO8859-1/htdocs/news/2002/Makefile b/en_US.ISO8859-1/htdocs/news/2002/Makefile new file mode 100644 index 0000000000..c996a252f3 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2002/Makefile @@ -0,0 +1,16 @@ +# $FreeBSD: www/en/news/2002/Makefile,v 1.6 2005/09/20 21:18:25 hrs Exp $ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +XMLDOCS+= index:${XSL_NEWS_NEWSFLASH_OLD}:news.xml: +DEPENDSET.index=transtable news + +XMLDOCS+= press:${XSL_NEWS_PRESS_OLD}:: +DEPENDSET.press=transtable press + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/news/2002/news.xml b/en_US.ISO8859-1/htdocs/news/2002/news.xml new file mode 100644 index 0000000000..3570ba85da --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2002/news.xml @@ -0,0 +1,821 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE news PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for News//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/news.dtd"> + +<!-- Simple schema for FreeBSD Project news. + + Divide time in to <year>, <month>, and <day> elements, each of which + has a <name>. + + each <day> element contains one or more <event> elements. + + Each <event> contains an optional <title>, and then a <p>. <p> elements + can contain <a> anchors. + + Use the <title> element if the <p> content is lengthy. When generating + synopses of this information (e.g., for syndication using RDF files), + the contents of <title> will be preferred over <p>. +--> + +<news> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD: www/en/news/2002/news.xml,v 1.2 2004/01/12 21:27:00 hrs Exp $ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2002</name> + + <month> + <name>11</name> + <day> + <name>25</name> + <event> + <title>September 2002 - October 2002 Status Report</title> + + <p>The September-October status report is now available; see the + <a href="&base;/news/status/status.html">status reports Web page</a> + for more information.</p> + </event> + </day> + + <day> + <name>23</name> + + <event> + <title>BSD Conference Japan 2002</title> + + <p><a href="http://bsdcon.jp/">BSD Conference Japan 2002</a> + was held in Tokyo on November 23rd, 2002. During the conference + FreeBSD/NetBSD/OpenBSD folks in Japan got together + to discuss various topics of mutual interest. + In addition, <a href="http://www.apple.com/">Apple + Computer, Inc.</a> gave us + excellent lectures about Mac OS X and Rendezvous. + <a href="http://www.matsui.co.jp/">Matsui Securities Co.,Ltd</a>, + <a href="http://www.yahoo.co.jp/">Yahoo Japan Corporation</a>, + and <a href="http://www.sakura.ad.jp/">SRS SAKURA Internet Inc.</a> + gave case studies of how FreeBSD is used in their + production environments. + <a href="http://www.brains.co.jp/eng-ver/e-index.html">Brains + Corporation</a> gave a talk on + <a href="http://www.brains.co.jp/eng-ver/e-mmeyedemo/index.html">mmEye</a>, + which is equipped with 32bit RISC CPU SH-3 and runs NetBSD.</p> + + <p>The event report published by Mainichi Communications inc., + can be found at + <a href="http://pcweb.mycom.co.jp/news/2002/11/25/10.html">MYCOM PCWEB + (but sorry, Japanese only)</a>. There were 172 attendees at + the conference. We are pleased with this turnout, considering + that this was the first attempt to hold such an event in Japan.</p> + </event> + </day> + + <day> + <name>18</name> + <event> + <title>FreeBSD 5.0 Developer Preview #2 Now Available</title> + + <p>The second developer preview snapshot of 5.0-CURRENT is + <a href="&base;/releases/5.0R/DP2/announce.html">now + available</a>. Please see the <a + href="&base;/releases/5.0R/DP2/relnotes.html">release + notes</a>, <a + href="&base;/releases/5.0R/DP2/errata.html">errata</a>, and + the new <a + href="&base;/releases/5.0R/DP2/early-adopter.html">Early + Adopter's Guide</a> for more information.</p> + + </event> + </day> + + <day> + <name>7</name> + <event> + <p>nVidia releases Geforce drivers for FreeBSD! Check out the <a + href="ftp://download.nvidia.com/freebsd/1.0-3203/README.txt">README</a> + for more information.</p> + </event> + </day> + + <day> + <name>1</name> + <event> + <p>New committer: <a + href="mailto:stephane@FreeBSD.org">Stéphane Legrand</a> + (Documentation Project)</p> + </event> + </day> + + </month> + + <month> + <name>10</name> + + <day> + <name>31</name> + <event> + <p>Opera is natively ported to FreeBSD! Read the official <a + href="http://www.FreeBSD.org/news/press-rel-6.html">press + release</a> for more information.</p> + </event> + </day> + + + <day> + <name>22</name> + + <event> + <p>New committer: <a + href="mailto:edwin@FreeBSD.org">Edwin Groothuis</a> + (Ports)</p> + </event> + </day> + + <day> + <name>18</name> + + <event> + <p>New committer: <a + href="mailto:arved@FreeBSD.org">Tilman Linneweh</a> + (Ports)</p> + </event> + </day> + + <day> + <name>18</name> + + <event> + <p>New committer: <a + href="mailto:daichi@FreeBSD.org">Daichi GOTO</a> + (Ports)</p> + </event> + + <event> + <p>New committer: <a + href="mailto:maho@FreeBSD.org">Maho Nakata</a> + (Ports)</p> + </event> + + </day> + + <day> + <name>16</name> + + <event> + <p>New committer: <a + href="mailto:adamw@FreeBSD.org">Adam Weinberger</a> + (Ports)</p> + </event> + </day> + + <day> + <name>11</name> + + <event> + <p>New committer: <a + href="mailto:cognet@FreeBSD.org">Olivier Houchard</a></p> + </event> + </day> + + <day> + <name>10</name> + + <event> + <title>FreeBSD 4.7-RELEASE is now available</title> + + <p><a href="&base;/releases/4.7R/announce.html">FreeBSD + 4.7-RELEASE</a> has been released. Please see the <a + href="&base;/releases/index.html">Release Information</a> + page for more details. Also be sure to check the <a + href="&base;/releases/4.7R/errata.html">release errata</a> + after installation for any late-breaking news and/or + issues with 4.7.</p> + </event> + </day> + + <day> + <name>9</name> + + <event> + <p>New committer: <a + href="mailto:emoore@FreeBSD.org">Eric Moore</a></p> + </event> + </day> + + <day> + <name>4</name> + + <event> + <p>New committer: <a + href="mailto:mheinen@FreeBSD.org">Martin Heinen</a> + (Documentation Project)</p> + </event> + </day> + + <day> + <name>3</name> + + <event> + <title>July 2002 - August 2002 Status Report</title> + + <p>The July-August status report is now available; see the + <a href="&base;/news/status/status.html">status reports Web page</a> + for more information.</p> + </event> + </day> + </month> + + <month> + <name>9</name> + + <day> + <name>10</name> + + <event> + <p>New committer: <a + href="mailto:grehan@FreeBSD.org">Peter Grehan</a> + (PowerPC)</p> + </event> + </day> + + <day> + <name>2</name> + <event> + <p>Notes from the USENIX ATC 2002 <a + href="&base;/events/2002/usenix-devsummit.html"> + FreeBSD Developer Summit</a> are now + available.</p> + </event> + </day> + + <day> + <name>1</name> + + <event> + <title>FreeBSD-STABLE tree frozen in preparation for 4.7</title> + + <p>The FreeBSD-STABLE branch of the source tree has now been + frozen in <a + href="&base;/releases/4.7R/schedule.html">preparation</a> + for the release of FreeBSD 4.7. This means that any new + commits to the -stable source tree must be approved by the + <a href="&base;/releng/">release engineering team</a> + first. Our expected "ship" date + for 4.7 is October 1, 2002.</p> + </event> + + <event> + <p>New committer: <a + href="mailto:davidxu@FreeBSD.org">David Xu</a> + (KSE)</p> + </event> + </day> + </month> + + <month> + <name>8</name> + + <day> + <name>21</name> + + <event> + <p>New committer: <a + href="mailto:obraun@FreeBSD.org">Oliver Braun</a> + (Ports)</p> + </event> + </day> + + <day> + <name>20</name> + + <event> + <p>New committer: <a + href="mailto:thomas@FreeBSD.org">Thomas Quinot</a></p> + </event> + </day> + + <day> + <name>15</name> + + <event> + <title>May 2002 - June 2002 Status Report</title> + + <p>The May-June 2002 status report is now available; see the + <a href="&base;/news/status/status.html">status reports Web page</a> + for more information.</p> + </event> + + + <event> + <title>FreeBSD 4.6.2-RELEASE is now available</title> + + <p><a href="&base;/releases/4.6.2R/announce.html">FreeBSD + 4.6.2-RELEASE</a> has been released. Please see the <a + href="&base;/releases/index.html">Release Information</a> + page for more details. Also be sure to check the <a + href="&base;/releases/4.6.2R/errata.html">release errata</a> + after installation for any late-breaking news and/or + issues with 4.6.2.</p> + </event> + + <event> + <p>New committer: <a + href="mailto:seanc@FreeBSD.org">Sean Chittenden</a> + (Ports)</p> + </event> + </day> + + <day> + <name>14</name> + + <event> + <p>New committer: <a + href="mailto:leeym@FreeBSD.org">Yen-Ming Lee</a> + (Ports)</p> + </event> + </day> + + <day> + <name>8</name> + + <event> + <p>New committer: <a + href="mailto:jennifer@FreeBSD.org">Jennifer Jihui Yang</a></p> + </event> + </day> + + <day> + <name>7</name> + + <event> + <p>New committer: <a + href="mailto:njl@FreeBSD.org">Nate Lawson</a></p> + </event> + </day> + + <day> + <name>1</name> + + <event> + <title>The Open Group makes a generous donation to FreeBSD</title> + + <p><a href="http://www.opengroup.org">The Open Group</a> has + generously donated several copies of the Authorized Guide to The + Single UNIX Specification, Version 3, books and CD-ROMs to + the <a href="&base;/projects/c99/index.html">FreeBSD C99 & + POSIX Conformance Project</a>. We are greatly appreciative of + their gift.</p> + </event> + </day> + </month> + + <month> + <name>7</name> + + <day> + <name>19</name> + + <event> + <p>New committer: <a + href="mailto:kan@FreeBSD.org">Alexander Kabaev</a></p> + </event> + </day> + + <day> + <name>1</name> + + <event> + <p>New committer: <a + href="mailto:johan@FreeBSD.org">Johan Karlsson</a></p> + </event> + </day> + </month> + + <month> + <name>6</name> + + <day> + <name>25</name> + + <event> + <p>New committer: <a + href="mailto:perky@FreeBSD.org">Hye-Shik Chang</a> + (Ports)</p> + </event> + </day> + + <day> + <name>18</name> + + <event> + <p>New committer: <a + href="mailto:scop@FreeBSD.org">Ville Skyttä</a> + (projects/cvsweb)</p> + </event> + </day> + + <day> + <name>16</name> + + <event> + <p>New committer: <a + href="mailto:blackend@FreeBSD.org">Marc Fonvieille</a> + (Documentation Project)</p> + </event> + </day> + + <day> + <name>15</name> + + <event> + <title>FreeBSD 4.6-RELEASE is now available</title> + + <p><a href="&base;/releases/4.6R/announce.html">FreeBSD + 4.6-RELEASE</a> has been released. Please see the <a + href="&base;/releases/index.html">Release Information</a> + page for more details. Also be sure to check the <a + href="&base;/releases/4.6R/errata.html">release errata</a> + after installation for any late-breaking news and/or + issues with 4.6.</p> + </event> + </day> + + <day> + <name>12</name> + + <event> + <p>New committer: <a + href="mailto:alane@FreeBSD.org">Alan Eldridge</a> + (Ports)</p> + </event> + </day> + </month> + + <month> + <name>5</name> + + <day> + <name>23</name> + + <event> + <title>FreeBSD PR Handling Guidelines</title> + + <p>The <a href="&base;/doc/en/articles/pr-guidelines/article.html"> + FreeBSD PR Handling Guidelines provide recommended practices + for working with FreeBSD problem reports.</a></p> + </event> + </day> + + <day> + <name>18</name> + + <event> + <title>February 2002 - April 2002 Status Report</title> + + <p>The February-April status report is now available; see the + <a href="&base;/news/status/status.html">status reports Web page</a> + for more information.</p> + </event> + </day> + + <day> + <name>16</name> + + <event> + <p>New committer: <a + href="mailto:gordon@FreeBSD.org">Gordon Tetlow</a></p> + </event> + </day> + + <day> + <name>7</name> + + <event> + <p>New committer: <a + href="mailto:fanf@FreeBSD.org">Tony Finch</a></p> + </event> + </day> + + <day> + <name>1</name> + + <event> + <title>FreeBSD-STABLE tree frozen in preparation for 4.6</title> + + <p>The FreeBSD-STABLE branch of the source tree has now been + frozen in <a + href="&base;/releases/4.6R/schedule.html">preparation</a> + for the release of FreeBSD 4.6. This means that any new + commits to the -stable source tree must be approved by the + release engineering team first. Our expected "ship" date + for 4.6 is June 1, 2002.</p> + </event> + </day> + </month> + + <month> + <name>4</name> + + <day> + <name>29</name> + + <event> + <p>New committer: <a + href="mailto:ikob@FreeBSD.org">Katsushi Kobayashi</a></p> + </event> + </day> + + <day> + <name>21</name> + + <event> + <p>New committer: <a + href="mailto:anholt@FreeBSD.org">Eric Anholt</a></p> + </event> + </day> + + <day> + <name>15</name> + + <event> + <p>New committer: <a + href="mailto:mini@FreeBSD.org">Jonathan Mini</a></p> + </event> + </day> + + <day> + <name>12</name> + + <event> + <p>New committer: <a + href="mailto:tjr@FreeBSD.org">Tim Robbins</a></p> + </event> + </day> + + <day> + <name>11</name> + + <event> + <p>New committer: <a + href="mailto:glewis@FreeBSD.org">Greg Lewis</a> + (Ports)</p> + </event> + </day> + + <day> + <name>8</name> + + <event> + <title>FreeBSD 5.0 Developer Preview #1 now + available</title> + + <p>A developer preview snapshot of 5.0-CURRENT is now <a + href="&base;/releases/5.0R/DP1/announce.html">available</a>. + Please see the <a + href="&base;/releases/5.0R/DP1/relnotes.html">release + notes</a> for more information. Also be sure to check the + <a href="&base;/releases/5.0R/DP1/errata.html">release + errata</a> for a list of known problems.</p> + </event> + + <event> + <p>New committer: <a + href="mailto:gerald@FreeBSD.org">Gerald Pfeifer</a> + (Ports)</p> + </event> + </day> + + <day> + <name>5</name> + + <event> + <p>New committer: <a + href="mailto:marcus@FreeBSD.org">Joe Marcus Clarke</a> + (Ports)</p> + </event> + </day> + + <day> + <name>1</name> + + <event> + <p>New committer: <a + href="mailto:nork@FreeBSD.org">Norikatsu Shigemura</a> + (Ports)</p> + </event> + </day> + </month> + + <month> + <name>3</name> + + <day> + <name>30</name> + + <event> + <p>Notes from the BSDCon 2002 <a + href="&base;/events/2002/bsdcon-devsummit.html"> + FreeBSD Developer Summit</a> are now + available.</p> + </event> + </day> + + <day> + <name>28</name> + + <event> + <p>New committer: <a + href="mailto:trhodes@FreeBSD.org">Tom Rhodes</a> + (Documentation Project)</p> + </event> + </day> + + <day> + <name>29</name> + + <event> + <p>New committer: <a + href="mailto:suz@FreeBSD.org">SUZUKI Shinsuke</a> + (IPv6)</p> + </event> + </day> + + <day> + <name>19</name> + + <event> + <p>New committer: <a + href="mailto:netchild@FreeBSD.org">Alexander Leidinger</a> + (Ports)</p> + </event> + </day> + + <day> + <name>17</name> + + <event> + <p>New committer: <a + href="mailto:ceri@FreeBSD.org">Ceri Davies</a> (Documentation)</p> + </event> + </day> + + <day> + <name>12</name> + + <event> + <title>Updated release schedule now available</title> + + <p>A new area of the FreeBSD web site has been created + dedicated to <a href="&base;/releng/index.html">release + engineering</a>. This new section contains information + about future releases of FreeBSD, a specific schedule for + the upcoming releases of FreeBSD 4.6 and 5.0, and + more.</p> + </event> + </day> + + <day> + <name>9</name> + + <event> + <title>SMP sparc64 now works</title> + + <p>FreeBSD now works with multiple processors on sparc64 systems, + thanks to the efforts of <a href="mailto:jake@FreeBSD.org">Jake + Burkholder</a>, and <a href="mailto:tmm@FreeBSD.org">Thomas + Moestl</a>.</p> + </event> + </day> + + <day> + <name>3</name> + + <event> + <p>New committer: <a + href="mailto:mux@FreeBSD.org">Maxime Henrion</a> + (VFS, SMP, ...)</p> + </event> + </day> + </month> + + <month> + <name>2</name> + + <day> + <name>25</name> + + <event> + <title>December 2001 - January 2002 Status Report</title> + + <p>The December/January status report is now available; see the + <a href="&base;/news/status/status.html">status reports Web page</a> + for more information.</p> + </event> + + <event> + <p>New committer: <a + href="mailto:jmallett@FreeBSD.org">J. Mallett</a></p> + </event> + </day> + + <day> + <name>18</name> + + <event> + <p>New committer: <a + href="mailto:ticso@FreeBSD.org">Bernd Walter</a> + (Alpha)</p> + </event> + </day> + + <day> + <name>11</name> + + <event> + <title>New GNOME section of the FreeBSD.org site</title> + + <p><a href="mailto:freebsd-gnome@FreeBSD.org">FreeBSD GNOME team</a> + is proud to announce new section of the FreeBSD.org site devoted to + various aspects of the GNOME desktop and development environment + on the FreeBSD. Check it out <a href="&base;/gnome/">here</a>. + </p> + </event> + </day> + + <day> + <name>7</name> + + <event> + <p>New committer: <a + href="mailto:maxim@FreeBSD.org">Maxim Konovalov</a></p> + </event> + </day> + </month> + + <month> + <name>1</name> + + <day> + <name>31</name> + + <event> + <title>BSDCon Europe 2002 - Call for Papers</title> + + <p>The <a + href="http://www.eurobsdcon2002.org/cfp.html">announcement + and call for papers</a> for BSDCon Europe 2002 has been + released. This conference will take place in Amsterdam, + The Netherlands some time in November 2002. Individuals + interested in presenting a paper at the conference should + submit an abstract by June 24, 2002.</p> + </event> + </day> + + <day> + <name>29</name> + + <event> + <title>FreeBSD 4.5 is now available</title> + + <p><a href="&base;/releases/4.5R/announce.html">FreeBSD + 4.5</a> has been released. Please see the <a + href="&base;/releases/index.html">Release Information</a> + page for more details. Also be sure to check the <a + href="&base;/releases/4.5R/errata.html">release errata</a> + after installation for any late-breaking issues with 4.5 + that may occur.</p> + </event> + </day> + + <day> + <name>12</name> + + <event> + <title>Testing Guide now available for upcoming 4.5 release.</title> + + <p>The FreeBSD 4.5 Release Engineering Team has submitted a + <a href="&base;/releases/4.5R/qa.html">testing guide</a> + for the upcoming FreeBSD 4.5 release. Please help us + ensure that 4.5 is our most stable and highest performance + release yet.</p> + </event> + </day> + + <day> + <name>10</name> + + <event> + <title>New tutorial: "The Euro symbol on FreeBSD"</title> + + <p>Aaron Kaplan has submitted a new article explaining how to + adjust your system configuration to use the new <a + href="&base;/doc/en_US.ISO8859-1/articles/euro/article.html">Euro + symbol on FreeBSD</a>.</p> + </event> + </day> + </month> + </year> +</news> + diff --git a/en_US.ISO8859-1/htdocs/news/2002/press.xml b/en_US.ISO8859-1/htdocs/news/2002/press.xml new file mode 100644 index 0000000000..098864de8b --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2002/press.xml @@ -0,0 +1,409 @@ +<press> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD$ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2002</name> + + <month> + <name>10</name> + + <story> + <name>Opera Software Releases Version for FreeBSD</name> + <url>http://www.opera.com/pressreleases/en/2002/10/31/b/</url> + <site-name>Opera Software</site-name> + <site-url>http://www.opera.com/</site-url> + <date>31 October 2002</date> + <author>Opera Software Press Release</author> + <p>Opera Software proudly announces the first golden release + of a new port of its software to FreeBSD.</p> + </story> + + <story> + <name>DVD Playback on FreeBSD</name> + <url>http://www.onlamp.com/pub/a/bsd/2002/10/03/FreeBSD_Basics.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>03 October 2002</date> + <author>Dru Lavigne</author> + <p>Dru Lavigne delves into the world of DVD playback on FreeBSD.</p> + </story> + </month> + + <month> + <name>9</name> + + <story> + <name>The BSDs: Sophisticated, Powerful and (Mostly) + Free</name> + <url>http://www.extremetech.com/article2/0,3973,555451,00.asp</url> + <site-name>Extreme Tech</site-name> + <site-url>http://www.extremetech.com/</site-url> + <date>26 September 2002</date> + <author>Brett Glass</author> + <p>An article on the history and culture of the BSD projects.</p> + </story> + + <story> + <name>Using Sound on FreeBSD</name> + <url>http://www.onlamp.com/pub/a/bsd/2002/09/19/FreeBSD_Basics.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>19 September 2002</date> + <author>Dru Lavigne</author> + <p>Dru Lavigne describes the process of configuring sound on a + FreeBSD multimedia workstation.</p> + </story> + + <story> + <name>BSD, An Enterprise OS? Well, Yes</name> + <url>http://www.itworld.com/nl/unix_insider/09172002/</url> + <site-name>ITworld.com</site-name> + <site-url>http://www.itworld.com/</site-url> + <date>17 September 2002</date> + <author>UNIX in the Enterprise</author> + <p>A short interview with committer Michael Lucas, on using BSD in enterprise environments.</p> + </story> + + <story> + <name>Turn FreeBSD into a Multimedia Workstation</name> + <url>http://www.onlamp.com/pub/a/bsd/2002/09/05/FreeBSD_Basics.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>05 September 2002</date> + <author>Dru Lavigne</author> + <p>Dru Lavigne explains how to create a multimedia workstation with FreeBSD.</p> + </story> + </month> + <month> + <name>8</name> + <story> + <name>Chasing Linux</name> + <url>http://www.infoworld.com/articles/fe/xml/02/08/12/020812fefreebsd.xml</url> + <site-name>InfoWorld</site-name> + <site-url>http://www.infoworld.com/</site-url> + <date>09 August 2002</date> + <author>Maggie Biggs</author> + <p>Maggie Biggs takes a look at the upcoming FreeBSD 5.0, and + discovers that this open-source OS shows significant gains + in available applications and tools along with beefed-up + security.</p> + </story> + </month> + <month> + <name>6</name> + + <story> + <name>Interview with Jordan Hubbard</name> + <url>http://kerneltrap.org/node.php?id=278</url> + <site-name>Kerneltrap</site-name> + <site-url>http://kerneltrap.org/</site-url> + <date>20 June 2002</date> + <author>Jeremy Andrews</author> + <p>Kerneltrap speaks with Jordan Hubbard, one of the creators + of FreeBSD, and currently manager of Apple's Darwin project.</p> + </story> + + </month> + + <month> + <name>5</name> + + <story> + <name>Dual-Booting FreeBSD and FreeBSD</name> + <url>http://www.onlamp.com/pub/a/bsd/2002/05/09/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>16 May 2002</date> + <author>Michael Lucas</author> + <p>Michael Lucas explains how a machine can be made to dual-boot + FreeBSD -CURRENT and -STABLE.</p> + </story> + + </month> + + <month> + <name>4</name> + + <story> + <name>Jordan Hubbard resigns from FreeBSD core</name> + <url>http://daily.daemonnews.org/view_story.php3?story_id=2837</url> + <site-name>Daemon News</site-name> + <site-url>http://www.daemonnews.org/</site-url> + <date>29 April 2002</date> + <author>Gregory Sutter</author> + <p>FreeBSD co-founder Jordan Hubbard leaves the core team.</p> + </story> + + <story> + <name>Technology a la Carte</name> + <url>http://www.byte.com/documents/s=7145/byt1019082849618/</url> + <site-name>Byte</site-name> + <site-url>http://www.byte.com/</site-url> + <date>22 April 2002</date> + <author>Bill Nicholls</author> + <p>A review of FreeBSD 4.5 with mention of the FreeBSD + 5.0 "Developer Preview" release.</p> + </story> + + <story> + <name>Testing FreeBSD-Current</name> + <url>http://www.onlamp.com/pub/a/bsd/2002/04/18/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>18 April 2002</date> + <author>Michael Lucas</author> + <p>Committer Michael Lucas takes a look at the FreeBSD 5.0 Developers' + Preview 1.</p> + </story> + + <story> + <name>Connecting to IPv6 with FreeBSD</name> + <url>http://www.linuxorbit.com/modules.php?op=modload&name=Sections&file=index&req=viewarticle&artid=524</url> + <site-name>Linux Orbit</site-name> + <site-url>http://www.linuxorbit.com/</site-url> + <date>18 April 2002</date> + <author>David LeCount</author> + <p>This tells how to use freenet6 from the ports collection to tunnel IPv6 over IPv4. + </p> + </story> + + <story> + <name>System Panics, Part 2: Recovering and Debugging</name> + <url>http://www.onlamp.com/pub/a/bsd/2002/04/04/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>04 April 2002</date> + <author>Michael Lucas</author> + <p>Michael Lucas talks about what to do when a system panic does + happen. This is the second part of a two part article; <a + href="http://www.onlamp.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html"> + part 1</a> dealt with preparing a FreeBSD system to deal with + panics.</p> + </story> + + <story> + <name>Configuring a FreeBSD Access Point for your Wireless Network</name> + <url>http://www.samag.com/documents/s=7121/sam0205a/sam0205a.htm</url> + <site-name>Sys Admin Magazine</site-name> + <site-url>http://www.samag.com/</site-url> + <date>April 2002</date> + <author>Michael S. DeGraw-Bertsch</author> + <p>This has instructions for securely configuring a PC running FreeBSD as a gateway + between an 802.11b network and a traditional wired network.</p> + </story> + + <story> + <name>Anti-Unix campaign falters</name> + <url>http://www.infoworld.com/articles/hn/xml/02/04/01/020401hnunixcamp.xml</url> + <site-name>InfoWorld</site-name> + <site-url>http://www.infoworld.com/</site-url> + <date>01 April 2002</date> + <author>Matt Berger</author> + <p>InfoWorld reports on the use of FreeBSD to power a website built + for a prominent advertising campaign.</p> + </story> + </month> + + <month> + <name>3</name> + + <story> + <name>A Multimedia Tutorial For FreeBSD</name> + <url>http://www.examnotes.net/forums/default.php?ind=122</url> + <site-name>ExamNotes.net</site-name> + <site-url>http://www.examnotes.net/</site-url> + <date>30 March 2002</date> + <author>Tracey J. Rosenblath</author> + <p>This tells how to set up and use the audio support in FreeBSD.</p> + </story> + + <story> + <name>System Panics, Part 1: Preparing for the Worst</name> + <url>http://www.onlamp.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>21 March 2002</date> + <author>Michael Lucas</author> + <p>Preparing a FreeBSD system to handle a panic.</p> + </story> + + + <story> + <name>Understanding CVSup, Mounting, Ports and Init on + FreeBSD</name> + <url>http://www.osnews.com/story.php?news_id=818</url> + <site-name>OS News</site-name> + <site-url>http://www.osnews.com/</site-url> + <date>19 March 2002</date> + <author>Nathan Mace</author> + <p>An article on configuring and maintaining a FreeBSD + install.</p> + </story> + + <story> + <name>Want a Windows alternative? Try BSD</name> + <url>http://zdnet.com.com/2100-1107-863169.html</url> + <site-name>ZDNet</site-name> + <site-url>http://www.zdnet.com/</site-url> + <date>19 March 2002</date> + <author>Stephan Somogyi</author> + <p>This is a non-technical introduction to the BSD family (except BSD/OS).</p> + </story> + + <story> + <name>Find: Part Two</name> + <url>http://www.onlamp.com/pub/a/bsd/2002/03/14/FreeBSD_Basics.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>14 March 2002</date> + <author>Dru Lavigne</author> + <p>Looking for your files with <tt>find</tt>.</p> + </story> + + <story> + <name>Building a CD Bootable Firewall</name> + <url>http://www.bsdtoday.com/2002/March/Features646.html</url> + <site-name>BSD Today</site-name> + <site-url>http://www.bsdtoday.com/</site-url> + <date>08 March 2002</date> + <author>Etienne de Bruin</author> + <p>This article has instructions for making a FreeBSD system which + boots from CD-ROM. Its use as a firewall is mentioned.</p> + </story> + + </month> + + <month> + <name>2</name> + + <story> + <name>IPv6, Meet FreeBSD</name> + <url>http://www.onlamp.com/pub/a/bsd/2002/02/22/ipv6.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>22 February 2002</date> + <author>Mike DeGraw-Bertsch</author> + <p>A walk-through on configuring IPv6 on FreeBSD.</p> + </story> + + <story> + <name>Finding Things in Unix</name> + <url>http://www.onlamp.com/pub/a/bsd/2002/02/21/FreeBSD_Basics.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>21 February 2002</date> + <author>Dru Lavigne</author> + <p>Getting acquainted with <tt>find</tt>.</p> + </story> + + <story> + <name>Understanding NFS</name> + <url>http://www.onlamp.com/pub/a/bsd/2002/02/14/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>14 February 2002</date> + <author>Michael Lucas</author> + <p>Using NFS in FreeBSD.</p> + </story> + + </month> + + <month> + <name>1</name> + + <story> + <name>How to Become a FreeBSD Committer</name> + <url>http://www.onlamp.com/pub/a/bsd/2002/01/31/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>31 January 2002</date> + <author>Michael Lucas</author> + <p>Michael documents the process of becoming a FreeBSD committer.</p> + </story> + + <story> + <name>FreeBSD Week: Migrating from Linux to FreeBSD</name> + <url>http://www.osnews.com/story.php?news_id=580</url> + <site-name>OS News</site-name> + <site-url>http://www.osnews.com/</site-url> + <date>31 January 2002</date> + <author>Nathan Mace</author> + <p>A guide for users migrating from Linux to FreeBSD.</p> + </story> + + <story> + <name>FreeBSD Week: Interview with Robert Watson</name> + <url>http://www.osnews.com/story.php?news_id=572</url> + <site-name>OS News</site-name> + <site-url>http://www.osnews.com/</site-url> + <date>29 January 2002</date> + <author>Eugenia Loli-Queru</author> + <p>An interview with Robert Watson, member of FreeBSD's core + and security on the upcoming FreeBSD 4.5 and FreeBSD 5.0 + releases.</p> + </story> + + <story> + <name>American Megatrends Inc. Releases Latest Version of StorTrends NAS Software</name> + <url>http://biz.yahoo.com/bw/020123/232287_1.html</url> + <site-name>Yahoo! Finance</site-name> + <site-url>http://biz.yahoo.com/</site-url> + <date>23 January 2002</date> + <author>AMI Press Release</author> + <p><a href="http://www.ami.com/">American Megatrends</a> Inc. announced the release of + StoreTrends(tm) NAS software version 1.1, which is based on + FreeBSD.</p> + </story> + + <story> + <name>Contributing to BSD</name> + <url>http://www.onlamp.com/pub/a/bsd/2002/01/17/Big_Scary_Daemons.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>17 January 2002</date> + <author>Michael Lucas</author> + <p>Michael Lucas shows what it takes for non-coders to contribute to + BSD.</p> + </story> + + <story> + <name>A basic guide to securing FreeBSD 4.x-STABLE</name> + <url>http://draenor.org/securebsd/secure.txt</url> + <site-name>draenor.org</site-name> + <site-url>http://draenor.org/</site-url> + <date>17 January 2002</date> + <author>Marc Silver</author> + <p>This article is for system administrators. It explains + how to configure and maintain a FreeBSD system for high + security.</p> + </story> + + <story> + <name>FreeBSD to change hands</name> + <url>http://dailynews.yahoo.com/h/cn/20020114/tc/freebsd_to_change_hands_1.html</url> + <site-name>Yahoo News</site-name> + <site-url>http://dailynews.yahoo.com/</site-url> + <date>14 January 2002</date> + <author>Stephen Shankland CNET</author> + <p><a href="http://www.windriver.com/">Wind River Systems</a> + announces the transfer of its FreeBSD assets to the + <a href="http://www.freebsdmall.com/">FreeBSD Mall</a>.</p> + </story> + + <story> + <name>Kerneltrap Interview with Matt Dillon</name> + <url>http://kerneltrap.com/article.php?sid=459</url> + <site-name>Kerneltrap</site-name> + <site-url>http://kerneltrap.com/</site-url> + <date>02 January 2002</date> + <author>Jeremy Andrews</author> + <p>Kerneltrap interviews Matt Dillon, one of FreeBSD's key + developers.</p> + </story> + </month> + </year> +</press> diff --git a/en_US.ISO8859-1/htdocs/news/2003/Makefile b/en_US.ISO8859-1/htdocs/news/2003/Makefile new file mode 100644 index 0000000000..8c81ce888d --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2003/Makefile @@ -0,0 +1,16 @@ +# $FreeBSD: www/en/news/2003/Makefile,v 1.3 2005/09/20 21:18:25 hrs Exp $ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +XMLDOCS+= index:${XSL_NEWS_NEWSFLASH_OLD}:news.xml: +DEPENDSET.index=transtable news + +XMLDOCS+= press:${XSL_NEWS_PRESS_OLD}:: +DEPENDSET.press=transtable press + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/news/2003/news.xml b/en_US.ISO8859-1/htdocs/news/2003/news.xml new file mode 100644 index 0000000000..c0a915cf8b --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2003/news.xml @@ -0,0 +1,607 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE news PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for News//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/news.dtd"> + +<!-- Simple schema for FreeBSD Project news. + + Divide time in to <year>, <month>, and <day> elements, each of which + has a <name>. + + each <day> element contains one or more <event> elements. + + Each <event> contains an optional <title>, and then a <p>. <p> elements + can contain <a> anchors. + + Use the <title> element if the <p> content is lengthy. When generating + synopses of this information (e.g., for syndication using RDF files), + the contents of <title> will be preferred over <p>. +--> + +<news> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD: www/en/news/2003/news.xml,v 1.1 2005/04/19 21:19:03 brueffer Exp $ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2003</name> + + <month> + <name>12</name> + + <day> + <name>28</name> + <event> + <p>New committer: <a href="mailto:ale@FreeBSD.org">Alex Dupre</a> + (Documentation Project)</p> + </event> + </day> + + <day> + <name>21</name> + <event> + <p>New committer: <a + href="mailto:rik@FreeBSD.org">Roman Kurakin</a> + (src)</p> + </event> + </day> + + <day> + <name>17</name> + <event> + <p>New committer: <a + href="mailto:clement@FreeBSD.org">Clement Laforet</a> + (ports)</p> + </event> + </day> + + <day> + <name>16</name> + <event> + <p>Hifn <a + href="http://www.hifn.com/info/pr/pressreleases/print/pr_121603_2.html"> + announces</a> official FreeBSD support for the 795x series + of crypto accelerators.</p> + </event> + </day> + </month> + + <month> + <name>11</name> + + + <day> + <name>21</name> + <event> + <p>New committer: <a + href="mailto:matk@FreeBSD.org">Mathew Kanner</a> + (midi,sound)</p> + </event> + </day> + + <day> + <name>12</name> + <event> + <p>New committer: <a + href="mailto:eik@FreeBSD.org">Oliver Eikemeier</a> + (Ports)</p> + </event> + + <event> + <p>New committer: <a href="mailto:pav@FreeBSD.org">Pav Lucistnik</a> + (ports)</p> + </event> + + <event> + <p>New committer: <a + href="mailto:andre@FreeBSD.org">Andre Oppermann</a> + (src)</p> + </event> + </day> + </month> + + <month> + <name>10</name> + + + <day> + <name>28</name> + + <event> + <title>FreeBSD 4.9-RELEASE is Now Available</title> + + <p><a href="&base;/releases/4.9R/announce.html">FreeBSD + 4.9-RELEASE</a> has been released. Please see the <a + href="&base;/releases/index.html">Release Information</a> + page for more details. Also be sure to check the <a + href="&base;/releases/4.9R/errata.html">release errata</a> + after installation for any late-breaking news and/or + issues with 4.9.</p> + </event> + </day> + + <day> + <name>22</name> + + <event> + <title>FreeBSD 10 year anniversary party in San Francisco 11/24/03</title> + + <p>Join us Monday November 24th to celebrate 10 years of + FreeBSD at the <a href="http://www.dnalounge.com">DNA + Lounge</a> in San Francisco. The name 'FreeBSD' was <a + href="&base;/news/1993/freebsd-coined.html">coined</a> in + June 1993, and FreeBSD 1.0 was released on CDROM in + December 1993. Click <a + href="http://www.offmyserver.com/cgi-bin/store/rsvp.html">here</a> + for more information or to be put on the guest list.</p> + + </event> + </day> + + <day> + <name>21</name> + <event> + <p>New committer: <a + href="mailto:sergei@FreeBSD.org">Sergei Kolobov</a> + (Ports)</p> + </event> + </day> + + <day> + <name>18</name> + + <event> + <title>BSD Conference Japan 2003</title> + + <p><a href="http://bsdcon.jp/">BSD Conference Japan 2003 + (in Japanese)</a>, the second conference concerning + *BSD in Japan, was held in Tokyo on October 18th, 2003. + There were about 170 attendees. It had two parallel + sessions (general and technical), and + four technical papers and twelve work-in-progress style talks + were presented during the conference.</p> + </event> + </day> + + <day> + <name>17</name> + <event> + <title>The FreeBSD Events page is now available</title> + <p>The <a href="&base;/events/events.html">FreeBSD Events</a> + page is now available with information about past and + upcoming FreeBSD related events.</p> + </event> + </day> + + <day> + <name>14</name> + <event> + <p>New committer: <a + href="mailto:linimon@FreeBSD.org">Mark Linimon</a> + (Ports)</p> + </event> + </day> + + <day> + <name>11</name> + <event> + <p>New committer: <a + href="mailto:rsm@FreeBSD.org">Scott Mitchell</a> + (if_xe)</p> + </event> + </day> + + <day> + <name>9</name> + <event> + <p>New committer: <a + href="mailto:emax@FreeBSD.org">Maksim Yevmenkin</a> + (Bluetooth)</p> + </event> + </day> + </month> + + <month> + <name>9</name> + + <day> + <name>15</name> + <event> + <p>New committer: <a + href="mailto:den@FreeBSD.org">Denis Peplin</a> + (Documentation Project)</p> + </event> + </day> + </month> + + <month> + <name>8</name> + + <day> + <name>25</name> + <event> + <p>The FreeBSD Foundation <a + href="http://www.freebsdfoundation.org/press/20030825-java131.shtml">announces</a> + native support for JDK 1.3.1 on FreeBSD</p> + </event> + </day> + + <day> + <name>18</name> + <event> + <p><a href="&base;/releases/4.9R/schedule.html">FreeBSD 4.9</a> code freeze begins August 25</p> + </event> + </day> + + <day> + <name>15</name> + <event> + <p>New committer: <a + href="mailto:kensmith@FreeBSD.org">Ken Smith</a> + (Documentation Project)</p> + </event> + + <event> + <p>New committer: <a + href="mailto:mat@FreeBSD.org">Mathieu Arnold</a> + (Ports)</p> + </event> + </day> + + <day> + <name>14</name> + <event> + <p>New committer: <a + href="mailto:bland@FreeBSD.org">Alexander Nedotsukov</a> + (Ports)</p> + </event> + </day> + + <day> + <name>11</name> + <event> + <title>FreeBSD Architecture Handbook now available</title> + + <p>The nascent <a + href="&base;/doc/en_US.ISO8859-1/books/arch-handbook/index.html">FreeBSD + Architecture Handbook</a> is now available online for + users who would like to know more about FreeBSD kernel + internals. Much of the material has been split out from + the <a + href="&base;/doc/en_US.ISO8859-1/books/developers-handbook/index.html">Developers' + Handbook</a>, which now focuses exclusively on userland + programming in FreeBSD. Both volumes are works in + progress.</p> + + </event> + </day> + + <day> + <name>9</name> + + <event> + <title>PAE support merged for upcoming FreeBSD 4.9</title> + + <p>Luoqi Chen has begun the process of merging PAE support + from FreeBSD 5 to FreeBSD 4-STABLE. The PAE support + allows FreeBSD machines to make use of more than 4 + gigabytes of RAM. This functionality was originally + written by Jake Burkholder under contract with DARPA and + Network Associates Laboratories. Additional changes for + individual device drivers will follow in the coming + weeks.</p> + </event> + + <event> + <p>New committer: <a + href="mailto:bms@FreeBSD.org">Bruce M. Simpson</a></p> + </event> + </day> + </month> + + <month> + <name>7</name> + + <day> + <name>24</name> + <event> + <p>New committer: <a + href="mailto:lofi@FreeBSD.org">Michael Nottebrock</a> + (Ports)</p> + </event> + </day> + + <day> + <name>21</name> + <event> + <p>New committer: <a + href="mailto:krion@FreeBSD.org">Kirill Ponomarew</a> + (Ports)</p> + </event> + </day> + + <day> + <name>20</name> + + <event> + <p>New committer: <a + href="mailto:simon@FreeBSD.org">Simon L. Nielsen</a></p> + </event> + </day> + </month> + + <month> + <name>6</name> + + <day> + <name>24</name> + <event> + <p>New committer: <a + href="mailto:smkelly@FreeBSD.org">Sean Kelly</a></p> + </event> + </day> + + <day> + <name>23</name> + <event> + <p>New committer: <a + href="mailto:dds@FreeBSD.org">Diomidis D. Spinellis</a></p> + </event> + </day> + + <day> + <name>19</name> + <event> + <title>Happy 10th Birthday, FreeBSD Project!</title> + + <p>Ten years ago on this day the name "FreeBSD" was coined + by David Greenman in <a + href="&base;/news/1993/freebsd-coined.html">this + email</a> message. Viva FreeBSD!</p> + + </event> + </day> + + <day> + <name>17</name> + <event> + <p>New committer: <a + href="mailto:lev@FreeBSD.org">Lev Serebryakov</a> + (Ports)</p> + </event> + </day> + + <day> + <name>13</name> + <event> + <p>Returning committer: <a + href="mailto:jmg@FreeBSD.org">John-Mark Gurney</a></p> + </event> + </day> + + <day> + <name>9</name> + <event> + <title>FreeBSD 5.1-RELEASE is Now Available</title> + + <p><a href="&base;/releases/5.1R/announce.html">FreeBSD + 5.1-RELEASE</a> is now available. Please see the <a + href="&base;/releases/index.html">Release Information</a> + page for more details. Also be sure to check the <a + href="&base;/releases/5.1R/errata.html">release errata</a> + for any late-breaking news and/or issues with 5.1.</p> + </event> + </day> + + <day> + <name>6</name> + <event> + <p>New committer: <a + href="mailto:osa@FreeBSD.org">Sergey A. Osokin</a> + (Ports)</p> + </event> + </day> + + <day> + <name>4</name> + <event> + <p>New committer: <a + href="mailto:erwin@FreeBSD.org">Erwin Lansing</a> + (Ports)</p> + </event> + </day> + </month> + + <month> + <name>5</name> + + <day> + <name>6</name> + <event> + <p>New committer: <a + href="mailto:oliver@FreeBSD.org">Oliver Lehmann</a> + (Ports)</p> + </event> + </day> + + <day> + <name>5</name> + <event> + <p>New committer: <a + href="mailto:mich@FreeBSD.org">Michael L. Hostbaek</a></p> + </event> + </day> + </month> + + <month> + <name>4</name> + + <day> + <name>14</name> + <event> + <p>New committer: <a + href="mailto:hmp@FreeBSD.org">Hiten M. Pandya</a></p> + </event> + </day> + + <day> + <name>9</name> + <event> + <title>New performance@ mailing list</title> + + <p>The performance@ mailing list exists to provide a place + for hackers, administrators, and/or concerned parties to + discuss performance related topics pertaining to FreeBSD. + Acceptable topics includes talking about FreeBSD + installations that are either under high load, are + experiencing performance problems, or are pushing the + limits of FreeBSD. Concerned parties that are willing to + work toward improving the performance of FreeBSD are + highly encouraged to subscribe to this list. This is a + highly technical list ideally suited for experienced + FreeBSD users, hackers, or administrators interested in + keeping FreeBSD fast, robust, and scalable. To subscribe, + please visit the <a + href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-performance">freebsd-performance@ + web interface</a>.</p> + </event> + </day> + + <day> + <name>8</name> + <event> + <title>FreeBSD.org mailing lists use Mailman</title> + + <p>Majordomo served its purpose well, but has been retired + in favor of <a href="http://www.list.org/">Mailman</a>. + It is now possible to browse through the authoritative + list of mailing lists by heading over to <a + href="http://lists.FreeBSD.org/mailman/listinfo">http://lists.FreeBSD.org/mailman/listinfo</a> + or by browsing through the <a + href="/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL">handbook's + section on mailing lists</a>. A big thanks to Peter Wemm + is in order for spending the time to seamlessly convert + the various lists over to Mailman, thank you.</p> + </event> + </day> + + <day> + <name>3</name> + <event> + <title>FreeBSD 4.8-RELEASE is Now Available</title> + + <p><a href="&base;/releases/4.8R/announce.html">FreeBSD + 4.8-RELEASE</a> has been released. Please see the <a + href="&base;/releases/index.html">Release Information</a> + page for more details. Also be sure to check the <a + href="&base;/releases/4.8R/errata.html">release errata</a> + after installation for any late-breaking news and/or + issues with 4.8.</p> + </event> + </day> + </month> + + <month> + <name>3</name> + + <day> + <name>15</name> + <event> + <title>January 2003 - February 2003 Status Report</title> + + <p>The January-February status report is now available; see the + <a href="&base;/news/status/status.html">status reports Web page</a> + for more information.</p> + </event> + </day> + + <day> + <name>6</name> + <event> + <p>New committer: <a + href="mailto:arun@FreeBSD.org">Arun Sharma</a></p> + </event> + </day> + + </month> + + <month> + <name>2</name> + + <day> + <name>21</name> + <event> + <p>New committer: <a + href="mailto:das@FreeBSD.org">David Schultz</a></p> + </event> + </day> + + </month> + + <month> + <name>1</name> + + <day> + <name>30</name> + <event> + <p>New committer: <a + href="mailto:harti@FreeBSD.org">Hartmut Brandt</a> + (Sparc and ATM)</p> + </event> + </day> + + <day> + <name>23</name> + <event> + <title>November 2002 - December 2002 Status Report</title> + + <p>The November-December status report is now available; see the + <a href="&base;/news/status/status.html">status reports Web page</a> + for more information.</p> + </event> + <event> + <p>New committer: <a + href="mailto:rushani@FreeBSD.org">Hideyuki KURASHINA</a> + (Documentation Project)</p> + </event> + </day> + + <day> + <name>19</name> + + <event> + <title>FreeBSD 5.0-RELEASE is now available</title> + + <p><a href="&base;/releases/5.0R/announce.html">FreeBSD + 5.0-RELEASE</a> has been released. Please see the <a + href="&base;/releases/index.html">Release Information</a> + page for more details. Also be sure to check the <a + href="&base;/releases/5.0R/errata.html">release errata</a> + after installation for any late-breaking news and/or + issues with 5.0.</p> + </event> + </day> + + <day> + <name>13</name> + <event> + <p>New committer: <a + href="mailto:brueffer@FreeBSD.org">Christian Brüffer</a> + (Documentation Project)</p> + </event> + </day> + + <day> + <name>6</name> + <event> + <p>New committer: <a + href="mailto:mtm@FreeBSD.org">Michael Telahun Makonnen</a></p> + </event> + </day> + + </month> + + </year> +</news> + diff --git a/en_US.ISO8859-1/htdocs/news/2003/press.xml b/en_US.ISO8859-1/htdocs/news/2003/press.xml new file mode 100644 index 0000000000..54a36c47d7 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2003/press.xml @@ -0,0 +1,568 @@ +<press> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD$ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2003</name> + + <month> + <name>12</name> + + <story> + <name>Apple unveils Panther OS</name> + <url>http://computerworld.com.my/pcwmy.nsf/unidlookup/3E918524EABCF22A48256E04001F413F?OpenDocument</url> + <site-name>ComputerWorld, Malaysia</site-name> + <site-url>http://computerworld.com.my/</site-url> + <date>31 December 2003</date> + <author>Blake Hoo</author> + <p>Apple Computer recently announced the availability of its + highly anticipated Mac OS X 10.3 Panther, based on + FreeBSD 5.</p> + </story> + + <story> + <name>Year in Review: Turbulence, troubles and triumph in OS market</name> + <url>http://www.computerworld.co.nz/news.nsf/PrintDoc/C20DECA717B0D5D5CC256DF1006B7A8E?OpenDocument&pub=Computerworld</url> + <site-name>Computerworld</site-name> + <site-url>http://www.computerworld.co.nz/</site-url> + <date>30 December 2003</date> + <author>Matthew Cooney</author> + <p>The year 2003 in retrospect of various operating systems, including FreeBSD.</p> + </story> + + <story> + <name>eRacks announces Linux/FreeBSD Centrino(TM) + Laptop</name> + <url>http://www.e-consultancy.com/newsfeatures/153803/eracks-announces-linux-centrino-tm-laptop.html</url> + <site-name>e-consultancy</site-name> + <site-url>http://www.e-consultancy.com/</site-url> + <date>30 December 2003</date> + <author>eRacks Press Release</author> + <p>eRacks Open Source Systems announces a Centrino(TM) based + laptop that features FreeBSD as a supported OS.</p> + </story> + + <story> + <name>Computing Clusters</name> + <url>http://www.g4techtv.com/feature.aspx?article_key=15807</url> + <site-name>G4TechTV</site-name> + <site-url>http://www.g4techtv.com/</site-url> + <date>17 December 2003</date> + <author>Leo Laporte and Roman Loyola</author> + <p>Matt Olander shows how to build a FreeBSD-based cluster.</p> + </story> + + <story> + <name>The FreeBSD Operating System 10 Year Anniversary Celebration: Silicon Valley is Alive and Kicking!</name> + <url>http://www.emediawire.com/releases/2003/12/emw93099.htm</url> + <site-name>eMediaWire</site-name> + <site-url>http://www.emediawire.com/</site-url> + <date>08 December 2003</date> + <author>Matt Olander</author> + <p>The offmyserver.com press release about the FreeBSD 10 year + anniversary party.</p> + </story> + + <story> + <name>Desktop FreeBSD Part 1: Installation</name> + <url>http://www.ofb.biz/modules.php?name=News&file=article&sid=272</url> + <site-name>Open For Business</site-name> + <site-url>http://www.ofb.biz/</site-url> + <date>02 December 2003</date> + <author>Ed Hurst</author> + <p>In this first part of a series of introductory articles, + the author shows how to use the FreeBSD installer.</p> + </story> + + <story> + <name>Using SNMP and RRDTool on FreeBSD</name> + <url>http://silverwraith.com/papers/freebsd-snmp.php</url> + <site-name>Silverwraith.com</site-name> + <site-url>http://silverwraith.com/</site-url> + <date>December 2003</date> + <author>Avleen Vig</author> + <p>A guide to generating server statistics for FreeBSD 4 and + 5.</p> + </story> + </month> + + <month> + <name>11</name> + + <story> + <name>Ten Years of FreeBSD: Anniversary Party a Success</name> + <url>http://www.osnews.com/story.php?news_id=5224</url> + <site-name>OSNews</site-name> + <site-url>http://www.osnews.com</site-url> + <date>25 November 2003</date> + <author>Eugenia Loli-Queru</author> + <p>A quick report about the evening including some pictures.</p> + </story> + + <story> + <name>Interview: AUUG's Greg Lehey</name> + <url>http://www.linuxworld.com.au/pp.php?id=337297289&fp=2&fpid=1</url> + <site-name>linuxworld.com.au</site-name> + <site-url>http://linuxworld.com.au/</site-url> + <date>24 November 2003</date> + <author>Howard Dahdah</author> + <p>An interview with FreeBSD developer Greg Lehey.</p> + </story> + + <story> + <name>From Linux to FreeBSD: A FreeBSD Review</name> + <url>http://www.osnews.com/story.php?news_id=5106</url> + <site-name>OSNews</site-name> + <site-url>http://www.osnews.com</site-url> + <date>11 November 2003</date> + <author>Gabe Yoder</author> + <p>The author quickly reviews FreeBSD 4.8 and compares it with + GNU/Linux.</p> + </story> + + <story> + <name>Printing for the Impatient</name> + <url>http://www.onlamp.com/lpt/a/4303</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com</site-url> + <date>06 November 2003</date> + <author>Michael Lucas</author> + <p>The author gives detailed instructions on how to + use Apsfilter for printing.</p> + </story> + + <story> + <name>One User's Thoughts on FreeBSD 4.9</name> + <url>http://www.osnews.com/story.php?news_id=5046</url> + <site-name>OSNews</site-name> + <site-url>http://www.osnews.com/</site-url> + <date>05 November 2003</date> + <author>Corey Holcomb-Hockin</author> + <p>The author reviews FreeBSD 4.9, describes how to upgrade + to the security and bug fixes branch, and how to build a + custom kernel.</p> + </story> + + <story> + <name>Improving User Passwords with apg</name> + <url>http://www.onlamp.com/lpt/a/4298</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>01 November 2003</date> + <author>Dru Lavigne</author> + <p>The author explains how to improve your password policy with + auto-generated passwords.</p> + </story> + </month> + + <month> + <name>10</name> + <story> + <name>FreeBSD Fills In The Blanks With v4.9</name> + <url>http://siliconvalley.internet.com/news/print.php/3101631</url> + <site-name>siliconvalley.internet.com</site-name> + <site-url>http://siliconvalley.internet.com/</site-url> + <date>30 October 2003</date> + <author>Michael Singer</author> + <p>The author gives a short summary on FreeBSD 4.9-RELEASE.</p> + </story> + + <story> + <name>FreeBSD 5.1</name> + <url>http://www.thejemreport.com/software/freebsd51.php</url> + <site-name>The Jem Report</site-name> + <site-url>http://www.thejemreport.com/</site-url> + <date>17 October 2003</date> + <author>Jem Matzan</author> + <p>The author reviews FreeBSD 5.1-RELEASE, and compares it with GNU/Linux.</p> + </story> + + <story> + <name>Build a Dynamic Web Serving Platform with FreeBSD</name> + <url>http://www.devx.com/opensource/Article/17534/1763/page/1</url> + <site-name>DevX.com</site-name> + <site-url>http://www.devx.com/</site-url> + <date>16 October 2003</date> + <author>Gregory L. Magnusson</author> + <p>A description on how to build Apache with MySQL and PHP support on + FreeBSD.</p> + </story> + + <story> + <name>Babe in the Woods: A Linux User Migrates to FreeBSD</name> + <url>http://www.ofb.biz/modules.php?name=News&file=print&sid=267</url> + <site-name>Open For Business</site-name> + <site-url>http://www.ofb.biz/</site-url> + <date>09 October 2003</date> + <author>Ed Hurst</author> + <p>The author describes his experience migrating from Linux to + FreeBSD.</p> + </story> + + <story> + <name>An Automated Binary Security Update System for FreeBSD</name> + <url>http://www.daemonology.net/freebsd-update/</url> + <site-name>Daemonology.net</site-name> + <site-url>http://www.daemonology.net/</site-url> + <date>09 October 2003</date> + <author>Colin Percival</author> + <p>In his paper, the author describes an automated system for building + and distributing binary security updates for FreeBSD.</p> + </story> + + <story> + <name>Netcraft: BT Most Reliable Hosting Site in September</name> + <url>http://thewhir.com/marketwatch/net100703.cfm</url> + <site-name>theWHIR</site-name> + <site-url>http://thewhir.com/</site-url> + <date>07 October 2003</date> + <author>theWHIR Web Team</author> + <p>Netcraft's latest survey reveals that seven out of the top thirteen + most reliable web hosting company sites in september ran FreeBSD.</p> + </story> + + <story> + <name>Working With ACLs in FreeBSD 5.X</name> + <url>http://ezine.daemonnews.org/200310/acl.html</url> + <site-name>DaemonNews</site-name> + <site-url>http://www.daemonnews.org/</site-url> + <date>06 October 2003</date> + <author>Grzegorz Czaplinski</author> + <p>The author explains how to create and configure unique access + permissions on files and directories using Access Control Lists (ACLs).</p> + </story> + + <story> + <name>Build your own FreeBSD Segway clone</name> + <url>http://www.theinquirer.net/default.aspx?article=11891</url> + <site-name>The Inquirer</site-name> + <site-url>http://www.theinquirer.net</site-url> + <date>02 October 2003</date> + <author>Adamson Rust</author> + <p>Trevor Blackwell has built his own FreeBSD powered Segway clone. + Read on for a closer description.</p> + </story> + </month> + + <month> + <name>9</name> + + <story> + <name>Cleaning and Customizing Your Ports</name> + <url>http://www.onlamp.com/lpt/a/4165</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>18 September 2003</date> + <author>Dru Lavigne</author> + <p>The author describes how to clean the FreeBSD ports tree + and how to customize the ports build options with + portupgrade tools.</p> + </story> + + <story> + <name>FreeBSD vs. Linux on TechTV! The OffMyServer OS Shootout</name> + <url>http://www.offmyserver.com/cgi-bin/store/news/techtv_090303.html</url> + <site-name>eMediaWire</site-name> + <site-url>http://www.emediawire.com/</site-url> + <date>05 September 2003</date> + <author>Matt Olander</author> + <p>This article describes how FreeBSD stacked up against Linux on TechTV's + latest The Screen Savers show.</p> + </story> + + <story> + <name>FreeBSD Jails</name> + <url>http://www.onlamp.com/lpt/a/4139</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>04 September 2003</date> + <author>Mike DeGraw-Bertsch</author> + <p>In this article the author explains how to set up and configure + Jails on FreeBSD.</p> + </story> + </month> + + <month> + <name>8</name> + + <story> + <name>Portupgrade</name> + <url>http://www.onlamp.com/lpt/a/4111</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>28 August 2003</date> + <author>Dru Lavigne</author> + <p>The author describes how to install and use portupgrade to + upgrade installed applications on a FreeBSD system.</p> + </story> + + <story> + <name>FreeBSD Serves Up Java JDK</name> + <url>http://siliconvalley.internet.com/news/article.php/3068481</url> + <site-name>siliconvalley.internet.com</site-name> + <site-url>http://siliconvalley.internet.com</site-url> + <date>26 August 2003</date> + <author>Michael Singer</author> + <p>The author talks about the benefits, native Java support has for FreeBSD.</p> + </story> + + <story> + <name>FreeBSD Access Control Lists</name> + <url>http://www.onlamp.com/lpt/a/4053</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>14 August 2003</date> + <author>Daniel Harris</author> + <p>The author describes how to use Access Control Lists, one of + FreeBSD 5.X new functionalities.</p> + </story> + + <story> + <name>Ports Tricks</name> + <url>http://www.onlamp.com/lpt/a/4057</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>07 August 2003</date> + <author>Dru Lavigne</author> + <p>In this edition of the FreeBSD Basics column, Dru Lavigne demonstrates + her favourite ports tricks.</p> + </story> + </month> + + <month> + <name>7</name> + + <story> + <name>Comparing Server OSes</name> + <url>http://www.thejemreport.com/articles/sco.htm</url> + <site-name>The Jem Report</site-name> + <site-url>http://www.thejemreport.com/</site-url> + <date>25 July 2003</date> + <author>Jem Matzan</author> + <p>A comparative survey of a number of free and proprietary server OSes. The + article strongly recommends the BSD family of OSes on account of their quality.</p> + </story> + + <story> + <name>Why Users Choose BSD Over Linux Or Commercial Software</name> + <url>http://www.internetweek.com/story/showArticle.jhtml?articleID=12800936</url> + <site-name>Internet Week</site-name> + <site-url>http://www.internetweek.com/</site-url> + <date>18 July 2003</date> + <author>Ean Kingston</author> + <p>The author recommends FreeBSD, highlighting its license, + simplicity, stability, and the myriad of supported + applications.</p> + </story> + + <story> + <name>Nearly 2 Million Active Sites running FreeBSD</name> + <url>http://news.netcraft.com/archives/2003/07/12/nearly_2_million_active_sites_running_freebsd.html</url> + <site-name>Netcraft</site-name> + <site-url>http://www.netcraft.com/</site-url> + <date>12 July 2003</date> + <author>Mike Prettejohn</author> + <p>The number of sites running FreeBSD is steadily growing. Netcraft + provides statistics and reasons.</p> + </story> + + <story> + <name>Top providers running FreeBSD: Netcraft</name> + <url>http://www.theage.com.au/articles/2003/07/10/1057783256883.html</url> + <site-name>The Age</site-name> + <site-url>http://www.theage.com.au/</site-url> + <date>10 July 2003</date> + <author>their online staff</author> + <p>A report from Netcraft states that five of the top 10 hosting providers + in the world are running the FreeBSD operating system.</p> + </story> + + <story> + <name>FreeBSD 5.1 Shows Handy New Features</name> + <url>http://www.eweek.com/article2/0,3959,1185897,00.asp</url> + <site-name>EWeek</site-name> + <site-url>http://www.eweek.com/</site-url> + <date>07 July 2003</date> + <author>Jason Brooks</author> + <p>Summary of new features in the FreeBSD 5.X branch, including + new jail management facilities.</p> + </story> + + </month> + + <month> + <name>6</name> + + <story> + <name>Advanced FreeBSD Installation Issues</name> + <url>http://www.informit.com/content/index.asp?product_id=%7B7309E848-0A1E-475A-A1CD-17B5462B1564%7D&062903</url> + <site-name>InformIT.com</site-name> + <site-url>http://www.informit.com</site-url> + <date>27 June 2003</date> + <author>Brian Tiemann, Michael Urban</author> + <p>An in-depth tutorial on installing FreeBSD.</p> + </story> + + <story> + <name>Is it time for BSD?</name> + <url>http://www.eweek.com/article2/0,3959,1135078,00.asp</url> + <site-name>EWeek</site-name> + <site-url>http://www.eweek.com/</site-url> + <date>23 June 2003</date> + <author>Jim Rapoza</author> + <p>The author recommends the BSD family of operating systems + for open-source IT projects.</p> + </story> + + <story> + <name>Basic Security Measures for FreeBSD</name> + <url>http://www.net-security.org/article.php?id=511</url> + <site-name>Net Security</site-name> + <site-url>http://www.net-security.org/</site-url> + <date>19 June 2003</date> + <author>Szekely Ervin</author> + <p>Describes the basic security measures that should be + applied to a FreeBSD 4.X workstation.</p> + </story> + + <story> + <name>New distribution point for FreeBSD</name> + <url>http://www.theage.com.au/articles/2003/06/19/1055828413910.html</url> + <site-name>The Age</site-name> + <site-url>http://www.theage.com.au/</site-url> + <date>18 June 2003</date> + <author>their online staff</author> + <p>Three companies pool together to operate a new mirror + of the FreeBSD website and CVSup services.</p> + </story> + + <story> + <name>FreeBSD Foundation Unleashes 5.1</name> + <url>http://www.internetnews.com/dev-news/article.php/2218991</url> + <site-name>Internetnews</site-name> + <site-url>http://www.internetnews.com/</site-url> + <date>09 June 2003</date> + <author>Thor Olavsrud</author> + <p>An article briefly covering the FreeBSD 5.1 release.</p> + </story> + </month> + + <month> + <name>5</name> + + <story> + <name>FreeBSD support for AMD64 on the way</name> + <url>http://www.theinquirer.net/?article=9383</url> + + <site-name>The Inquirer</site-name> + <site-url>http://www.theinquirer.net</site-url> + <date>08 May 2003</date> + <author>Arron Rouse</author> + + <p>A short article about upcoming support for the AMD64 + platform in FreeBSD 5.x.</p> + </story> + + <story> + <name>Beyond Linux</name> + <url>http://www.infoworld.com/article/03/05/23/21OPconnection_1.html</url> + <site-name>InfoWorld</site-name> + <site-url>http://www.infoworld.com</site-url> + <date>03 May 2003</date> + <author>Chad Dickerson</author> + + <p>The author recommends FreeBSD, praising its TCP/IP stack and + its liberal license.</p> + </story> + + </month> + + <month> + <name>4</name> + + <story> + <name>Focus on FreeBSD: Interview with the Core Team</name> + <url>http://www.osnews.com/story.php?news_id=3415</url> + + <site-name>OS News</site-name> + <site-url>http://www.osnews.com/</site-url> + <date>28 April 2003</date> + <author>Eugenia Loli-Queru</author> + + <p>OS News features an in-depth interview with Wes Peters, + Greg Lehey, Warner M. Losh of the FreeBSD core team + and developer Scott Long. Topics include Java support, + the Linux competition, and the FreeBSD 5.x branch.</p> + </story> + + </month> + + <month> + <name>3</name> + + <story> + <name>FreeBSD featured on TechTV</name> + <url>http://www.offmyserver.com/cgi-bin/oms/news/techtv_031403.html</url> + + <site-name>offmyserver.com</site-name> + <site-url>http://www.techtv.com/</site-url> + <date>14 March 2003</date> + <author>Offmyserver Press Release</author> + + <p>FreeBSD core-team member Murray Stokely appeared on TechTV + with Matt Olander from Offmyserver to talk about FreeBSD and + perform an installation on live television. The press + release includes a link to a RealVideo stream of the + episode.</p> + </story> + + </month> + + <month> + <name>2</name> + + <story> + <name>FreeBSD 5.0 looks to the enterprise</name> + <url>http://www.linuxworld.com.au/news.php3?nid=2187&tid=1</url> + <site-name>linuxworld.com.au</site-name> + <site-url>http://linuxworld.com.au/</site-url> + <date>04 February 2003</date> + <author>Howard Dahdah</author> + <p>Linuxworld looks at the capabilities of FreeBSD 5.0 as an + enterprise operating system and interviews FreeBSD developer + Scott Long.</p> + </story> + + </month> + + <month> + <name>1</name> + + <story> + <name>Odds and Ends</name> + <url>http://www.onlamp.com/pub/a/bsd/2003/01/23/FreeBSD_Basics.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>23 January 2003</date> + <author>Dru Lavigne</author> + <p>Dru Lavigne on easy ways for a new user to get familiar with FreeBSD. + </p> + </story> + + <story> + <name>FreeBSD 5.0 Unleashed</name> + <url>http://www.internetnews.com/dev-news/article.php/1571431</url> + <site-name>InternetNews</site-name> + <site-url>http://www.internetnews.com/</site-url> + <date>17 January 2003</date> + <author>Michael Singer</author> + <p>Internetnews.com reviews FreeBSD 5.0 and interviews + FreeBSD's release engineering team member, Murray Stokely.</p> + </story> + + </month> + </year> +</press> diff --git a/en_US.ISO8859-1/htdocs/news/2004/Makefile b/en_US.ISO8859-1/htdocs/news/2004/Makefile new file mode 100644 index 0000000000..5965ae5945 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2004/Makefile @@ -0,0 +1,16 @@ +# $FreeBSD$ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +XMLDOCS+= index:${XSL_NEWS_NEWSFLASH_OLD}:news.xml: +DEPENDSET.index=transtable news + +XMLDOCS+= press:${XSL_NEWS_PRESS_OLD}:: +DEPENDSET.press=transtable press + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/news/2004/news.xml b/en_US.ISO8859-1/htdocs/news/2004/news.xml new file mode 100644 index 0000000000..03643e5aa8 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2004/news.xml @@ -0,0 +1,733 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE news PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for News//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/news.dtd"> + +<!-- Simple schema for FreeBSD Project news. + + Divide time in to <year>, <month>, and <day> elements, each of which + has a <name>. + + each <day> element contains one or more <event> elements. + + Each <event> contains an optional <title>, and then a <p>. <p> elements + can contain <a> anchors. + + Use the <title> element if the <p> content is lengthy. When generating + synopses of this information (e.g., for syndication using RDF files), + the contents of <title> will be preferred over <p>. +--> + +<news> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD$ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2004</name> + + <month> + <name>12</name> + + <day> + <name>28</name> + + <event> + <title>Mozilla approves FreeBSD's thunderbird and firefox ports</title> + + <p>The <a href="http://www.mozilla.org/foundation/licensing.html">Mozilla License Team</a> + has <a href="http://people.freebsd.org/~ahze/firefox_thunderbird-approved.txt">granted permission</a> + to the <a href="/gnome/index.html">FreeBSD Gnome Team</a> + for use of the Firefox and Thunderbird names, + official icons, and permission to do + officially branded builds.</p> + </event> + <event> + <p>New committer: <a href="mailto:sah@FreeBSD.org">Sam Hopkins</a> (src)</p> + </event> + </day> + + <day> + <name>23</name> + + <event> + <title>FreeBSD Foundation Quarterly Newsletter Published</title> + + <p>The FreeBSD Foundation has published its <a + href="http://www.freebsdfoundation.org/press/20041221-newsletter.shtml">Quarterly + Newsletter</a>, which includes a call for donations so + the Foundation can keep its non-profit public charity + 501(c)3 status.</p> + </event> + </day> + + <day> + <name>18</name> + + <event> + <title>FreeBSD 4.11 RC1 Available</title> + + <p>The first Release Candidate for FreeBSD 4.11 has been + made available. Please see the full announcement on + the FreeBSD-STABLE mailing list <a + href="http://docs.freebsd.org/cgi/getmsg.cgi?fetch=495816+0+archive/2004/freebsd-stable/20041219.freebsd-stable">here</a>. + The full 4.11 release schedule is <a + href="&base;/releases/4.11R/schedule.html"> + here</a>.</p> + </event> + </day> + + <day> + <name>13</name> + + <event> + <p>New committer: <a + href="mailto:niels@FreeBSD.org">Niels Heinen</a> + (ports)</p> + </event> + </day> + + <day> + <name>6</name> + + <event> + <p>The <a href="http://www.FreeSBIE.org/">FreeSBIE</a> 1.1 FreeBSD + Live CD is released -- see the <a href="http://www.freesbie.org/doc/1.1/ANNOUNCE.txt">release + announcement</a> for details.</p> + </event> + + <event> + <p>New committer: <a + href="mailto:girgen@FreeBSD.org">Palle Girgensohn</a> + (ports)</p> + </event> + </day> + + <day> + <name>2</name> + + <event> + <title>FreeBSD 4.11 release schedule announced</title> + + <p>The schedule for the FreeBSD 4.11 Release has been + announced, with a target release date of January 24th, + 2005. The full schedule is <a + href="http://www.freebsd.org/releases/4.11R/schedule.html"> + here</a>.</p> + </event> + </day> + + <day> + <name>1</name> + + <event> + <p>New committer: <a + href="mailto:dumbbell@FreeBSD.org">Jean-Sébastien Pédron</a> + (src)</p> + </event> + </day> + </month> + + <month> + <name>11</name> + + <day> + <name>27</name> + + <event> + <title>FreeBSD trademark transferred to Foundation</title> + + <p>The 'FreeBSD' trademark, which was originally granted + to Walnut Creek CDROM (now <a + href="http://www.freebsdmall.com">FreeBSD Mall, + Inc.</a>) in 1996, has been transferred to the <a + href="http://www.freebsdfoundation.org">FreeBSD + Foundation</a>.</p> + </event> + </day> + + <day> + <name>19</name> + + <event> + <p>New committer: <a + href="mailto:carvay@FreeBSD.org">Vicente Carrasco</a> + (doc)</p> + </event> + </day> + + <day> + <name>11</name> + + <event> + <p>New committer: <a + href="mailto:jkois@FreeBSD.org">Johann Kois</a> + (doc)</p> + </event> + </day> + + <day> + <name>7</name> + + <event> + <title>GNOME 2.8.1 released for FreeBSD</title> + + <p>GNOME 2.8.1 was merged into the ports tree + following the release of FreeBSD 5.3. See + the <a href="/gnome/index.html">FreeBSD GNOME + Homepage</a> for more details as well + as upgrade instructions.</p> + </event> + </day> + + <day> + <name>6</name> + + <event> + <title>FreeBSD 5.3-RELEASE is Now Available</title> + + <p><a href="&base;/releases/5.3R/announce.html">FreeBSD + 5.3-RELEASE</a> has been released. Please check the <a + href="&base;/releases/5.3R/errata.html">release errata</a> + before installation for any late-breaking news and/or + issues with 5.3. The <a + href="&base;/releases/index.html">Release Information</a> + page has more information about FreeBSD releases.</p> + + </event> + </day> + </month> + + <month> + <name>10</name> + + <day> + <name>31</name> + + <event> + <title>FreeBSD 5.3-RC2 released</title> + + <p>The FreeBSD Release Engineering Team is proud to + announce the availability of FreeBSD 5.3-RC2. Two + critical issues came up during RC1 testing and it is + felt the fixes warrant one more RC so they receive + widespread testing. If no more show-stopper problems + are found this will be the last test release done before + 5.3-RELEASE. Please see the full announcement on + FreeBSD-CURRENT <a + href="http://docs.freebsd.org/cgi/getmsg.cgi?fetch=219950+0+current/freebsd-current">here</a>.</p> + </event> + </day> + + <day> + <name>29</name> + + <event> + <p>New committer: <a + href="mailto:ahze@FreeBSD.org">Michael Johnson</a> (ports)</p> + </event> + </day> + + <day> + <name>16</name> + + <event> + <p>New committer: <a + href="mailto:remko@FreeBSD.org">Remko Lodder</a> (doc)</p> + </event> + </day> + + <day> + <name>12</name> + <event> + <p>New committer: <a + href="mailto:gnn@FreeBSD.org">George V. Neville-Neil</a> + (src)</p> + </event> + </day> + + <day> + <name>8</name> + <event> + <p>New committer: <a + href="mailto:ups@FreeBSD.org">Stephan Uphoff</a> + (src)</p> + </event> + </day> + + </month> + + <month> + <name>9</name> + + <day> + <name>15</name> + <event> + <p>New committer: <a + href="mailto:kwm@FreeBSD.org">Koop Mast</a> + (ports)</p> + </event> + + <event> + <p>New committer: <a + href="mailto:delphij@FreeBSD.org">Xin Li</a> + (src, doc)</p> + </event> + </day> + + </month> + + <month> + <name>8</name> + + <day> + <name>20</name> + <event> + <p>New committer: <a + href="mailto:danfe@FreeBSD.org">Alexey Dokuchaev</a> + (ports)</p> + </event> + </day> + + <day> + <name>19</name> + <event> + <p>New committer: <a + href="mailto:lesi@FreeBSD.org">Dejan Lesjak</a> + (ports)</p> + </event> + </day> + + <day> + <name>18</name> + <event> + <p>New committer: <a + href="mailto:clsung@FreeBSD.org">Cheng-Lung Sung</a> + (ports)</p> + </event> + </day> + + <day> + <name>10</name> + <event> + <p>New committer: <a + href="mailto:marck@FreeBSD.org">Dmitry Morozovsky</a> + (doc)</p> + </event> + </day> + + <day> + <name>5</name> + <event> + <p>New committer: <a + href="mailto:hq@FreeBSD.org">Herve Quiroz</a> + (ports)</p> + </event> + </day> + + <day> + <name>2</name> + <event> + <p>New committer: <a + href="mailto:yongari@FreeBSD.org">Pyun YongHyeon</a> + (src)</p> + </event> + </day> + + </month> + + <month> + <name>7</name> + + <day> + <name>27</name> + <event> + <p>New committer: <a + href="mailto:bz@FreeBSD.org">Bjoern A. Zeeb</a> + (src)</p> + </event> + </day> + + <day> + <name>26</name> + <event> + <title>May 2004 - June 2004 Status Report</title> + + <p>The May-June status report is now available; see the <a + href="&base;/news/status/status.html">status reports Web + page</a> for more information.</p> </event> + </day> + + <day> + <name>24</name> + <event> + <p>New committer: <a + href="mailto:ssouhlal@FreeBSD.org">Suleiman Souhlal</a> + (PowerPC)</p> + </event> + </day> + + <day> + <name>23</name> + <event> + <title>FreeBSD switches to X.Org</title> + <p>FreeBSD-CURRENT now ships with X.Org's X Window System per default, + though XFree86 is still supported. For more information on how to + upgrade for -CURRENT and -STABLE, take + a look at this + <a href="http://lists.freebsd.org/pipermail/freebsd-current/2004-July/032267.html"> + HEADS UP</a>.</p> + </event> + </day> + + <day> + <name>14</name> + <event> + <p>New committer: <a + href="mailto:glebius@FreeBSD.org">Gleb Smirnoff</a> + (src)</p> + </event> + </day> + + <day> + <name>7</name> + <event> + <p>New committer: <a + href="mailto:sem@FreeBSD.org">Sergey Matveychuk</a> + (ports)</p> + </event> + </day> + + </month> + + <month> + <name>5</name> + + <day> + <name>30</name> + <event> + <p>New committer: <a + href="mailto:lth@FreeBSD.org">Lars Thegler</a> + (ports)</p> + </event> + </day> + + <day> + <name>27</name> + <event> + <title>FreeBSD 4.10-RELEASE is Now Available</title> + + <p><a href="&base;/releases/4.10R/announce.html">FreeBSD + 4.10-RELEASE</a> has been released. Please check the <a + href="&base;/releases/4.10R/errata.html">release errata</a> + before installation for any late-breaking news and/or + issues with 4.10. The <a + href="&base;/releases/index.html">Release Information</a> + page has more information about FreeBSD releases.</p> + </event> + </day> + + <day> + <name>23</name> + <event> + <p>New committer: <a + href="mailto:metal@FreeBSD.org">Koichi Suzuki</a> + (doc)</p> + </event> + </day> + + <day> + <name>15</name> + <event> + <title>March 2004 - April 2004 Status Report</title> + + <p>The March-April status report is now available; see the + <a href="&base;/news/status/status.html">status reports Web page</a> + for more information.</p> + </event> + </day> + + <day> + <name>4</name> + <event> + <p>New committer: <a + href="mailto:csjp@FreeBSD.org">Christian S.J. Peron</a> + (src)</p> + </event> + <event> + <p>New committer: <a + href="mailto:stefanf@FreeBSD.org">Stefan Farfeleder</a> + (src)</p> + </event> + </day> + + </month> + + <month> + <name>4</name> + + <day> + <name>30</name> + <event> + <p>New committer: <a + href="mailto:mezz@FreeBSD.org">Jeremy Messenger</a> + (ports)</p> + </event> + </day> + + <day> + <name>19</name> + <event> + <p>New committer: <a + href="mailto:tackerman@FreeBSD.org">Tony Ackerman</a> + (src)</p> + </event> + </day> + + <day> + <name>17</name> + <event> + <p>New committer: <a + href="mailto:marius@FreeBSD.org">Marius Strobl</a> + (src)</p> + </event> + </day> + + <day> + <name>5</name> + <event> + <p>New committer: <a + href="mailto:dhartmei@FreeBSD.org">Daniel Hartmeier</a> + (src)</p> + </event> + </day> + + </month> + + <month> + <name>3</name> + + <day> + <name>29</name> + <event> + <p>New committer: <a + href="mailto:niklas@FreeBSD.org">Niklas J. Saers</a> + (doc)</p> + </event> + </day> + + + <day> + <name>25</name> + <event> + <title>Removal of Gallery</title> + + <p>Because of the hard maintenance and low benefit the + <a href="../gallery/">gallery</a> + pages bring to the Project and the listed websites, + it has been decided to spend the time working on other + stuff related to FreeBSD than these pages. The gallery + will be removed in two weeks, no further submissions will + be processed. However, this has no influence on the + <a href="../commercial/">Commercial Gallery</a>.</p> + </event> + </day> + + <day> + <name>18</name> + <event> + <p>New committer: <a + href="mailto:marks@FreeBSD.org">Mark Santcroos</a> + (src)</p> + </event> + </day> + + <day> + <name>17</name> + <event> + <title>January 2004 - February 2004 Status Report</title> + + <p>The January-February status report is now available; see the + <a href="&base;/news/status/status.html">status reports Web page</a> + for more information.</p> + </event> + </day> + <day> + <name>13</name> + <event> + <p>New committer: <a + href="mailto:thierry@FreeBSD.org">Thierry Thomas</a> + (ports)</p> + </event> + </day> + + <day> + <name>10</name> + <event> + <p>New committer: <a + href="mailto:vs@FreeBSD.org">Volker Stolz</a> + (ports)</p> + </event> + </day> + + <day> + <name>9</name> + <event> + <p>New committer: <a + href="mailto:peadar@FreeBSD.org">Peter Edwards</a> + (src)</p> + </event> + </day> + + </month> + + <month> + <name>2</name> + + <day> + <name>26</name> + <event> + <p>New committer: <a + href="mailto:vkashyap@FreeBSD.org">Vinod Kashyap</a> + (src)</p> + </event> + </day> + + <day> + <name>25</name> + <event> + <title>FreeBSD 5.2.1-RELEASE is Now Available</title> + + <p><a href="&base;/releases/5.2.1R/announce.html">FreeBSD + 5.2.1-RELEASE</a> has been released. Please check the <a + href="&base;/releases/5.2.1R/errata.html">release errata</a> + before installation for any late-breaking news and/or + issues with 5.2.1. The <a + href="&base;/releases/index.html">Release Information</a> + page has more information about FreeBSD releases.</p> + + </event> + </day> + + <day> + <name>22</name> + <event> + <p>New committer: <a + href="mailto:markus@FreeBSD.org">Markus Brüffer</a> + (Ports)</p> + </event> + </day> + + <day> + <name>17</name> + <event> + <p>New committer: <a + href="mailto:rees@FreeBSD.org">Jim Rees</a> + (src)</p> + </event> + </day> + + <day> + <name>15</name> + <event> + <p>Core member resigned: <a + href="mailto:grog@FreeBSD.org">Greg Lehey</a> </p> + </event> + </day> + + <day> + <name>10</name> + <event> + <p>New committer: <a + href="mailto:mlaier@FreeBSD.org">Max Laier</a> + (src)</p> + </event> + </day> + + <day> + <name>2</name> + <event> + <p>New committer: <a + href="mailto:le@FreeBSD.org">Lukas Ertl</a> + (src)</p> + </event> + + <event> + <p>New committer: <a + href="mailto:pjd@FreeBSD.org">Pawel Jakub Dawidek</a> + (src)</p> + </event> + </day> + + </month> + + <month> + <name>1</name> + + <day> + <name>28</name> + + <event> + <title>October 2003 - December 2003 Status Report</title> + + <p>The October-December status report is now available; see the + <a href="&base;/news/status/status.html">status reports Web page</a> + for more information.</p> + </event> + </day> + + <day> + <name>21</name> + <event> + <p>New committer: <a + href="mailto:philip@FreeBSD.org">Philip Paeps</a> + (src)</p> + </event> + + <event> + <p>New committer: <a + href="mailto:cperciva@FreeBSD.org">Colin Percival</a> + (src)</p> + </event> + </day> + + <day> + <name>15</name> + <event> + <p>New committer: <a + href="mailto:josef@FreeBSD.org">Josef El-Rayes</a> + (docs)</p> + </event> + </day> + + <day> + <name>12</name> + <event> + <title>FreeBSD 5.2-RELEASE is Now Available</title> + + <p><a href="&base;/releases/5.2R/announce.html">FreeBSD + 5.2-RELEASE</a> has been released. Please check the <a + href="&base;/releases/5.2R/errata.html">release errata</a> + before installation for any late-breaking news and/or + issues with 5.2. The <a + href="&base;/releases/index.html">Release Information</a> + page has more information about FreeBSD releases.</p> + + </event> + </day> + + <day> + <name>4</name> + <event> + <p>New committer: <a + href="mailto:viny@FreeBSD.org">Vincent Tougait</a> + (Documentation Project)</p> + </event> + </day> + + </month> + + </year> +</news> + diff --git a/en_US.ISO8859-1/htdocs/news/2004/press.xml b/en_US.ISO8859-1/htdocs/news/2004/press.xml new file mode 100644 index 0000000000..29c7efbed4 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2004/press.xml @@ -0,0 +1,414 @@ +<press> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD$ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2004</name> + + <month> + <name>11</name> + + <story> + <name>Deep study: The world's safest computing + environment</name> + <url>http://www.mi2g.com/cgi/mi2g/frameset.php?pageid=http%3A//www.mi2g.com/cgi/mi2g/press/021104.php</url> + <site-name>mi2g</site-name> + <site-url>http://www.mi2g.com/</site-url> + <date>2 November 2004</date> + <author>mi2g News Alert</author> + <p>A study by a London-based computer security firm reveals + that the open-source BSD operating systems and Apple's Mac + OS X are the most secure popular operating systems on the + Internet today.</p> + </story> + </month> + + <month> + <name>9</name> + + <story> + <name>Building Diskless Clients with FreeBSD 5.2</name> + <url>http://www.onlamp.com/pub/a/bsd/2004/09/30/diskless_clients.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>30 September 2004</date> + <author>Mikhail Zakharov</author> + <p>How to build diskless clients with FreeBSD Netboot server.</p> + </story> + + <story> + <name>Building a BSD Netboot Server</name> + <url>http://www.onlamp.com/pub/a/bsd/2004/09/09/diskless_server.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>09 September 2004</date> + <author>Mikhail Zakharov</author> + <p>How to configure a FreeBSD 5.2.1 server to support + diskless clients.</p> + </story> + </month> + + <month> + <name>8</name> + + <story> + <name>FreeBSD 5.3 beta is released</name> + <url>http://news.zdnet.co.uk/0,39020330,39164597,00.htm</url> + <site-name>ZDNet</site-name> + <site-url>http://www.zdnet.co.uk/</site-url> + <date>25 August 2004</date> + <author>Michael Parsons</author> + <p>A story about the FreeBSD 5.3 release cycle</p> + </story> + + <story> + <name>Desktop FreeBSD Part 5: Internet Mail Setup</name> + <url>http://www.ofb.biz/modules.php?name=News&file=article&sid=326</url> + <site-name>Open For Business</site-name> + <site-url>http://www.ofb.biz/</site-url> + <date>17 August 2004</date> + <author>Ed Hurst</author> + <p>Part five of this series of introductory articles describes + how to use FreeBSD for email purposes.</p> + </story> + + <story> + <name>Differentiating Among BSD Distros</name> + <url>http://www.serverwatch.com/tutorials/article.php/3393051</url> + <site-name>ServerWatch</site-name> + <site-url>http://www.serverwatch.com/</site-url> + <date>10 August 2004</date> + <author>Martin Brown</author> + <p>An article that compares and contrasts the four main BSD + variants.</p> + </story> + + <story> + <name>Desktop FreeBSD Part 4: Printing</name> + <url>http://www.ofb.biz/modules.php?name=News&file=article&sid=321</url> + <site-name>Open For Business</site-name> + <site-url>http://www.ofb.biz/</site-url> + <date>06 August 2004</date> + <author>Ed Hurst</author> + <p>Part four of this series of introductory articles covers the + installation and the configuration of Apsfilter on FreeBSD.</p> + </story> + + <story> + <name>Building Systems to be Shared Securely</name> + <url>http://www.acmqueue.org/modules.php?name=Content&pa=showpage&pid=170</url> + <site-name>ACM Queue</site-name> + <site-url>http://www.acmqueue.org/</site-url> + <date>August 2004</date> + <author>Poul-Henning Kamp, Robert Watson</author> + <p>Robert Watson and Poul-Henning Kamp write an article for + the ACM Queue magazine on FreeBSD's <tt>jail</tt> facility + and on the general concept of sharing and security from an + operating system architecture/design point of view.</p> + </story> + </month> + + <month> + <name>7</name> + + <story> + <name>FreeBSD milestone nears release</name> + <url>http://news.zdnet.co.uk/software/linuxunix/0,39020390,39162245,00.htm</url> + <site-name>ZDNet</site-name> + <site-url>http://www.zdnet.co.uk/</site-url> + <date>30 July 2004</date> + <author>Matt Loney</author> + <p>This article is about the upcoming FreeBSD 5.3 release.</p> + </story> + + <story> + <name>Local company develops FreeBSD-based radars</name> + <url>http://www.computerworld.com.au/index.php/id;1357495171;fp;16;fpid;0</url> + <site-name>Computerworld</site-name> + <site-url>http://www.computerworld.com.au/</site-url> + <date>26 July 2004</date> + <author>Rodney Gedda</author> + <p>Genesis Software builds FreeBSD-based radar systems.</p> + </story> + + <story> + <name>Linux servers stats reveal fall in Red Hat dominance</name> + <url>http://www.techworld.com/opsys/news/index.cfm?newsid=1908</url> + <site-name>Techworld</site-name> + <site-url>http://www.techworld.com/</site-url> + <date>13 July 2004</date> + <author>Matthew Broersma</author> + <p>An article mentioning FreeBSD's growth in the hosting market.</p> + </story> + + <story> + <name>Unix Printing Basics</name> + <url>http://www.onlamp.com/pub/a/bsd/2004/07/08/FreeBSD_Basics.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>08 July 2004</date> + <author>Dru Lavigne</author> + <p>This article explains printing with Unix, using FreeBSD as + an example.</p> + </story> + + <story> + <name>Building a Web Cluster with FreeSBIE</name> + <url>http://www.onlamp.com/pub/a/bsd/2004/07/01/freesbie.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>01 July 2004</date> + <author>Alexander Prohorenko</author> + <p>How to build a web services cluster using the FreeBSD based + FreeSBIE live CD image.</p> + </story> + + </month> + + <month> + <name>6</name> + + <story> + <name>Preventing Denial of Service Attacks</name> + <url>http://www.onlamp.com/pub/a/bsd/2004/06/24/anti_dos.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>24 June 2004</date> + <author>Avleen Vig</author> + <p>This article shows how to defend against denial of service attacks with + FreeBSD.</p> + </story> + + <story> + <name>Siberian coal mine digs out FreeBSD funding</name> + <url>http://news.zdnet.co.uk/software/developer/0,39020387,39158017,00.htm</url> + <site-name>ZDNet</site-name> + <site-url>http://www.zdnet.co.uk</site-url> + <date>18 June 2004</date> + <author>Matt Loney</author> + <p>A story about Poul-Henning Kamp's recent appeal for funds.</p> + </story> + + <story> + <name>FreeBSD, Stealth-Growth Open Source Project</name> + <url>http://www.internetnews.com/dev-news/article.php/3367381</url> + <site-name>Internetnews</site-name> + <site-url>http://www.internetnews.com/</site-url> + <date>11 June 2004</date> + <author>Sean Michael Kerner</author> + <p>This article tries to outline the reasons for FreeBSD's + growth over the last years.</p> + </story> + + <story> + <name>Desktop FreeBSD Part 3: Adding Software</name> + <url>http://www.ofb.biz/modules.php?name=News&file=article&sid=306</url> + <site-name>Open For Business</site-name> + <site-url>http://www.ofb.biz/</site-url> + <date>07 June 2004</date> + <author>Ed Hurst</author> + <p>Part three of this series of introductory articles covers the + installation of third party applications on FreeBSD.</p> + </story> + + <story> + <name>Nearly 2.5 Million Active Sites running FreeBSD</name> + <url>http://news.netcraft.com/archives/2004/06/07/nearly_25_million_active_sites_running_freebsd.html</url> + <site-name>Netcraft</site-name> + <site-url>http://www.netcraft.com/</site-url> + <date>07 June 2004</date> + <author>mandy</author> + <p>FreeBSD continues to grow in the web hosting market.</p> + </story> + + <story> + <name>IEEE and The Open Group Okay 'FreeBSD Project' to + Incorporate Material from the POSIX Standard</name> + <url>http://www.opengroup.org/press/01jun04.htm</url> + <site-name>The Open Group</site-name> + <site-url>http://www.opengroup.org/</site-url> + <date>01 June 2004</date> + <author>IEEE/Open Group press release</author> + <p>The IEEE and the Open Group allow the FreeBSD project to + incorporate material from a few of their published + standards.</p> + </story> + + <story> + <name>Build Your Own FreeBSD-powered Motorcycle</name> + <url>http://bike.owns.com/</url> + <site-name>BikeOwns</site-name> + <site-url>http://bike.owns.com/</site-url> + <date>June 2004</date> + <author>Ben</author> + <p>The description of a FreeBSD-powered motorcycle.</p> + </story> + </month> + + <month> + <name>5</name> + + <story> + <name>FreeBSD Networking Basics</name> + <url>http://www.onlamp.com/pub/a/bsd/2004/05/13/FreeBSD_Basics.html?page=2</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>13 May 2004</date> + <author>Dru Lavigne</author> + <p>Dru Lavigne explains how to connect a FreeBSD machine to + an existing network.</p> + </story> + + <story> + <name>Intel Labs' Natural Born Killer Technologies</name> + <url>http://www.eweek.com/article2/0,1759,1586655,00.asp</url> + <site-name>EWeek</site-name> + <site-url>http://www.eweek.com/</site-url> + <date>06 May 2004</date> + <author>Rob Enderle</author> + <p>An overview about the research projects in Intel's laboratories. + Some of the research is done using the FreeBSD operating system.</p> + </story> + + <story> + <name>Open Source to the Core</name> + <url>http://www.acmqueue.org/modules.php?name=Content&pa=showpage&pid=151</url> + <site-name>ACM Queue</site-name> + <site-url>http://www.acmqueue.org/</site-url> + <date>May 2004</date> + <author>Jordan Hubbard</author> + <p>Jordan Hubbard talks about FreeBSD in an article on using + open-source software in commercial products.</p> + </story> + + </month> + + <month> + <name>4</name> + + <story> + <name>FreeBSD - The Power to Serve</name> + <url>http://www.distrowatch.com/dwres.php?resource=review-freebsd</url> + <site-name>Distrowatch</site-name> + <site-url>http://www.distrowatch.com/</site-url> + <date>27 April 2004</date> + <author>Robert Storey</author> + <p>A review of FreeBSD 5.2.1, including a short overview of the history + of the BSDs and installation instructions.</p> + </story> + + <story> + <name>Mail Scanning With Exim And The Exiscan ACL</name> + <url>http://www.net-security.org/article.php?id=676</url> + <site-name>Help Net Security</site-name> + <site-url>http://www.net-security.org/</site-url> + <date>13 April 2004</date> + <author>Michael Oliveri</author> + <p>This article describes setting up Exim with the Exiscan-ACL + patch on FreeBSD.</p> + </story> + + <story> + <name>Most Reliable Hosting Providers during March</name> + <url>http://news.netcraft.com/archives/2004/04/04/most_reliable_hosting_providers_during_march.html</url> + <site-name>Netcraft</site-name> + <site-url>http://www.netcraft.com/</site-url> + <date>04 April 2004</date> + <author>mandy</author> + <p>Five of the ten most reliable hosting providers in March + were running FreeBSD. Read on for more information.</p> + </story> + + </month> + + <month> + <name>3</name> + + <story> + <name>FreeBSD 5.2.1 on SPARC64</name> + <url>http://www.osnews.com/story.php?news_id=6552</url> + <site-name>OS News</site-name> + <site-url>http://www.osnews.com/</site-url> + <date>31 March 2004</date> + <author>Tony Bourke</author> + <p>An article reviewing FreeBSD 5.2.1 on SPARC64 machines. + The author finds FreeBSD/SPARC64 to be a very complete, + useful and flexible server.</p> + </story> + + <story> + <name>The 64-bit Question: AMD64 vs. i386</name> + <url>http://www.thejemreport.com/modules.php?op=modload&name=News&file=article&sid=117&mode=thread&order=0&thold=0</url> + <site-name>The Jem Report</site-name> + <site-url>http://www.thejemreport.com/</site-url> + <date>15 March 2004</date> + <author>Valour</author> + <p>A comparison between FreeBSD 5.2.1's performance on + an AMD Athlon64 3200+ and on a Pentium4 3.2E.</p> + </story> + + <story> + <name>Experimental free Wi-Fi LAN gaining momentum in SF</name> + <url>http://www.newsforge.com/mobility/04/03/02/0023236.shtml</url> + <site-name>Newsforge</site-name> + <site-url>http://www.newsforge.com/</site-url> + <date>02 March 2004</date> + <author>Chris Preimesberger</author> + <p>An article about free wireless networks in San Francisco, + mentioning FreeBSD as one of the operating systems of choice.</p> + </story> + </month> + + <month> + <name>1</name> + + <story> + <name>Bacula: Cross-Platform Client-Server Backups</name> + <url>http://www.onlamp.com/pub/a/onlamp/2004/01/09/bacula.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>08 January 2004</date> + <author>Dan Langille</author> + <p>A guide on setting up and running the backup program Bacula on FreeBSD</p> + </story> + + <story> + <name>Simple FreeBSD installation yields functional desktop system</name> + <url>http://www.newsforge.com/os/04/01/05/211225.shtml?tid=8&tid=82&tid=94</url> + <site-name>Newsforge</site-name> + <site-url>http://www.newsforge.com/</site-url> + <date>07 January 2004</date> + <author>Terrell Prude, Jr.</author> + <p>A review of FreeBSD 5.1 as a desktop system.</p> + </story> + + <story> + <name>Desktop FreeBSD Part 2: Initial Setup</name> + <url>http://www.ofb.biz/modules.php?name=News&file=article&sid=282</url> + <site-name>Open For Business</site-name> + <site-url>http://www.ofb.biz/</site-url> + <date>03 January 2004</date> + <author>Ed Hurst</author> + <p>This is the second part of a series of introductory articles. + The author explains how to set up X and the postfix mail system.</p> + </story> + + <story> + <name>How is Open-Source affecting Software Development?</name> + <url>http://csdl.computer.org/comp/mags/so/2004/01/s1028.pdf</url> + <site-name>IEEE Computer Society</site-name> + <site-url>http://www.computer.org/</site-url> + <date>January 2004</date> + <author>Diomidis Spinellis, Clemens Sxyperski (Guest Editors)</author> + <p>This IEEE journal article looks at how the availability of + high-quality open-source software is affecting the way + software is developed. FreeBSD is one of the open-source + projects examined.</p> + </story> + + </month> + </year> +</press> diff --git a/en_US.ISO8859-1/htdocs/news/2005/Makefile b/en_US.ISO8859-1/htdocs/news/2005/Makefile new file mode 100644 index 0000000000..5965ae5945 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2005/Makefile @@ -0,0 +1,16 @@ +# $FreeBSD$ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +XMLDOCS+= index:${XSL_NEWS_NEWSFLASH_OLD}:news.xml: +DEPENDSET.index=transtable news + +XMLDOCS+= press:${XSL_NEWS_PRESS_OLD}:: +DEPENDSET.press=transtable press + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/news/2005/news.xml b/en_US.ISO8859-1/htdocs/news/2005/news.xml new file mode 100644 index 0000000000..4964a8a2a5 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2005/news.xml @@ -0,0 +1,1004 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE news PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for News//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/news.dtd"> + +<!-- Simple schema for FreeBSD Project news. + + Divide time in to <year>, <month>, and <day> elements, each of which + has a <name>. + + each <day> element contains one or more <event> elements. + + Each <event> contains an optional <title>, and then a <p>. <p> elements + can contain <a> anchors. + + Use the <title> element if the <p> content is lengthy. When generating + synopses of this information (e.g., for syndication using RDF files), + the contents of <title> will be preferred over <p>. +--> + +<news> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD$ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2005</name> + + <month> + <name>12</name> + + <day> + <name>23</name> + <event> + <title>FreeBSD Foundation December Newsletter Published</title> + + <p>The FreeBSD Foundation has published its <a + href="http://www.freebsdfoundation.org/press/2005Dec-newsletter.shtml">December + Newsletter</a>, which summarizes the activities the Foundation has + undertaken this year.</p> + </event> + </day> + + <day> + <name>21</name> + <event> + <p>Returned committer: <a + href="mailto:jasone@FreeBSD.org">Jason Evans</a> + (src)</p> + </event> + </day> + + <day> + <name>17</name> + <event> + <title>Release schedule for 2006</title> + + <p>The release engineering team, represented by Scott Long, + has announced the release schedule for 2006. Please refer + to the <a + href="http://lists.freebsd.org/pipermail/freebsd-current/2005-December/058964.html"> + announcement</a> for more information.</p> + </event> + </day> + + <day> + <name>14</name> + <event> + <title>Read-only XFS support in FreeBSD-CURRENT</title> + + <p>Read-only support for the XFS file system has been committed + to FreeBSD-CURRENT. The code is derived from sources provided + by SGI and is covered by the GPL. Additional information + can be found in the <a + href="http://lists.freebsd.org/pipermail/freebsd-current/2005-December/058907.html"> + announcement</a>.</p> + </event> + </day> + + <day> + <name>12</name> + <event> + <p>New committer: <a + href="mailto:anray@FreeBSD.org">Andrey Slusar</a> + (ports)</p> + </event> + </day> + + <day> + <name>7</name> + <event> + <title>New website section: Projects and ideas for volunteers</title> + + <p>The FreeBSD project has hundreds of active developers spread all + over the world, and many of them have their own parts of the + source-tree that they work on. However, there are always a lot of + new interesting projects and ideas that needs to be investigated + and evaluated, and this is where the FreeBSD project relies on + heroic efforts from volunteers. A new section on the FreeBSD + website has been created with the purpose of listing such + projects. The list is in no way complete, but it should serve as + a nice starting point for volunteers who would like to become + committers in the future. You can <a + href="&base;/projects/ideas/">view the projects list here</a>.</p> + </event> + </day> + + <day> + <name>1</name> + + <event> + <title>Hewlett-Packard Donates Blade Cluster + to The FreeBSD Foundation</title> + + <p>The FreeBSD Foundation received a donation of a blade system + from Hewlett-Packard for use as a third-party software build + cluster. This 20-node HP BladeSystem cluster triples + the speed of the build process for i386 packages. You can <a + href="http://www.freebsdfoundation.org/press/20051201-PRreleaseHP.pdf">see + more details from here</a>.</p> + </event> + + <event> + <p>New committer: <a + href="mailto:tdb@FreeBSD.org">Tim Bishop</a> + (ports)</p> + </event> + </day> + </month> + + <month> + <name>11</name> + + <day> + <name>29</name> + <event> + <p>New committer: <a + href="mailto:oleg@FreeBSD.org">Oleg Bulyzhin</a> + (src)</p> + </event> + </day> + + <day> + <name>27</name> + + <event> + <title>New article: Building Products with FreeBSD</title> + + <p>A new article, <a + href="&base;/doc/en_US.ISO8859-1/articles/building-products/"> + Building Products with FreeBSD</a> describes the benefits of + collaborating with the FreeBSD project when developing + products. Much of the engineering cost of software product + development for a successful product comes from the need to + evolve to keep pace with the market. By working with a mature, + reuse-friendly source base like that of the FreeBSD + project, and by following the best-practices listed in this article, + organizations can reap the benefits of reduced engineering costs + and improved market adaptability.</p> + </event> + </day> + + <day> + <name>18</name> + + <event> + <title>July-October 2005 Status Report</title> + + <p>The July-October, 2005 status report is <a + href="&base;/news/status/report-july-2005-oct-2005.html">now + available</a> with 37 entries.</p> + </event> + </day> + + <day> + <name>5</name> + + <event> + <title>KDE 3.4.3 available for FreeBSD</title> + + <p>KDE 3.4.3 has been merged into the ports tree. For a + detailed list of improvements since the KDE 3.4.2 release, + please refer to the KDE 3.4.2 <a + href="http://www.kde.org/announcements/changelogs/changelog3_4_2to3_4_3.php"> + changelog</a>. For more information, see the KDE 3.4.3 + <a href="http://www.kde.org/info/3.4.3.php">info page</a>. + For general information about KDE on FreeBSD, please see + the KDE on FreeBSD <a href="http://freebsd.kde.org">project + page</a>.</p> + </event> + + <event> + <title>GNOME 2.12.1 available for FreeBSD</title> + + <p>Now that 6.0 is out the door, GNOME 2.12.1 has been merged + into the ports tree. Be sure to checkout + our <a href="&base;/gnome/docs/faq212.html">upgrade FAQ</a> + for all the changes, upgrade instructions, and + known issues. Additional resources can be found + at the <a href="&base;/gnome/index.html">FreeBSD GNOME + homepage</a>.</p> + </event> + </day> + + <day> + <name>4</name> + + <event> + <title>FreeBSD 6.0-RELEASE is Now Available</title> + + <p><a href="&base;/releases/6.0R/announce.html">FreeBSD + 6.0-RELEASE</a> has been released. Please check the <a + href="&base;/releases/6.0R/errata.html">release errata</a> + before installation for any late-breaking news and/or + issues with 6.0. The <a + href="&base;/releases/index.html">Release Information</a> + page has more information about FreeBSD releases.</p> + </event> + </day> + + <day> + <name>1</name> + <event> + <title>FreeBSD Logo Design Competition Result</title> + + <p>We are pleased to announce the winner of our logo + competition: Anton K. Gural. For competition details, + please see the <a + href="http://logo-contest.freebsd.org/result/">result + page</a>. With our new logo, we will be able to show our + own identity on the 'net, and this will make our marketing + efforts much easier. We will publish soon a guideline page + which gives usage rules and usable (vector format) logo data + under the same BSD license as the rest of FreeBSD.</p> + </event> + </day> + </month> + + <month> + <name>10</name> + + <day> + <name>30</name> + <event> + <p>New committer: <a + href="mailto:aaron@FreeBSD.org">Aaron Dalton</a> + (ports)</p> + </event> + </day> + + <day> + <name>18</name> + <event> + <p>New committer: <a + href="mailto:ariff@FreeBSD.org">Ariff Abdullah</a> + (src)</p> + </event> + </day> + + <day> + <name>11</name> + <event> + <title>FreeBSD 6.0-RC1 Available</title> + + <p>The first release candidate of FreeBSD 6.0 is now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2005-October/018790.html">available</a>. + The RC1 ISO images and FTP based install support are + available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD Mirror sites</a>.</p> + + </event> + </day> + + <day> + <name>6</name> + <event> + <title>New Case Study: Argentina.com</title> + + <p>A new case study, <a + href="&base;/doc/en_US.ISO8859-1/articles/casestudy-argentina.com/"> + argentina.com</a>, + describes how a successful ISP in Latin America excels in + a competitive market with FreeBSD.</p> + </event> + </day> + + <day> + <name>5</name> + <event> + <title>New website launched</title> + + <p>A new website has been launched. We hope you find the + new design easier to navigate. The site was implemented + by Emily Boyd as part of + <a + href="http://code.google.com/summerofcode.html">Google's + Summer of Code</a> program. A copy of the old site for + comparison purposes is archived + <a href="http://www.FreeBSD.org/old">here</a>. Please + post your comments and suggestions about the new site to + the freebsd-www@FreeBSD.org list.</p> + </event> + </day> + + <day> + <name>3</name> + <event> + <p>New committer: <a + href="mailto:bvs@FreeBSD.org">Vitaly Bogdanov</a> + (doc)</p> + </event> + + <event> + <p>New committer: <a + href="mailto:ehaupt@FreeBSD.org">Emanuel Haupt</a> + (ports)</p> + </event> + + <event> + <p>New committer: <a + href="mailto:az@FreeBSD.org">Andrej Zverev</a> + (ports)</p> + </event> + </day> + </month> + + <month> + <name>9</name> + + <day> + <name>18</name> + <event> + <p>New committer: <a + href="mailto:tmclaugh@FreeBSD.org">Tom McLaughlin</a> + (ports)</p> + </event> + </day> + + <day> + <name>15</name> + <event> + <p>New committer: <a + href="mailto:mnag@FreeBSD.org">Marcus Alves Grando</a> + (ports)</p> + </event> + </day> + + <day> + <name>7</name> + <event> + <title>FreeBSD 6.0-BETA4 Available</title> + <p><a href="http://lists.freebsd.org/pipermail/freebsd-stable/2005-September/018186.html">6.0-BETA4 announcement</a>.</p> + </event> + </day> + </month> + + <month> + <name>8</name> + + <day> + <name>29</name> + <event> + <title>FreeBSD 6.0-BETA3 Available</title> + <p><a href="http://lists.freebsd.org/pipermail/freebsd-stable/2005-August/018061.html">6.0-BETA3 announcement</a>.</p> + </event> + </day> + + <day> + <name>22</name> + <event> + <p>New committer: <a + href="mailto:garys@FreeBSD.org">Gary W. Swearingen</a> + (doc)</p> + </event> + </day> + + <day> + <name>21</name> + + <event> + <title>New Security Officer: Colin Percival</title> + + <p>After 43 months Jacques Vidrine has passed the + Security Officer hat to Colin Percival, known for his + FreeBSD Update, portsnap, and bsdiff utilities, and + recently for his paper "Cache missing for fun and profit" + regarding sensitive information disclosure within + hyperthreaded processor systems. You can read more about + this <a + href="http://lists.freebsd.org/pipermail/freebsd-security/2005-August/003115.html"> + here</a>. + </p> + </event> + </day> + + <day> + <name>17</name> + + <event> + <title>FreeBSD Events iCalendar Feed Introduced</title> + + <p>Users with organisational software that understands + iCalendar format files can now subscribe to the + <a href="&base;/events/events.ics">FreeBSD Events + Calendar</a>.</p> + </event> + + <event> + <title>New Article: Choosing a FreeBSD Version</title> + + <p>A new article, <a + href="&base;/doc/en_US.ISO8859-1/articles/version-guide/"> + Choosing the FreeBSD Version That Is Right For You</a>, + discusses considerations that should go into the selection + of the most suitable version of FreeBSD for individual needs. + Included are such concepts as the differences between a + Release and a Branch, and between FreeBSD-STABLE and + FreeBSD-CURRENT. Also covered is how FreeBSD development + is moving towards a goal of more frequent major releases, + each of which introduces smaller feature sets, as compared + to how releases were done in the past. The target audience + is both the user who is considering installing FreeBSD, and + also existing users who wish to plan their future upgrades.</p> + </event> + </day> + + <day> + <name>5</name> + + <event> + <title>FreeBSD 6.0-BETA2 Available</title> + + <p><a href="http://lists.freebsd.org/pipermail/freebsd-stable/2005-August/017586.html">6.0-BETA2 announcement</a>.</p> + </event> + </day> + + <day> + <name>1</name> + + <event> + <title>New FreeBSD/Linux Whitepaper</title> + + <p>Dru Lavigne has just published <a + href="&base;/doc/en_US.ISO8859-1/articles/linux-comparison/">FreeBSD: + An Open Source Alternative to Linux</a>. The objective of + this whitepaper is to explain some of the features and + benefits provided by FreeBSD, and where applicable, + compare those features to Linux. This paper provides a + starting point for those interested in exploring Open + Source alternatives to Linux.</p> + </event> + </day> + </month> + + <month> + <name>7</name> + + <day> + <name>22</name> + + <event> + <title>March-June 2005 Status Report</title> + + <p>The March-June, 2005 status report is <a + href="&base;/news/status/report-mar-2005-june-2005.html">now + available</a> with 43 entries.</p> + </event> + </day> + + <day> + <name>20</name> + <event> + <p>New committer: <a + href="mailto:vsevolod@FreeBSD.org">Vsevolod Stakhov</a> + (ports)</p> + </event> + </day> + + <day> + <name>18</name> + <event> + <p>New committer: <a + href="mailto:bruno@FreeBSD.org">Bruno Ducrot</a> + (src)</p> + </event> + </day> + + <day> + <name>16</name> + + <event> + <title>Funded Student Projects Announced</title> + + <p>The FreeBSD Project received over 350 applications for <a + href="http://code.google.com/summerofcode.html">Google's + Summer of Code</a> program, amongst which 18 were selected + for funding. Unfortunately, there were far more first rate + applications than available spots for students. However, + we encourage students to work together with us all year + round. The FreeBSD Project is always willing to help + mentor students learn more about operating system + development through our normal community mailing lists and + development forums. Contributing to an open source + software project is a valuable component of a computer + science education and great preparation for a career in + software development.</p> + + <p>More information about the funded student projects is + available from the <a + href="http://wiki.freebsd.org/moin.cgi/SummerOfCode2005">FreeBSD + Summer of Code Wiki</a>.</p> + + </event> + </day> + + <day> + <name>15</name> + + <event> + <title>FreeBSD 6.0-BETA1 Available</title> + + <p><a href="http://lists.freebsd.org/pipermail/freebsd-stable/2005-July/016958.html">6.0-BETA1 announcement</a>.</p> + </event> + </day> + + <day> + <name>11</name> + + <event> + <title>6-STABLE branch (RELENG_6) forked</title> + + <p>Next milestone in 6.0-RELEASE process is reached. RELENG_6 + CVS branch is forked from HEAD. The upcoming 6.0-RELEASE, and + all following 6.x releases will be cut from this branch. + For more information see: + <a href="&base;/releases/6.0R/schedule.html">6.0-RELEASE schedule</a>, + <a href="http://lists.freebsd.org/pipermail/freebsd-stable/2005-July/016855.html">RELENG_6 announcement</a>.</p> + </event> + + <event> + <p>New committer: <a + href="mailto:garga@FreeBSD.org">Renato Botelho</a> + (ports)</p> + </event> + </day> + + <day> + <name>6</name> + <event> + <p>New committer: <a + href="mailto:jkim@FreeBSD.org">Jung-uk Kim</a> + (src)</p> + </event> + </day> + + <day> + <name>2</name> + + <event> + <title>Snapshot Release in July 2005 Available</title> + + <p>The FreeBSD 6-CURRENT snapshot releases in July 2005 are + now available. This will likely be the last snapshot + of 6.0-CURRENT before the RELENG_6 branch is made. + The FreeBSD Release Engineering Team has released + snapshot releases of 5-STABLE and 6-CURRENT to encourage + people to test new features and improve the reliability. + For more details, please visit + <a href="&base;/snapshots/index.html">the snapshots page</a>.</p> + </event> + </day> + + <day> + <name>1</name> + + <event> + <p>New committer: <a + href="mailto:wsalamon@FreeBSD.org">Wayne Salamon</a> + (src)</p> + </event> + </day> + </month> + + <month> + <name>6</name> + + <day> + <name>17</name> + + <event> + <p>New contributor: <a + href="mailto:matteo@FreeBSD.org">Matteo Riondato</a> + (PR database)</p> + </event> + + <event> + <p>New committer: <a + href="mailto:kmacy@FreeBSD.org">Kip Macy</a> + (src)</p> + </event> + </day> + + <day> + <name>11</name> + + <event> + <title>Code Freeze for 6.0-RELEASE</title> + + <p>The <a href="&base;/releases/6.0R/schedule.html">FreeBSD + 6.0</a> code freeze has begun. Developers must have + approval from re@FreeBSD.org to commit to the HEAD branch of + src/. 6.0 snapshots are available from the FTP sites for + those able to help test the upcoming major new release of + FreeBSD. For more information, please see the <a + href="&base;/releng/index.html">release engineering</a> area + of the web site.</p> + </event> + </day> + + <day> + <name>1</name> + + <event> + <title>Funded Student Coding Opportunity</title> + + <p>The FreeBSD Project is happy to participate in Google's + <a href="http://code.google.com/summerofcode.html">Summer + of Code 2005</a> program. This program will provide + funding for students to spend the summer contributing to + open source software projects. A list of FreeBSD specific + projects and potential mentors is available <a + href="&base;/projects/summerofcode.html">here</a>.</p> + </event> + + <event> + <p>New committer: <a + href="mailto:brd@FreeBSD.org">Brad Davis</a> + (doc)</p> + </event> + </day> + </month> + + <month> + <name>5</name> + + <day> + <name>26</name> + + <event> + <p>New committer: <a + href="mailto:thompsa@FreeBSD.org">Andrew Thompson</a> + (src)</p> + </event> + </day> + + <day> + <name>21</name> + + <event> + <p>New committer: <a + href="mailto:rodrigc@FreeBSD.org">Craig Rodrigues</a> + (src)</p> + </event> + </day> + + <day> + <name>15</name> + + <event> + <title>Successful BSDCan Concluded</title> + + <p>Another great <a href="http://www.bsdcan.org">BSD + conference</a> in Ottawa has just concluded. There was a + highly successful 2 day FreeBSD Developer summit + preceding the official conference. Special thanks should + go to Dan Langille for organizing the conference and to + Scott Long for organizing the developer summit.</p> + + </event> + </day> + + <day> + <name>9</name> + + <event> + <title>FreeBSD 5.4-RELEASE is Now Available</title> + + <p><a href="&base;/releases/5.4R/announce.html">FreeBSD + 5.4-RELEASE</a> has been released. Please check the <a + href="&base;/releases/5.4R/errata.html">release errata</a> + before installation for any late-breaking news and/or + issues with 5.4. The <a + href="&base;/releases/index.html">Release Information</a> + page has more information about FreeBSD releases.</p> + + </event> + </day> + + <day> + <name>3</name> + + <event> + <title>FreeBSD 5.4-RC4 Release Available</title> + + <p>The FreeBSD 5.4-RC4 release is now available. + The FreeBSD Release Engineering Team is pleased to announce + the availability of FreeBSD 5.4-RC4, the last Release + Candidate of the FreeBSD 5.4 unless a major problem is + discovered as part of RC4. The RC4 ISO images and FTP based + install support are available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD Mirror sites</a>.</p> + </event> + + <event> + <title>PF updated to 3.7</title> + + <p>The packet filter (pf) code has been updated to the upcoming + OpenBSD release 3.7. Several new features including nested + anchors and connection rate limiting are now available to + the FreeBSD userbase.</p> + </event> + </day> + </month> + + <month> + <name>4</name> + + <day> + <name>21</name> + + <event> + <title>January-March 2005 Status Report</title> + + <p>The January-March, 2005 status report is <a + href="&base;/news/status/report-jan-2005-mar-2005.html">now + available</a> with 39 entries.</p> + </event> + </day> + + <day> + <name>18</name> + + <event> + <title>FreeBSD 5.4-RC3 Release Available</title> + + <p>The FreeBSD 5.4-RC3 release is now available. + The FreeBSD Release Engineering Team is pleased to announce + the availability of FreeBSD 5.4-RC3, the third Release + Candidate of the FreeBSD 5.4 release cycle. The RC3 ISO images + and FTP based install support are available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html" + >FreeBSD Mirror sites</a>.</p> + </event> + </day> + + <day> + <name>13</name> + + <event> + <p>New committer: <a + href="mailto:qingli@FreeBSD.org">Qing Li</a> + (src)</p> + </event> + </day> + + <day> + <name>12</name> + + <event> + <p>New committer: <a + href="mailto:jylefort@FreeBSD.org">Jean-Yves Lefort</a> + (ports)</p> + </event> + + <event> + <p>New committer: <a + href="mailto:lawrance@FreeBSD.org">Sam Lawrance</a> + (ports)</p> + </event> + </day> + + <day> + <name>11</name> + + <event> + <title>FreeBSD 5.4-RC2 Release Available</title> + + <p>The FreeBSD 5.4-RC2 release is now available. + The FreeBSD Release Engineering Team is pleased to announce + the availability of FreeBSD 5.4-RC2, the second Release + Candidate of the FreeBSD 5.4 release cycle. We encourage people + to help with testing so that any final bugs can be identified + and worked out before the actual release. The RC2 ISO images + and FTP based install support are available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html" + >FreeBSD Mirror sites</a>.</p> + </event> + </day> + + <day> + <name>7</name> + + <event> + <p>New committer: <a + href="mailto:joel@FreeBSD.org">Joel Dahl</a> + (doc)</p> + </event> + </day> + + <day> + <name>5</name> + + <event> + <title>FreeBSD 5.4-RC1 Release Available</title> + + <p>The FreeBSD 5.4-RC1 release is now available. + The FreeBSD Release Engineering Team is pleased to announce + the availability of FreeBSD 5.4-RC1, the first Release + Candidate of the FreeBSD 5.4 release cycle. We encourage people + to help with testing so that any final bugs can be identified + and worked out before the actual release. The RC1 ISO images + and FTP based install support are available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html" + >FreeBSD Mirror sites</a>.</p> + </event> + </day> + </month> + + <month> + <name>3</name> + + <day> + <name>31</name> + + <event> + <p>Enhanced commit privileges: <a href="mailto:netchild@FreeBSD.org">Alexander Leidinger</a> (src, ports)</p> + </event> + </day> + + <day> + <name>20</name> + + <event> + <title>FreeBSD 5.4-BETA1 Release Available</title> + + <p>The FreeBSD 5.4-BETA1 release is now available. + This is the first BETA release for the FreeBSD 5.4 release + cycle and the Release Engineering Team encourages people + to help with testing so that any final bugs can be identified + and worked out before the actual release. + The BETA1 ISO images and FTP based install support + are available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html" + >FreeBSD Mirror sites</a>.</p> + </event> + </day> + + <day> + <name>17</name> + + <event> + <title>Snapshot Release in March 2005 Available</title> + + <p>The FreeBSD 6-CURRENT snapshot releases in March 2005 are + now available. Note that 5-STABLE snapshots are not available + in this month because 5.4-PRERELEASE builds will be available soon. + The FreeBSD Release Engineering Team has released + snapshot releases of 5-STABLE and 6-CURRENT on a monthly basis + to encourage people to test new features + and improve the reliability. For more details, please visit + <a href="&base;/snapshots/index.html">the snapshots page</a>.</p> + </event> + </day> + + <day> + <name>12</name> + + <event> + <title>GNOME 2.10.0 available for FreeBSD</title> + + <p>GNOME 2.10.0 has been released and merged into the ports + tree in time for 5.4-RELEASE. Be sure to checkout + our <a href="&base;/gnome/docs/faq210.html">upgrade FAQ</a> + for all the changes, upgrade instructions, and + known issues. Additional resources can be found + at the <a href="&base;/gnome/index.html">FreeBSD GNOME + homepage</a>.</p> + </event> + </day> + + <day> + <name>7</name> + + <event> + <p>New committer: <a href="mailto:novel@FreeBSD.org">Roman Bogorodskiy</a> (ports)</p> + </event> + </day> + + <day> + <name>3</name> + + <event> + <p>New committer: <a href="mailto:damien@FreeBSD.org">Damien Bergamini</a> (src)</p> + </event> + </day> + + <day> + <name>1</name> + + <event> + <p>New committer: <a href="mailto:jcamou@FreeBSD.org">Jesus R. Camou</a> (doc)</p> + </event> + + <event> + <p>New committer: <a href="mailto:flz@FreeBSD.org">Florent Thoumie</a> (ports)</p> + </event> + </day> + </month> + + <month> + <name>2</name> + + <day> + <name>27</name> + + <event> + <p>New committer: <a href="mailto:barner@FreeBSD.org">Simon Barner</a> (ports)</p> + </event> + </day> + + <day> + <name>22</name> + + <event> + <p><a href="http://logo-contest.FreeBSD.org/">Logo design competition</a> is open</p> + </event> + + <event> + <p>New committer: <a href="mailto:avatar@FreeBSD.org">Tai-hwa Liang</a> (src)</p> + </event> + </day> + </month> + + <month> + <name>1</name> + + <day> + <name>25</name> + <event> + <title>FreeBSD 4.11-RELEASE is Now Available</title> + + <p><a href="&base;/releases/4.11R/announce.html">FreeBSD + 4.11-RELEASE</a> has been released. Please check the <a + href="&base;/releases/4.11R/errata.html">release errata</a> + before installation for any late-breaking news and/or + issues with 4.11. The <a + href="&base;/releases/index.html">Release Information</a> + page has more information about FreeBSD releases.</p> + </event> + </day> + + <day> + <name>17</name> + + <event> + <title>July-December 2004 Status Report</title> + + <p>The July-December, 2004 status report is <a + href="&base;/news/status/report-july-2004-dec-2004.html">now + available</a> with 44 entries.</p> + </event> + + <event> + <title>FreeBSD 4.11 RC3 Available</title> + + <p>The third Release Candidate for FreeBSD 4.11 has been + made available. Please see the full announcement on + the FreeBSD-STABLE mailing list <a + href="http://docs.freebsd.org/cgi/mid.cgi?20050117020739.GA2736">here</a>. + The full 4.11 release schedule is <a + href="&base;/releases/4.11R/schedule.html">here</a>.</p> + </event> + </day> + + <day> + <name>2</name> + + <event> + <title>FreeBSD 4.11 RC2 Available</title> + + <p>The second Release Candidate for FreeBSD 4.11 has been + made available. Please see the full announcement on + the FreeBSD-STABLE mailing list <a + href="http://docs.freebsd.org/cgi/mid.cgi?20050103054251.GA60361">here</a>. + The full 4.11 release schedule is <a + href="&base;/releases/4.11R/schedule.html">here</a>.</p> + </event> + </day> + </month> + </year> +</news> diff --git a/en_US.ISO8859-1/htdocs/news/2005/press.xml b/en_US.ISO8859-1/htdocs/news/2005/press.xml new file mode 100644 index 0000000000..11a1ec2f93 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2005/press.xml @@ -0,0 +1,329 @@ +<press> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD$ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2005</name> + + <month> + <name>12</name> + <story> + <name>FreeBSD Waters Are Easily Waded</name> + <url>http://www.serverwatch.com/sreviews/article.php/3569631</url> + <site-name>ServerWatch</site-name> + <site-url>http://www.serverwatch.com/</site-url> + <date>8 December 2005</date> + <author>Charlie Schluting</author> + <p>According to this review, "FreeBSD is an enterprise-grade + operating system that leaves little to be desired."</p> + </story> + </month> + + <month> + <name>11</name> + + <story> + <name>Beyond The Big Three BSDs, BSD Alternatives</name> + <url>http://www.serverwatch.com/tutorials/article.php/3565016</url> + <site-name>Serverwatch</site-name> + <site-url>http://www.serverwatch.com/</site-url> + <date>17 November 2005</date> + <author>Martin Brown</author> + <p>Covers a few FreeBSD-derived operating systems.</p> + </story> + + <story> + <name>Using Software RAID-1 with FreeBSD</name> + <url>http://www.onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html</url> + <site-name>Onlamp</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>10 November 2005</date> + <author>Dru Lavigne</author> + <p>The author shows how to set up a RAID 1 using the gmirror + facility available in FreeBSD 5 and 6.</p> + </story> + + <story> + <name>Return of The BSDs</name> + <url>http://www.internetnews.com/dev-news/article.php/3561526</url> + <site-name>Internetnews.Com</site-name> + <site-url>http://www.internetnews.com/</site-url> + <date>03 November 2005</date> + <author>Sean Michael Kerner</author> + <p>Press about new releases from the *BSD projects.</p> + </story> + + <story> + <name>Desktop FreeBSD: Upgrading to 6.0</name> + <url>http://www.ofb.biz/modules.php?name=News&file=article&sid=387</url> + <site-name>Open For Business</site-name> + <site-url>http://www.ofb.biz/</site-url> + <date>08 November 2005</date> + <author>Ed Hurst</author> + <p>A reviewer recommends FreeBSD 6.0 for the desktop.</p> + </story> + </month> + + <month> + <name>10</name> + + <story> + <name>Selecting a Secure Enterprise OS: Don't Make the First + Step the Wrong Step</name> + <url>http://www.informit.com/articles/article.asp?p=421896</url> + <site-name>Informit</site-name> + <site-url>http://www.informit.com/</site-url> + <date>28 October 2005</date> + <author>Bruce Potter</author> + <p>A comparison of the operational security of Windows(r), + Linux and FreeBSD.</p> + </story> + + <story> + <name>A Comparison of Solaris, Linux, and FreeBSD Kernels</name> + <url>http://www.opensolaris.org/os/article/2005-10-14_a_comparison_of_solaris__linux__and_freebsd_kernels/</url> + <site-name>OpenSolaris</site-name> + <site-url>http://www.opensolaris.org/</site-url> + <date>14 October 2005</date> + <author>Max Bruning</author> + <p>A technical article comparing scheduling, memory + management, and file system architecture in these three + open-source kernels.</p> + </story> + + <story> + <name>Destination FreeBSD: Interview with Release Engineer Scott + Long</name> + <url>http://www.bsdforums.org/forums/showthread.php?t=35212</url> + <site-name>BSDForums.org</site-name> + <site-url>http://www.bsdforums.org</site-url> + <date>04 October 2005</date> + <author>BSDForums.org</author> + <p>BSDForums interviews FreeBSD release engineer Scott Long + about various aspects of FreeBSD, including FreeBSD 6.0, + Apple G4 PowerMac support, AMD64 and wireless + compatibility.</p> + </story> + </month> + + <month> + <name>9</name> + + <story> + <name>Sun Cobalt Ported to FreeBSD</name> + <url>http://www.emediawire.com/releases/2005/9/emw282859.htm</url> + <site-name>eMediaWire</site-name> + <site-url>http://www.emediawire.com/</site-url> + <date>09 September 2005</date> + <author>OffMyServer, Inc. Press Release</author> + <p>The Sun Cobalt RaQ550 web hosting platform has been ported + to FreeBSD.</p> + </story> + + <story> + <name>Developer aims for Dtrace on FreeBSD</name> + <url>http://www.zdnet.com.au/news/software/soa/Developer_aims_for_Dtrace_on_FreeBSD/0,2000061733,39210618,00.htm</url> + <site-name>ZDNet Australia</site-name> + <site-url>http://www.zdnet.com.au/</site-url> + <date>08 September 2005</date> + <author>Renai LeMay</author> + <p>An article about work being done to port Sun's DTrace to + FreeBSD.</p> + </story> + </month> + + <month> + <name>8</name> + + <story> + <name>FreeBSD 6.0 will target wireless devices</name> + <url>http://news.zdnet.co.uk/software/linuxunix/0,39020390,39214098,00.htm</url> + <site-name>ZDNet UK</site-name> + <site-url>http://www.zdnet.co.uk/</site-url> + <date>19 August 2005</date> + <author>Ingrid Marson</author> + <p>An interview with FreeBSD release engineer Scott Long about + the upcoming 6.0 release.</p> + </story> + + </month> + + <month> + <name>7</name> + + <story> + <name>Information Security with Colin Percival</name> + <url>http://www.onlamp.com/pub/a/bsd/2005/07/21/Big_Scary_Daemons.html</url> + <site-name>Onlamp</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>21 July 2005</date> + <author>Michael W. Lucas</author> + <p>Colin Percival, FreeBSD developer and independent security + researcher, describes his recent work on covert channels in + hyperthreaded processors.</p> + </story> + + <story> + <name>Why FreeBSD</name> + <url>http://www.ibm.com/developerworks/opensource/library/os-freebsd/</url> + <site-name>developerWorks</site-name> + <site-url>http://www.ibm.com/developerworks/</site-url> + <date>19 July 2005</date> + <author>Frank Pohlmann</author> + <p>A brief introduction to the BSD family of OSes.</p> + </story> + + <story> + <name>Project Evil: Windows network drivers on FreeBSD</name> + <url>http://www.pingwales.co.uk/tutorials/project-evil.html</url> + <site-name>Ping Wales</site-name> + <site-url>http://www.pingwales.co.uk/</site-url> + <date>15 July 2005</date> + <author>David Chisnall</author> + <p>On using Windows(R) network drivers in FreeBSD.</p> + </story> + + </month> + + <month> + <name>6</name> + + <story> + <name>Open-source projects get free checkup by automated tools</name> + <url>http://www.securityfocus.com/news/11230</url> + <site-name>SecurityFocus</site-name> + <site-url>http://www.securityfocus.com/</site-url> + <date>28 June 2005</date> + <author>Robert Lemos</author> + <p>Code analysis software firm Coverity analyses FreeBSD's source base and + finds a very low number of software flaws.</p> + </story> + + <story> + <name>Interview: Looking at FreeBSD 6 and Beyond</name> + <url>http://www.osnews.com/story.php?news_id=10951</url> + <site-name>OSnews</site-name> + <site-url>http://www.osnews.com/</site-url> + <date>23 June 2005</date> + <author>Eugenia Loli-Queru</author> + <p>OSnews interviews FreeBSD developers Scott Long, Robert + Watson and John Baldwin about the upcoming FreeBSD 6 + release.</p> + </story> + + <story> + <name>Eric Raymond advocates BSD license over GPL</name> + <url>http://www.myfreebsd.com.br/static/raymond-20050604.html</url> + <site-name>MyFreeBSD Brazil</site-name> + <site-url>http://www.MyFreeBSD.com.br/</site-url> + <date>4 June 2005</date> + <author>Luiz Gustavo Ramos</author> + <p>"Freedom and choice are pretty cool. But we should talk + about many other things. GPL is based on the belief that + open source software is weak and needs to be protected. With + it, we continue injuring ourselves, cutting ourselves from + the economic benefits of BSD license".</p> + </story> + </month> + + <month> + <name>5</name> + + <story> + <name>First BitDefender for FreeBSD products launched</name> + <url>http://www.moneyweb.co.za/business_today/440831.htm</url> + <site-name>MoneyWeb</site-name> + <site-url>http://www.moneyweb.co.za/</site-url> + <date>17 May 2005</date> + <author>BitDefender Press Release</author> + <p>BitDefender announces their move into enterprise space + with a FreeBSD version of their products.</p> + </story> + + <story> + <name>LSI MegaRAID(R) Adapters Now Feature FreeBSD 5.4 + Support</name> + <url>http://biz.yahoo.com/prnews/050511/sfw107.html</url> + <site-name>Yahoo News</site-name> + <site-url>http://biz.yahoo.com/</site-url> + <date>11 May 2005</date> + <author>LSI Logic Press Release</author> + <p>LSI Logic MegaRAID(R) SCSI and SATA adapters now support + the latest FreeBSD 5.4 release.</p> + </story> + </month> + + <month> + <name>4</name> + <story> + <name>Desktop FreeBSD: New Life for Old Laptops</name> + <url>http://www.ofb.biz/modules.php?name=News&file=article&sid=358</url> + <site-name>Open for Business</site-name> + <site-url>http://www.ofb.biz</site-url> + <date>27 April 2005</date> + <author>Ed Hurst</author> + <p>An article on using FreeBSD 5.4 on a laptop.</p> + </story> + + <story> + <name>Large Web Hosting Provider Switches to FreeBSD</name> + <url>http://www.w3reports.com/index.php?itemid=869</url> + <site-name>W3reports</site-name> + <site-url>http://www.w3reports.com</site-url> + <date>24 April 2005</date> + <author>Submission</author> + <p>Offmyserver, a rackmount server provider, recently migrated + 50 servers to FreeBSD, on account of its reliability and ability + to handle large amounts of disk.</p> + </story> + </month> + + <month> + <name>3</name> + <story> + <name>FreeBSD Process Management</name> + <url>http://www.informit.com/articles/article.asp?p=366888&rl=1</url> + <site-name>InformIT</site-name> + <site-url>http://www.informit.com/</site-url> + <date>03 March 2005</date> + <author>George Neville-Neil, Marshall Kirk McKusick</author> + <p>An excerpt from the book "The Design and Implementation of the + FreeBSD Operating System".</p> + </story> + </month> + + <month> + <name>2</name> + + <story> + <name>FreeBSD Tips and Tricks for 2005</name> + <url>http://www.onlamp.com/pub/a/bsd/2005/02/17/FreeBSD_Basics.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com</site-url> + <date>17 February 2005</date> + <author>Dru Lavigne</author> + <p>Dru Lavigne describes the steps taken for maintaining up to date + a FreeBSD system this year.</p> + </story> + </month> + + <month> + <name>1</name> + + <story> + <name>FreeBSD's SMPng</name> + <url>http://www.onlamp.com/pub/a/bsd/2005/01/20/smpng.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>20 January 2005</date> + <author>Federico Biancuzzi</author> + <p>OnLamp.com's writer interviews FreeBSD's Core Team member + Scott Long about FreeBSD's implementation on SMPng.</p> + </story> + </month> + + </year> +</press> diff --git a/en_US.ISO8859-1/htdocs/news/2006/Makefile b/en_US.ISO8859-1/htdocs/news/2006/Makefile new file mode 100644 index 0000000000..56ec0fd3bf --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2006/Makefile @@ -0,0 +1,16 @@ +# $FreeBSD: www/en/news/2005/Makefile,v 1.1 2007/03/15 16:21:15 murray Exp $ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +XMLDOCS+= index:${XSL_NEWS_NEWSFLASH_OLD}:news.xml: +DEPENDSET.index=transtable news + +XMLDOCS+= press:${XSL_NEWS_PRESS_OLD}:: +DEPENDSET.press=transtable press + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/news/2006/news.xml b/en_US.ISO8859-1/htdocs/news/2006/news.xml new file mode 100644 index 0000000000..11c8ca2220 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2006/news.xml @@ -0,0 +1,1011 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE news PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for News//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/news.dtd"> + +<!-- Simple schema for FreeBSD Project news. + + Divide time in to <year>, <month>, and <day> elements, each of which + has a <name>. + + each <day> element contains one or more <event> elements. + + Each <event> contains an optional <title>, and then a <p>. <p> elements + can contain <a> anchors. + + Use the <title> element if the <p> content is lengthy. When generating + synopses of this information (e.g., for syndication using RDF files), + the contents of <title> will be preferred over <p>. +--> + +<news> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD: www/en/news/2006/news.xml,v 1.1 2008/01/04 21:16:27 jkois Exp $ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2006</name> + <month> + <name>12</name> + + <day> + <name>27</name> + <event> + <p>New committer: <a href="mailto:jls@FreeBSD.org">Jordan Sissel</a> + (src)</p> + </event> + + <event> + <title>FreeBSD 6.2-RC2 Available</title> + + <p>The second release candidate of FreeBSD 6.2 has been <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2006-December/031742.html">announced</a>. + ISO images and distributions for Tier-1 architectures are now available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD mirror sites</a>.</p> + </event> + </day> + + <day> + <name>26</name> + <event> + <p>New committer: <a href="mailto:dryice@FreeBSD.org">Dryice Liu</a> + (ports)</p> + </event> + </day> + + <day> + <name>22</name> + <event> + <p>New committer: <a href="mailto:nox@FreeBSD.org">Juergen Lock</a> + (ports)</p> + </event> + </day> + + <day> + <name>10</name> + <event> + <title>Podcast Interview with FreeBSD Developer Joseph Koshy</title> + + <p>In his latest <a href="http://bsdtalk.blogspot.com/">bsdtalk</a> + podcast, Will Backman interviews FreeBSD Developer Joseph Koshy + about his recent work on libElf. The podcast is + available at + <a + href="http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk087.mp3"> + http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk087.mp3</a>.</p> + </event> + </day> + + <day> + <name>7</name> + <event> + <title>Podcast Interview with FreeBSD Developer Kip Macy</title> + + <p>In his latest <a href="http://bsdtalk.blogspot.com/">bsdtalk</a> + podcast, Will Backman interviews FreeBSD Developer Kip Macy + about the FreeBSD/sun4v port. The podcast is + available at + <a + href="http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk086.mp3"> + http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk086.mp3</a>.</p> + </event> + </day> + + <day> + <name>5</name> + <event> + <p>New committer: <a href="mailto:nivit@FreeBSD.org">Nicola Vitale</a> + (ports)</p> + </event> + + <event> + <title>New committer: <a href="mailto:gabor@FreeBSD.org">Gábor Kövesdán</a> + (ports). An SoC2006 alumnus.</title> + + <p><a href="mailto:gabor@FreeBSD.org">Gábor Kövesdán</a>, a + successful student from last year's Summer of Code + program, has continued working with the FreeBSD Project + and is now a full ports/ committer.</p> + + </event> + </day> + + <day> + <name>1</name> + <event> + <title>Podcast Interview with FreeBSD Developer Tom McLaughlin</title> + + <p>In his latest <a href="http://bsdtalk.blogspot.com/">bsdtalk</a> + podcast, Will Backman interviews FreeBSD Developer Tom McLaughlin + about the BSD# project and Mono on FreeBSD. The podcast is + available at + <a + href="http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk085.mp3"> + http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk085.mp3</a>.</p> + </event> + </day> + </month> + + <month> + <name>11</name> + + <day> + <name>29</name> + <event> + <p>New committer: <a href="mailto:lx@FreeBSD.org">David Thiel</a> + (ports)</p> + </event> + + <event> + <title>Podcast Interview with FreeBSD Release Engineer Bruce Mah</title> + + <p>In his latest <a href="http://bsdtalk.blogspot.com/">bsdtalk</a> + podcast, Will Backman interviews FreeBSD Release Engineer Bruce + Mah about the upcoming 6.2 release of FreeBSD. The podcast is + available at + <a + href="http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk084.mp3"> + http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk084.mp3</a>.</p> + </event> + </day> + + <day> + <name>17</name> + <event> + <title>FreeBSD 6.2-RC1 Available</title> + + <p>The first release candidate of FreeBSD 6.2 is now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2006-November/030811.html">available</a>. + ISO images for Tier-1 architectures are now available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD mirror sites</a>.</p> + </event> + </day> + + <day> + <name>16</name> + <event> + <title>FreeBSD Foundation Fall Fundraising Campaign</title> + + <p>The <a + href="http://www.freebsdfoundation.org/">FreeBSD Foundation</a> + is kicking off its <a + href="http://www.freebsdfoundation.org/donate/">Fall Fundraising + Campaign</a>. The success of this effort will have a large + impact on the Foundations budget for the next year.</p> + </event> + </day> + + <day> + <name>14</name> + <event> + <title>FreeBSD.org systems move postponed</title> + + <p>The move of the FreeBSD.org systems which was scheduled + for Monday November 13th has been postponed. Currently it + is expected to happen on Friday November 17th (still US + Pacific Standard Time).</p> + </event> + </day> + + <day> + <name>12</name> + <event> + <title>FreeBSD/sun4v Install / Live CD Available</title> + + <p>The port of FreeBSD to Sun's UltraSparc-T1 architecture + has produced an install ISO containing a live file system. + More information is available at the + <a href="http://www.FreeBSD.org/platforms/sun4v.html">FreeBSD/sun4v Project page</a>.</p> + </event> + + <event> + <p>New committer: <a href="mailto:koitsu@FreeBSD.org">Jeremy Chadwick</a> + (ports)</p> + </event> + </day> + + <day> + <name>7</name> + <event> + <p>New committer: <a href="mailto:farrokhi@FreeBSD.org">Babak Farrokhi</a> + (ports)</p> + </event> + + <event> + <p>New committer: <a href="mailto:laszlof@FreeBSD.org">Frank J. Laszlo</a> + (ports)</p> + </event> + </day> + + <day> + <name>5</name> + <event> + <title>FreeBSD.org systems moving</title> + + <p>The FreeBSD.org servers handling mail, web, CVS etc. for + the FreeBSD Project will be moving to a new data-center + soon. The move is currently scheduled to take place on + Monday November 13th (US Pacific Standard Time).</p> + + <p>Due to preparations for the move there may be short + outages when FreeBSD.org services are not working in the + time up to the actual move. On the day of the move only + the static parts (IE. plain HTML pages, no CGI) of <a + href="http://www.FreeBSD.org/">http://www.FreeBSD.org/</a> + will work.</p> + </event> + </day> + </month> + + <month> + <name>10</name> + + <day> + <name>31</name> + <event> + <title>FreeBSD 6.2-BETA3 Available</title> + + <p>The third beta release of FreeBSD 6.2 is now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2006-November/030277.html">available</a>. + ISO images for Tier-1 architectures are now available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD mirror sites</a>.</p> + </event> + </day> + + <day> + <name>25</name> + <event> + <title>Summer of Code Projects Completed</title> + + <p>We are happy to report that all 14 students successfully + completed their FreeBSD <a + href="&base;/projects/summerofcode-2006.html">Summer of + Code</a> projects. Congratulations to both mentors and + students, and thanks to <a + href="http://www.google.com/bsd">Google</a> for running + this program and providing funding.</p> + + </event> + </day> + + <day> + <name>19</name> + <event> + <title>June-October, 2006 Status Report</title> + + <p>The June-October, 2006 Status Report is <a + href="&base;/news/status/report-2006-06-2006-10.html">now + available</a> with 49 entries.</p> + </event> + </day> + + <day> + <name>14</name> + <event> + <title>GNOME 2.16.1 Released for FreeBSD</title> + + <p>GNOME 2.16.1 has been released, and merged into the FreeBSD + ports tree. Check out the + <a href="&base;/gnome/index.html">FreeBSD GNOME homepage</a> + for the official announcement as well as important + <a href="&base;/gnome/docs/faq216.html">upgrade + instructions</a>.</p> + </event> + </day> + + <day> + <name>8</name> + <event> + <title>New committer: <a + href="mailto:syrinx@FreeBSD.org">Shteryana Shopova</a> + (src). An SoC2006 alumnus.</title> + + <p><a + href="mailto:syrinx@FreeBSD.org">Shteryana Shopova</a>, a + successful student from last year's Summer of Code + program, has continued working with the FreeBSD Project + and is now a full src/ committer.</p> + </event> + </day> + + <day> + <name>5</name> + <event> + <title>FreeBSD 6.2-BETA2 Available</title> + + <p>The second beta release of FreeBSD 6.2 is now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2006-October/029171.html">available</a>. + ISO images for Tier-1 architectures are now available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD mirror sites</a>.</p> + </event> + </day> + </month> + <month> + <name>9</name> + + <day> + <name>28</name> + <event> + <p>New committer: <a href="mailto:xride@FreeBSD.org">Soeren Straarup</a> (ports)</p> + </event> + </day> + + <day> + <name>21</name> + <event> + <p>New committer: <a href="mailto:jfv@FreeBSD.org">Jack F. Vogel</a> + (src)</p> + </event> + + <event> + <title>FreeBSD 6.2-BETA1 Available</title> + + <p>The first beta version of FreeBSD 6.2 is now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2006-September/028584.html">available</a>. + The BETA1 ISO images are available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD Mirror sites</a>.</p> + </event> + </day> + + <day> + <name>20</name> + <event> + <p>New committer: <a href="mailto:chinsan@FreeBSD.org">Chin-San Huang</a> + (doc)</p> + </event> + </day> + + <day> + <name>18</name> + <event> + <p>New committer: <a href="mailto:stas@FreeBSD.org">Stanislav Sedov</a> + (ports)</p> + </event> + </day> + + <day> + <name>12</name> + <event> + <p>New committer: <a href="mailto:alexbl@FreeBSD.org">Alexander Botero-Lowry</a> + (ports)</p> + </event> + </day> + + <day> + <name>1</name> + <event> + <p>New committer: <a href="mailto:rrs@FreeBSD.org">Randall R. Stewart</a> + (src)</p> + </event> + </day> + </month> + <month> + <name>8</name> + + <day> + <name>20</name> + <event> + <p>New committer: <a href="mailto:danger@FreeBSD.org">Daniel + Geržo</a> (doc)</p> + </event> + </day> + </month> + + <month> + <name>7</name> + + <day> + <name>26</name> + <event> + <title>New FreeBSD Core Team elected</title> + + <p>FreeBSD Core Team elections have been finished. + The announcement is available <a + href="http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/2006/freebsd-announce/20060730.freebsd-announce">here</a>. + </p> + </event> + </day> + + <day> + <name>19</name> + <event> + <title>Podcast Interview with FreeBSD Developer Greg Lehey</title> + + <p>In his latest <a href="http://bsdtalk.blogspot.com/">bsdtalk</a> + podcast, Will Backman interviews FreeBSD developer Greg Lehey + about his work on FreeBSD and MySQL. The podcast is available at + <a + href="http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk055.mp3"> + http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk055.mp3</a>.</p> + </event> + </day> + + <day> + <name>18</name> + <event> + <p>New committer: <a href="mailto:acm@FreeBSD.org">Jose Alonso Cardenas Marquez</a> + (ports)</p> + </event> + </day> + + <day> + <name>13</name> + <event> + <title>Podcast Interview with FreeBSD Developer Pawel Jakub Dawidek</title> + + <p>In his latest <a href="http://bsdtalk.blogspot.com/">bsdtalk</a> + podcast, Will Backman interviews FreeBSD developer Pawel Jakub Dawidek + about his work on FreeBSD, most notably the GEOM Journal project. The + podcast is available at <a + href="http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk052.mp3"> + http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk052.mp3</a>.</p> + </event> + </day> + + <day> + <name>12</name> + <event> + <title>April-June 2006 Status Report</title> + + <p>The April-June, 2006 status report is <a + href="&base;/news/status/report-2006-04-2006-06.html">now + available</a> with 39 entries.</p> + </event> + </day> + + <day> + <name>5</name> + <event> + <title>The FreeBSD Foundation Releases Java Binaries for FreeBSD 5.5, 6.1, and the AMD64 Platform</title> + + <p>The FreeBSD Foundation now provides native Java JDK and JRE + 1.5 binaries based on the latest UPDATE7 from Sun Microsystems. + For further details, please see the FreeBSD Foundation <a + href="http://www.freebsdfoundation.org/press/20060705-PRrelease.shtml"> + press release</a>.</p> + </event> + </day> + </month> + + <month> + <name>6</name> + + <day> + <name>24</name> + <event> + <p> + New committer: <a href="mailto:rafan@FreeBSD.org">Rong-En Fan</a> + (ports) + </p> + </event> + </day> + + <day> + <name>21</name> + <event> + <p> + New committer: <a href="mailto:bsam@FreeBSD.org">Boris Samorodov</a> + (ports) + </p> + </event> + </day> + + <day> + <name>19</name> + <event> + <p>New committer: <a + href="mailto:shaun@FreeBSD.org">Shaun Amott</a> + (ports)</p> + </event> + </day> + + <day> + <name>5</name> + <event> + <p>New committer: <a + href="mailto:kib@FreeBSD.org">Konstantin Belousov</a> + (src)</p> + </event> + + <event> + <p>New committer: <a + href="mailto:miwi@FreeBSD.org">Martin Wilke</a> + (ports)</p> + </event> + </day> + </month> + + <month> + <name>5</name> + <day> + <name>30</name> + <event> + <title>Funded Student Projects Announced</title> + + <p>The FreeBSD Project received over 120 applications for <a + href="http://code.google.com/summerofcode.html">Google's + Summer of Code</a> program, amongst which 14 were selected + for funding. Unfortunately, there were far more first rate + applications than available spots for students. However, + we encourage students to work together with us all year + round. The FreeBSD Project is always willing to help + mentor students learn more about operating system + development through our normal community mailing lists and + development forums. Contributing to an open source + software project is a valuable component of a computer + science education and great preparation for a career in + software development.</p> + + <p>A complete list of the winning students and projects is + available <a +href="http://www.freebsd.org/projects/summerofcode.html">here</a>. A <a +href="http://wiki.freebsd.org/moin.cgi/SummerOfCode2006">Summer of Code wiki</a> is also available with additional information.</p> + </event> + + <event> + <title>New committer: <a + href="mailto:piso@FreeBSD.org">Paolo Pisati</a> + (src). An SoC2005 alumnus.</title> + + <p><a href="mailto:piso@FreeBSD.org">Paolo Pisati</a>, a + successful student from last year's Summer of Code + program, has continued working with the FreeBSD Project + and is now a full src/ committer.</p> + + </event> + </day> + + <day> + <name>26</name> + <event> + <title>Podcast Interview with FreeBSD Developer Poul-Henning Kamp</title> + + <p>In his latest <a href="http://bsdtalk.blogspot.com/">bsdtalk</a> + podcast, Will Backman interviews FreeBSD developer Poul-Henning Kamp + about his work on FreeBSD. The podcast is available at <a + href="http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk048.mp3"> + http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk048.mp3</a>.</p> + </event> + </day> + + <day> + <name>25</name> + <event> + <title>FreeBSD 5.5-RELEASE Now Available</title> + + <p><a href="&base;/releases/5.5R/announce.html">FreeBSD + 5.5-RELEASE</a> is now available. Please check the <a + href="&base;/releases/5.5R/errata.html">errata</a> + before installation for any late-breaking news and/or + issues with this release. The <a + href="&base;/releases/index.html">Release Information</a> + page has more information about FreeBSD releases.</p> + </event> + </day> + + <day> + <name>21</name> + <event> + <title>FreeBSD Self-Hosting on the Sun T1 Processor</title> + + <p>FreeBSD is now able to complete a full run of the + "make buildworld" command on machines running the <a + href="http://www.sun.com/processors/UltraSPARC-T1/">Sun T1 processor + with CoolThreads technology</a>, and is thus self-hosting. + The code currently resides in the <a + href="http://perforce.freebsd.org/branchView.cgi?BRANCH=kmacy%5fsun4v"> + FreeBSD Perforce revision control system</a> and will be merged to + the official CVS repository when support for logical domaining + is complete. A log file of the boot process can be found <a + href="http://www.fsmware.com/sun4v/dmesg_latest.txt">here</a>.</p> + </event> + </day> + + <day> + <name>17</name> + <event> + <p>New committer: <a + href="mailto:twinterg@FreeBSD.org">Thomas Wintergerst</a> + (src)</p> + </event> + </day> + + <day> + <name>16</name> + + <event> + <title>FreeBSD 5.5-RC1 Available</title> + + <p>The first and most likely last release candidate of + FreeBSD 5.5 is now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2006-May/025589.html">available</a>. + The RC1 ISO images are available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD Mirror sites</a>.</p> + </event> + </day> + + <day> + <name>8</name> + <event> + <title>FreeBSD 6.1-RELEASE is Now Available</title> + + <p><a href="&base;/releases/6.1R/announce.html">FreeBSD + 6.1-RELEASE</a> has been released. Please check the <a + href="&base;/releases/6.1R/errata.html">release errata</a> + before installation for any late-breaking news and/or + issues with 6.1. The <a + href="&base;/releases/index.html">Release Information</a> + page has more information about FreeBSD releases.</p> + </event> + + <event> + <title>Summer of Code Deadline Extended 1 day</title> + + <p>The application period for Google's <a + href="http://code.google.com/summerofcode.html">Summer + of Code 2006</a> program has been extended until Tuesday + 11:00AM PDT. More information about FreeBSD specific + projects and potential mentors is available <a + href="&base;/projects/summerofcode.html">here</a>.</p> + </event> + + </day> + + <day> + <name>7</name> + <event> + <p>New committer: <a + href="mailto:itetcu@FreeBSD.org">Ion-Mihai Tetcu</a> + (ports)</p> + </event> + </day> + + <day> + <name>6</name> + <event> + <p>New committer: <a + href="mailto:stefan@FreeBSD.org">Stefan Walter</a> + (ports)</p> + </event> + + <event> + <p>New committer: <a + href="mailto:sat@FreeBSD.org">Andrew Pantyukhin</a> + (ports)</p> + </event> + </day> + + <day> + <name>2</name> + + <event> + <title>FreeBSD 6.1-RC2 Available</title> + + <p>The second and most likely last release candidate of + FreeBSD 6.1 is now <a + href="http://lists.freebsd.org/pipermail/freebsd-hackers/2006-May/016386.html">available</a>. + The RC2 ISO images are available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD Mirror sites</a>.</p> + </event> + </day> + + <day> + <name>1</name> + <event> + <title>Accepting Applications for Summer of Code</title> + + <p>The FreeBSD Project is now accepting applications for + the previously announced Google <a + href="http://code.google.com/summerofcode.html">Summer + of Code 2006</a> program. This program will provide + funding for students to spend the summer contributing to + open source software projects. A list of FreeBSD specific + projects and potential mentors is available <a + href="&base;/projects/summerofcode.html">here</a>.</p> + + <p>Once a suitable project and mentor have been identified, + interested students should complete a proposal and submit + it to Google. Proposals are now being accepted and the + final deadline is May 8, 2006 at 17:00 Pacific Daylight + Time (midnight May 9, 2006 0:00 UTC). Winning candidates + will be announced in late May. Please see the <a + href="http://code.google.com/soc/studentfaq.html">Student + FAQ</a> for more information.</p> + </event> + + <event> + <title>New Driver for HighPoint RocketRAID 232x SATA RAID Controllers</title> + + <p>A driver for HighPoint's RocketRAID 232x series of SATA + RAID controllers, rr232x(4), has been added to FreeBSD-CURRENT + as well as the RELENG_6 and RELENG_6_1 branches. It will + be included in the upcoming FreeBSD 6.1-RELEASE.</p> + </event> + + <event> + <p>Enhanced commit privileges: <a + href="mailto:delphij@FreeBSD.org">Xin LI</a> + (src, doc, ports)</p> + </event> + </day> + </month> + + <month> + <name>4</name> + + <day> + <name>30</name> + <event> + <p>New committer: <a + href="mailto:lbr@FreeBSD.org">Lars Balker Rasmussen</a> + (ports)</p> + </event> + </day> + + <day> + <name>15</name> + <event> + <title>Podcast Interview with FreeBSD Developer Joe Marcus Clarke</title> + + <p>In his latest <a href="http://bsdtalk.blogspot.com/">bsdtalk</a> + podcast, Will Backman interviews FreeBSD developer Joe Marcus Clarke + about the GNOME desktop environment on FreeBSD. The podcast is + available at <a + href="http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk032.mp3"> + http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk032.mp3</a>.</p> + </event> + </day> + + <day> + <name>14</name> + <event> + <title>January-March 2006 Status Report</title> + + <p>The January-March, 2006 status report is <a + href="&base;/news/status/report-2006-01-2006-03.html">now + available</a> with 29 entries.</p> + </event> + + <event> + <title>Summer of Code</title> + + <p>The FreeBSD Project is happy to participate in Google's + <a href="http://code.google.com/summerofcode.html">Summer + of Code 2006</a> program. This program will provide + funding for students to spend the summer contributing to + open source software projects. A list of FreeBSD specific + projects and potential mentors is available <a + href="&base;/projects/summerofcode.html">here</a>.</p> + </event> + </day> + + <day> + <name>13</name> + <event> + <title>FreeBSD 6.1-RC1 Available</title> + + <p>The first release candidate of FreeBSD 6.1 is now <a + href="http://lists.freebsd.org/pipermail/freebsd-hackers/2006-April/016104.html">available</a>. + The RC1 ISO images are available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD Mirror sites</a>.</p> + </event> + </day> + + <day> + <name>11</name> + <event> + <title>New Driver for Broadcom NetXtreme II Gigabit Ethernet Chips</title> + + <p>A driver for the Broadcom NetXtreme II family of Gigabit + Ethernet chips, bce(4), has been added to FreeBSD-CURRENT. + It will be merged to the FreeBSD 6-STABLE branch in the near + future.</p> + </event> + </day> + + <day> + <name>6</name> + <event> + <title>The FreeBSD Foundation Announces Java JDK and JRE 1.5 Binaries for FreeBSD</title> + + <p>The FreeBSD Foundation now provides native Java JDK and JRE + 1.5 binaries for FreeBSD. For further details, please see the + FreeBSD Foundation <a + href="http://www.freebsdfoundation.org/press/20060405-PRrelease.shtml"> + press release</a>.</p> + </event> + </day> + + <day> + <name>4</name> + <event> + <p>New committer: <a + href="mailto:alepulver@FreeBSD.org">Alejandro Pulver</a> + (ports)</p> + </event> + </day> + + <day> + <name>2</name> + <event> + <p>New committer: <a + href="mailto:johans@FreeBSD.org">Johan van Selst</a> + (ports)</p> + </event> + </day> + </month> + + <month> + <name>3</name> + + <day> + <name>31</name> + <event> + <p>New committer: <a + href="mailto:jmelo@FreeBSD.org">Jean Milanez Melo</a> + (ports)</p> + </event> + </day> + + <day> + <name>15</name> + <event> + <title>FreeBSD 5.5-BETA4 and 6.1-BETA4 Available</title> + + <p>The fourth beta releases of FreeBSD 5.5 and FreeBSD 6.1 are now <a + href="http://lists.freebsd.org/pipermail/freebsd-hackers/2006-March/015730.html">available</a>. + The respective BETA4 ISO images are available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD Mirror sites</a>.</p> + </event> + </day> + </month> + + <month> + <name>2</name> + + <day> + <name>22</name> + <event> + <p>New committer: <a + href="mailto:wkoszek@FreeBSD.org">Wojciech A. Koszek</a> + (src)</p> + </event> + </day> + + <day> + <name>20</name> + <event> + <title>FreeBSD 5.5-BETA2 and 6.1-BETA2 Available</title> + + <p>The second beta releases of FreeBSD 5.5 and FreeBSD 6.1 are now <a + href="http://lists.freebsd.org/pipermail/freebsd-hackers/2006-February/015499.html">available</a>. + The respective BETA2 ISO images are available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD Mirror sites</a>.</p> + </event> + </day> + + <day> + <name>18</name> + <event> + <title>Podcast Interview with FreeBSD Developer Kirk McKusick</title> + + <p>In his latest <a href="http://bsdtalk.blogspot.com/">bsdtalk</a> + podcast, Will Backman interviews FreeBSD developer Marshall Kirk + McKusick. The podcast is available at <a + href="http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk018.mp3"> + http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk018.mp3</a>.</p> + </event> + </day> + + <day> + <name>17</name> + <event> + <title>Podcast Interview with FreeBSD Release Engineer Scott Long</title> + + <p>In issue 17 of his <a href="http://bsdtalk.blogspot.com/">bsdtalk</a> + series of podcasts, Will Backman interviews FreeBSD release engineer + Scott Long about the upcoming FreeBSD 5.5 and 6.1 releases and + related topics. The podcast is available at <a + href="http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk017.mp3"> + http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk017.mp3</a>. + </p> + </event> + </day> + + <day> + <name>13</name> + <event> + <p>New committer: <a + href="mailto:cel@FreeBSD.org">Chuck Lever</a> + (src)</p> + </event> + + <event> + <title>Upcoming FreeBSD Kernel Code Reading Evening Course</title> + + <p>The ``FreeBSD Kernel Internals: An Intensive Code + Walkthrough'' course will be taught during the Spring of + 2006. The class will be held at the historic Hillside Club + at 2286 Cedar Strett, Berkeley, CA 94709 just three blocks + north of the Berkeley campus once per week from 6:30PM to + 9:45PM starting Wednesday February 22nd and finishing + Tuesday June 13th. You can get more information or sign up + for the class <a + href="http://www.mckusick.com/courses/adveveclass.html">here</a>.</p> + </event> + </day> + + <day> + <name>9</name> + <event> + <title>FreeBSD 5.5-BETA1 and 6.1-BETA1 Available</title> + + <p>The first beta releases of FreeBSD 5.5 and FreeBSD 6.1 are now <a + href="http://lists.freebsd.org/pipermail/freebsd-hackers/2006-February/015418.html">available</a>. + The respective BETA1 ISO images are available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD Mirror sites</a>.</p> + </event> + </day> + </month> + + <month> + <name>1</name> + + <day> + <name>31</name> + <event> + <p>Enhanced commit privileges: <a + href="mailto:cperciva@FreeBSD.org">Colin Percival</a> + (src, ports)</p> + </event> + </day> + + <day> + <name>26</name> + <event> + <title>October-December 2005 Status Report</title> + + <p>The October-December, 2005 status report is <a + href="&base;/news/status/report-2005-10-2005-12.html">now + available</a> with 26 entries.</p> + </event> + </day> + <day> + <name>19</name> + <event> + <p>New committer: <a + href="mailto:matteo@FreeBSD.org">Matteo Riondato</a> + (src)</p> + </event> + + <event> + <p>New committer: <a + href="mailto:vd@FreeBSD.org">Vasil Dimov</a> + (ports)</p> + </event> + </day> + + <day> + <name>16</name> + <event> + <p>New committer: <a + href="mailto:rink@FreeBSD.org">Rink Springer</a> + (src)</p> + </event> + </day> + </month> + </year> + +</news> diff --git a/en_US.ISO8859-1/htdocs/news/2006/press.xml b/en_US.ISO8859-1/htdocs/news/2006/press.xml new file mode 100644 index 0000000000..ac7dbe9563 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2006/press.xml @@ -0,0 +1,580 @@ +<?xml version="1.0"?> +<!DOCTYPE press PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Press//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/press.dtd"> +<!-- + COMMITTERS PLEASE NOTE: + News articles referenced in this file are also to be archived under + "freefall:/c/www/bsddoc/press/". +--> +<press> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD$ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2006</name> + + <month> + <name>12</name> + + <story> + <name>Secure email servers from scratch with FreeBSD 6 (Part 2)</name> + <url>http://www.freesoftwaremagazine.com/articles/secure_email_servers_from_scratch_with_freebsd_6_part_2</url> + <site-name>Free Software Magazine</site-name> + <site-url>http://www.freesoftwaremagazine.com/</site-url> + <date>13 December 2006</date> + <author>Yousef Ourabi</author> + <p>All the bells and whistles of a high end-mail setup: web-mail, + anti-virus filtering, spam filtering, and hosting unlimited domains + with virtual domains and users stored in MySQL.</p> + </story> + + <story> + <name>Installing FreeBSD 6.1</name> + <url>http://www.openaddict.com/installing_freebsd_6_1.html</url> + <site-name>OpenAddict</site-name> + <site-url>http://www.openaddict.com/</site-url> + <date>11 December 2006</date> + <author>Sharaz</author> + <p>An article that guides the reader through an installation of + FreeBSD 6.1.</p> + </story> + + <story> + <name>Quick and Dirty Guide to Deploying a FreeBSD 6.1 Server</name> + <url>http://www.openaddict.com/quick_and_dirty_guide_to_deploying_a_freebsd_6_1_server.html</url> + <site-name>OpenAddict</site-name> + <site-url>http://www.openaddict.com/</site-url> + <date>08 December 2006</date> + <author>Rich Morgan</author> + <p>An article showing how to configure a FreeBSD 6.1 server with + Apache, Webmin, PHP 5, MySQL 5.0, Sendmail with SMTP-AUTH, Bind + DNS, SNMP, and synchronized local time.</p> + </story> + + <story> + <name>China Develops Server OS; Lenovo On Board</name> + <url>http://www.pacificepoch.com/newsstories/82819_0_5_0_M/</url> + <site-name>Pacific Epoch</site-name> + <site-url>http://www.pacificepoch.com/</site-url> + <date>04 December 2006</date> + <author>Zhengqian Zhou</author> + <p>China's Ministry of Science and Technology (MOST) has announced + that China has completed development of a server operating + system based on FreeBSD.</p> + </story> + </month> + + <month> + <name>11</name> + + <story> + <name>FreeBSD Security Event Auditing</name> + <url>http://www.securityfocus.com/columnists/422</url> + <site-name>Security Focus</site-name> + <site-url>http://www.securityfocus.com/</site-url> + <date>10 November 2006</date> + <author>Federico Biancuzzi</author> + <p>An interview with FreeBSD developer Robert Watson on the features of + the new audit subsystem in FreeBSD 6.2.</p> + </story> + + <story> + <name>FreeBSD Puts Out 6.2 Beta 3 Release</name> + <url>http://www.itjungle.com/tug/tug110906-story06.html</url> + <site-name>IT Jungle</site-name> + <site-url>http://www.itjungle.com/</site-url> + <date>9 November 2006</date> + <author>Timothy Prickett Morgan</author> + <p>News about the upcoming 6.2 release, and coverage of the new + features in FreeBSD 7.</p> + </story> + </month> + + <month> + <name>10</name> + + <story> + <name>Secure email servers from scratch with FreeBSD 6.1 (part 1)</name> + <url>http://www.freesoftwaremagazine.com/articles/secure_email_server_bsd_part_1</url> + <site-name>Free Software Magazine</site-name> + <site-url>http://www.freesoftwaremagazine.com/</site-url> + <date>25 October 2006</date> + <author>Yousef Ourabi</author> + <p>Build a secure email server with FreeBSD, Postifx, ClamAV, + Spamassasin, and MySQL</p> + </story> + + <story> + <name>Enterprise Unix Roundup: PC-BSD May Be the Next Linux</name> + <url>http://www.serverwatch.com/eur/article.php/3640151</url> + <site-name>ServerWatch.com</site-name> + <site-url>http://www.serverwatch.com/</site-url> + <date>25 October 2006</date> + <author>Brian Proffitt</author> + <p>Commentary in the trade press on the acquisition of FreeBSD-based + PC-BSD by iXsystems.</p> + </story> + + <story> + <name>Why iXsystems Bought PC-BSD</name> + <url>http://www.onlamp.com/pub/a/bsd/2006/10/23/ixsystems-pc-bsd.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>23 October 2006</date> + <author>Dru Lavigne</author> + <p>An interview with Kris Moore and Matt Olander on the + acquisition of PC-BSD by iXsystems Inc.</p> + </story> + + <story> + <name>Build a Nas device using virtualisation</name> + <url>http://www.itweek.co.uk/2166671</url> + <site-name>IT Week</site-name> + <site-url>http://www.itweek.co.uk/</site-url> + <date>18 October 2006</date> + <author>Alan Stevens</author> + <p>Create your own virtual network-attached storage appliance using + FreeBSD-based FreeNAS in a VMWare virtual machine.</p> + </story> + + <story> + <name>Desktop FreeBSD: Fully Optimized 6.x Installation</name> + <url>http://www.ofb.biz/safari/article/402.html</url> + <site-name>Open For Business</site-name> + <site-url>http://www.ofb.biz/</site-url> + <date>12 October 2006</date> + <author>Ed Hurst</author> + <p>This article describes the process of (re)building a FreeBSD + system from source code with an aim to improve its performance.</p> + </story> + + <story> + <name>FreeBSD based PC-BSD Gets 'Acquired'</name> + <url>http://www.internetnews.com/dev-news/article.php/3637341</url> + <site-name>InternetNews.com</site-name> + <site-url>http://www.internetnews.com/</site-url> + <date>12 October 2006</date> + <author>Sean Michael Kerner</author> + <p>iXsystems Inc. acquires the trademarks and intellectual property + rights associated with PC-BSD, a desktop operating system based + on FreeBSD.</p> + </story> + + <story> + <name>Turn an Old Laptop Into a Portable Network-Troubleshooting + System</name> + <url>http://www.techbuilder.org/recipes/193105146</url> + <site-name>TechBuilder</site-name> + <site-url>http://www.techbuilder.org/</site-url> + <date>09 October 2006</date> + <author>David S. Markowitz</author> + <p>How to build a network monitoring system using an old laptop and + FreeBSD.</p> + </story> + + <story> + <name>Desktop FreeBSD: 64-bit Future</name> + <url>http://www.ofb.biz/safari/article/400.html</url> + <site-name>Open For Business</site-name> + <site-url>http://www.ofb.biz/</site-url> + <date>04 October 2006</date> + <author>Ed Hurst</author> + <p>The article's author reports excellent results after building a + 64-bit FreeBSD-based desktop computer.</p> + </story> + </month> + + <month> + <name>9</name> + + <story> + <name>Win4BSD has been released</name> + <url>http://win4bsd.com/content/index.php?option=com_content&task=view&id=20&Itemid=2</url> + <site-name>Win4BSD</site-name> + <site-url>http://www.win4bsd.com/</site-url> + <date>25 September 2006</date> + <author>Dan Perlman</author> + <p>Virtual Bridges, a provider of enterprise and SMB solutions + using virtualization for business, announced today the release + of Win4BSD Pro Desktop™. Win4BSD Pro Desktop runs as a + &os;/PC-BSD application and allows users to run Windows + Applications and Desktops with seamless ease on the BSD + platform.</p> + </story> + + <story> + <name>POSIX Asynchronous I/O</name> + <url>http://www.informit.com/articles/article.asp?p=607373&seqNum=1&rl=1</url> + <site-name>InformIT</site-name> + <site-url>http://www.informit.com/</site-url> + <date>22 September 2006</date> + <author>David Chisnall</author> + <p>A look at programming with asynchronous I/O in FreeBSD and other + open-source OSes.</p> + </story> + + <story> + <name>DesktopBSD 1.0: FreeBSD for the desktop</name> + <url>http://os.newsforge.com/os/06/09/01/2053249.shtml</url> + <site-name>NewsForge</site-name> + <site-url>http://www.newsforge.com/</site-url> + <date>11 September 2006</date> + <author>Stefan Vrabie</author> + <p>A review of DesktopBSD 1.0.</p> + </story> + + <story> + <name>A (late) look at FreeBSD 6.1</name> + <url>http://weblog.infoworld.com/venezia/archives/007779.html</url> + <site-name>InfoWorld</site-name> + <site-url>http://www.infoworld.com/</site-url> + <date>06 September 2006</date> + <author>Paul Venezia</author> + <p>The author describes the setup of a FreeBSD 6.1 based mail server + and web host using software RAID and PF.</p> + </story> + </month> + + <month> + <name>8</name> + + <story> + <name>VMware's Virtual Appliance Challenge - and the Winner is?</name> + <url>http://weblog.infoworld.com/virtualization/archives/2006/08/vmwares_virtual_1.html</url> + <site-name>InfoWorld</site-name> + <site-url>http://www.infoworld.com/</site-url> + <date>15 August 2006</date> + <author>David Marshall</author> + <p>The FreeBSD based FreeNAS storage server project wins an award in VMWare Inc.'s + virtualization contest.</p> + </story> + + <story> + <name>Advanced Installation Tasks in FreeBSD 6</name> + <url>http://www.informit.com/articles/article.asp?p=597694&rl=1</url> + <site-name>InformIT</site-name> + <site-url>http://www.informit.com</site-url> + <date>11 August 2006</date> + <author>Brian Tiemann</author> + <p>An excerpt from the book "FreeBSD 6 Unleashed" covering the ins and + outs of non-standard FreeBSD installations.</p> + </story> + + <story> + <name>PC-BSD: The Most Beginner Friendly OS</name> + <url>http://www.osweekly.com/index.php?option=com_content&task=view&id=2287&Itemid=449</url> + <site-name>OSWeekly.com</site-name> + <site-url>http://www.osweekly.com/</site-url> + <date>10 August 2006</date> + <author>Matt Hartley</author> + <p>A review of PC-BSD, covering installation and package management.</p> + </story> + + <story> + <name>The BSD Unix Projects Keep Humming Along</name> + <url>http://www.itjungle.com/breaking/bn080206-story01.html</url> + <site-name>ITJungle</site-name> + <site-url>http://www.itjungle.com/</site-url> + <date>2 August 2006</date> + <author>Timothy Prickett Morgan</author> + <p>This article covers the FreeBSD project's Sparc (T1) porting + effort and mentions the scalability improvements in + recent releases. New developments in the other BSD projects + also get a mention.</p> + </story> + + <story> + <name>Working with gmirror on a Sun Fire X2100</name> + <url>http://ezine.daemonnews.org/200608/gmirror_1.html</url> + <site-name>DaemonNews</site-name> + <site-url>http://www.daemonnews.org/</site-url> + <date>August 2006</date> + <author>Grzegorz Czaplinski</author> + <p>The first of a two part series on building up and tearing down + a gmirror system.</p> + </story> + </month> + + <month> + <name>7</name> + + <story> + <name>CBC's web site using Open Source everywhere!</name> + <url>http://www.insidethecbc.com/2006/07/15/under-the-hood-at-cbcca-open-source</url> + <site-name>InsideTheCBC.com</site-name> + <site-url>http://www.insidethecbc.com/</site-url> + <date>15 July 2006</date> + <author>Blake Crosby</author> + <p>An article by the Canadian Broadcasting Corporation describes their use + of FreeBSD in their IT infrastructure.</p> + </story> + + <story> + <name>Interview with Andy Ritger and Christian Zander from NVIDIA</name> + <url>http://bsdtalk.blogspot.com/2006/07/bsdtalk054-interview-with-andy-ritger.html</url> + <site-name>BSDTalk</site-name> + <site-url>http://bsdtalk.blogspot.com/</site-url> + <date>14 July 2006</date> + <author>Will Backman</author> + <p>Will Backman speaks with Andy Ritger and Christian Zander from NVIDIA + about the NVIDIA FreeBSD graphics driver. The interview gives an + overview of the drivers current features, plans for future + improvements, and a brief discussion about licensing and NVIDIA's + open source efforts.</p> + </story> + + <story> + <name>Using DesktopBSD</name> + <url>http://www.onlamp.com/pub/a/bsd/2006/07/13/FreeBSDBasics.html</url> + <site-name>OnLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>13 July 2006</date> + <author>Dru Lavigne</author> + <p>This article explores DesktopBSD, a desktop oriented and easy-to-use + version of FreeBSD 5.5.</p> + </story> + + <story> + <name>PC-BSD works for community center</name> + <url>http://os.newsforge.com/os/06/06/23/1442207.shtml?tid=8</url> + <site-name>NewsForge</site-name> + <site-url>http://www.newsforge.com/</site-url> + <date>03 July 2006</date> + <author>Henry Gillow-Wiles</author> + <p>An IT director for a non-profit community center is happy with the + speed, stability and hardware compatibility of the FreeBSD-based + PC-BSD operating system on low-end hardware.</p> + </story> + </month> + + <month> + <name>6</name> + + <story> + <name>Build a Mail Server with Commodity Hardware and FreeBSD, + Part 2</name> + <url>http://www.techbuilder.org/article/189400686</url> + <site-name>TechBuilder</site-name> + <site-url>http://www.techbuilder.org/</site-url> + <date>12 June 2006</date> + <author>David S. Markowitz</author> + <p>Part 2 of a TechBuilder recipe covers adding virus protection, spam detection + and webmail access to a mail server built using FreeBSD and a PC.</p> + </story> + + <story> + <name>Six Hosting Companies Most Reliable Hoster in May</name> + <url>http://news.netcraft.com/archives/2006/06/06/six_hosting_companies_most_reliable_hoster_in_may.html</url> + <site-name>Netcraft</site-name> + <site-url>http://www.netcraft.com/</site-url> + <date>06 June 2006</date> + <author>Mandy</author> + <p>A Netcraft survey for May 2006 indicates that FreeBSD is being + used by four out of five most reliable Internet hosting companies + in the world.</p> + </story> + + <story> + <name>Build a Mail Server with Commodity Hardware and FreeBSD, + Part 1</name> + <url>http://www.techbuilder.org/article/188701471</url> + <site-name>TechBuilder</site-name> + <site-url>http://www.techbuilder.org/</site-url> + <date>05 June 2006</date> + <author>David S. Markowitz</author> + <p>How to use a PC and FreeBSD to build a mail server for a small + or medium business.</p> + </story> + </month> + + <month> + <name>5</name> + + <story> + <name>A look at the FreeNAS server</name> + <url>http://hardware.newsforge.com/hardware/06/05/19/1349206.shtml?tid=69</url> + <site-name>NewsForge</site-name> + <site-url>http://www.newsforge.com/</site-url> + <date>30 May 2006</date> + <author>Gary Sims</author> + <p>A review of FreeNAS, a FreeBSD-based network attached storage product.</p> + </story> + + <story> + <name>DTrace reaches prime time on FreeBSD</name> + <url>http://www.zdnet.com.au/news/software/soa/DTrace_reaches_prime_time_on_FreeBSD/0,2000061733,39257452,00.htm</url> + <site-name>ZDNet Australia</site-name> + <site-url>http://www.zdnet.com.au/</site-url> + <date>29 May 2006</date> + <author>Renai LeMay</author> + <p>ZDNet article about DTrace on FreeBSD.</p> + </story> + + <story> + <name>BSD Packaging Systems</name> + <url>http://www.informit.com/articles/article.asp?p=471098&rl=1</url> + <site-name>InformIT.com</site-name> + <site-url>http://www.informit.com/</site-url> + <date>26 May 2006</date> + <author>David Chisnall</author> + <p>An article on package management in the BSD family of operating systems.</p> + </story> + + <story> + <name>Interview with Karl Lehenbauer of FlightAware</name> + <url>http://bsdtalk.blogspot.com/2006/05/bsdtalk042-interview-with-karl.html</url> + <site-name>BSDTalk</site-name> + <site-url>http://bsdtalk.blogspot.com/</site-url> + <date>15 May 2006</date> + <author>Will Backman</author> + <p><a href="http://www.amd.com/us-en/Corporate/VirtualPressRoom/0,,51_104_566~107687,00.html">FlightAware + uses FreeBSD/amd64 systems</a> to track the locations of + up to 70,000 flights per day. Will Backman speaks with Karl Lehenbauer + about how FlightAware is successfully using FreeBSD with other + open source technologies to drive their product.</p> + </story> + + <story> + <name>FreeBSD vows to compete with desktop Linux</name> + <url>http://news.com.com/2100-1011_3-6071598.html</url> + <site-name>News.com</site-name> + <site-url>http://news.com.com/</site-url> + <date>12 May 2006</date> + <author>Ingrid Marson</author> + <p>ZDNet article about FreeBSD's upcoming desktop features.</p> + </story> + + <story> + <name>FreeBSD 6.1 Review</name> + <url>http://www.softwareinreview.com/cms/content/view/37/1/</url> + <site-name>Software in review</site-name> + <site-url>http://www.softwareinreview.com/</site-url> + <date>12 May 2006</date> + <author>Jem Matzan</author> + <p>A review of FreeBSD 6.1 for the amd64 architecture.</p> + </story> + + <story> + <name>Stability in FreeBSD 6.1</name> + <url>http://www.internetnews.com/dev-news/article.php/3605211</url> + <site-name>InternetNews.com</site-name> + <site-url>http://www.internetnews.com/</site-url> + <date>10 May 2006</date> + <author>Sean Michael Kerner</author> + <p>An article describing the FreeBSD project's focus on stability + and quality for its 6.1 and 5.5 releases.</p> + </story> + + </month> + + <month> + <name>4</name> + + <story> + <name>Interview: Deb Goodkin from the FreeBSD Foundation</name> + <url>http://blogs.ittoolbox.com/unix/bsd/archives/008670.asp</url> + <site-name>Blog: A Year in the Life of a BSD Guru</site-name> + <site-url>http://blogs.ittoolbox.com/unix/bsd/</site-url> + <date>11 April 2006</date> + <author>Dru Lavigne</author> + <p>In this interview, Deb Goodkin provides some pieces of interesting + information about the inner working of the FreeBSD Foundation.</p> + </story> + + <story> + <name>Interview: John Baldwin on FreeBSD</name> + <url>http://blogs.ittoolbox.com/unix/bsd/archives/008672.asp</url> + <site-name>Blog: A Year in the Life of a BSD Guru</site-name> + <site-url>http://blogs.ittoolbox.com/unix/bsd/</site-url> + <date>10 April 2006</date> + <author>Dru Lavigne</author> + <p>In this interview, John Baldwin of the FreeBSD project gives + some insight on what it is like to be a FreeBSD developer and + some of the things that happen behind the scenes of a large Open + Source project.</p> + </story> + </month> + + <month> + <name>3</name> + + <story> + <name>Setting up Linux compatibility on FreeBSD 6</name> + <url>http://os.newsforge.com/os/06/03/22/1531252.shtml?tid=8&tid=2</url> + <site-name>Newsforge</site-name> + <site-url>http://www.newsforge.com/</site-url> + <date>31 March 2006</date> + <author>Gordon McEwen</author> + <p>A guide to configuring and running Linux applications on a FreeBSD 6 + system.</p> + </story> + </month> + + <month> + <name>2</name> + + <story> + <name>Network Filtering by Operating System</name> + <url>http://www.onlamp.com/pub/a/bsd/2006/02/16/os_fingerprint_filtering.html</url> + <site-name>Onlamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>16 February 2006</date> + <author>Avleen Vig</author> + <p>Keep worms and malware from monopolizing your network + connection using FreeBSD, pf, ALTQ, and squid.</p> + </story> + + <story> + <name>Opening the digital doorway for South African youth</name> + <url>http://www.tectonic.co.za/view.php?id=859</url> + <site-name>tectonic</site-name> + <site-url>http://www.tectonic.co.za/</site-url> + <date>08 February 2006</date> + <author>Lunga Madlala</author> + <p>An article mentioning the use of FreeBSD in so called + "Digital Doorways" in South African provinces.</p> + </story> + </month> + + <month> + <name>1</name> + + <story> + <name>BSD: The Other Free UNIX Family</name> + <url>http://www.informit.com/articles/article.asp?p=439601&rl=1</url> + <site-name>InformIT</site-name> + <site-url>http://www.informit.com/</site-url> + <date>20 January 2006</date> + <author>David Chisnall</author> + <p>An introduction to the open-source BSD operating systems.</p> + </story> + + <story> + <name>Interview: Dru Lavigne, BSD Certification Group</name> + <url>http://business.newsforge.com/business/06/01/13/173233.shtml?tid=35&tid=8</url> + <site-name>Newsforge</site-name> + <site-url>http://www.newsforge.com/</site-url> + <date>20 January 2006</date> + <author>Federico Biancuzzi</author> + <p>An interview with the founder of the BSD Certification Group, + a non-profit organization established to create certification + standards for BSD-based operating systems.</p> + </story> + + <story> + <name>Running Commercial Linux Software on FreeBSD</name> + <url>http://www.onlamp.com/pub/a/bsd/2006/01/12/Big_Scary_Daemons.html</url> + <site-name>Onlamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>12 January 2006</date> + <author>Michael W. Lucas</author> + <p>The author shows how to use software built for a + Linux-based OS on FreeBSD.</p> + </story> + </month> + </year> + +</press> diff --git a/en_US.ISO8859-1/htdocs/news/2007/Makefile b/en_US.ISO8859-1/htdocs/news/2007/Makefile new file mode 100644 index 0000000000..5965ae5945 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2007/Makefile @@ -0,0 +1,16 @@ +# $FreeBSD$ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +XMLDOCS+= index:${XSL_NEWS_NEWSFLASH_OLD}:news.xml: +DEPENDSET.index=transtable news + +XMLDOCS+= press:${XSL_NEWS_PRESS_OLD}:: +DEPENDSET.press=transtable press + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/news/2007/news.xml b/en_US.ISO8859-1/htdocs/news/2007/news.xml new file mode 100644 index 0000000000..243dce1529 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2007/news.xml @@ -0,0 +1,836 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE news PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for News//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/news.dtd"> + +<!-- Simple schema for FreeBSD Project news. + + Divide time in to <year>, <month>, and <day> elements, each of which + has a <name>. + + each <day> element contains one or more <event> elements. + + Each <event> contains an optional <title>, and then a <p>. <p> elements + can contain <a> anchors. + + Use the <title> element if the <p> content is lengthy. When generating + synopses of this information (e.g., for syndication using RDF files), + the contents of <title> will be preferred over <p>. +--> + +<news> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD$ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2007</name> + + <month> + <name>12</name> + + <day> + <name>31</name> + <event> + <title>FreeBSD 6.3-RC2 Available</title> + + <p>The second release candidate of FreeBSD 6.3 has been <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2007-December/039352.html">announced</a>. + ISO images and distributions for Tier-1 architectures are + now available on most of the <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD mirror sites</a>.</p> + </event> + </day> + + <day> + <name>30</name> + <event> + <title>FreeBSD 7.0-RC1 Available</title> + + <p>The first release candidate of FreeBSD 7.0 is now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2007-December/039334.html">available</a>. + ISO images for Tier-1 architectures are now available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD mirror sites</a>.</p> + </event> + </day> + + <day> + <name>28</name> + <event> + <p>New committer: <a href="mailto:weongyo@FreeBSD.org">Weongyo Jeong</a> + (src)</p> + </event> + </day> + + <day> + <name>26</name> + <event> + <p>New committer: <a href="mailto:raj@FreeBSD.org">Rafal Jaworowski</a> + (src)</p> + </event> + </day> + + <day> + <name>25</name> + <event> + <title>Juniper Networks, Inc has donated a reference FreeBSD + port to the MIPS architecture</title> + + <p>Juniper Networks, Inc. (http://www.juniper.net) has donated a + reference FreeBSD port to the MIPS architecture to The FreeBSD + Project. + This code will be used as one reference for creating an official + project-supported FreeBSD/MIPS offering.</p> + <p>Information about the code drop can be found <a + href="http://people.freebsd.org/~obrien/juniper-mips.html">here</a>.</p> + </event> + </day> + + <day> + <name>10</name> + <event> + <title>End-of-Year Fund Raising Drive</title> + + <p>The <a href="http://www.freebsdfoundation.org">FreeBSD + Foundation</a> has announced an End-of-Year Fund Raising + Drive. The goal this year is to raise over $250,000. + This money is used for sponsoring FreeBSD related conferences, + providing travel grants to developers to attend these conferences, + providing grants for projects that improve FreeBSD, and + providing legal support on issues like understanding + the GPLv3 impact on FreeBSD, trademarks, and other legal + issues that come up.</p> + + <p>Donations can be made online from <a + href="http://www.freebsdfoundation.org/donate/">http://www.freebsdfoundation.org/donate/</a>.</p> + </event> + </day> + + <day> + <name>5</name> + <event> + <title>&os; 7.0-BETA4 Available</title> + + <p>The &os; 7.0 release process proceeds and as a consequence + the 7.0-BETA4 ISO images for Tier-1 architectures are now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2007-December/038873.html"> + available</a> for download on most <a + href="&enbase;/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + &os; mirror sites</a>. We ask our users to report any + outstanding bugs, as this will presumably be the last BETA + release before the first RC release.</p> + </event> + </day> + </month> + + <month> + <name>11</name> + + <day> + <name>29</name> + + <event> + <title>FreeBSD 6.3-RC1 Available</title> + + <p>The first release candidate of FreeBSD 6.3 has been <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2007-November/038670.html">announced</a>. + ISO images and distributions for Tier-1 architectures are now available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD mirror sites</a>.</p> + </event> + </day> + + <day> + <name>19</name> + <event> + <title>&os; 7.0-BETA3 Available</title> + + <p>The &os; 7.0 release process proceeds and as a consequence + the 7.0-BETA3 ISO images for Tier-1 architectures are now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2007-November/038388.html"> + available</a> for download on most <a + href="&enbase;/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + &os; mirror sites</a>. We ask our users to report any + outstanding bugs.</p> + </event> + </day> + + <day> + <name>4</name> + <event> + <title>&os; 7.0-BETA2 Available</title> + + <p>The &os; 7.0 release process proceeds and as a consequence + the 7.0-BETA2 ISO images for Tier-1 architectures are now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2007-November/037966.html"> + available</a> for download on most <a + href="&enbase;/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + &os; mirror sites</a>. We ask our users to report any + outstanding bugs, as this will presumably be the last BETA + release before the first RC release.</p> + </event> + </day> + + <day> + <name>1</name> + <event> + <p>New committer: <a href="mailto:brix@FreeBSD.org">Henrik Brix Andersen</a> + (ports)</p> + </event> + </day> + </month> + + <month> + <name>10</name> + + <day> + <name>27</name> + <event> + <title>The FreeBSD Foundation auctions the first copy of the book + "Absolute &os;, 2nd Edition"</title> + + <p>The &os; Foundation has started its Fall Fund-Raising + Campaign with an auction of the first copy of the book + "Absolute &os;, 2nd Edition" which was graciously + donated by the author Michael Lucas. The winner of this + auction will get a laser-printed Certificate of Authenticity + together with a signed bookplate. All proceeds will go to + The &os; Foundation! The bidding ends on November 2nd. + More information is available on <a + href="http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=120175384688&ssPageName=ADME:L:LCA:US:1123">eBay</a>.</p> + </event> + </day> + + <day> + <name>26</name> + <event> + <p>Enhanced commit privileges: <a href="mailto:miwi@FreeBSD.org">Martin Wilke</a> + (ports, doc)</p> + </event> + </day> + + <day> + <name>25</name> + <event> + <title>New committer: <a href="mailto:lulf@FreeBSD.org">Ulf Lilleengen</a> + (src). SoC2007 alumnus.</title> + + <p><a href="mailto:lulf@FreeBSD.org">Ulf Lilleengen</a> is now a src/ + committer. He participated in the Summer of Code program, where he + worked on gvinum. In FreeBSD, Ulf will continue to work on gvinum, + as well as csup and filesystem-related parts.</p> + </event> + </day> + <day> + <name>22</name> + <event> + <title>&os; 7.0-BETA1 Available</title> + + <p>The final stage of the &os;-7.0 Release cycle has begun + with the first beta release. The &os; 7.0-BETA1 ISO images + for Tier-1 architectures are now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2007-October/037539.html">available</a> + for download on most of the <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + &os; mirror sites</a>. The more people that test and + report bugs, the better &os; 7.0-RELEASE will be. For more + information about the &os; 7.0 release process, please check + the official <a + href="http://www.freebsd.org/releases/7.0R/schedule.html">schedule</a> + and the <a + href="http://www.freebsd.org/releases/7.0R/todo.html">todo</a> + list.</p> + </event> + </day> + <day> + <name>10</name> + <event> + <title>July-October, 2007 Status Reports</title> + + <p>The July-October, 2007 Status Reports is <a + href="&enbase;/news/status/report-2007-07-2007-10.html">now + available</a> with 21 entries.</p> + </event> + </day> + <day> + <name>3</name> + <event> + <title>PC-BSD 1.4 Released</title> + + <p>PC-BSD 1.4 has just been released. PC-BSD is a + successful desktop operating system based on FreeBSD that + focuses on providing an easy to use desktop system for + casual computer users. The release may be <a + href="http://www.pcbsd.org">downloaded</a> or <a + href="http://www.freebsdmall.com">purchased</a> on CD.</p> + </event> + </day> + </month> + + <month> + <name>9</name> + + <day> + <name>28</name> + <event> + <title>New committer: <a href="mailto:kaiw@FreeBSD.org">Kai Wang</a> + (src). SoC2007 alumnus.</title> + + <p><a href="mailto:kaiw@FreeBSD.org">Kai Wang</a>, a + student in the Summer of Code program, is now a + src/ committer.</p> + </event> + </day> + <day> + <name>25</name> + <event> + <title>New committer: <a href="mailto:rpaulo@FreeBSD.org">Rui Paulo</a> + (src). SoC2007 alumnus.</title> + + <p><a href="mailto:rpaulo@FreeBSD.org">Rui Paulo</a>, a + student in the Summer of Code program, is now a full + src/ committer.</p> + </event> + </day> + <day> + <name>17</name> + <event> + <title>Summer of Code Projects Completed</title> + + <p>We are happy to report that 22 students successfully + completed their FreeBSD <a + href="&enbase;/projects/summerofcode-2007.html">Summer of + Code</a> projects. Congratulations to both mentors and + students, and thanks to <a + href="http://www.google.com/">Google</a> for running + this program and providing funding.</p> + + </event> + </day> + </month> + + <month> + <name>8</name> + + <day> + <name>29</name> + <event> + <title>FreeBSD Foundation August 2007 newsletter</title> + + <p>The FreeBSD Foundation has published their + <a href="http://www.freebsdfoundation.org/press/2007Aug-newsletter.shtml"> + August 2007 newsletter</a> which summarizes their activities + so far this year.</p> + </event> + </day> + + <day> + <name>20</name> + <event> + <p>New committer: <a href="mailto:tabthorpe@FreeBSD.org">Thomas Abthorpe</a> + (ports)</p> + </event> + </day> + + <day> + <name>2</name> + <event> + <title>IPv6 live at the FreeBSD.org cluster</title> + + <p>Most of the machines and services in the FreeBSD.org cluster + are now available through IPv6. This includes www, mail and + developer ssh access. Connectivity is provided from ISC using + a tunnel.</p> + </event> + + <event> + <p>New committer: <a href="mailto:loader@FreeBSD.org">Fukang Chen</a> + (doc)</p> + </event> + </day> + </month> + + <month> + <name>7</name> + + <day> + <name>10</name> + <event> + <title>April-June, 2007 Status Report</title> + + <p>The April-June, 2007 Status Report is <a + href="&enbase;/news/status/report-2007-04-2007-06.html">now + available</a> with 49 entries.</p> + </event> + </day> + + <day> + <name>9</name> + <event> + <p>New committer: <a href="mailto:lme@FreeBSD.org">Lars Engels</a> + (ports)</p> + </event> + </day> + </month> + + <month> + <name>6</name> + + <day> + <name>25</name> + <event> + <p>Enhanced commit privileges: <a href="mailto:edwin@FreeBSD.org">Edwin Groothuis</a> + (src, ports)</p> + </event> + </day> + + <day> + <name>24</name> + <event> + <p>New committer: <a href="mailto:scf@FreeBSD.org">Sean C. Farley</a> + (src)</p> + </event> + </day> + + <day> + <name>12</name> + <event> + <p>New committer: <a + href="mailto:timur@FreeBSD.org">Timur I. Bakeyev</a> + (ports)</p> + </event> + + <event> + <p>Enhanced commit privileges: <a + href="mailto:chinsan@FreeBSD.org">Chin-San Huang</a> + (doc, ports)</p> + </event> + </day> + + <day> + <name>7</name> + <event> + <title>FreeBSD Project Integrates Support for the Camellia Block Cipher</title> + + <p>Support for the Camellia block cipher has been integrated + into FreeBSD 7-CURRENT and will be part of the upcoming + FreeBSD 7-RELEASE. For more information, please refer to the <a + href="http://www.emediawire.com/releases/2007/6/emw531216.htm"> + press release</a>.</p> + </event> + </day> + + <day> + <name>4</name> + + <event> + <p>Enhanced commit privileges: <a href="mailto:jkois@FreeBSD.org">Johann Kois</a> + (full doc/www)</p> + </event> + </day> + </month> + + <month> + <name>5</name> + + <day> + <name>30</name> + <event> + <p>New committer: <a + href="mailto:beech@FreeBSD.org">Beech Rintoul</a> + (ports)</p> + </event> + </day> + + <day> + <name>29</name> + <event> + <title>New committer: <a href="mailto:attilio@FreeBSD.org">Attilio Rao</a> + (src). SoC2007 alumnus.</title> + + <p><a href="mailto:attilio@FreeBSD.org">Attilio Rao</a>, a + student in the Summer of Code program, is now a full + src/ committer.</p> + </event> + </day> + + <day> + <name>19</name> + <event> + <title>Xorg 7.2 imported into the ports collection.</title> + <p>Thanks to the hard work of + <a href="mailto:flz@FreeBSD.org">Florent Thoumie</a> (and + others), the FreeBSD ports collection now uses the modular + Xorg 7.2 as its default X server. i386 and AMD64 6.2-STABLE + packages are available and other architectures/releases + will be available later, or you can compile it from + source. In both cases, see <a + href="http://www.freebsd.org/cgi/cvsweb.cgi/ports/UPDATING?rev=1.504;content-type=text%2Fplain"> + the 20070519 entry in /usr/ports/UPDATING</a> on how to upgrade. Please track <a + href="http://docs.freebsd.org/mail/archive/freebsd-ports.html">-ports</a> + for last minute information. + </p> + </event> + </day> + </month> + + <month> + <name>4</name> + + <day> + <name>26</name> + <event> + <p>New committer: <a href="mailto:araujo@FreeBSD.org">Marcelo Araujo</a> + (ports)</p> + </event> + </day> + + <day> + <name>25</name> + <event> + <p>New committer: <a href="mailto:nemoliu@FreeBSD.org">Tong Liu</a> + (ports)</p> + </event> + </day> + + <day> + <name>13</name> + + <event> + <title>Funded Summer of Code Projects Announced</title> + + <p>The FreeBSD Project received over 120 applications for <a + href="http://code.google.com/soc">Google's + Summer of Code</a> program, amongst which 25 were selected + for funding. Unfortunately, there were far more first rate + applications than available spots for students. However, + we encourage students to work together with us all year + round. The FreeBSD Project is always willing to help + mentor students learn more about operating system + development through our normal community mailing lists and + development forums. Contributing to an open source + software project is a valuable component of a computer + science education and great preparation for a career in + software development.</p> + + <p>A complete list of the winning students and projects is + available <a +href="http://www.freebsd.org/projects/summerofcode-2007.html">here</a>. +A <a href="http://wiki.freebsd.org/moin.cgi/SummerOfCode2007">Summer +of Code wiki</a> is also available with additional information.</p> + </event> + + <event> + <p>New committer: <a href="mailto:trasz@FreeBSD.org">Edward Tomasz Napierala</a> + (ports)</p> + </event> + <event> + <title>Mongolian FreeBSD Documentation Project Launches</title> + + <p>Under the supervision of <a + href="mailto:ganbold@micom.mng.net">Ganbold Tsagaankhuu</a> the + Mongolian translation goes live. The official translation of the + FreeBSD Handbook, completed by the Mongolian FreeBSD Documentation + Project, adds support for documentation in another language. For + more information about the ongoing work of the MFDP, please refer + to the <a href="&enbase;/docproj/translations.html">Translations page + of the FreeBSD Documentation Project</a>.</p> + </event> + </day> + + <day> + <name>12</name> + <event> + <p>New committer: <a href="mailto:mav@FreeBSD.org">Alexander Motin</a> + (src)</p> + </event> + </day> + + <day> + <name>9</name> + <event> + <title>January-March, 2007 Status Report</title> + + <p>The January-March, 2007 Status Report is <a + href="&enbase;/news/status/report-2007-01-2007-03.html">now + available</a> with 19 entries.</p> + </event> + </day> + + <day> + <name>6</name> + <event> + <title>ZFS Now Part of FreeBSD</title> + + <p>Support for Sun's <a href="http://www.sun.com/2004-0914/feature/"> + ZFS</a> has been committed + to the FreeBSD 7-CURRENT development branch and will be available + as an experimental feature in FreeBSD 7.0-RELEASE. For more + information please refer to the <a + href="http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070544.html"> + announcement</a>.</p> + </event> + </day> + + <day> + <name>4</name> + <event> + <p>New committer: <a href="mailto:mm@FreeBSD.org">Martin Matuska</a> + (ports)</p> + </event> + </day> + + <day> + <name>3</name> + <event> + <p>New committer: <a href="mailto:lwhsu@FreeBSD.org">Li-Wen Hsu</a> + (ports)</p> + </event> + </day> + </month> + + <month> + <name>3</name> + + <day> + <name>28</name> + <event> + <p>New committer: <a href="mailto:sephe@FreeBSD.org">Sepherosa Ziehau</a> + (src)</p> + </event> + </day> + + <day> + <name>14</name> + <event> + <title>Accepting Applications for Summer of Code</title> + + <p>The FreeBSD Project is now accepting applications for + the Google <a + href="http://code.google.com/summerofcode.html">Summer + of Code 2007</a> program. This program will provide + funding for students to spend the summer contributing to + open source software projects. A list of FreeBSD specific + projects and potential mentors is available <a + href="&enbase;/projects/summerofcode.html">here</a>.</p> + + <p>Once a suitable project and mentor have been identified, + interested students should complete a proposal and submit + it to Google. Proposals are now being accepted and the + final deadline is March 24, 2007. Please see the <a + href="http://code.google.com/support/bin/topic.py?topic=10442">Google + FAQ</a> for more information.</p> + </event> + </day> + + <day> + <name>12</name> + <event> + <title>March 2007 Snapshot Releases Available</title> + + <p>FreeBSD 7-CURRENT and 6-STABLE snapshot releases for + March 2007 now available. The FreeBSD Release Engineering + Team issues snapshot releases to encourage users to test + new features and improve the reliability. For more + details, please visit + <a href="&enbase;/snapshots/index.html">the snapshots + page</a>.</p> + </event> + </day> + + <day> + <name>11</name> + <event> + <title>New committer: <a + href="mailto:bushman@FreeBSD.org">Michael Bushkov</a> + (src). An SoC2006 alumnus.</title> + + <p><a href="mailto:bushman@FreeBSD.org">Michael Bushkov</a>, a + successful student from last year's Summer of Code + program, has continued working with the FreeBSD Project + and is now a full src/ committer.</p> + </event> + </day> + + <day> + <name>10</name> + <event> + <title>Progress on scaling of FreeBSD on 8 CPU systems</title> + + <p>Recently there has been significant progress on optimizing + FreeBSD 7.0 for MySQL running an 8-core amd64 system. Under the + test workload FreeBSD has peak performance consistent with Linux, + and outperforms it by a factor of 4 under higher loads. Continue + reading for a more <a + href="http://people.freebsd.org/~kris/scaling/mysql.html">detailed + report here.</a></p> + </event> + </day> + + <day> + <name>7</name> + <event> + <title>FreeBSD Announces Intel Approval for Redistribution of Wireless Firmware</title> + + <p>The FreeBSD project has reached an agreement with Intel about the redistribution + of firmware images for Intel wireless cards. Please refer to the <a + href="http://www.prweb.com/releases/2007/03/prweb509818.htm">press release</a> + for more information.</p> + </event> + </day> + </month> + + <month> + <name>2</name> + + <day> + <name>27</name> + <event> + <p><a href="&enbase;/releng/dst_info.html">Information</a> + about how the change in Daylight Savings Time for some + time zones affects FreeBSD releases.</p> + </event> + </day> + + <day> + <name>23</name> + <event> + <p>Enhanced commit privileges: <a + href="mailto:remko@FreeBSD.org">Remko Lodder</a> + (doc,src)</p> + </event> + </day> + + <day> + <name>17</name> + <event> + <p>New committer: <a href="mailto:jinmei@FreeBSD.org">JINMEI, Tatuya</a> + (src)</p> + </event> + </day> + + <day> + <name>16</name> + <event> + <p>New committer: <a href="mailto:sepotvin@FreeBSD.org">Stephane E. Potvin</a> + (src)</p> + </event> + </day> + + <day> + <name>10</name> + <event> + <p>New committer: <a href="mailto:benjsc@FreeBSD.org">Benjamin Close</a> + (src)</p> + </event> + </day> + + <day> + <name>9</name> + <event> + <title>Podcast Interview with FreeBSD Core Team Member and + AsiaBSDCon 2007 Program Committee Chair George V. + Neville-Neil.</title> + + <p>In his latest <a href="http://bsdtalk.blogspot.com/">bsdtalk</a> + podcast, Will Backman interviews FreeBSD Developer George V. + Neville-Neil about the upcoming AsiaBSDCon conference. + <a + href="http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk099.mp3"> + http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk099.mp3</a>.</p> + </event> + </day> + + <day> + <name>8</name> + <event> + <title>AsiaBSDCon 2007 Announces Conference Schedule</title> + + <p>AsiaBSDCon, the BSD conference for Asia, has posted its schedule of + tutorials, papers and presentations for the conference, taking place + in Tokyo from March 8th through 11th 2007. The complete schedule can + be found <a href="http://www.asiabsdcon.org/timetable.html">here</a>.</p> + + <p>Registration will begin on or about the 12th of February.</p> + </event> + </day> + + <day> + <name>2</name> + <event> + <p>Enhanced commit privileges: <a + href="mailto:gabor@FreeBSD.org">Gábor Kövesdán</a> + (doc, ports)</p> + </event> + </day> + </month> + + <month> + <name>1</name> + + <day> + <name>31</name> + <event> + <p>Enhanced commit privileges: <a + href="mailto:rafan@FreeBSD.org">Rong-En Fan</a> + (src, ports)</p> + </event> + </day> + + <day> + <name>18</name> + <event> + <p>New committer: <a href="mailto:db@FreeBSD.org">Diane Bruce</a> + (ports)</p> + </event> + </day> + + <day> + <name>16</name> + <event> + <title>October-December, 2006 Status Report</title> + + <p>The October-December, 2006 Status Report is <a + href="&enbase;/news/status/report-2006-10-2006-12.html">now + available</a> with 41 entries.</p> + </event> + </day> + + <day> + <name>15</name> + + <event> + <title>FreeBSD 6.2-RELEASE is Now Available</title> + + <p><a href="&enbase;/releases/6.2R/announce.html">FreeBSD + 6.2-RELEASE</a> has been released. Please check the <a + href="&enbase;/releases/6.2R/errata.html">release errata</a> + before installation for any late-breaking news and/or + issues with 6.2. The <a + href="&enbase;/releases/index.html">Release Information</a> + page has more information about FreeBSD releases.</p> + </event> + </day> + + <day> + <name>9</name> + + <event> + <title>Hungarian FreeBSD Documentation Project Launches</title> + + <p>Under the supervision of FreeBSD developer Gábor Kövesdán, the + Hungarian translation goes live. This official translation, + completed by the Hungarian FreeBSD Documentation Project, adds + support for documentation in another language. For more + information about the ongoing work of the HFDP team, please refer + to <a href="http://www.FreeBSD.org/docproj/translations.html">the + Translations page of the FreeBSD Documentation Project</a>.</p> + </event> + </day> + </month> + </year> + +</news> diff --git a/en_US.ISO8859-1/htdocs/news/2007/press.xml b/en_US.ISO8859-1/htdocs/news/2007/press.xml new file mode 100644 index 0000000000..3d72d94f7f --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2007/press.xml @@ -0,0 +1,470 @@ +<?xml version="1.0"?> +<!DOCTYPE press PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Press//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/press.dtd"> +<!-- + COMMITTERS PLEASE NOTE: + News articles referenced in this file are also to be archived under + "freefall:/c/www/bsddoc/press/". +--> +<press> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD$ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2007</name> + + <month> + <name>11</name> + + <story> + <name>DataPipe and Rackspace are the Most Reliable Hosting Companies in October 2007</name> + <url>http://news.netcraft.com/archives/2007/11/19/datapipe_and_rackspace_are_the_most_reliable_hosting_companies_in_october_2007.html</url> + <site-name>Netcraft</site-name> + <site-url>http://www.netcraft.com/</site-url> + <date>19 November 2007</date> + <author>Paul Mutton</author> + <p>FreeBSD using web hosting provider DataPipe was ranked the + most reliable provider in October 2007 by Netcraft.</p> + </story> + </month> + + <month> + <name>10</name> + + <story> + <name>Desktop FreeBSD Part 9: FreeBSD and Broadband</name> + <url>http://www.ofb.biz/safari/article/441.html</url> + <site-name>Open For Business</site-name> + <site-url>http://www.ofb.biz/</site-url> + <date>30 October 2007</date> + <author>Ed Hurst</author> + <p>An article that briefly covers broadband setup on FreeBSD.</p> + </story> + + <story> + <name>Squeeze Your Gigabit NIC for Top Performance</name> + <url>http://www.enterprisenetworkingplanet.com/nethub/article.php/3485486</url> + <site-name>Enterprise Networking Planet</site-name> + <site-url>http://www.enterprisenetworkingplanet.com/</site-url> + <date>24 October 2007</date> + <author>Charlie Schluting</author> + <p>Describes the TCP stack tuning process used to get FreeBSD + 5.3 to run at gigabit speeds.</p> + </story> + + <story> + <name>Low-Cost Storage Tools</name> + <url>http://www.processor.com/editorial/article.asp?article=articles/p2942/23p42/23p42.asp&guid=&searchtype=&WordList=&bJumpTo=True</url> + <site-name>Processor Magazine</site-name> + <site-url>http://www.processor.com/</site-url> + <date>19 October 2007</date> + <author>Processor magazine staff</author> + <p>FreeBSD-based FreeNAS is touched upon in an article on + open-source storage tools.</p> + </story> + + <story> + <name>Creating And Managing A Jailed Virtual Host + in FreeBSD</name> + <url>http://www.openaddict.com/node/36</url> + <site-name>OpenAddict</site-name> + <site-url>http://www.openaddict.com/</site-url> + <date>18 October 2007</date> + <author>Sharaz</author> + <p>An article discussing how to build and subsequently manage + FreeBSD jails.</p> + </story> + + <story> + <name>Managing Multiple FreeBSD Systems</name> + <url>http://www.openaddict.com/node/35</url> + <site-name>OpenAddict</site-name> + <site-url>http://www.openaddict.com/</site-url> + <date>18 October 2007</date> + <author>Sharaz</author> + <p>An article on keeping multiple FreeBSD machines upto-date + by building from source code.</p> + </story> + + <story> + <name>Desktop FreeBSD Part 8: Updating the Core System</name> + <url>http://www.ofb.biz/safari/article/439.html</url> + <site-name>Open For Business</site-name> + <site-url>http://www.ofb.biz/</site-url> + <date>5 October 2007</date> + <author>Ed Hurst</author> + <p>An article that touches on the process of rebuilding a + FreeBSD system from source.</p> + </story> + </month> + + <month> + <name>9</name> + <story> + <name>PC-BSD revisited</name> + <url>http://blogs.ittoolbox.com/webdesign/php/archives/pcbsd-revisited-18820</url> + <site-name>ITToolbox</site-name> + <site-url>http://www.ittoolbox.com/</site-url> + <date>6 September 2007</date> + <author>Gregory L. Magnusson</author> + <p>A reviewer is impressed by the FreeBSD-based PC-BSD desktop + system.</p> + </story> + </month> + + <month> + <name>8</name> + + <story> + <name>Downtime, What's That?</name> + <url>http://www.processor.com/editorial/article.asp?article=articles/P2935/21p35/21p35.asp&guid=</url> + <site-name>Processor Magazine</site-name> + <site-url>http://www.processor.com/</site-url> + <date>31 August 2007</date> + <author>Processor Magazine staff</author> + <p>An article in the Processor Magazine discusses using + FreeBSD or OpenBSD as part of a strategy to increase server + uptime.</p> + </story> + + <story> + <name>Linux vs. BSD, What's the Difference?</name> + <url>http://www.linuxdevcenter.com/pub/a/linux/2007/08/23/linux-vs-bsd-whats-the-difference.html</url> + <site-name>Linux Dev Center</site-name> + <site-url>http://www.linuxdevcenter.com/</site-url> + <date>23 August 2007</date> + <author>Dru Lavigne</author> + <p>An introduction to PC-BSD for Linux users.</p> + </story> + + <story> + <name>Desktop FreeBSD Part 7: Terminal Emulator Settings</name> + <url>http://www.ofb.biz/safari/article/435.html</url> + <site-name>Open For Business</site-name> + <site-url>http://www.ofb.biz/</site-url> + <date>10 August 2007</date> + <author>Ed Hurst</author> + <p>An article on using and configuring the command line in + FreeBSD.</p> + </story> + + <story> + <name>The INQ takes a dip into open sauce</name> + <url>http://www.theinquirer.net/?article=41377</url> + <site-name>The Inquirer</site-name> + <site-url>http://www.theinquirer.net/</site-url> + <date>1 August 2007</date> + <author>Dr. John</author> + <p>The Inquirer takes FreeBSD-based PC-BSD 1.4 (beta) for a test + drive.</p> + </story> + </month> + + <month> + <name>7</name> + + <story> + <name>BSDTalk Interview: Embedding FreeBSD</name> + <url>http://bsdtalk.blogspot.com/2007/07/bsdtalk122-embedding-freebsd-with-m.html</url> + <site-name>bsdtalk</site-name> + <site-url>http://bsdtalk.blogspot.com/</site-url> + <date>26 July 2007</date> + <author>Will Backman</author> + <p>A podcast interview with M. Warner Losh on embedding + FreeBSD.</p> + </story> + + <story> + <name>BSDTalk Interview: George Neville-Neil</name> + <url>http://bsdtalk.blogspot.com/2007/07/bsdtalk121-fast-ipsec-with-george.html</url> + <site-name>bsdtalk</site-name> + <site-url>http://bsdtalk.blogspot.com</site-url> + <date>18 July 2007</date> + <author>Will Backman</author> + <p>BSDTalk interviews FreeBSD developer George Neville-Neil + about FAST IPSec</p> + </story> + + <story> + <name>Desktop FreeBSD Part 6: User PPP Connections</name> + <url>http://www.ofb.biz/safari/article/433.html</url> + <site-name>Open For Business</site-name> + <site-url>http://www.ofb.biz/</site-url> + <date>7 July 2007</date> + <author>Ed Hurst</author> + <p>A tutorial on setting up user PPP on FreeBSD.</p> + </story> + </month> + + <month> + <name>6</name> + + <story> + <name>24-hour test drive: PC-BSD</name> + <url>http://arstechnica.com/reviews/os/pc-bsd-a-24-hour-test-drive.ars</url> + <site-name>Ars Technica</site-name> + <site-url>http://www.arstechnica.com/</site-url> + <date>18 June 2007</date> + <author>Troy Unrau</author> + <p>Ars Technica reviews PC-BSD 1.3 and is favorably impressed.</p> + </story> + + <story> + <name>Desktop FreeBSD Part 5: Printing</name> + <url>http://www.ofb.biz/safari/article/430.html</url> + <site-name>Open For Business</site-name> + <site-url>http://www.ofb.biz/</site-url> + <date>11 June 2007</date> + <author>Ed Hurst</author> + <p>An introduction to printing on a FreeBSD desktop.</p> + </story> + + <story> + <name>Kazakhs shower president with cryptic questions</name> + <url>http://www.reuters.com/article/technologyNews/idUSL0131903220070601</url> + <site-name>Reuters</site-name> + <site-url>http://www.reuters.com/</site-url> + <date>1 June 2007</date> + <author>Reuters</author> + <p>An article about FreeBSD being part of the most popular + question in a webcast with the Kazakhian president.</p> + </story> + </month> + + <month> + <name>5</name> + + <story> + <name>A BSD Rootkit Primer</name> + <url>http://www.onlamp.com/pub/a/bsd/2007/05/31/defending-against-rootkits-under-bsd.html</url> + <site-name>ONLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>31 May 2007</date> + <author>Federico Biancuzzi</author> + <p>An interview with the author of the first book on BSD + rootkits.</p> + </story> + + <story> + <name>BSDTalk Interview: FreeBSD Core Team</name> + <url>http://bsdtalk.blogspot.com/2007/05/bsdtalk114-few-freebsd-core-team.html</url> + <site-name>bsdtalk</site-name> + <site-url>http://bsdtalk.blogspot.com/</site-url> + <date>25 May 2007</date> + <author>Will Backman</author> + <p>BSDTalk interviews a few FreeBSD Core team members + at BSDCAN '07.</p> + </story> + + <story> + <name>Desktop FreeBSD Part 4: Internet Mail Setup</name> + <url>http://www.ofb.biz/safari/article/427.html</url> + <site-name>Open For Business</site-name> + <site-url>http://www.ofb.biz/</site-url> + <date>18 May 2007</date> + <author>Ed Hurst</author> + <p>An article on setting up email for a FreeBSD desktop.</p> + </story> + + <story> + <name>Linux too vanilla? Try this</name> + <url>http://www.theinquirer.net/default.aspx?article=39621</url> + <site-name>The Inquirer</site-name> + <site-url>http://www.theinquirer.net/</site-url> + <date>15 May 2007</date> + <author>Liam Proven</author> + <p>A review of PC-BSD 1.3.</p> + </story> + + <story> + <name>BSDTalk Interview: Diane Bruce</name> + <url>http://bsdtalk.blogspot.com/2007/05/bsdtalk111-freebsd-developer-diane.html</url> + <site-name>bsdtalk</site-name> + <site-url>http://bsdtalk.blogspot.com</site-url> + <date>9 May 2007</date> + <author>Will Backman</author> + <p>BSDTalk interviews FreeBSD developer Diane Bruce about Ham + radio on BSD.</p> + </story> + + </month> + + <month> + <name>4</name> + + <story> + <name>BSDTalk Interview: George Neville-Neil</name> + <url>http://bsdtalk.blogspot.com/2007/04/bsdtalk109-george-neville-neil-and.html"</url> + <site-name>bsdtalk</site-name> + <site-url>http://bsdtalk.blogspot.com</site-url> + <date>26 April 2007</date> + <author>Will Backman</author> + <p>In this BSDTalk interview FreeBSD developer George Neville-Neil + talks about using VMs for development.</p> + </story> + + <story> + <name>Desktop FreeBSD Part 3: Adding Software</name> + <url>http://www.ofb.biz/safari/article/425.html</url> + <site-name>Open For Business</site-name> + <site-url>http://www.ofb.biz/</site-url> + <date>12 April 2007</date> + <author>Ed Hurst</author> + <p>An article that walks the reader through the process of + installing 3rd party software using the FreeBSD's ports + and package collection.</p> + </story> + </month> + + <month> + <name>3</name> + + <story> + <name>Deploying a FreeBSD 6.2 Server</name> + <url>http://www.openaddict.com/deploying_a_freebsd_6_2_server.html</url> + <site-name>OpenAddict</site-name> + <site-url>http://www.openaddict.com/</site-url> + <date>10 March 2007</date> + <author>Sharaz</author> + <p>The third article in a series covering the deployment of a + FreeBSD based server with Apache 2.2, PHP 5, MySQL 5.0, Sendmail + with SMTP-AUTH, Webmail, Bind DNS, SNMP, synchronized local time, + Webmin and with graphing using rrdtool/cacti.</p> + </story> + + <story> + <name>BSDTalk Interview: Randall Stewart</name> + <url>http://bsdtalk.blogspot.com/2007/03/bsdtalk102-cisco-distinguished-engineer.html</url> + <site-name>bsdtalk</site-name> + <site-url>http://bsdtalk.blogspot.com</site-url> + <date>6 March 2007</date> + <author>Will Backman</author> + <p>BSDTalk interviews FreeBSD developer Randall Stewart + about his work bringing SCTP to FreeBSD.</p> + </story> + + </month> + + <month> + <name>2</name> + + <story> + <name>BSDTalk Interview: George Neville-Neil</name> + <url>http://bsdtalk.blogspot.com/2007/02/bsdtalk101-freebsd-developer-george.html</url> + <site-name>bsdtalk</site-name> + <site-url>http://bsdtalk.blogspot.com</site-url> + <date>26 February 2007</date> + <author>Will Backman</author> + <p>BSDTalk interviews FreeBSD developer George Neville-Neil + on his packet construction set and packet debugger tools.</p> + </story> + + <story> + <name>Interview: The BSD Certification Group's Dru Lavigne</name> + <url>http://www.thejemreport.com/mambo/content/view/305/</url> + <site-name>The Jem Report</site-name> + <site-url>http://www.thejemreport.com/</site-url> + <date>20 February 2007</date> + <author>Jem Matzan</author> + <p>BSD Certification Group member Dru Lavigne puts forth the idea + that free/open source software provided an excellent opportunity + to inexpensively change one's career path.</p> + </story> + + <story> + <name>Interview: Sam Leffler of the FreeBSD Foundation</name> + <url>http://www.thejemreport.com/mambo/content/view/304/</url> + <site-name>The Jem Report</site-name> + <site-url>http://www.thejemreport.com/</site-url> + <date>15 February 2007</date> + <author>Jem Matzan</author> + <p>An interview with FreeBSD developer and FreeBSD Foundation Director + Sam Leffler about the FreeBSD Foundation.</p> + </story> + + <story> + <name>Open source is the ticket for In Ticketing</name> + <url>http://business.newsforge.com/business/07/01/25/1642213.shtml?tid=33</url> + <site-name>NewsForge</site-name> + <site-url>http://www.newsforge.com/</site-url> + <date>2 February 2007</date> + <author>Tina Gasperson</author> + <p>Ticket broking firm <a href="http://www.inticketing.com/">In Ticketing</a> + prefers FreeBSD on account of the security it provides.</p> + </story> + </month> + + <month> + <name>1</name> + + <story> + <name>Inside PC-BSD 1.3</name> + <url>http://www.onlamp.com/pub/a/bsd/2007/01/25/inside-pc-bsd-13.html</url> + <site-name>Onlamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>25 January 2007</date> + <author>Dru Lavigne</author> + <p>An interview with Kris Moore, Andrei Kolu, and Charles + Landemaine of the PC-BSD release engineering team.</p> + </story> + + <story> + <name>Interview with Matteo Riondato, FreeSBIE</name> + <url>http://distrowatch.com/weekly.php?issue=20070122#interview</url> + <site-name>DistroWatch</site-name> + <site-url>http://distrowatch.com/</site-url> + <date>22 January 2007</date> + <author>Distrowatch staff</author> + <p>An interview with Matteo Riondato, FreeBSD developer and release + engineer for FreeSBIE, a FreeBSD-based ``Live CD''.</p> + </story> + + <story> + <name>FreeBSD 6.2: Polished, More Stable</name> + <url>http://www.internetnews.com/dev-news/article.php/3654371</url> + <site-name>InternetNews.com</site-name> + <site-url>http://www.internetnews.com/</site-url> + <date>17 January 2007</date> + <author>Sean Michael Kerner</author> + <p>A brief look at FreeBSD 6.2.</p> + </story> + + <story> + <name>FreeSBIE 2.0-RELEASE is Now Available!</name> + <url>http://osnews.com/story.php/16957/FreeSBIE-2.0-Released</url> + <site-name>OSnews</site-name> + <site-url>http://www.osnews.com</site-url> + <date>16 January 2007</date> + <author>Thom Holwerda</author> + <p>A new release of FreeSBIE, a FreeBSD Live-CD, has been + released after two years of development.</p> + </story> + + <story> + <name>New Year, New Look For PC-BSD</name> + <url>http://www.internetnews.com/dev-news/article.php/3651641</url> + <site-name>InternetNews.com</site-name> + <site-url>http://www.internetnews.com/</site-url> + <date>2 January 2007</date> + <author>Sean Michael Kerner</author> + <p>A look at the new features in PC-BSD 1.3.</p> + </story> + + <story> + <name>Project of the Month: January 2007 - FreeNAS</name> + <url>http://sourceforge.net/potm/potm-2007-01.php</url> + <site-name>SourceForge.Net</site-name> + <site-url>http://sourceforge.net/</site-url> + <date>January 2007</date> + <author>SF.Net Staff</author> + <p>An interview with the developers of the FreeBSD-based FreeNAS + project, on the occasion of it being selected as SourceForge's + Project of the Month.</p> + </story> + </month> + </year> + +</press> diff --git a/en_US.ISO8859-1/htdocs/news/2008/Makefile b/en_US.ISO8859-1/htdocs/news/2008/Makefile new file mode 100644 index 0000000000..3a43951672 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2008/Makefile @@ -0,0 +1,16 @@ +# $FreeBSD: www/en/news/2008/Makefile,v 1.2 2009/03/16 07:58:53 pgj Exp $ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +XMLDOCS+= index:${XSL_NEWS_NEWSFLASH_OLD}:news.xml: +DEPENDSET.index=transtable news + +XMLDOCS+= press:${XSL_NEWS_PRESS_OLD}:: +DEPENDSET.press=transtable press + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/news/2008/news.xml b/en_US.ISO8859-1/htdocs/news/2008/news.xml new file mode 100644 index 0000000000..7edef03e52 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2008/news.xml @@ -0,0 +1,902 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE news PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for News//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/news.dtd"> + +<!-- Simple schema for FreeBSD Project news. + + Divide time in to <year>, <month>, and <day> elements, each of which + has a <name>. + + each <day> element contains one or more <event> elements. + + Each <event> contains an optional <title>, and then a <p>. <p> elements + can contain <a> anchors. + + Use the <title> element if the <p> content is lengthy. When generating + synopses of this information (e.g., for syndication using RDF files), + the contents of <title> will be preferred over <p>. + + *** Former Summer of Code Students: Please note that you are an + SoC alumnus when you add your new committer announcement. + Also, don't feel shy to add more information about what you + would like to work on. *** +--> + +<news> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD$ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2008</name> + + <month> + <name>12</name> + + <day> + <name>25</name> + + <event> + <title>FreeBSD 7.1-RC2 Available</title> + + <p>The second and last release candidate of &os; 7.1 is now + <a href="http://lists.freebsd.org/pipermail/freebsd-stable/2008-December/047203.html">available</a>. ISO images for Tier-1 architectures are now + available on most of the <a + href="&url.doc.base-en;/books/handbook/mirrors-ftp.html">&os; + mirror sites</a>.</p> + </event> + </day> + + <day> + <name>23</name> + + <event> + <title>&os; Foundation December 2008 Newsletter</title> + + <p>The &os; Foundation has published their <a + href="http://www.freebsdfoundation.org/press/2008Dec-newsletter.shtml">Semi-Annual December 2008 newsletter</a> + which summarizes what they have done to help the &os; + Project and community.</p> + </event> + </day> + + <day> + <name>9</name> + + <event> + <title>FreeBSD 7.1-RC1 Available</title> + + <p>The first release candidate of &os; 7.1 is now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2008-December/047014.html">available</a>. + ISO images for Tier-1 architectures are now available on + most of the <a + href="&url.doc.base-en;/books/handbook/mirrors-ftp.html">&os; + mirror sites</a>.</p> + </event> + </day> + + <day> + <name>3</name> + + <event> + <title>BSD channel launched on YouTube</title> + + <p>We are pleased to announce the availability of a + dedicated YouTube channel for technical lectures about + FreeBSD and other BSD operating systems. The channel is + available at <a + href="http://www.youtube.com/bsdconferences">www.youtube.com/bsdconferences</a>.</p> + + <p>This channel allows us to post full hour long lectures + from FreeBSD conferences. The first four videos that + Julian Elisher recorded at <a + href="http://www.meetbsd.com">MeetBSD</a> have been + posted, and more are on the way.</p> + + </event> + </day> + </month> + <month> + <name>11</name> + + <day> + <name>28</name> + + <event> + <title>FreeBSD 6.4-RELEASE Available</title> + + <p><a href="&enbase;/releases/6.4R/announce.html">FreeBSD + 6.4-RELEASE</a> is now available. Please be sure to check + the <a + href="&enbase;/releases/6.4R/relnotes.html">Release Notes</a> + and <a href="&enbase;/releases/6.4R/errata.html">Release + Errata</a> + before installation for any late-breaking news and/or + issues with 6.4. More information about FreeBSD releases + can be found on the <a + href="&enbase;/releases/index.html">Release Information</a> + page.</p> + </event> + </day> + + <day> + <name>18</name> + + <event> + <p>Commit bit restored: <a href="mailto:pho@FreeBSD.org">Peter + Holm</a> (src)</p> + </event> + </day> + + <day> + <name>16</name> + + <event> + <title>Official FreeBSD Forums Launched</title> + + <p>The FreeBSD project is finally, after much work, pleased to + announce the availability of an official FreeBSD web based + discussion forum. It is our hope that this forum will serve + as a public support channel for FreeBSD users around the world + and as a complement to our fine mailing lists.</p> + + <p>You can register and start using our new service here: <a + href="http://forums.FreeBSD.org">http://forums.FreeBSD.org</a>.</p> + </event> + </day> + + <day> + <name>10</name> + + <event> + <title>July - September, 2008 Status Reports</title> + + <p>The July - September, 2008 Status Reports are <a + href="&enbase;/news/status/report-2008-07-2008-09.html">now + available</a> with 14 entries.</p> + </event> + </day> + + <day> + <name>3</name> + <event> + <p>New committer: <a href="mailto:rene@FreeBSD.org"> + René Ladan</a> (doc-nl)</p> + </event> + + <event> + <title>&os; 6.4-RC2 Available</title> + + <p>The second Release Candidate for &os; 6.4 is now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2008-November/046364.html">available</a>. + ISO images for Tier-1 architectures are available for + download on most of the <a + href="&url.doc.base-en;/books/handbook/mirrors-ftp.html">&os; mirror sites</a>. + &os; 6.4-RC2 should be the last of the public test builds + for the FreeBSD 6.4 release cycle, therefore we encourage + people to test and report any outstanding bugs as soon as + possible.</p> + </event> + </day> + + <day> + <name>1</name> + <event> + <title>New committer: <a href="mailto:versus@FreeBSD.org"> + Konrad Jankowski</a> (src) - SoC2008 alumnus.</title> + + <p>New committer: <a href="mailto:versus@FreeBSD.org">Konrad Jankowski</a> (src). + Konrad participated in <a href="http://code.google.com/soc">Summer Of Code 2008</a>. + He will begin his work in the i18n area, specifically in + bringing his SoC code (UTF-8 collation) to the coming releases.</p> + </event> + </day> + + </month> + + <month> + <name>10</name> + + <day> + <name>19</name> + <event> + <title>&os; 7.1-BETA2 Available</title> + + <p>The second beta release of &os; 7.1 is now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2008-October/046037.html">available</a>. + ISO images for Tier-1 architectures can be found on most of the <a + href="&url.doc.base-en;/books/handbook/mirrors-ftp.html">&os; mirror sites</a>.</p> + </event> + </day> + + <day> + <name>12</name> + + <event> + <title>FreeBSD 6.4-RC1 Available</title> + + <p>The first release candidate of FreeBSD 6.4 is now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2008-October/045869.html">available</a>. + ISO images for Tier-1 architectures are now available on + most of the <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD mirror sites</a>.</p> + </event> + </day> + + <day> + <name>6</name> + + <event> + <p>New committer: <a href="mailto:lstewart@FreeBSD.org">Lawrence + Stewart</a> (src)</p> + </event> + </day> + </month> + + <month> + <name>9</name> + + <day> + <name>18</name> + + <event> + <title>Summer of Code Projects Completed</title> + + <p>We are happy to report that 19 students successfully + completed their FreeBSD <a + href="&enbase;/projects/summerofcode-2008.html">Summer of + Code</a> projects. Congratulations to both mentors and + students, and thanks to <a + href="http://www.google.com/">Google</a> for running this + program and providing funding.</p> + </event> + + <event> + <p>New committer: <a href="mailto:zec@FreeBSD.org">Marko Zec</a> + (src)</p> + </event> + </day> + + <day> + <name>15</name> + + <event> + <title>PC-BSD 7 Released</title> + + <p>PC-BSD 7 has just been released. PC-BSD is a + successful desktop operating system based on FreeBSD that + focuses on providing an easy to use desktop system for + casual computer users. The release may be <a + href="http://www.pcbsd.org">downloaded</a> or <a + href="http://www.freebsdmall.com">purchased</a> on DVD.</p> + </event> + + <event> + <p>New committer: <a href="mailto:rnoland@FreeBSD.org">Robert Noland</a> + (src)</p> + </event> + </day> + + <day> + <name>13</name> + + <event> + <title>&os; 6.4-BETA/7.1-BETA Available</title> + + <p>The final stage of the &os;-6.4 and &os;-7.1 Release cycle + has begun with the first beta releases. The ISO images for + Tier-1 architectures are now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045016.html">available</a> + for download on most of the <a + href="&url.doc.base-en;/books/handbook/mirrors-ftp.html">&os; mirror sites</a>. + We encourage people to test and report any outstanding bugs. + Please find more information about these releases on the <a + href="&base;/releng/">Release Engineering Information</a> + page.</p> + </event> + </day> + + <day> + <name>5</name> + <event> + <p>New committer: <a href="mailto:jpaetzel@FreeBSD.org">Josh Paetzel</a> + (ports)</p> + </event> + </day> + </month> + + <month> + <name>8</name> + <day> + <name>26</name> + <event> + <p>New committer: <a href="mailto:makc@FreeBSD.org">Max Brazhnikov</a> + (ports)</p> + </event> + </day> + + <day> + <name>25</name> + + <event> + <p>Enhanced commit privileges: <a + href="mailto:stas@FreeBSD.org">Stanislav Sedov</a> + (src, ports)</p> + </event> + </day> + + <day> + <name>22</name> + + <event> + <p>Enhanced commit privileges: <a + href="mailto:trasz@FreeBSD.org">Edward Tomasz Napierala</a> + (src, ports) SoC2008 alumnus.</p> + </event> + </day> + + <day> + <name>19</name> + + <event> + <title>April - June, 2008 Status Reports</title> + + <p>The April - June, 2008 Status Reports are <a + href="&enbase;/news/status/report-2008-04-2008-06.html">now + available</a> with 14 entries.</p> + </event> + </day> + + <day> + <name>6</name> + + <event> + <p>Enhanced commit privileges: <a + href="mailto:pgj@FreeBSD.org">Gábor Páli</a> + (full doc/www)</p> + </event> + </day> + </month> + + <month> + <name>7</name> + + <day> + <name>28</name> + <event> + <title>&os; Foundation Requesting Project Proposals</title> + + <p>The &os; Foundation is seeking the submission of proposals + for work relating to any of the major &os; subsystems or + infrastructure. A budget of $80,000 was allocated for 2008 + to fund multiple development projects. Proposals will be + evaluated based on desirability, technical merit and + cost-effectiveness.</p> + + <p>To find out more about the proposal process please read <a + href="http://www.freebsdfoundation.org/documents/FreeBSD%20Foundation%20Proposals.pdf">the call</a>. + </p> + </event> + </day> + + <day> + <name>21</name> + <event> + <p>New committer: <a href="mailto:rnoland@FreeBSD.org">Robert Noland</a> + (ports)</p> + </event> + + <event> + <p>New committer: <a href="mailto:vanhu@FreeBSD.org">Yvan Vanhullebus</a> + (src)</p> + </event> + </day> + + <day> + <name>18</name> + + <event> + <title>&os; Foundation July 2008 Newsletter</title> + + <p>The &os; Foundation has published their <a + href="http://www.freebsdfoundation.org/press/2008Jul-newsletter.shtml">Semi-Annual July 2008 newsletter</a> + which summarizes what they have done to help the &os; + Project and community.</p> + </event> + </day> + + <day> + <name>17</name> + + <event> + <title>New &os; Core Team elected</title> + + <p>The &os; Project is pleased to announce the conclusion + of our fourth consecutive democratic election of project + leadership. The &os; Core Team constitutes the + project's "Board of Directors" and is responsible for + vetting new src committers, arbitrating technical + disagreements, weighing in on policy and administrative + issues, and appointing sub-committees for handling + specific duties (security officer, release engineers, port + managers, webmasters, etc..). The core team has been + democratically elected every 2 years by active &os; + committers since 2000.</p> + + <p>Peter Wemm is rejoining the team after a 2 year hiatus, + and Kris Kennaway is joining the team for the first time. + The remaining 7 slots were filled with incumbents Wilko + Bulte, Brooks Davis, Giorgos Keramidas, George + V. Neville-Neil, Hiroki Sato, Murray Stokely, and Robert + Watson.</p> + + <p>The new core team would like to especially thank outgoing + members Wes Peters and Warner Losh for their many years of + service to &os;, our electioneer Dr. Josef Karthauser + for running another election for us, and our returning + core secretary Philip Paeps.</p> + </event> + + <event> + <p>New committer: <a href="mailto:pgollucci@FreeBSD.org">Philip M. Gollucci</a> + (ports)</p> + </event> + + <event> + <p>New committer: <a href="mailto:glarkin@FreeBSD.org">Greg Larkin</a> + (ports)</p> + </event> + </day> + + <day> + <name>8</name> + <event> + <title>iXsystems Announces Professional &os; and PC-BSD Support + Offering</title> + <p>A <a + href="http://www.prweb.com/releases/2008/7/prweb1073304.htm">press + release</a> announcing the launch of iXsystems' Professional + Services Division which will provide Professional Enterprise + Grade support, consulting, and development for &os; and PC-BSD.</p> + </event> + + <event> + <p>New committer: <a href="mailto:sson@FreeBSD.org">Stacey + Son</a> (src)</p> + </event> + </day> + + <day> + <name>3</name> + <event> + <p>New committer: <a href="mailto:nwhitehorn@FreeBSD.org">Nathan + Whitehorn</a> (src)</p> + </event> + </day> + </month> + + <month> + <name>6</name> + + <day> + <name>23</name> + <event> + <p>New committer: <a href="mailto:erik@FreeBSD.org">Erik + Cederstrand</a> (projects)</p> + </event> + + <event> + <title>FreeBSD Technologies in Firefox 3</title> + <p>A + <a href="http://www.prweb.com/releases/2008/6/prweb1042664.htm">press + release</a> describing FreeBSD technologies used by Mozilla + Firefox.</p> + </event> + </day> + + <day> + <name>19</name> + <event> + <p>New committer: <a href="mailto:amdmi3@FreeBSD.org">Dmitry Marakasov</a> + (ports)</p> + </event> + </day> + + <day> + <name>16</name> + + <event> + <p>New committer: <a href="mailto:eri@FreeBSD.org">Ermal + Luçi</a> (src)</p> + </event> + </day> + + <day> + <name>10</name> + + <event> + <title>New committer: <a href="mailto:ivoras@FreeBSD.org">Ivan Voras</a> + (src). SoC2005-2007 alumnus.</title> + + <p><a href="mailto:ivoras@FreeBSD.org">Ivan Voras</a> is now + a src/ committer. He participated in the <a + href="http://code.google.com/soc">Google Summer of + Code</a> program in 2005, 2006, and 2007.</p> + + </event> + </day> + + <day> + <name>3</name> + + <event> + <title>FreeBSD begins switch to Subversion</title> + + <p>The FreeBSD Project has begun the switch of its source code + management system from CVS to <a + href="http://subversion.tigris.org/">Subversion</a>. At this + point in time, FreeBSD's developers are making changes to the + base system in the Subversion repository. We have a replication + system in place that exports our work to the legacy CVS tree on + a continuous basis.</p> + + <p>People who are using our extensive CVS based distribution + network (including anoncvs, CVSup, cvsweb, ftp) will not be + interrupted by our work-in-progress. We are committed to + maintaining the existing CVS based distribution system for + at least the support lifetime of all existing "stable" + branches. Security and errata patches will continue to be made + available in their usual CVS locations.</p> + + <p>We expect to make our Subversion based source tree and other + supporting infrastructure public soon. There will be new + mailing lists to subscribe to if you wish to receive Subversion + commit notifications.</p> + + <p>Our ports, doc and www trees are not affected at this time. A + separate decision will be made regarding those CVS repositories + soon.</p> + + <p>Many people have contributed to the effort, but we wish + to thank Michael Haggerty and the <a + href="http://cvs2svn.tigris.org/">cvs2svn</a> project developers + for their assistance with cvs2svn. <a + href="mailto:peter@FreeBSD.org">Peter Wemm</a> spent several weeks + of <a href="http://www.yahoo.com/">Yahoo!'s</a> time repairing + the CVS tree, preparing for and performing the conversion, and + the configuration of the Subversion infrastructure. Yahoo! + donated the server hardware.</p> + </event> + </day> + </month> + + <month> + <name>5</name> + <day> + <name>24</name> + + <event> + <p>New committer: <a href="mailto:manolis@FreeBSD.org">Manolis + Kiagias</a> (doc/www)</p> + </event> + </day> + + <day> + <name>22</name> + + <event> + <p>New committer: <a href="mailto:ed@FreeBSD.org">Ed + Schouten</a> (src)</p> + </event> + + </day> + + <day> + <name>14</name> + + <event> + <title>January - March, 2008 Status Reports</title> + + <p>The January - March, 2008 Status Reports are <a + href="&enbase;/news/status/report-2008-01-2008-03.html">now + available</a> with 13 entries.</p> + </event> + + </day> + </month> + + <month> + <name>4</name> + <day> + <name>22</name> + + <event> + <title>Funded Summer of Code Projects Announced</title> + + <p>The FreeBSD Project received over 100 applications for <a + href="http://code.google.com/soc">Google's + Summer of Code</a> program, amongst which 21 were selected + for funding. Unfortunately, there were far more first rate + applications than available spots for students. However, + we encourage students to work together with us all year + round. The FreeBSD Project is always willing to help + mentor students learn more about operating system + development through our normal community mailing lists and + development forums. Contributing to an open source + software project is a valuable component of a computer + science education and great preparation for a career in + software development.</p> + + <p>A complete list of the winning students and projects is + available <a + href="http://www.freebsd.org/projects/summerofcode-2008.html">here</a>. + A <a + href="http://wiki.FreeBSD.org/SummerOfCode2008">Summer of + Code wiki</a> has been created and additional information + about the projects will be added there soon.</p> + </event> + + <event> + <p>New committer: <a href="mailto:pgj@FreeBSD.org">Gábor + Páli</a> (Hungarian doc/www)</p> + </event> + + </day> + </month> + + <month> + <name>3</name> + <day> + <name>31</name> + <event> + <title>Student deadline extended for Summer of Code</title> + + <p>The deadline for student applications to participate in + the <a href="http://code.google.com/soc">Google Summer of + Code</a> has been extended by one week. The new deadline + is Monday, April 7, 2008. If you haven't already, please + visit our <a + href="http://www.FreeBSD.org/projects/summerofcode.html">FreeBSD + Summer of Code page</a> and look at the example project + ideas we've listed there, or propose your own. There are + many new ideas listed since the first announcements went + out.</p> + </event> + </day> + + <day> + <name>26</name> + <event> + <title>Now Accepting Student Applications for Google Summer of Code</title> + + <p>The student application period for the Google <a + href="http://code.google.com/summerofcode.html">Summer of + Code 2008</a> program has begun. Please peruse our list + of FreeBSD specific <a + href="&enbase;/projects/summerofcode.html">projects and + potential mentors</a> and prepare your application before + the March 31 deadline. Earlier applications are + encouraged as this provides an opportunity for potential + mentors to work on improving the applications with + students before the deadline.</p> + </event> + </day> + + <day> + <name>17</name> + <event> + <title>Participating in Google Summer of Code</title> + + <p>The FreeBSD Project will soon be accepting applications for + the Google <a + href="http://code.google.com/summerofcode.html">Summer + of Code 2008</a> program. This program will provide + funding for students to spend the summer contributing to + open source software projects. A list of FreeBSD specific + projects and potential mentors is available <a + href="&enbase;/projects/summerofcode.html">here</a>.</p> + + <p>Once a suitable project and mentor have been identified, + interested students should complete a proposal and submit + it to Google. The application period begins on March 24, + 2008 and the final deadline is April 1, 2008 0:00 UTC. + Please see the <a + href="http://code.google.com/opensource/gsoc/2008/faqs.html">Google + FAQ</a> for more information.</p> + </event> + </day> + + <day> + <name>14</name> + <event> + <title>New committer: <a href="mailto:rdivacky@FreeBSD.org">Roman Divacky</a> + (src). SoC2006-2007 alumnus.</title> + + <p><a href="mailto:rdivacky@FreeBSD.org">Roman Divacky</a> + is now a src/ committer. He participated in the Summer of + Code program in 2006 and 2007, where he worked on Linux + 2.6 compatibility.</p> + + </event> + </day> + + <day> + <name>8</name> + <event> + <p>New committer: <a href="mailto:lippe@FreeBSD.org">Felippe M. Motta</a> + (ports)</p> + </event> + </day> + + <day> + <name>2</name> + <event> + <p>New committer: <a href="mailto:jadawin@FreeBSD.org">Philippe Audeoud</a> + (ports)</p> + </event> + </day> + </month> + + <month> + <name>2</name> + <day> + <name>27</name> + <event> + <title>FreeBSD 7.0-RELEASE Available</title> + + <p><a href="&enbase;/releases/7.0R/announce.html">FreeBSD + 7.0-RELEASE</a> is now available. The + <a href="&enbase;/releases/7.0R/errata.html">release errata</a> + will be updated with late-breaking news and/or + issues with 7.0, and should be consulted before + installation. For more information about FreeBSD releases, + see the <a + href="&enbase;/releases/index.html">Release Information</a> + page.</p> + </event> + </day> + + <day> + <name>26</name> + <event> + <p>pfSense 1.2 <a + href="http://blog.pfsense.org/?p=170">released</a>.</p> + </event> + <event> + <p>New committer: <a href="mailto:ganbold@FreeBSD.org">Ganbold Tsagaankhuu</a> + (doc/www)</p> + </event> + </day> + + <day> + <name>21</name> + <event> + <p>New committer: <a href="mailto:gahr@FreeBSD.org">Pietro Cerutti</a> + (ports)</p> + </event> + </day> + + <day> + <name>17</name> + <event> + <title>October-December, 2007 Status Reports</title> + + <p>The October-December, 2007 Status Reports are <a + href="&enbase;/news/status/report-2007-10-2007-12.html">now + available</a> with 25 entries.</p> + </event> + </day> + + <day> + <name>14</name> + <event> + <p>New committer: <a href="mailto:olli@FreeBSD.org">Oliver Fromme</a> + (src)</p> + </event> + </day> + + <day> + <name>12</name> + <event> + <title>FreeBSD 7.0-RC2 Available</title> + + <p>The second release candidate of FreeBSD 7.0 is now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2008-February/040426.html">available</a>. + ISO images for Tier-1 architectures are now available on most of the + <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"> + FreeBSD mirror sites</a>.</p> + </event> + </day> + + <day> + <name>5</name> + <event> + <p>New committer: <a href="mailto:antoine@FreeBSD.org">Antoine Brodin</a> + (src)</p> + </event> + </day> + </month> + + <month> + <name>1</name> + + <day> + <name>27</name> + <event> + <p>New committer: <a href="mailto:gonzo@FreeBSD.org">Oleksandr Tymoshenko</a> + (src)</p> + </event> + </day> + + + <day> + <name>18</name> + + <event> + <title>FreeBSD 6.3-RELEASE Available</title> + + <p><a href="&enbase;/releases/6.3R/announce.html">FreeBSD + 6.3-RELEASE</a> is now available. Please be sure to check + the <a + href="&enbase;/releases/6.3R/errata.html">release errata</a> + before installation for any late-breaking news and/or + issues with 6.3. More information about FreeBSD releases + can be found on the <a + href="&enbase;/releases/index.html">Release Information</a> + page.</p> + </event> + </day> + + <day> + <name>17</name> + <event> + <title>6 New RSS 2.0 Feeds Available</title> + + <p>Six new RSS 2.0 feeds have been made available on the + FreeBSD website. It is now possible to subscribe to RSS + 2.0 feeds for : <a + href="http://www.FreeBSD.org/news/rss.xml">FreeBSD Project + News</a>, <a + href="http://www.FreeBSD.org/news/press-rss.xml">FreeBSD + In the Media</a>, <a + href="http://www.FreeBSD.org/events/rss.xml">Upcoming + FreeBSD Events</a>, <a + href="http://www.FreeBSD.org/security/rss.xml">FreeBSD + Security Advisories</a>, <a + href="http://www.FreeBSD.org/java/rss.xml">FreeBSD Java + Updates</a>, and <a + href="http://www.FreeBSD.org/gnome/rss.xml">FreeBSD GNOME + Updates</a>. There is also an RSS 0.91 feed available for + <a href="http://freebsd.kde.org/news.rdf">FreeBSD KDE + Updates</a>.</p> + + <p>The new feeds all validate properly and have been tested + with popular feed reading software. Please mail <a + href="mailto:freebsd-www@FreeBSD.org">freebsd-www@FreeBSD.org</a> + if you have any problems with the new feeds.</p> + + </event> + </day> + + <day> + <name>9</name> + <event> + <p>DesktopBSD 1.6 is <a + href="http://www.desktopbsd.net/index.php?id=43&tx_ttnews[tt_news]=33&tx_ttnews[backPid]=55&cHash=46bfdce5e4">released</a>.</p> + </event> + </day> + + <day> + <name>4</name> + <event> + <p>New committer: <a href="mailto:wxs@FreeBSD.org">Wesley Shields</a> + (ports)</p> + </event> + </day> + </month> + </year> + +</news> diff --git a/en_US.ISO8859-1/htdocs/news/2008/press.xml b/en_US.ISO8859-1/htdocs/news/2008/press.xml new file mode 100644 index 0000000000..6f93529221 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2008/press.xml @@ -0,0 +1,159 @@ +<?xml version="1.0"?> +<!DOCTYPE press PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Press//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/press.dtd"> +<!-- + COMMITTERS PLEASE NOTE: + News articles referenced in this file are also to be archived under + "freefall:/c/www/bsddoc/press/". +--> +<press> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD$ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2008</name> + + <month> + <name>10</name> + <story> + <name>Review: PC-BSD 7</name> + <url>http://www.osnews.com/story/20351/Review_PC-BSD_7</url> + <site-name>OS News</site-name> + <site-url>http://www.osnews.com/</site-url> + <date>02 October 2008</date> + <author>Amjith Ramanujam</author> + <p>A review of PC-BSD 7.</p> + </story> + </month> + + <month> + <name>8</name> + <story> + <name>Network-Attached Storage on the Cheap</name> + <url>http://www.washingtonpost.com/wp-dyn/content/article/2008/08/26/AR2008082600237.html</url> + <site-name>Washington Post</site-name> + <site-url>http://www.washingtonpost.com/</site-url> + <date>27 August 2008</date> + <author>Tom Mainelli</author> + <p>FreeBSD based FreeNAS is recommended for turning an old PC + into a storage appliance.</p> + </story> + + <story> + <name>How Do Open Source Installations Compare by Operating System?</name> + <url>https://www.osscensus.org/newsletter/Census-News-August-2008.html</url> + <site-name>The Open-Source Census</site-name> + <site-url>http://www.osscensus.org/</site-url> + <date>August 2008</date> + <author>Stormy Peters</author> + <p>A recent census shows interesting data about FreeBSD use.</p> + </story> + </month> + + <month> + <name>7</name> + <story> + <name>Book Review: Building a Server with FreeBSD 7</name> + <url>http://www.freesoftwaremagazine.com/articles/book_review_building_server_freebsd_7</url> + <site-name>Free Software Magazine</site-name> + <site-url>http://www.freesoftwaremagazine.com/</site-url> + <date>7 July 2008</date> + <author>Ken Leyba</author> + <p>A review of the book "Building a Server with FreeBSD 7" by Bryan J. + Hong.</p> + </story> + + <story> + <name>Book Review: The Best of FreeBSD Basics</name> + <url>http://www.osnews.com/story/19947/Book_Review:_The_Best_of_FreeBSD_Basics</url> + <site-name>OS News</site-name> + <site-url>http://www.osnews.com/</site-url> + <date>2 July 2008</date> + <author>Peter Hummers</author> + <p>A review of the book "The Best of FreeBSD Basics".</p> + </story> + </month> + + <month> + <name>6</name> + <story> + <name>How FreeBSD makes vulnerability auditing easy: portaudit</name> + <url>http://blogs.techrepublic.com.com/security/?p=477</url> + <site-name>Tech Republic</site-name> + <site-url>http://www.techrepublic.com.com/</site-url> + <date>24 June 2008</date> + <author>Chad Perrin</author> + <p>An article that highlights the ease with which a FreeBSD + system can be kept upto-date with respect to vulnerabilities.</p> + </story> + + <story> + <name>Writing a kernel module for FreeBSD 7</name> + <url>http://www.freesoftwaremagazine.com/articles/writing_a_kernel_module_for_freebsd</url> + <site-name>Free Software Magazine</site-name> + <site-url>http://www.freesoftwaremagazine.com/</site-url> + <date>19 June 2008</date> + <author>Yousef Ourabi</author> + <p>A short introduction to building kernel modules on FreeBSD 7.</p> + </story> + </month> + + <month> + <name>3</name> + + <story> + <name>Review of FreeBSD 7</name> + <url>http://www.freesoftwaremagazine.com/articles/review_of_freebsd_7</url> + <site-name>Free Software Magazine</site-name> + <site-url>http://www.freesoftwaremagazine.com/</site-url> + <date>5 March 2008</date> + <author>Yousef Ourabi</author> + <p>A review of FreeBSD 7.0 Beta 3.</p> + </story> + </month> + + <month> + <name>2</name> + <story> + <name>Faster Performance, Fewer Machines For FreeBSD?</name> + <url>http://www.internetnews.com/dev-news/article.php/3731386/Faster+Performance+Fewer+Machines+For+FreeBSD.htm</url> + <site-name>InternetNews.com</site-name> + <site-url>http://www.internetnews.com/</site-url> + <date>29 February 2008</date> + <author>Sean Michael Kerner</author> + <p>A brief look at FreeBSD 7.0.</p> + </story> + + <story> + <name>What's New in FreeBSD 7.0</name> + <url>http://www.onlamp.com/pub/a/bsd/2008/02/26/whats-new-in-freebsd-70.html</url> + <site-name>ONLamp.com</site-name> + <site-url>http://www.onlamp.com/</site-url> + <date>26 February 2008</date> + <author>Federico Biancuzzi</author> + <p>An interview with several FreeBSD developers about features in + FreeBSD 7.0-RELEASE.</p> + </story> + </month> + + <month> + <name>1</name> + + <story> + <name>DesktopBSD 1.6 Released</name> + <url>http://www.osnews.com/story/19134/DesktopBSD_1.6_Released</url> + <site-name>OSNews</site-name> + <site-url>http://www.osnews.com/</site-url> + <date>9 January 2008</date> + <author>Thom Holwerda</author> + <p>Version 1.6 of DesktopBSD has been released. <a + href="http://www.desktopbsd.net/">DesktopBSD</a> is a + desktop operating system based on FreeBSD.</p> + </story> + </month> + </year> + +</press> diff --git a/en_US.ISO8859-1/htdocs/news/2009/Makefile b/en_US.ISO8859-1/htdocs/news/2009/Makefile new file mode 100644 index 0000000000..9f6d4afb22 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2009/Makefile @@ -0,0 +1,16 @@ +# $FreeBSD: www/en/news/2009/Makefile,v 1.1 2010/03/05 00:17:57 danger Exp $ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +XMLDOCS+= index:${XSL_NEWS_NEWSFLASH_OLD}:news.xml: +DEPENDSET.index=transtable news + +XMLDOCS+= press:${XSL_NEWS_PRESS_OLD}:: +DEPENDSET.press=transtable press + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/news/2009/news.xml b/en_US.ISO8859-1/htdocs/news/2009/news.xml new file mode 100644 index 0000000000..7c9e087d29 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2009/news.xml @@ -0,0 +1,869 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE news PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for News//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/news.dtd"> + +<!-- Simple schema for FreeBSD Project news. + + Divide time in to <year>, <month>, and <day> elements, each of which + has a <name>. + + each <day> element contains one or more <event> elements. + + Each <event> contains an optional <title>, and then a <p>. <p> elements + can contain <a> anchors. + + Use the <title> element if the <p> content is lengthy. When generating + synopses of this information (e.g., for syndication using RDF files), + the contents of <title> will be preferred over <p>. + + *** Former Summer of Code Students: Please note that you are an + SoC alumnus when you add your new committer announcement. + Also, don't feel shy to add more information about what you + would like to work on. *** +--> + +<news> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD$ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2009</name> + + <month> + <name>12</name> + + <day> + <name>20</name> + + <event> + <p>New committer: <a href="mailto:ryusuke@FreeBSD.org">Ryusuke + SUZUKI</a> (doc/ja_JP, www/ja)</p> + </event> + </day> + + <day> + <name>7</name> + + <event> + <p>New committer: <a href="mailto:gavin@FreeBSD.org">Gavin + Atkinson</a> (src)</p> + </event> + </day> + + <day> + <name>3</name> + + <event> + <title>Official support for NVIDIA graphics cards on amd64 + architecture</title> + + <p>The NVIDIA Corporation releases an initial BETA version of + NVIDIA 195.22 &os; graphics drivers for both i386 and amd64 + architectures. The drivers support recent versions of the + &os; operating system, i.e. 7.2-STABLE and 8.0-RELEASE and + provide support for features like SLI, improved + compatibility and performance, especially on systems with + 4GB or more of RAM. This marks the first driver release for + amd64, as it was previously available only for i386 + architecture. Please see the original <a + href="http://www.nvnews.net/vbulletin/showthread.php?t=142120">announcement</a> + for more information.</p> + </event> + </day> + </month> + + <month> + <name>11</name> + + <day> + <name>27</name> + + <event> + <title>FreeBSD 8.0 press release</title> + + <p>The <a href="&enbase;/releases/8.0R/pressrelease.html">FreeBSD + 8.0 press release</a> is now available.</p> + </event> + </day> + + <day> + <name>26</name> + + <event> + <title>FreeBSD 8.0-RELEASE Available</title> + + <p><a href="&enbase;/releases/8.0R/announce.html">FreeBSD + 8.0-RELEASE</a> is now available. Please be sure to check + the <a href="&enbase;/releases/8.0R/relnotes.html">Release + Notes</a> and <a + href="&enbase;/releases/8.0R/errata.html">Release + Errata</a> before installation for any late-breaking news + and/or issues with 8.0. More information about FreeBSD + releases can be found on the <a + href="&enbase;/releases/index.html">Release + Information</a> page.</p> + </event> + </day> + + <day> + <name>18</name> + + <event> + <p>New committer: <a href="mailto:mandree@FreeBSD.org">Matthias Andree</a> (ports)</p> + </event> + </day> + + <day> + <name>12</name> + + <event> + <title>&os; 8.0-RC3 Available</title> + + <p>The third of the Release Candidates for the &os;-8.0 + release cycle is now available. ISO images for Tier-1 + architectures and a <em>memory stick</em> image for + amd64/i386 are now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2009-November/052699.html">available</a> + on most of the <a + href="&url.doc.base-en;/books/handbook/mirrors-ftp.html">&os; + mirror sites</a>.</p> + </event> + </day> + </month> + + <month> + <name>10</name> + + <day> + <name>29</name> + <event> + <p>New committer: <a href="mailto:sylvio@FreeBSD.org">Sylvio + Cesar Teixeira</a> (ports)</p> + </event> + </day> + + <day> + <name>28</name> + + <event> + <title>&os; 8.0-RC2 Available</title> + + <p>The second of the Release Candidates for the &os;-8.0 + release cycle is now available. ISO images for Tier-1 + architectures and a <em>memory stick</em> image for + amd64/i386 are now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2009-October/052544.html">available</a> + on most of the <a + href="&url.doc.base-en;/books/handbook/mirrors-ftp.html">&os; + mirror sites</a>.</p> + </event> + </day> + + <day> + <name>11</name> + + <event> + <title>April-September, 2009 Status Report</title> + + <p>The April-September, 2009 Status Report is <a + href="&base;/news/status/report-2009-04-2009-09.html">now + available</a> with 38 entries.</p> + </event> + </day> + + <day> + <name>4</name> + + <event> + <p>New committer: <a href="mailto:jh@FreeBSD.org">Jaakko + Heinonen</a> (src)</p> + </event> + </day> + </month> + + <month> + <name>9</name> + + <day> + <name>21</name> + + <event> + <title>&os; 8.0-RC1 Available</title> + + <p>The first of the Release Candidates for the &os;-8.0 + release cycle is now available. ISO images for Tier-1 + architectures and a <em>memory stick</em> image for + amd64/i386 are now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2009-September/052024.html">available</a> + on most of the <a + href="&url.doc.base-en;/books/handbook/mirrors-ftp.html">&os; + mirror sites</a>.</p> + </event> + </day> + + <day> + <name>15</name> + <event> + <p>New committer: <a href="mailto:wen@FreeBSD.org">Wen + Heping</a> (ports)</p> + </event> + </day> + + <day> + <name>7</name> + + <event> + <title>&os; 8.0-BETA4 Available</title> + + <p>The fourth and last of the BETA builds for the &os;-8.0 + release cycle is now available. ISO images for Tier-1 + architectures and a <em>memory stick</em> image for + amd64/i386 are now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2009-September/051801.html">available</a> + on most of the <a + href="&url.doc.base-en;/books/handbook/mirrors-ftp.html">&os; + mirror sites</a>.</p> + </event> + </day> + </month> + + <month> + <name>8</name> + + <day> + <name>24</name> + + <event> + <title>&os; 8.0-BETA3 Available</title> + + <p>The third of the BETA builds for the &os;-8.0 release + cycle is now available. ISO images for Tier-1 architectures + and a <em>memory stick</em> image for amd64/i386 are now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2009-August/051628.html">available</a> + on most of the <a + href="&url.doc.base-en;/books/handbook/mirrors-ftp.html">&os; + mirror sites</a>.</p> + </event> + </day> + + <day> + <name>10</name> + <event> + <p>New committer: <a href="mailto:fluffy@FreeBSD.org">Dima + Panov</a> (ports)</p> + </event> + </day> + + </month> + + <month> + <name>7</name> + + <day> + <name>20</name> + <event> + <p>New committer: <a href="mailto:yzlin@FreeBSD.org">Yi-Jheng + Lin</a> (ports)</p> + </event> + </day> + + <day> + <name>18</name> + + <event> + <title>&os; 8.0-BETA2 Available</title> + + <p>The final stage of the &os;-8.0 Release cycle continues + with the second public beta release. The &os; 8.0-BETA2 + ISO images for Tier-1 architectures are now available for + download on most of the <a + href="&url.doc.base-en;/books/handbook/mirrors-ftp.html"> + &os; mirror sites</a>. As with the first beta release, + this is not yet intended for use in a production + environment. However we encourage our users to test this + release and report any bugs and problems you may have + found. For more information about this release and + updating details please see the official <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2009-July/051181.html"> + announcement</a>.</p> + </event> + </day> + + <day> + <name>7</name> + + <event> + <title>&os; 8.0-BETA1 Available</title> + + <p>The final stage of the &os;-8.0 Release cycle has begun + with the first public beta release. The &os; 8.0-BETA1 + ISO images for Tier-1 architectures are now available for + download on most of the <a + href="&url.doc.base-en;/books/handbook/mirrors-ftp.html"> + &os; mirror sites</a>. We encourage our users to give + &os; 8.0-BETA1 a try and provide us with the feedback, + however please read the official <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2009-July/051018.html"> + announcement</a> carefully before starting to use this + release.</p> + </event> + </day> + </month> + + <month> + <name>6</name> + + <day> + <name>8</name> + + <event> + <p>New committer: <a href="mailto:np@FreeBSD.org">Navdeep + Parhar</a> (src)</p> + </event> + + <event> + <p>New committer: <a href="mailto:tuexen@FreeBSD.org">Michael + Tuexen</a> (src)</p> + </event> + </day> + + <day> + <name>4</name> + + <event> + <title>Portmgr reorganization</title> + + <p>Portmgr is happy to announce that two new members will + join the team.</p> + + <p>Martin Wilke has been one of our most active committers + since receiving his commit bit today 3 years ago. He has + been working in a number of subgroups including python, + ports-security and the KDE team.</p> + + <p>Ion-Mihai Tetcu has been interested in regression testing + and qualitiy assurance, creating QAT automated tinderbox + testing of all port commits on a per-commit basis, and adding + on-the-fly feedback to the snapshot builds from the pointyhat + package cluster.</p> + + <p>Unfortunately, we will also be saying goodbye to Kirill + Ponomarew, who hasn't had much time to spend on FreeBSD and + will be stepping down from portmgr.</p> + + <p>We thank Kirill for all his contributions in the past and + wish Martin and Ion-Mihai the best of luck with the new tasks + bestowed upon them.</p> + </event> + </day> + + <day> + <name>3</name> + <event> + <p>New bugmeister members: + <a href="mailto:gavin@FreeBSD.org">Gavin Atkinson</a>, + <a href="mailto:vwe@FreeBSD.org">Volker Werth</a> + </p> + </event> + </day> + + </month> + + <month> + <name>5</name> + + <day> + <name>28</name> + + <event> + <p>New committer: <a href="mailto:avl@FreeBSD.org">Alexander + Logvinov + </a> (ports)</p> + </event> + </day> + + <day> + <name>27</name> + + <event> + <p>New committer: <a href="mailto:kmoore@FreeBSD.org">Kris + Moore</a> (ports)</p> + </event> + </day> + + <day> + <name>23</name> + + <event> + <p>New committer: <a href="mailto:bcr@FreeBSD.org">Benedict + Reuschling</a> (doc/de_DE, www/de)</p> + </event> + </day> + + <day> + <name>22</name> + + <event> + <p>New committer: <a href="mailto:jilles@FreeBSD.org">Jilles + Tjoelker</a> (src)</p> + </event> + </day> + + <day> + <name>20</name> + + <event> + <p>New committer: <a href="mailto:tota@FreeBSD.org">TAKATSU + Tomonari</a> (ports)</p> + </event> + </day> + + <day> + <name>10</name> + + <event> + <title>Google Summer of Code Projects Announced</title> + + <p>The FreeBSD Project again received many high quality + applications from students participating + in <a href="http://code.google.com/soc">Google's Summer of + Code</a> program. This year 20 student proposals were + accepted to work with the FreeBSD Project as part of this + program. For those with projects that were not accepted + this year, we'd like to note that the FreeBSD Project is + always willing to help mentor students so they can learn + more about operating system development through our normal + community mailing lists and development forums.</p> + + <p>The complete list of student projects selected for funding + is : + + <ul> +<li><a href="http://wiki.FreeBSD.org/AdityaSarawgi">Aditya Sarawgi</a>, <a href="http://wiki.FreeBSD.org/SOC2009AdityaSarawgi">Improving + Second Extended File system (ext2fs) and making it GPL free</a> + (Mentor: <a href="http://wiki.FreeBSD.org/UlfLilleengen">Ulf Lilleengen</a>) +</li><li><a href="http://wiki.FreeBSD.org/AlejandroPulver">Alejandro Pulver</a>, <em>Ports license + infrastructure (part 2: integration)</em> + (Mentor: <a href="http://wiki.FreeBSD.org/ErwinLansing">Erwin Lansing</a>) +</li><li><a href="http://wiki.FreeBSD.org/AnaKukec">Ana Kukec</a>, <em>IPv6 Secure Neighbor Discovery + - native kernel APIs for FreeBSD</em> + (Mentor: <a href="http://wiki.FreeBSD.org/BjoernZeeb">Bjoern Zeeb</a>) +</li><li><a href="http://wiki.FreeBSD.org/DavidForsythe">David Forsythe</a>, <em><a href="http://wiki.FreeBSD.org/SoC2009DavidForsythe">Package + tools rewrite via a new package library, with new + features</a></em> (Mentor: <a href="http://wiki.FreeBSD.org/TimKientzle">Tim Kientzle</a>) +</li><li><a class="nonexistent" + href="http://wiki.FreeBSD.org/EdwardTomaszNapierala">Edward Tomasz Napierala</a>, <em>Hierarchical + Resource Limits</em> + (Mentor: <a href="http://wiki.FreeBSD.org/BrooksDavis">Brooks Davis</a>) +</li><li><a href="http://wiki.FreeBSD.org/FabioChecconi">Fabio Checconi</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009FabioChecconi">Geom-based + Disk Schedulers</a></em> (Mentor: <a class="nonexistent" + href="http://wiki.FreeBSD.org/LuigiRizzo">Luigi Rizzo</a>) +</li><li><a href="http://wiki.FreeBSD.org/FangWang">Fang Wang</a>, <em>Implement TCP UTO</em> + (Mentor: <a href="http://wiki.FreeBSD.org/RuiPaulo">Rui Paulo</a>) +</li><li><a href="http://wiki.FreeBSD.org/G%C3%A1borK%C3%B6vesd%C3%A1n">Gábor Kövesdán</a>, <em><a href="http://wiki.FreeBSD.org/G%C3%A1borSoC2009">BSD-licensed + libiconv in base system</a></em> + (Mentor: <a href="http://wiki.FreeBSD.org/XinLi">Xin Li</a>) +</li><li><a href="http://wiki.FreeBSD.org/GlebKurtsov">Gleb Kurtsov</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009GlebKurtsov">In + kernel stackable cryptographic filesystem (pefs)</a></em> + (Mentor: <a class="nonexistent" + href="http://wiki.FreeBSD.org/StanislavSedov">Stanislav Sedov</a>) +</li><li><a href="http://wiki.FreeBSD.org/IliasMarinos">Ilias Marinos</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009IliasMarinos">Application-Specific + Audit Trails</a></em> + (Mentor: <a href="http://wiki.FreeBSD.org/RobertWatson">Robert Watson</a>) +</li><li><a href="http://wiki.FreeBSD.org/MartaCarbone">Marta Carbone</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009MartaCarbone">Ipfw + and dummynet improvements</a></em> (Mentor: <a class="nonexistent" + href="http://wiki.FreeBSD.org/LuigiRizzo">Luigi Rizzo</a>) +</li><li><a href="http://wiki.FreeBSD.org/NikhilBysani">Nikhil Bysani</a>, <em>Porting <a class="nonexistent" + href="http://wiki.FreeBSD.org/NetworkManager">NetworkManager</a> to FreeBSD</em> + (Mentor: <a href="http://wiki.FreeBSD.org/EdSchouten">Ed Schouten</a>) +</li><li><a href="http://wiki.FreeBSD.org/P%C3%A1liG%C3%A1borJ%C3%A1nos">Páli Gábor János</a>, <em><a href="http://wiki.FreeBSD.org/PGJSoC2009">Design + and Implementation of Subsystem Support Libraries for Monitoring + and Management</a></em> + (Mentor: <a href="http://wiki.FreeBSD.org/OleksandrTymoshenko">Oleksandr Tymoshenko</a>) +</li><li><a href="http://wiki.FreeBSD.org/PrashantVaibhav">Prashant Vaibhav</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009PrashantVaibhav">Reworking + the callout scheme: towards a tickless kernel</a></em> + (Mentor: <a href="http://wiki.FreeBSD.org/EdMaste">Ed Maste</a>) +</li><li><a href="http://wiki.FreeBSD.org/SatishSrinivasan">Satish Srinivasan</a>, <em>TrustedBSD + Audit: Developing BSD licensed tools for importing, exporting + from/to Linux audit log format and BSM</em> + (Mentor: <a class="nonexistent" + href="http://wiki.FreeBSD.org/StaceySon">Stacey Son</a>) +</li><li><a href="http://wiki.FreeBSD.org/SylvestreGallon">Sylvestre Gallon</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009SylvestreGallon">USB + improvements under FreeBSD</a></em> + (Mentor: <a href="http://wiki.FreeBSD.org/PhilipPaeps">Philip Paeps</a>) +</li><li><a class="nonexistent" + href="http://wiki.FreeBSD.org/TatsianaElavaya">Tatsiana Elavaya</a>, <em><a class="nonexistent" + href="http://wiki.FreeBSD.org/SOC2009TatsianaElavaya">ipfw ruleset optimization and + highlevel rule definition language</a></em> + (Mentor: <a href="http://wiki.FreeBSD.org/DiomidisSpinellis">Diomidis Spinellis</a>) +</li><li><a href="http://wiki.FreeBSD.org/TatsianaSeveryna">Tatsiana Severyna</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009TatsianaSeveryna">puffs + (pass-to-userspace framework file system) port for + FreeBSD</a></em> (Mentor: <a class="nonexistent" + href="http://wiki.FreeBSD.org/KonstantinBelousov">Konstantin Belousov</a>) +</li><li><a href="http://wiki.FreeBSD.org/ZachariahRiggle">Zachariah Riggle</a>, <em>TCP\IP + Regression Testing Suite</em> + (Mentor: <a href="http://wiki.FreeBSD.org/GeorgeNevilleNeil">George Neville Neil</a>) +</li><li><a href="http://wiki.FreeBSD.org/ZhaoShuai">Zhao Shuai</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009ZhaoShuai">FIFO + Optimizations</a></em> + (Mentor: <a href="http://wiki.FreeBSD.org/JohnBaldwin">John Baldwin</a>) +</li> +</ul></p> + + <p>The <a href="http://wiki.FreeBSD.org/SummerOfCode2009">Summer + of Code wiki</a> contains additional information about + FreeBSD Participation in this program. Coding starts May + 23, so please join us in welcoming the 20 new students to + our community.</p> + </event> + </day> + + <day> + <name>7</name> + + <event> + <title>January - March, 2009 Status Reports</title> + + <p>The January - March, 2009 Status Reports are <a + href="&enbase;/news/status/report-2009-01-2009-03.html">now + available</a> with 15 entries.</p> + </event> + </day> + + <day> + <name>5</name> + + <event> + <p>New committer, SoC alumnus: <a href="mailto:snb@FreeBSD.org">Nick + Barkas</a> (src)</p> + </event> + </day> + + <day> + <name>4</name> + + <event> + <title>FreeBSD 7.2-RELEASE Available</title> + + <p><a href="&enbase;/releases/7.2R/announce.html">FreeBSD + 7.2-RELEASE</a> is now available. Please be sure to check + the <a href="&enbase;/releases/7.2R/relnotes.html">Release + Notes</a> and <a + href="&enbase;/releases/7.2R/errata.html">Release + Errata</a> before installation for any late-breaking news + and/or issues with 7.2. More information about FreeBSD + releases can be found on the <a + href="&enbase;/releases/index.html">Release + Information</a> page.</p> + </event> + </day> + </month> + + <month> + <name>4</name> + + <day> + <name>24</name> + + <event> + <title>FreeBSD 7.2-RC2 Available</title> + + <p>The second of two planned Release Candidates for the &os; + 7.2-RELEASE cycle is now available. ISO images for Tier-1 + architectures are now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2009-April/049591.html">available</a> + on most of the <a + + href="&url.doc.base-en;/books/handbook/mirrors-ftp.html">&os; + mirror sites</a>.</p> + </event> + </day> + + <day> + <name>21</name> + + <event> + <title>DCBSDCon Videos Posted</title> + + <p>All of the technical sessions from the recent <a + href="http://www.dcbsdcon.org">DCBSDCon 2009</a> + conference were recorded and are now available in the <a + href="http://www.youtube.com/bsdconferences">BSDConferences</a> + channel on <a href="http://www.youtube.com">YouTube</a>. + There are now 50 separate videos of technical talks from + MeetBSD, NYCBSDCon, AsiaBSDCon, and BSDCan available in + the channel.</p> + </event> + </day> + + <day> + <name>17</name> + + <event> + <title>FreeBSD 7.2-RC1 Available</title> + + <p>The first of two planned Release Candidates for the &os; + 7.2-RELEASE cycle is now available. ISO images for Tier-1 + architectures are now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2009-April/049464.html">available</a> + on most of the <a + + href="&url.doc.base-en;/books/handbook/mirrors-ftp.html">&os; + mirror sites</a>.</p> + </event> + </day> + + <day> + <name>12</name> + + <event> + <p>Enhanced commit privileges: <a + href="mailto:pgj@FreeBSD.org">Gábor Páli</a> + (ports, doc)</p> + </event> + </day> + + <day> + <name>10</name> + + <event> + <title>PC-BSD 7.1 Released</title> + + <p>PC-BSD 7.1 has been released. PC-BSD is a + successful desktop operating system based on FreeBSD that + focuses on providing an easy to use desktop system for + casual computer users. A list of new features/updates + since the last version can be found <a + href="http://www.pcbsd.org/content/view/104/30/">here</a>.</p> + + <p>The new release may be <a + href="http://www.pcbsd.org">downloaded</a> or <a + href="http://www.freebsdmall.com">purchased</a> on DVD.</p> + </event> + </day> + + <day> + <name>6</name> + + <event> + <p>New committer: <a href="mailto:rmacklem@FreeBSD.org">Rick + Macklem</a> (src)</p> + </event> + </day> + + <day> + <name>3</name> + + <event> + <title>FreeBSD 7.2-BETA1 Available</title> + + <p>The final stage of the &os; 7.2-RELEASE cycle has begun + with the first beta release. ISO images for Tier-1 + architectures are now <a + href="http://lists.freebsd.org/pipermail/freebsd-stable/2009-April/049233.html">available</a> + on most of the <a + +href="&url.doc.base-en;/books/handbook/mirrors-ftp.html">&os; mirror +sites</a>.</p> + </event> + </day> + </month> + + <month> + <name>3</name> + + <day> + <name>25</name> + + <event> + <p>New committer: <a href="mailto:skreuzer@FreeBSD.org">Steven + Kreuzer</a> (ports)</p> + </event> + </day> + + <day> + <name>22</name> + + <event> + <title>The &os; Project participates in the Google Summer of + Code 2009 program</title> + + <p>We are pleased to announce that Google has invited the &os; + Project to participate in their Summer of Code 2009 program, + which allows students to get paid to work on the &os; source + code. We invite students interested in working on &os; to + submit their proposals as soon as possible.</p> + + <p>For more information please see the <a + href="&enbase;/projects/summerofcode.html">&os; Summer Projects</a> + page for recommended project ideas and the official <a + href="http://lists.freebsd.org/pipermail/freebsd-announce/2009-March/001242.html">announcement</a>.</p> + </event> + </day> + + <day> + <name>16</name> + + <event> + <p>New committer: <a href="mailto:fabient@FreeBSD.org">Fabien + Thomas</a> (src)</p> + </event> + </day> + + <day> + <name>12</name> + + <event> + <title>Follow FreeBSD on Twitter</title> + + <p>There are a number of semi-official Twitter streams + available now with the latest updates from the FreeBSD + Project. The <a + href="http://twitter.com/freebsdannounce">@freebsdannounce</a> + stream provides a short summary and link to the full + newsflash posts. <a + href="http://twitter.com/freebsdblogs">@freebsdblogs</a> + syndicates the FreeBSD developer blogs from <a + href="http://planet.freebsdish.org">Planet FreeBSD</a>. + <a href="http://twitter.com/freebsd">@freebsd</a> + syndicates both of the above sources and more. Finally, + the new <a + href="http://twitter.com/bsdevents">@bsdevents</a> stream + includes all the events from our <a + href="http://www.FreeBSD.org/events">events page</a> plus + additional reminders and notices of BSD gatherings.</p> + </event> + </day> + + <day> + <name>3</name> + + <event> + <p>New committer: <a href="mailto:dhn@FreeBSD.org">Dennis + Herrmann</a> (ports)</p> + </event> + </day> + + <day> + <name>1</name> + + <event> + <p>New committer: <a href="mailto:dchagin@FreeBSD.org">Dmitry + Chagin</a> (src)</p> + </event> + </day> + + </month> + + <month> + <name>2</name> + + <day> + <name>19</name> + + <event> + <p>New committer: <a href="mailto:mva@FreeBSD.org">Marcus von + Appen</a> (ports)</p> + </event> + </day> + + <day> + <name>18</name> + + <event> + <p>New committer: <a href="mailto:avg@FreeBSD.org">Andriy Gapon</a> + (src)</p> + </event> + </day> + + <day> + <name>14</name> + + <event> + <title>KDE 4.2.0 available for FreeBSD</title> + + <p>KDE 4.2.0 has been merged into the ports tree. For a + detailed list of improvements, please refer to the + <a href="http://kde.org/announcements/4.2/index.php"> + announcement</a>. For general information about KDE on + FreeBSD, please see the <a href="http://freebsd.kde.org"> + KDE on FreeBSD</a> project page.</p> + </event> + </day> + </month> + + <month> + <name>1</name> + + <day> + <name>28</name> + + <event> + <title>October - December, 2008 Status Reports</title> + + <p>The October - December, 2008 Status Reports are <a + href="&enbase;/news/status/report-2008-10-2008-12.html">now + available</a> with 19 entries.</p> + </event> + + <event> + <p>New committer: <a href="mailto:beat@FreeBSD.org">Beat Gätzi</a> + (ports)</p> + </event> + <event> + <p>New committer: <a href="mailto:jamie@FreeBSD.org">Jamie + Gritton</a> (src)</p> + </event> + </day> + + <day> + <name>17</name> + + <event> + <title>FreeBSD Kernel Internals Video Posted</title> + + <p>The first lecture from Kirk McKusick's full + length <a href="http://www.youtube.com/watch?v=nwbqBdghh6E">FreeBSD + Kernel Internals</a> course has been posted to + the <a href="http://www.youtube.com/bsdconferences">BSD + Conferences</a> channel + on <a href="http://www.youtube.com">YouTube</a>.</p> + </event> + </day> + <day> + <name>9</name> + + <event> + <title>GNOME 2.24.2 Available for FreeBSD</title> + + <p>The FreeBSD GNOME team is proud to announce the release of + GNOME 2.24.2 for FreeBSD. More details can be found on + the <a href="&enbase;/gnome/index.html">FreeBSD GNOME Project + page</a>.</p> + </event> + </day> + + <day> + <name>5</name> + + <event> + <title>FreeBSD 7.1-RELEASE Available</title> + + <p><a href="&enbase;/releases/7.1R/announce.html">FreeBSD + 7.1-RELEASE</a> is now available. Please be sure to check + the <a href="&enbase;/releases/7.1R/relnotes.html">Release + Notes</a> and <a + href="&enbase;/releases/7.1R/errata.html">Release + Errata</a> before installation for any late-breaking news + and/or issues with 7.1. More information about FreeBSD + releases can be found on the <a + href="&enbase;/releases/index.html">Release + Information</a> page.</p> + </event> + </day> + </month> + </year> + +</news> diff --git a/en_US.ISO8859-1/htdocs/news/2009/press.xml b/en_US.ISO8859-1/htdocs/news/2009/press.xml new file mode 100644 index 0000000000..6dfa5ceebf --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/2009/press.xml @@ -0,0 +1,216 @@ +<?xml version="1.0"?> +<!DOCTYPE press PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Press//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/press.dtd"> +<!-- + COMMITTERS PLEASE NOTE: + News articles referenced in this file are also to be archived under + "freefall:/c/www/bsddoc/press/". +--> +<press> + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD$ + </cvs:keyword> + </cvs:keywords> + + <year> + <name>2009</name> + + <month> + <name>11</name> + + <story> + <name>FreeNAS 0.7 adds ZFS support</name> + <url>http://www.h-online.com/open/news/item/FreeNAS-0-7-adds-ZFS-support-853475.html</url> + <site-name>The H</site-name> + <site-url>http://www.h-online.com/</site-url> + <date>09 November 2009</date> + <author>crve</author> + <p>A description of the new features in version 0.7 of the FreeBSD-based FreeNAS project.</p> + </story> + + <story> + <name>Update your FreeBSD software with care</name> + <url>http://blogs.techrepublic.com.com/security/?p=2615</url> + <site-name>Tech Republic</site-name> + <site-url>http://www.techrepublic.com/</site-url> + <date>09 November 2009</date> + <author>Chad Perrin</author> + <p>Chad Perrin describes how he keeps his FreeBSD system up to date.</p> + </story> + </month> + + <month> + <name>8</name> + + <story> + <name>&os; 8 Getting New Routing Architecture</name> + <url>http://www.internetnews.com/dev-news/article.php/3835746</url> + <site-name>InternetNews.com ‐ WebMediaBrands Inc.</site-name> + <site-url>http://www.internetnews.com/</site-url> + <date>21 August 2009</date> + <author>Sean Michael Kerner</author> + <p>This article introduces recent work on &os; network routing + architecture done by senior network architect from Blue Coat + ‐ Qing Li. Its main goal is to optimize &os; routing + code to better utilize parallel processing CPUs.</p> + </story> + + <story> + <name>FreeNAS: A Simple Data Storage Solution</name> + <url>http://www.radioworld.com/article/85170</url> + <site-name>Radio World</site-name> + <site-url>http://www.radioworld.com/</site-url> + <date>11 August 2009</date> + <author>Todd Dixon</author> + <p>The author is impressed by the speed and low resource usage of + FreeBSD-based FreeNAS.</p> + </story> + </month> + + <month> + <name>7</name> + + <story> + <name>Why &os; 8 Won't Rewrite the Book</name> + <url>http://www.internetnews.com/dev-news/article.php/3830041</url> + <site-name>InternetNews.com ‐ WebMediaBrands Inc.</site-name> + <site-url>http://www.internetnews.com/</site-url> + <date>15 July 2009</date> + <author>Sean Michael Kerner</author> + <p>An article about the upcoming &os; 8.0 release, which + includes interviews with Michael Lucas, author of the Absolute + &os; book, Matt Olander of iXsystems, and Kris Moore of + PC-BSD. The primary focus of the article is how &os;, even + across major releases, still keeps the disruption for users + to a minimum, and introduces new features and improvements + without forcing a paradigm shift on the users.</p> + </story> + </month> + + <month> + <name>6</name> + + <story> + <name>Most Reliable Hosting Company Sites in May 2009</name> + <url>http://news.netcraft.com/archives/2009/06/02/most_reliable_hosting_company_sites_in_may_2009.html</url> + <site-name>Netcraft Ltd.</site-name> + <site-url>http://www.netcraft.com/</site-url> + <date>02 June 2009</date> + <author>Paul Mutton</author> + <p>Three of the top five hosting providers in Netcraft's list + run FreeBSD.</p> + </story> + + <story> + <name>Securing Network Services with FreeBSD Jails</name> + <url>http://www.packtpub.com/article/securing-network-services-with-freebsd-jails</url> + <site-name>Packt Publishing</site-name> + <site-url>http://www.packtpub.com/</site-url> + <date>June 2009</date> + <author>Christer Edwards</author> + <p>An article on using FreeBSD's jails to safely run network services.</p> + </story> + </month> + + <month> + <name>5</name> + + <story> + <name>FreeBSD 7.2 released, now with Superpages</name> + <url>http://www.h-online.com/open/FreeBSD-7-2-released-now-with-Superpages--/news/113204</url> + <site-name>The H</site-name> + <site-url>http://www.h-online.com/</site-url> + <date>04 May 2009</date> + <author>djwm</author> + <p>An brief article on FreeBSD 7.2.</p> + </story> + + <story> + <name>FreeBSD 7.2 Review: Improved Virtualization</name> + <url>http://www.cyberciti.biz/tips/freebsd-72-review-improved-virtualization.html</url> + <site-name>nixCraft</site-name> + <site-url>http://www.cyberciti.biz/</site-url> + <date>02 May 2009</date> + <author>Vivek Gite</author> + <p>Coverage of the new jail features in FreeBSD 7.2.</p> + </story> + </month> + + <month> + <name>4</name> + + <story> + <name>Great Bay Software Switches to BSD from Linux</name> + <url>http://www.marketwire.com/press-release/Great-Bay-Software-975478.html</url> + <site-name>Great Bay Software</site-name> + <site-url>http://www.greatbaysoftware.com/</site-url> + <date>16 April 2009</date> + <author>Bob Durkee</author> + <p>Great Bay Software, the innovator of Endpoint Profiling for enterprise networks, + has switched to &os; from Linux for all of its appliances including the + Beacon Endpoint Profiler 3.0.</p> + </story> + + <story> + <name>First look at PC-BSD 7.1</name> + <url>http://distrowatch.com/weekly.php?issue=20090413#feature</url> + <site-name>Distro Watch</site-name> + <site-url>http://www.distrowatch.com/</site-url> + <date>13 April 2009</date> + <p>A reviewer takes PC-BSD 7.1 out for a spin.</p> + </story> + + <story> + <name>Combining Debian and FreeBSD; Pushing the Envelope of FOSS</name> + <url>http://www.linux-mag.com/id/7295</url> + <site-name>Linux Magazine</site-name> + <site-url>http://www.linux-mag.com/</site-url> + <date>9 April 2009</date> + <author>Nathan Willis</author> + <p>Coverage of Debian GNU/kFreeBSD, a GNU operating system that + uses the FreeBSD kernel.</p> + </story> + </month> + + <month> + <name>3</name> + <story> + <name>Tomahawk Desktop Switches to BSD from Linux</name> + <url>http://www.tomahawkcomputers.com/fund-raising/phase-one.html</url> + <site-name>Tomahawk Computers</site-name> + <site-url>http://www.tomahawkcomputers.com/</site-url> + <date>10 March 2009</date> + <author>Sagara Wijetunga</author> + <p>Tomahawk Computers Pte Ltd. has switched to &os; from + Linux to make the next version of the Tomahawk Desktop operating + system.</p> + </story> + </month> + + <month> + <name>1</name> + <story> + <name>Coyote Point Builds on FreeBSD to Accelerate</name> + <url>http://www.internetnews.com/infra/article.php/3795791</url> + <site-name>Internet News</site-name> + <site-url>http://www.internetnews.com/</site-url> + <date>13 January 2009</date> + <author>Sean Michael Kerner</author> + <p>FreeBSD is at the core of Coyote Point's appliance.</p> + </story> + + <story> + <name>FreeBSD 7.1 Gets a Little Help from Sun</name> + <url>http://www.internetnews.com/dev-news/article.php/3794561</url> + <site-name>Internet News</site-name> + <site-url>http://www.internetnews.com/</site-url> + <date>06 January 2009</date> + <author>Sean Michael Kerner</author> + <p>An article covering technology sharing between Sun and the FreeBSD + project and other new features in FreeBSD 7.1.</p> + </story> + </month> + </year> + +</press> diff --git a/en_US.ISO8859-1/htdocs/news/Makefile b/en_US.ISO8859-1/htdocs/news/Makefile new file mode 100644 index 0000000000..badc792a31 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/Makefile @@ -0,0 +1,54 @@ +# $FreeBSD: www/en/news/Makefile,v 1.52 2009/02/11 17:15:28 pgj Exp $ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +DOCS+= news.sgml + +# press releases +DOCS+= pressreleases.sgml +DOCS+= press-rel-1.sgml +DOCS+= press-rel-2.sgml +DOCS+= press-rel-3.sgml +DOCS+= press-rel-4.sgml +DOCS+= press-rel-5.sgml +DOCS+= press-rel-6.sgml +DOCS+= press-rel-7.sgml +DOCS+= press-rel-8.sgml +DOCS+= press-rel-9.sgml + +# The yearly State of the Union address +DOCS+= sou1999.sgml + +INDEXLINK= news.html + +DEPENDSET.DEFAULT= transtable news press + +XMLDOCS= newsflash:${XSL_NEWS_NEWSFLASH}:${XML_NEWS_NEWS_MASTER}: +XMLDOCS+= news-rdf:${XSL_NEWS_NEWS_RDF}:${XML_NEWS_NEWS_MASTER}:news.rdf +XMLDOCS+= news-rss:${XSL_NEWS_NEWS_RSS}:${XML_NEWS_NEWS_MASTER}:rss.xml +XMLDOCS+= press:${XSL_NEWS_PRESS}:${XML_NEWS_PRESS_MASTER}: +XMLDOCS+= press-rss:${XSL_NEWS_PRESS_RSS}:${XML_NEWS_PRESS_MASTER}:press-rss.xml + +SUBDIR= 1993 +SUBDIR+= 1996 +SUBDIR+= 1997 +SUBDIR+= 1998 +SUBDIR+= 1999 +SUBDIR+= 2000 +SUBDIR+= 2001 +SUBDIR+= 2002 +SUBDIR+= 2003 +SUBDIR+= 2004 +SUBDIR+= 2005 +SUBDIR+= 2006 +SUBDIR+= 2007 +SUBDIR+= 2008 +SUBDIR+= 2009 +SUBDIR+= status + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/news/Makefile.inc b/en_US.ISO8859-1/htdocs/news/Makefile.inc new file mode 100644 index 0000000000..9db38b7970 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/Makefile.inc @@ -0,0 +1,4 @@ +# $FreeBSD: www/en/news/Makefile.inc,v 1.1 2000/03/22 16:20:52 phantom Exp $ + +WEBBASE?= /data/news +WEB_PREFIX?= ${.CURDIR}/../../.. diff --git a/en_US.ISO8859-1/htdocs/news/news.sgml b/en_US.ISO8859-1/htdocs/news/news.sgml new file mode 100644 index 0000000000..52f1404e71 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/news.sgml @@ -0,0 +1,91 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA ".."> +<!ENTITY date "$FreeBSD: www/en/news/news.sgml,v 1.52 2010/05/19 13:45:53 ryusuke Exp $"> +<!ENTITY title "FreeBSD News"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<html> + &header; + + <img src="../gifs/news.jpg" alt="FreeBSD News" align="right" border="0"> + + <h2>Local news</h2> + + <ul> + <li> + <p><b><a href="newsflash.html">Newsflash</a></b>: New releases, + drivers, committers, security announcements, and other news.</p> + </li> + + <li> + <p><b><a href="http://freebsdfoundation.org/press/">Foundation Press Releases</a></b>: Press releases from the FreeBSD Foundation (also see <a href="pressreleases.html">archived pre-2005 press releases</a>).</p> + </li> + + <li> + <p><b><a href="press.html">Press articles</a></b>: FreeBSD appearing + in the regular press.</p> + </li> + + <li> + <p><b><a href="status/status.html">Status reports</a></b>: FreeBSD + development status reports.</p> + </li> + </ul> + + <h2>Other sites</h2> + + <ul> + <li> + <p><b><a href="http://www.onlamp.com/bsd/">BSD DevCenter</a></b>: + The ONLamp.com/O'Reilly Network's clearing house for BSD articles, news, tutorials, or generally community information.</p> + </li> + + <li> +<!-- + <p><b><a href="http://www.bsdforums.org">BSDForums.org</a></b>: +--> + <p><b><a href="http://www.daemonforums.org">Daemon Forums</a></b>: + Active online forums and news community site dedicated + to FreeBSD and other BSDs.</p> + </li> +<!-- + <li> + <p><b><a href="http://www.bsdnews.org/">BSDnews.org</a></b>: + An online magazine dedicated to all BSDs.</p> + </li> +--> + <li> +<!-- + (<b><a href="http://www.bsdnews.com/">BSDnews.com</a></b>): +--> + </li> + + <li> + <p><b><a href="http://www.freebsddiary.org/">FreeBSD Diary</a></b>: + One man's record of his trials and triumphs with FreeBSD.</p> + </li> + + <li> + <p><b><a href="http://www.kerneltrap.org">Kerneltrap</a></b>: + Daily articles and current kernel news, about BSD and Linux + kernels.</p> + </li> + + <li> + <p><b><a href="http://www.osnews.com">OSNews</a></b>: + Daily articles and news about Linux, BSD and other + operating systems.</p> + </li> + + <li> + <p><b><a href="http://slashdot.org/bsd/">Slashdot's BSD + section</a></b>: Pointers and discussion about BSD news, not + just FreeBSD.</p> + </li> + + </ul> + + &footer; + </body> +</html> diff --git a/en_US.ISO8859-1/htdocs/news/press-rel-1.sgml b/en_US.ISO8859-1/htdocs/news/press-rel-1.sgml new file mode 100644 index 0000000000..37bd98de9e --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/press-rel-1.sgml @@ -0,0 +1,58 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA ".."> +<!ENTITY date "$FreeBSD: www/en/news/press-rel-1.sgml,v 1.9 2005/10/04 19:43:48 hrs Exp $"> +<!ENTITY title "FreeBSD Press Release: April 22, 1999"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<html> +&header; + +<!-- +<img src="../gifs/news.jpg" align="right" border="0" alt="FreeBSD News"> +--> + +<p></p> + +<h2>FreeBSD Used to Generate Spectacular Special Effects</h2> + +<p><b>Concord, CA, April 22, 1999</b>: +32 Dual-Processor FreeBSD systems were used to generate a large number of +special effects in the cutting edge Warner Brothers film, <em>The +Matrix</em>.</p> + +<p>Manex Visual Effects used 32 Dell Precision 410 Dual P-II/450 +Processor systems running FreeBSD as the core CG Render Farm. Charles +Henrich, the senior systems administrator at Manex, says, "We came to a +point in the production where we realized we just did not have enough +computing power on our existing SGI infrastructure to get through the +3-D intensive sequences. It was at that point we decided on going +with a FreeBSD based solution, due to the ability to get the hardware +quickly as well as the reliability and ease of administration that +FreeBSD provides us. Working with Dell, we purchased 32 of these +systems on a Wednesday, and had them rendering in production by +Saturday afternoon. It was truly an amazing effort on everyone's +part, and I don't believe it would've been possible had we chosen to +go with any other Operating System solution."</p> + +<p>The FreeBSD operating system is a powerful, completely open-source +system based on the Berkeley Software Distribution of UNIX. It is +available free of charge from numerous Internet websites and also on +CD-ROM from Walnut Creek CDROM, and includes thousands of ported +applications including 3-D graphics rendering and many other equally +powerful tools. FreeBSD is optimized for use on the Intel x86 +processor line that is the heart of today's versatile commodity +personal computers. Infinitely customizable, FreeBSD is at the heart +of such Internet powerhouse applications as Yahoo! and U.S. West +because it is unencumbered by commercial license restrictions and can be +copied and modified freely.</p> + +<p>For more information on FreeBSD, visit <a href="http://www.FreeBSD.org/"> +http://www.FreeBSD.org/</a> and <a href="http://www.wccdrom.com/"> +http://www.wccdrom.com/</a>. For more information about Manex Visual +Effects, please visit <a href="http://www.mvfx.com/">http://www.mvfx.com/ +</a>.</p> + +&footer; +</body> +</html> diff --git a/en_US.ISO8859-1/htdocs/news/press-rel-2.sgml b/en_US.ISO8859-1/htdocs/news/press-rel-2.sgml new file mode 100644 index 0000000000..dfc9ec7a75 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/press-rel-2.sgml @@ -0,0 +1,88 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA ".."> +<!ENTITY date "$FreeBSD: www/en/news/press-rel-2.sgml,v 1.12 2005/10/04 19:43:48 hrs Exp $"> +<!ENTITY title "FreeBSD Press Release: April 29, 1999"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<html> +&header; + + +<!-- +<img src="../gifs/news.jpg" align="right" border="0" alt="FreeBSD News"> +--> +<p></p> + +<h2>Complete XML Development System Integrated with FreeBSD</h2> + +<p><b>Concord, CA, April 29, 1999</b>: Included with FreeBSD 3.1 is a +complete, integrated SGML/XML development system that installs with a +simple, easy to use command sequence.</p> + +<p>FreeBSD's Ports system and multitasking architecture makes it easy for an +SGML/XML developer to download and install all the latest versions of the +tools and reference material he needs to develop SGML and XML formatting +languages and documents, and the online Internet mailing lists help him learn +and keep up-to-date with the evolving XML implementation.</p> + +<p>FreeBSD is a full-featured open-source operating system which runs on +virtually all Intel x86-based personal computers. Its 580 page "Handbook" +has recently been completely done over into DocBook format, and it is a +living example of an evolving document built with SGML tools. The Handbook +is available on the Internet at: +</p> +<ul> +<li><a href="http://www.FreeBSD.org/handbook/">http://www.FreeBSD.org/handbook/</a></li> +<li><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/</a></li> +</ul> + +<p>The FreeBSD Documentation Project is also making available the +"FreeBSD Documentation Project Primer" to make it as painless as +possible for newcomers to contribute to the FreeBSD Documentation Set. +Much of the information in the primer is appropriate to all SGML/XML +users, and is freely available. The primer, which is constantly being +updated by the Documentation Project team, can be found at:</p> +<ul> +<li><a href="http://www.FreeBSD.org/tutorials/primer/"> +http://www.FreeBSD.org/tutorials/primer/</a></li> +</ul> + +<h3>Features of the Document Project SGML/XML System include:</h3> + +<ul> +<li>James Clark's Jade 1.2.1 and SP suite version 1.3.3, enabling +formatting and validation of SGML and XML documents.</li> +<li>A complete set of 19 ISO SGML character set entities</li> +<li>The DocBook (v2.4.1, v3.0, v3.1), HTML (all versions), and +LinuxDoc Document Type Definitions (DTD)</li> +<li>Norm Walsh's Modular DocBook Stylesheets, allowing fine control +over the appearance and formatting of DocBook documents.</li> +<li>Emacs and XEmacs, in conjunction with the PSGML extension package, +provide a customizable industrial-strength SGML editing solution.</li> +<li>The teTeX-beta package in conjunction with the JadeTeX macros make +it possible to convert DocBook documents to DVI, Postscript, and +PDF formats with embedded hyperlinks.</li> +<li>Additional SGML-aware programs and utilities can be found in the +FreeBSD ports system.</li> +</ul> + +<p>The FreeBSD Documentation Project is actively migrating from the +LinuxDoc DTD to the DocBook DTD, and has been providing feedback to +the DocBook maintainers regarding new features and possible +implementations for the past year. For more information about the +FreeBSD Documentation Project, please contact the freebsd-doc@FreeBSD.org +mailing list.</p> + +<p>The FreeBSD operating system is available on the Internet from the +master FreeBSD website and from various mirror systems around the +world, and it can also be obtained on convenient CDROMs from Walnut +Creek CDROM. Information on all of these options is available through:</p> +<ul> +<li><a href="http://www.FreeBSD.org/">http://www.FreeBSD.org/</a></li> +<li><a href="http://www.wccdrom.com/">http://www.wccdrom.com/</a></li> +</ul> + +&footer; +</body> +</html> diff --git a/en_US.ISO8859-1/htdocs/news/press-rel-3.sgml b/en_US.ISO8859-1/htdocs/news/press-rel-3.sgml new file mode 100644 index 0000000000..f66b262643 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/press-rel-3.sgml @@ -0,0 +1,89 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA ".."> +<!ENTITY date "$FreeBSD: www/en/news/press-rel-3.sgml,v 1.8 2005/10/04 19:43:48 hrs Exp $"> +<!ENTITY title "FreeBSD Press Release: June 7, 1999"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<html> +&header; + +<!-- +<img src="../gifs/news.jpg" align="right" border="0" alt="FreeBSD News"> +--> +<p></p> + +<h2>BSD Community Welcomes Apple's New Open Source Operating System</h2> + +<p><b>Concord, CA, June 7, 1999</b>: Today, at the start of the UNIX +development community's annual Usenix convention, operating system +influentials embraced Apple Computer's Darwin (www.apple.com/darwin) +as a new member of the Berkeley Software Distribution (BSD) +operating system family.</p> + +<p>"We're very pleased to have Apple's participation in the BSD +community," said Jordan Hubbard, chairman of the USENIX convention's +Freenix track and co-founder of the FreeBSD Project. "As more smart +businesses discover the incredible free resource that is BSD software, +they'll realize that contributing to open source development is in +their best interest."</p> + +<p>According to Herb Peyerl of the NetBSD Project, "Our interaction with +Apple on the Darwin project has been extremely rewarding for NetBSD +and is the kind of open cooperation of which we would like to see +more."</p> + +<p>"Leveraging the twenty-year BSD heritage allows Apple developers to +concentrate on adding a unique user experience to the solid, robust +foundation of the BSD code," according to Avie Tevanian, Apple +Computer's senior vice president of Software Engineering. "We believe +that by embracing the open source movement with our Darwin software, +the result will be better products for millions of Mac customers +worldwide. The BSD code in Darwin is an essential part of our +operating system strategy."</p> + +<p>This type of reciprocation is a return to the original software +development model that was universal in the early days of computing, +before PCs. Wilfredo Sanchez, technical lead for the Darwin Project, +will speak on Darwin at this week's Freenix track, a series of +programs at Usenix devoted exclusively to this sort of open source +software development.</p> + +<h3>About NetBSD and FreeBSD</h3> + +<p>NetBSD and FreeBSD are open source operating systems based on the last +public release of BSD UNIX, 4.4BSDLite2. Each effort has kept up with +the latest technologies in processors and software +architectures. While having different priorities, the BSD development +teams share a friendly competitive rivalry, spurring each other on to +produce better product for their worldwide users. Over the twenty +years of development, a huge base of software has been developed +around BSD -- including much of the Internet infrastructure -- +enabling the OS to be used effectively in almost any computing +application. The open development model means there are no secrets, +creating a worldwide understanding of the code which enables BSD +developers to build on the efforts of prior developers without the +hassles endemic to proprietary operating systems and applications.</p> + +<h3>For More Information, Contact:</h3> +<p> +The FreeBSD Project<br> +Concord, California<br> +925-682-7859<br> +<a href="mailto:freebsd-questions@FreeBSD.org"> +freebsd-questions@FreeBSD.org</a><br> +<a href="http://www.FreeBSD.org">http://www.FreeBSD.org</a><br> +</p> + +<p> +The NetBSD Project<br> +C/O Charles M. Hannum<br> +81 Bromfield Rd, #2<br> +Somerville, MA 02144<br> +<a href="mailto:mindshare@netbsd.org">mindshare@netbsd.org</a><br> +<a href="http://www.netbsd.org">http://www.netbsd.org</a><br> +</p> + +&footer; +</body> +</html> diff --git a/en_US.ISO8859-1/htdocs/news/press-rel-4.sgml b/en_US.ISO8859-1/htdocs/news/press-rel-4.sgml new file mode 100644 index 0000000000..43f160cf5f --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/press-rel-4.sgml @@ -0,0 +1,232 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA ".."> +<!ENTITY date "$FreeBSD: www/en/news/press-rel-4.sgml,v 1.5 2005/10/04 19:43:48 hrs Exp $"> +<!ENTITY title "FreeBSD Press Release: March 9, 2000"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<html> +&header; + +<p></p> + +<h3>FOR IMMEDIATE RELEASE</h3> + +<h3>BSD SUPPLIERS UNITE TO DELIVER THE WORLD'S MOST POPULAR INTERNET + OPERATING SYSTEMS</h3> + +<h4>The New BSDI To Deliver Renowned BSD Operating System Technologies And + Back The Rapidly Growing FreeBSD Open Source Community</h4> + +<p><b>Colorado Springs, Colo., March 9, 2000:</b> Berkeley Software + Design, Inc. (BSDI) announced today that it has merged with Walnut + Creek CDROM, the distributor of the popular FreeBSD operating system. + As a merged company, the new BSDI unites the leading developers and + suppliers of the Berkeley Software Distribution operating system + BSDI will develop and deliver advanced BSD® Internet operating systems + and platforms, while providing the open source FreeBSD Project with + technology, backing and expanded support.</p> + +<p>BSD operating systems run some of the Internet's most highly trafficked + sites and largest service providers, including Yahoo!, Microsoft's + Hotmail and UUNET, an MCI WorldCom company. BSD and Linux are today's + fastest-growing operating systems, according to Survey.com, the leading + eResearch company.</p> + +<p>BSD operating system, networking and Internet technologies have + achieved widespread acceptance in the Internet infrastructure. Over + 100,000 commercial Internet customers run BSD operating systems on more + than 2,000,000 BSD-powered servers. It is estimated that nine out of 10 + Internet Service Providers (ISPs) and Network Service Providers (NSPs) + as well as 15 percent of all Internet sites run BSD systems. BSD + operating systems are also embedded in innovative Internet appliances + from Intel, IBM, Lucent, F5 Labs, Hitachi and many others.</p> + +<p>BSDI also announced that Yahoo! Inc. will take an equity interest in + the new company. BSDI will leverage the equity interest to execute on + its plan to build a bridge between open source innovation and commercial + requirements. The equity position will be used to grow BSDI's presence + as a leading provider of the most advanced Internet operating systems + for the Internet infrastructure.</p> + +<p>BSDI intends to form a united front for the BSD operating systems. The + company will deliver, support and enhance both BSD/OS and FreeBSD. BSDI + and the FreeBSD Project are jointly evaluating the technology and market + requirements for merging parts of the code bases for the two operating + systems.</p> + +<h3>The New BSDI's Leadership</h3> + +<p>"BSD technologies have evolved from a long history of advanced + computing at the core of the Internet," said Dr. Marshall Kirk + McKusick, BSDI's chairman of the board. "The new BSDI will further + enrich the popular BSD computing platform, which is already widely + deployed throughout the world." McKusick was a founding member of the + University of California at Berkeley's Computer Systems Research Group + (CSRG) and is widely acknowledged as a key early contributor to the open + source movement.</p> + +<p>To drive the new BSDI's vision, roadmap and continued profitable + growth, Gary J. Johnson has been appointed chief executive officer. + Johnson is an experienced technology executive who has served in a + variety of senior management, sales, marketing and operations capacities + with leading Silicon Valley companies including Tandem Computers + (Compaq), Convergent Technologies (Unisys) and SCO. Johnson most + recently served as president of ClickService Software, a leading + provider of e-commerce, customer relationship management (CRM) + software.</p> + +<p>"Innovation in the operating systems arena relies heavily on work in + the open source community," said Johnson. "To date, Linux suppliers, + such as Red Hat Software and VA Linux, have captured impressive + attention for the open source approach to development. At the core of + the Internet, however, BSD technologies are pervasive. The new BSDI will + be working closely with the open source community to ensure that + advanced BSD Internet operating systems and platforms continue to meet + the ever-increasing demands for Internet servers, applications, + appliances and other elements vital to the Internet infrastructure."</p> + +<p>In addition to his current responsibilities, Mike Karels, BSDI's vice + president of engineering and the former chief system architect and + principal programmer for the University of California at Berkeley's + CSRG, plans to join the architectural team for the FreeBSD Project. + Karels, who replaced Sun Microsystems co-founder Bill Joy at the CSRG, + is recognized as one of the world's foremost developers of Unix + internals and TCP/IP networking software.</p> + +<p>"BSD technologies have contributed to Yahoo!'s continued success by + offering the reliability and level of service necessary to ensure the + availability and scalability we need to keep Yahoo! up and running + around the clock regardless of increasing user demand," said David Filo, + co-founder and Chief Yahoo, Yahoo! Inc.</p> + +<h3>BSDI Continues To Deliver BSD/OS And FreeBSD; Expands And Accelerates + FreeBSD Open Source Initiatives</h3> + +<p>The new BSDI will sell and support FreeBSD, BSD/OS, BSDI Internet Super + Server and value-added BSD product lines through its worldwide sales + channels to Internet infrastructure providers, appliance developers and + business users. BSDI will offer commercially supported BSD operating + systems and related applications, Internet appliance platforms, + technical support and services, open source software development, and + consulting services. The company will deliver its BSD Internet and + networking technologies on leading microprocessor platforms, including + Intel, SPARC, Alpha, PowerPC and StrongARM.</p> + +<p>BSDI will continue to develop, enhance and distribute BSD/OS and + FreeBSD according to the terms of the business-friendly, unencumbered + Berkeley software license, which encourages development for open source + software projects, embedded systems, specialized applications, + information appliances and other operating system-enabled products.</p> + +<p>BSDI will expand and accelerate Walnut Creek CDROM's FreeBSD open + source initiatives by sharing BSD/OS technical innovations with the + FreeBSD Project and by providing this open source project with + operational and technical support, marketing and funding. BSDI will + continue to distribute packaged versions of FreeBSD and also plans to + develop value-added products based on FreeBSD as well as to provide + technical support, consulting services, educational services and + training for FreeBSD customers. These steps are expected to promote and + invigorate the BSD open source computing movement. The FreeBSD Project + develops the popular FreeBSD operating system and aggregates and + integrates contributed software from more than 5,000 developers + worldwide.</p> + +<h3>Internet and Open Source Leaders Support The New BSDI</h3> + +<p>"We are delighted that BSDI is backing the FreeBSD open source + community," said Jordan Hubbard, chief evangelist and co-founder of the + FreeBSD Project. "The new BSDI has considerable expertise in + commercializing, maintaining, distributing and supporting the world's + most advanced Internet operating systems. We are excited and greatly + looking forward to partnering with BSDI's chief developers, especially + Mike Karels and other original members of UC Berkeley's CSRG, to + accelerate operating system, networking and Internet innovation."</p> + +<p>"Open source operating systems like BSD offer better technology and + more choices to the customer," said Eric Raymond, president of the Open + Source Initiative. "I expect BSDI to prove yet again that the open + source and business communities can really to do great things together, + driving the industry forward as dramatically as the Internet."</p> + +<p>"Our research shows that BSD and Linux will increase their share of + enterprise servers by between 100 percent and 500 percent over the next + two years in the fundamental applications that run U.S. business," said + Dave Trowbridge, senior analyst at Survey.com. "This new company will + help ensure that BSD gets its place in the sun, which its rich heritage + and solid technical foundations deserve."</p> + +<h3>About the Berkeley Software Distribution Operating System</h3> + +<p>Berkeley Software Distribution operating system technologies were + originally developed from 1979 to 1992 by the Computer Systems Research + Group (CSRG) at the University of California at Berkeley. + Berkeley-derived operating system and networking technologies are at the + heart of most modern Unix and Unix-like operating systems. Today, + virtually every major Internet infrastructure provider uses BSD + operating systems. BSD operating system technologies are used by + leading mission-critical network computing environments and are embedded + in Internet appliance platforms that require advanced Internet + functionality, reliability and security.</p> + +<h3>About the FreeBSD Project</h3> + +<p>FreeBSD is a popular open source operating system developed by the + FreeBSD Project and its worldwide team, consisting of more than 5,000 + developers funneling their work to 185 "committer" developers. It is + available free of charge from ftp.FreeBSD.org and also distributed as a + shrink-wrap software product through CompUSA, Fry's, Borders, Ingram, + FreeBSDmall.com and others. FreeBSD includes thousands of ported + applications, including the most popular Web, Internet and E-mail + applications. FreeBSD is distributed under the Berkeley Software + Distribution license, which means that it can be copied and modified + freely. For more information about the FreeBSD Project, visit <a + href="http://www.FreeBSD.org/">www.FreeBSD.org</a>.</p> + +<h3>About Walnut Creek CDROM</h3> + +<p>Walnut Creek CDROM was founded in 1991 and began publishing Linux + software in 1992, and BSD software in 1993. The company has a long + history of working closely with the free software community and + providing funding, staffing and other resources for open source + projects. Walnut Creek CDROM publishes numerous software titles, + including FreeBSD and Slackware, the most BSD-like version of Linux.</p> + +<p>About Berkeley Software Design, Inc. (BSDI)</p> + +<p>Leading BSD developers founded Berkeley Software Design, Inc. in 1991 + to commercialize BSD technologies and continue the Berkeley Unix + tradition of robust, reliable and extremely secure Internet operating + systems for network computing. By merging Berkeley Software Design, Inc. + and Walnut Creek CDROM, BSDI becomes the world's leading supplier of + advanced Internet operating systems for the Internet infrastructure. + Contact BSDI at <a href="mailto:info@BSDI.com">info@BSDI.com</a> or at + <a href="http://www.BSDI.com/">www.BSDI.com</a> or call 1-719-593-9445 + (toll free: 1-800-800-4273).</p> + +<h3># # #</h3> + +<p>BSD is a registered trademark and BSD/OS and BSDI are trademarks of + Berkeley Software Design, Inc. Yahoo! and the Yahoo! logo are registered + trademarks of Yahoo! Inc. All trademarks mentioned in this document are + the property of their respective owners.</p> + +<p>Contact:<br> +Kevin Rose<br> +BSDI<br> +801-553-8166<br> +<a href="mailto:kgr@bsdi.com">kgr@bsdi.com</a></p> + +<p>Jordan Hubbard<br> +FreeBSD Project<br> +925-691-2863<br> +<a href="mailto:jkh@FreeBSD.org">jkh@FreeBSD.org</a></p> + +<p>Brigid Fuller<br> +ZNA Communications<br> +831-425-1581<br> +<a href="mailto:brigid@zna.com">brigid@zna.com</a></p> + +&footer; +</body> +</html> diff --git a/en_US.ISO8859-1/htdocs/news/press-rel-5.sgml b/en_US.ISO8859-1/htdocs/news/press-rel-5.sgml new file mode 100644 index 0000000000..7f6312db6c --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/press-rel-5.sgml @@ -0,0 +1,134 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA ".."> +<!ENTITY date "$FreeBSD: www/en/news/press-rel-5.sgml,v 1.7 2005/10/04 19:43:48 hrs Exp $"> +<!ENTITY title "FreeBSD Press Release: October 18, 2000"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<html> +&header; + +<p></p> + +<h3>New FreeBSD Core Team Elected</h3> + +<p><b>BSD Conference, Monterey, CA, October 18, 2000</b> The FreeBSD Project +announced today the election of a new Core Team, the project's management +board. This marks the first occasion on which the team has been selected +by means of an election among the project's developers. Joining the Core +team as new members are Greg Lehey, Warner Losh, Mike Smith, and Robert +Watson. Re-elected members are Satoshi Asami, David Greenman, Jordan +Hubbard, Doug Rabson, and Peter Wemm.</p> + +<p>FreeBSD Project co-founder and continuing Core Team member Jordan +Hubbard expressed excitement over the results, <cite>"For the first time +since the FreeBSD project was formed, open elections have determined +the composition of its core team and set an important precedent +whereby any developer can now become part of the project's +leadership."</cite> The new core team also well-represents FreeBSD's +diverse and highly skilled group of international developers, with +expertise ranging from RAID filesystem and device-driver development +to extensive security backgrounds.</p> + +<p>New Core Team members were elected from and by the FreeBSD committers +team, the formal development staff of the FreeBSD project. Committers +have direct access to the FreeBSD source repository, and perform the +majority of software development associated with the project. Until this +point, the Core Team was a self-selected board providing architectural and +administrative direction.</p> + +<p>This summer, the committers voted to move to a democratic model allowing +the project to adapt to the changing development requirements of the open +source operating system community. However, with over half of the prior +Core Team re-elected from the old team, strong continuity exists.</p> + +<p>Departing Core Team member Poul-Henning Kamp said, <cite>"I'm +very proud of what we have done together in the Core Team over the last +8 years. The new Core, and the fact that they are elected by the +committers, means that the project will be much more responsive to +change in the future."</cite></p> + +<p>The changing of the guard in project leadership comes amid good feelings, +Kamp indicated: all past Core members will continue on with the project +with increased emphasis on development, <cite>"Now I get to spend more time on +the FreeBSD source code instead of on project management."</cite></p> + +<h3>Elected Core Team Members</h3> + +<p><b>Satoshi Asami</b> is a co-founder and CTO of DecorMagic, Inc., and manages +the FreeBSD Ports Collection.</p> + +<p><b>David Greenman</b> is a co-founder of the FreeBSD Project and is currently +President of TeraSolutions, Inc., a company that manufactures Internet +servers and RAID storage systems.</p> + +<p><b>Jordan Hubbard</b> is a co-founder of the FreeBSD Project as well as its +public relations officer and release engineer. He is also Vice President +for Open Source Solutions at BSDi.</p> + +<p><b>Greg Lehey</b> is an Open Source Researcher with Linuxcare; he has spent +most of his professional career in Germany, where he worked for +computer manufacturers such as Univac, Tandem, and Siemens-Nixdorf. +He is the author of the Vinum volume management and RAID software for +FreeBSD, has been involved in the FreeBSD SMPng project, and is the +author of Porting Unix Software and The Complete FreeBSD.</p> + +<p><b>Warner Losh</b> has been porting NetBSD's pccard code to FreeBSD and has +been FreeBSD Security Officer for the past two years.</p> + +<p><b>Doug Rabson</b> is a co-founder of Qube Software Ltd., which specializes +in 3D graphics technology. His work on FreeBSD includes the alpha and +ia64 ports, and he was the main architect for FreeBSD's device driver +framework.</p> + +<p><b>Mike Smith</b> is Principal Engineer in BSDi's Open Source Solutions group +and has been active in the FreeBSD developer community as a developer +resource, OEM liaison, sometime architect and device driver author.</p> + +<p><b>Robert Watson</b> is a research scientist at NAI Labs, working on network +and operating system security research. His contributions to the +FreeBSD Project include work on trusted operating system extensions +(<a href="http://www.trustedbsd.org">TrustedBSD</a>), +security architecture, and work on the security-officer team.</p> + +<p><b>Peter Wemm</b> has been involved with FreeBSD since the early days of the +ISP Industry in Australia and has since relocated to the US to work as +a Software Engineer for Yahoo!, Inc. His involvement in FreeBSD +includes management of the FreeBSD source code repository and kernel +development.</p> + +<h3>About FreeBSD</h3> + +<p>FreeBSD is a liberally-licensed open source operating system with its +origins in BSD Net/2 and 4.4 Lite, the Berkeley Software Distributions +developed at the University of California at Berkeley until 1994. It +is developed and maintained by a global organization of paid and +volunteer contributors. FreeBSD is distinguished by its high +performance networking and filesystem support, and is widely used +among Internet service providers, including industry-recognized +companies such as <b>Yahoo!</b>, <b>above.net</b>, +and <b>Verio</b>. FreeBSD is also +frequently used as a platform for embedded networking devices, +including products from <b>IBM</b>, <b>Inktomi</b>, <b>Juniper Networks</b>, +and <b>Network Alchemy - a Nokia Company</b>.</p> + +<p>More information may be found at +<a href="http://www.FreeBSD.org">http://www.FreeBSD.org/</a>.</p> + +<h3>Press Contact</h3> + +<p>Jordan Hubbard<br> +The FreeBSD Project<br> +925-682-7859<br> +<a href="mailto:jkh@FreeBSD.org">jkh@FreeBSD.org</a></p> + +<h3># # #</h3> + +<p>BSD is a registered trademark of Berkeley Software Design, Inc. Other + trademarks are property of their respective owners. BSD technologies were + originally developed by the University of California, Berkeley and its + contributors.</p> + +&footer; +</body> +</html> diff --git a/en_US.ISO8859-1/htdocs/news/press-rel-6.sgml b/en_US.ISO8859-1/htdocs/news/press-rel-6.sgml new file mode 100644 index 0000000000..2b88a5e719 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/press-rel-6.sgml @@ -0,0 +1,103 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA ".."> +<!ENTITY date "$FreeBSD: www/en/news/press-rel-6.sgml,v 1.3 2005/10/04 19:43:48 hrs Exp $"> +<!ENTITY title "FreeBSD Press Release: October 31, 2002"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<html> +&header; + +<p></p> + +<h3>The Daemon of the Opera: Opera Software Releases Version for FreeBSD</h3> + +<p><b>Oslo, Norway, October 31, 2002:</b> Opera Software is proud to +announce the first golden release of its new port to the UNIX variance +FreeBSD. With FreeBSD joining the Opera family, Opera is now available on +eight different operating systems.</p> + +<p>The BSD (Berkeley Software Distribution) operating system has its origins +at the University of California, Berkeley. It started out as a supplement to +UNIX, but over time it evolved into several operating systems. Of the +different BSD flavors available, the most widely distributed is FreeBSD, +popular among high-end users like system administrators who are looking for a +fast, reliable operating system.</p> + +<p><cite>"Opera and FreeBSD´s users are alike in that they emphasize and +expect stability and reliability. The match between FreeBSD and Opera should +strike a cord with many enterprise customers,"</cite> says Jon S. von +Tetzchner, CEO, Opera Software ASA. <cite>"On a personal level, I'm also happy +to welcome FreeBSD users into the Opera family. FreeBSD is strictly not only +an operating system, but also a community and a philosophy with values I know +resonate well with our own."</cite></p> + +<p>The FreeBSD community is enthusiastic to finally be able to surf with +Opera.</p> + +<p><cite>"With the release of Opera for FreeBSD, FreeBSD users who download +Opera for FreeBSD can browse the Web with one of the fastest browsers +available on the market,"</cite> says Robert Watson, FreeBSD Core Team member. +<cite>"FreeBSD´s reputation as a reliable and fast desktop operating system is +becoming widely known, and we are glad to see that Opera Software is helping +us create a more complete desktop environment."</cite></p> + +<p>Opera 6.1 for FreeBSD can be downloaded from +<a href="http://www.opera.com/">www.opera.com</a>.</p> + +<h3>About Opera Software</h3> + +<p>Opera Software ASA is an industry leader in the development of Web +browsers for the desktop and embedded markets, partnering with companies +such as IBM, AMD, Symbian, Canal+ Technologies, Ericsson, Sharp and Lineo +(now a division of Embedix). The Opera browser has received international +recognition from end users and the industry press for being faster, +smaller and more standards-compliant than other browsers. Opera is +available on Windows, Mac, Linux, Solaris, FreeBSD, OS/2, Symbian OS and +QNX. Opera Software ASA is a privately held company headquartered in Oslo, +Norway. Learn more about Opera at +<a href="http://www.opera.com/">www.opera.com</a>.</p> + +<h3>About the Berkeley Software Distribution Operating System</h3> + +<p>Berkeley Software Distribution operating system technologies were +originally developed from 1979 to 1992 by the Computer Systems Research +Group (CSRG) at the University of California at Berkeley. Berkeley-derived +operating system and networking technologies are at the heart of most modern +Unix and Unix-like operating systems. Today, virtually every major Internet +infrastructure provider uses BSD operating systems. BSD operating system +technologies are used by leading mission- critical network computing +environments and are embedded in Internet appliance platforms that require +advanced Internet functionality, reliability and security.</p> + +<h3>About the FreeBSD Project</h3> + +<p>FreeBSD is a popular open source operating system developed by the FreeBSD +Project and its worldwide team, consisting of more than 5,000 developers +funneling their work to 185 "committer" developers. It is available free of +charge from <a href="ftp://ftp.FreeBSD.org/">ftp.FreeBSD.org</a> and also +distributed as a shrink-wrap software product through CompUSA, Fry's, Borders, +Ingram, FreeBSDmall.com and others. FreeBSD includes thousands of ported +applications, including office automation, groupware and multimedia +applications, and is widely used in companies all over the world as a web +server, file server, firewall and router. FreeBSD is distributed under the +Berkeley Software Distribution license, which means that it can be copied and +modified freely or commercially. For more information about the FreeBSD +Project, visit <a href="http://www.FreeBSD.org/">www.FreeBSD.org</a>.</p> + +<h3>Press Contact</h3> + +<p>Opera Software<br> +Pal A. Hvistendahl<br> +Marcom Director<br> +Tel: +47 99 72 43 31<br> +Fax: +47 24 16 40 01<br> +<a href="mailto:pal@opera.com">pal@opera.com</a><br> +US Toll Free: 1-888-624-4846, press only please</p> + +<p>The FreeBSD Project<br> +<a href="mailto:press@FreeBSD.org">press@FreeBSD.org</a></p> + +&footer; +</body> +</html> diff --git a/en_US.ISO8859-1/htdocs/news/press-rel-7.sgml b/en_US.ISO8859-1/htdocs/news/press-rel-7.sgml new file mode 100644 index 0000000000..afc4af8f81 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/press-rel-7.sgml @@ -0,0 +1,76 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA ".."> +<!ENTITY date "$FreeBSD: www/en/news/press-rel-7.sgml,v 1.5 2005/10/04 19:43:48 hrs Exp $"> +<!ENTITY title "FreeBSD 5.0 Press Release"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<html> +&header; + +<h3>FreeBSD Project announces FreeBSD 5.0</h3> + + <p><b>Berkeley, CA - January 20, 2003 - The FreeBSD Project</b> The + FreeBSD Project announced today the availability of FreeBSD 5.0 + after almost three years of continuous development. The latest + version of the project's powerful open source operating system + includes several ground breaking features:</p> + +<ul> + <li><b>Multiprocessor support</b> has been extended and enhanced. + We support SMP on all platforms, and have the infrastructure in + place for extensive performance improvements.</li> + + <li><b>Background filesystem checks</b> offer quicker start up in + disaster situations.</li> + + <li><b>File system snapshots</b> permit administrators to + duplicate file systems in real time.</li> + + <li><b>Experimental support for Mandatory Access Controls (MAC)</b> + provides an extensible and flexible means for administrators to + define system security policies.</li> + + <li><b>Kernel Schedulable Entities</b> implement a high-performance + many-to-many multiprocessor threading model.</li> + + <li><b>Expanded hardware support</b> now includes hardware + cryptographic acceleration, ACPI, Bluetooth, and FireWire.</li> + +</ul> + + <p>The release also includes new, reimplemented, and incremental + improvements in areas where FreeBSD already dominates, such as + network performance, stability, and reliability.</p> + + <p><cite>"This release represents our largest engineering success to + date."</cite>, says Murray Stokely, Vice President of Engineering + at FreeBSD Mall Inc and member of the FreeBSD Release Engineering + Team. <cite>" The new technologies present in FreeBSD 5.X will + provide our customers with exciting new functionality without + sacrificing our legendary reliability."</cite> + +<h3>About the FreeBSD Project</h3> + + <p>The FreeBSD Project provides a free UNIX-like operating system + for the Intel-compatible, Alpha, and Sparc platforms, based on the + industry-standard Berkeley Software Distribution. The FreeBSD + Project includes several thousand developers from dozens of + countries around the world, who funnel their work through a team + of several hundred committers. FreeBSD is available for free on + the Internet, and as a shrink-wrap product through many different + retail vendors, listed at <a + href="http://www.FreeBSD.org/vendors.html">www.FreeBSD.org/vendors.html</a>. + For more information, please visit FreeBSD on the Web at <a + href="http://www.FreeBSD.org/">www.FreeBSD.org</a>.</p> + +<h3>Press Contact</h3> + + <p><a href="mailto:press@FreeBSD.org">press@FreeBSD.org</a>, or phone + 1-925-674-0783</p> + +&footer; +</body> +</html> + + diff --git a/en_US.ISO8859-1/htdocs/news/press-rel-8.sgml b/en_US.ISO8859-1/htdocs/news/press-rel-8.sgml new file mode 100644 index 0000000000..1263befebd --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/press-rel-8.sgml @@ -0,0 +1,66 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA ".."> +<!ENTITY date "$FreeBSD: www/en/news/press-rel-8.sgml,v 1.1 2005/11/05 13:10:53 ceri Exp $"> +<!ENTITY title "FreeBSD Project Launches FreeBSD 6.0"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<html> +&header; + +<h3>FreeBSD raises the bar for open source operating systems.</h3> + + <p>FOR IMMEDIATE RELEASE<br> + Berkeley, CA November 4, 2005</p> + + <p>The FreeBSD Project announces the availability of FreeBSD 6.0, an open + source operating system derived from BSD UNIX, which offers a powerful + alternative to Linux, Solaris, and Windows. FreeBSD enables enterprise + organizations to utilize open source technologies that focus on + reliability, security, and scalability.</p> + + <p>"Yahoo! is impressed with the performance and stability of FreeBSD 6.0," + says David Filo, Yahoo! co-founder. Yahoo! is one of many enterprise + companies that rely on the world-renowned stability and performance of the + FreeBSD operating system.</p> + + <p>One of the new features in FreeBSD 6.0 is a multithreaded filesystem, + which greatly improves data access times for local disks, RAID + configurations, network filesystems, and SANs. Recent performance + benchmarks show that FreeBSD 6.0 outperforms Linux in raw data + throughput.</p> + + <p>Additionally, FreeBSD 6.0 extends support for wireless devices such as + Intel Centrino and adds support for the popular new WPA wireless security + protocol. Several improvements are incorporated into NDISulator, a + component of the operating system that allows Windows network drivers to + run natively under FreeBSD.</p> + + <p>FreeBSD now scales much more efficiently across multiple processor + systems. Support for 8 or more processors, such as the new dual core AMD + Opteron configurations, gives consumers a viable alternative against more + expensive, proprietary hardware platforms and operating systems from IBM, + HP, and Sun.</p> + +<h3>About the FreeBSD Project</h3> + + <p>The FreeBSD Project provides a free, open source operating system for + several platforms, including Intel x86 and AMD64. FreeBSD is derived from + BSD, the version of UNIX developed at UC Berkeley. The unencumbered BSD + license permits modification and redistribution of the software while + allowing an individual or company to retain intellectual property.</p> + + <p>For more information, please visit + <a href="http://www.FreeBSD.org/">www.FreeBSD.org</a>.</p> + +<h3>Press Contact</h3> + + <p>For interviews or further information, contact: <a + href="mailto:marketing@FreeBSD.org">marketing@FreeBSD.org</a>, + +1-408-943-4100 ext 113; or The FreeBSD Foundation, +1-720-207-5142</p> + +&footer; +</body> +</html> + + diff --git a/en_US.ISO8859-1/htdocs/news/press-rel-9.sgml b/en_US.ISO8859-1/htdocs/news/press-rel-9.sgml new file mode 100644 index 0000000000..6cc59b6ed2 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/press-rel-9.sgml @@ -0,0 +1,76 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA ".."> +<!ENTITY date "$FreeBSD: www/en/news/press-rel-9.sgml,v 1.1 2006/01/07 04:07:38 jkoshy Exp $"> +<!ENTITY title "Hewlett-Packard donates blade cluster to FreeBSD"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<html> +&header; + +<!-- +<img src="../gifs/news.jpg" align="right" border="0" alt="FreeBSD News"> +--> + +<p></p> + +<p><b>The FreeBSD Foundation received a donation of a blade system from +Hewlett-Packard for use as a third-party software build cluster. +This 20-node HP BladeSystem cluster triples the speed of the build +process for i386 packages.</b></p> + +<p><i>"With this generous donation from HP, we are able to continuously +produce up-to-date packages from more than 13000 ports of third-party +software available in the FreeBSD Ports Collection, at about three +times the rate of the previous hardware cluster,"</i> said Kris Kennaway, +member of the FreeBSD Port Management Team.</p> + +<p><i>"This directly benefits the users of FreeBSD through the rapid +availability of new and updated software packages, and through the +increased testing and QA of FreeBSD that the new hardware allows."</i></p> + +<p><i>"We at HP recognize the important role of FreeBSD in the Internet's +global network infrastructure, and we are happy that the HP +BladeSystem cluster can contribute to the on-going success of the +FreeBSD Foundation,"</i> said Mark Potter, vice president of the +Hewlett-Packard BladeSystem division.</p> + +<p><i>"They're just standard i386 systems, architecturally, with a very +nice ssh- and serial-based management server,"</i> said Kennaway, who +maintains the FreeBSD Ports cluster.</p> + +<p>Kennaway said FreeBSD has a few dozen other machines scattered +around the globe for package builds. A big concentration of sparc +machines hosted by Hiroki Sato in Japan include some large +multiprocessor e4500's (10, 12 and 14 CPUs) that have been extremely +valuable for SMP testing. Also, a couple of machines hosted by ISC, +an amd64 hosted by Scott Long, three i386 machines at Yahoo! Korea, +and sometimes Kennaway's own machines in Canada are used for the +official package builds.</p> + +<p>The HP BladeSystem cluster is hosted at the Yahoo! datacenter in +the San Francisco Bay area. In addition to Kennaway, Paul Saab +and Peter Wemm from the FreeBSD project, and John Cagle from HP +helped with blade system setup.</p> + +<h3>About The FreeBSD Project</h3> + +<p>The FreeBSD Project provides an up-to-date and scalable modern operating +system that offers high-performance, security, and advanced networking for +personal workstations, Internet servers, routers, and firewalls. The +FreeBSD packages collection includes popular software like Apache Web +Server, Gnome, KDE, X.org X11 Window System, Python, Mozilla, and over +13,000 software suites. FreeBSD can be found on the Internet at +<a href="http://www.FreeBSD.org/">http://www.FreeBSD.org</a>.</p> + +<h3>More Information:</h3> + +<p>FreeBSD Ports webpage<br> +<a href="http://www.freebsd.org/ports/">http://www.FreeBSD.org/ports/</a> +<br><br> +FreeBSD Package building logs and errors webpage<br> +<a href="http://pointyhat.freebsd.org/errorlogs/">http://pointyhat.freebsd.org/errorlogs/</a></p> + +&footer; +</body> +</html> diff --git a/en_US.ISO8859-1/htdocs/news/pressreleases.sgml b/en_US.ISO8859-1/htdocs/news/pressreleases.sgml new file mode 100644 index 0000000000..7fd49a6dcc --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/pressreleases.sgml @@ -0,0 +1,87 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA ".."> +<!ENTITY date "$FreeBSD: www/en/news/pressreleases.sgml,v 1.14 2008/12/08 09:21:40 murray Exp $"> +<!ENTITY title "FreeBSD Press Releases"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<html> +&header; + +<!-- +<img src="../gifs/news.jpg" alt="FreeBSD News" align="right" border="0" alt="FreeBSD News"> +<p></p> +--> + +<p>Most press releases are now handled by the <a href="http://www.FreeBSDFoundation.org/press/">FreeBSD Foundation</a>.</p> + +<dl> + +<dt>November 25, 2005</dt> +<dd> +<a href="press-rel-9.html">Hewlett-Packard donates blade cluster to FreeBSD</a> +<p></p> +<dd> + +<dt>November 4, 2005</dt> +<dd> +<a href="press-rel-8.html">FreeBSD Project Launches FreeBSD 6.0</a> +<p></p> +</dd> + +<dt>January 20, 2003</dt> +<dd> +<a href="press-rel-7.html">FreeBSD Project announces FreeBSD 5.0</a> +<p></p> +</dd> + +<dt>October 31, 2002</dt> +<dd> +<a href="press-rel-6.html"> +The Daemon of the Opera: Opera Software Releases Version for FreeBSD +</a> +<p></p> +</dd> + +<dt>October 18, 2000 : New Core</dt> +<dd> +<a href="press-rel-5.html"> +First FreeBSD Core Team Elections +</a> +<p></p> +</dd> + +<dt>March 9, 2000</dt> +<dd> +<a href="press-rel-4.html"> +BSD Suppliers Unite to Deliver the World's Most Popular Internet Operating +Systems</a> +<p></p> +</dd> + +<dt>June 7, 1999</dt> +<dd> +<a href="press-rel-3.html"> +BSD Community Welcomes Apple's New Open Source Operating System.</a> +<p></p> +</dd> + +<dt>April 29, 1999</dt> +<dd> +<a href="press-rel-2.html">Complete XML Development System Integrated +with FreeBSD.</a> +<p></p> +</dd> + +<dt>April 22, 1999: The Matrix</dt> +<dd> +<a href="press-rel-1.html">FreeBSD Used to Generate Spectacular Special +Effects for the Warner Brothers film <em>The Matrix</em>.</a> +<p></p> +</dd> + +</dl> + +&footer; +</body> +</html> diff --git a/en_US.ISO8859-1/htdocs/news/sou1999.sgml b/en_US.ISO8859-1/htdocs/news/sou1999.sgml new file mode 100644 index 0000000000..8cb3d1a88d --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/sou1999.sgml @@ -0,0 +1,374 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA ".."> +<!ENTITY date "$FreeBSD: www/en/news/sou1999.sgml,v 1.7 2005/10/04 19:43:48 hrs Exp $"> +<!ENTITY title "FreeBSD State of the Union, 1999"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<html> + &header; + + <p><i>From Jordan Hubbard <jkh@FreeBSD.ORG>, Sunday January 10th, + 1999.</i></p> + + <p>Well, it's another year behind us, folks, and probably high time for + another state of the union report!</p> + + <p>Ahem... I'm never quite sure how to word these things since I'm + always reminded of a U.S. president sitting in front of fireplace, + trying to sound down-home and folksy for the corn growing states, or + perhaps England's Queen on Christmas day, giving her usual + somber-yet-hopeful address on how things went for Britannia during the + previous year and what everyone should perhaps think about for the + next. Neither one of those is really me, basically, so perhaps I'll + just cut to the chase and focus on the most pertinent lessons (and + objectives) to come out of the year 1998 for me.</p> + + <p>1998 was, of course, the year that the Internet got bigger (no + surprise), various "internetpraneurs" (gag) got richer and FreeBSD's + user base, as measured by the ftp download stats grew at its usual + 200-300% rate. More companies also entered the FreeBSD arena, either + offering add-ons for or solutions incorporating FreeBSD, and our PR + machine, as flimsy and low-key as it often is, managed to ratchet + things up another notch. All in all, it was a very good year for + FreeBSD and I don't think that even the most paranoid of us could + claim otherwise - Microsoft took one in the shorts, we got bigger and + just a bit better known, life was good.</p> + + <p>Well, mostly. Whipping off my rosy glasses for a second, I can also + say that there were still a number of rocks in the road and unexpected + bends that left us not always in the best of control there. While + downloads have gone up, CD sales aren't quite following suit since the + whole CD market in general is suffering from increased Internet + availability and its erosion of some of the CD's fundamental + advantages. We still did quite well, considering the market's gradual + implosion, but it would be foolish to continue to rely on a single CD + product to provide the kinds of subsidies that have been steadily + oiling the project's gears (we more than doubled the size of the + FreeBSD.org computing cluster, for example, and significantly enlarged + our developer equipment grant program in 1998, all things which cost + $$$). It's fairly obvious that Walnut Creek CDROM will need to + increase the number of products it offers if it wishes to remain an + effective player in the FreeBSD game and we must continue, as a + project, to be flexible in exploring all types of relationships with + those who may now have a vested interest in FreeBSD's success. Things + are well past the point where we can do everything that needs to be + done as a serious and "grown up" solution just on good will and + volunteerism alone.</p> + + <p>With that in mind, sites like the <a + href="http://www.freebsdmall.com">FreeBSD Mall</a> + have been set up to try and market a wider variety of FreeBSD-related + products and we've also begun exploring relationships with various + companies who can derive measurable value from any PR campaign that + enhances FreeBSD's reputation (translation: we want them to help pay + for it :). As many people have somewhat bitterly pointed out by now, + this business has become a 10% technology and 90% perception equation + as far as the direction in which people stampede is concerned, and + hate them for the mindless little sheep that they are, you still need + to understand people's tendencies and behavioral patterns when it + comes to dealing with anything they don't really understand. We've + done a great job on the technology, we really have (and should be + proud of that), but all too frequently we just throw up our hands over + the perception issue and tell people to think whatever the hell they + want to. Bad techies! Myopic techies! :-)</p> + + <p>What can we do to change this in 1999? Well, I've also heard our + advocate corps calling for logistical support ("Backup! We need some + <em>backup</em> here!!") and I've listened to them, part of my project + for the new years being to get more digital daemon imagery made available + (which I have already commissioned), more glossies with various handy + comparison charts on them ("FreeBSD and NT", "FreeBSD and Solaris", + "FreeBSD and Linux", etc) and more newsletters for passing out to people. + We can also produce more marketing periphenalia like buttons, stickers, + new T-shirts, etc. to give people a wider array of stuff to proudly point + to in support of the "emerging FreeBSD phenomenon." If we can manage to + raise more money for PR, we can also perhaps buy some of these items in + bulk to use as give-aways in various promotional deals. Other than that, + I'm always open to suggestions. We need to do more effective PR, that + much is inarguable, it's only a question of picking our targets for + maximum effect given a limited operating budget.</p> + + <h2>The core team:</h2> + + <p>1998 also ended with a bit of a bang as far as FreeBSD's project + management was concerned, frustration with a mostly recumbent core + team goading a couple of bearded Danish Vikings into staging a + midnight raid on -current, ruthlessly culling the weak and the lame + from the source tree. Unfortunately, some of those weak or lame bits + of code were still in use at the time and, with no prior public + warning having been given, it did not exactly leave the various + followers of -current with the feeling that the event was going to be + the highlight of their Christmas season. Their complaints led, in + turn, to something of a constitutional crisis within core, the rival + factions each accusing one another of either impeding progress or + using cowboy tactics to achieve that progress, and each faction had + its legitimate points just as it had its wholly unreasonable ones. + Coming out of this, various suggestions were bandied about concerning + how we might put together a "better core team" to which such things + simply did not happen (or, if they did, would not be our fault since + we'd all be long gone :-) and many of these suggested cures were + eventually deemed, quite rightly, to be worse than the disease. So + what did we learn from the exercise then?</p> + + <p>First off, I think everyone is now pretty much in agreement that these + sorts of drive-by shootings are just not an option for the future, no + matter what the justification. Anyone who contemplates a major + addition or removal of functionality from the source tree MUST + communicate those intentions well in advance and give the readership + of -current, -stable or -announce (the former two depending on the + branch the changes affect and the latter on the extent of the changes) + ample time to respond. If there is a conclusively negative response + to a proposed change, it just doesn't happen until and unless the + proposal somehow manages to win people over through sheer dint of + persuasive argument in its favor. If it's more a mixed bag of + reactions, or there is little reaction at all, the developer is free + to proceed at his or her discretion but still never without advance + notice.</p> + + <p>Second, in reaction to the various proposals put forward to either gut + core or have core elected by popular vote, let me just say that we're + not going to do that. There are probably several people currently in + core who would gladly step aside and retire if they felt that adequate + replacements had been found and the project was in good hands, but + none of us like the scenario where anyone is overtly forced out of + core. It's just not a reasonable way of going about it when so many + less painful alternatives exist, and I, for one, would far rather + simply grow core and let the inactive members fall off when they + themselves have come to a decision that they have nothing left to + contribute at a "core level", resignation from core having not stopped + several folks from remaining as effective committers or making other + valuable contributions.</p> + + <p>We're a free software project and nobody's paid to be in core, no + matter how seriously we may be tempted to take the whole core thing + sometimes, and we need to remember that all of this started as a bunch + of folks who simply wanted to work together in creating something + useful and interesting. The day we lose that kind of informal + atmosphere of productivity over politics is the day that something + pretty fundamental goes out at the center of core and also the day + that I'll retire from it myself, handing my hat to a replacement and + wishing everyone the very best of luck.</p> + + <p>I can also only sound a similar cautionary note about the idea of + electing core from the user base, or with committers serving as a kind + of "electoral college", as nice and democratic an idea as that might + sound. The FreeBSD core team does not represent a democratically + selected body and was, in fact, very carefully put together in a very + non-democratic way. We picked core with the specific intention that + it represent as diverse a set of hard-core FreeBSD evangelist/developers + as we knew how to find and we've continued to add people using the + same criteria.</p> + + <p>In bringing someone into core, we don't look at whether they've been + winning popularity contests lately or won the Programming Olympiad 3 + times in a row, we ask ourselves: "Does this person bring a unique + talent or viewpoint to the group? Will the resulting whole be greater + than the sum of its parts?" These are our two most overriding + concerns and, in fact, are the only grounds on which we've ever felt + it necessary to actually ask for someone's resignation from core. We + can tolerate quite a bit from people but not when it impacts core's + fundamental ability to work together or seeks to undermine the very + diversity of opinion we've worked so hard to cultivate. It's good to + be an effective group of decision makers as a core team, and we do + have our moments (both ways), but sometimes it's even better to know + simply when to stay out of the way and just make sure the train stays + roughly on the tracks. We've prevented a lot more stupidity through + having such a diverse and carefully selected core team than I think + we've ever caused and I do not trust the democratic process to leave + us with the same thing after a few elections.</p> + + <p>Core is also continuing to work on drafting some internal documents + which cover, in much better detail, just what our rules as committers + are, those superseding any "core member privileges", governing how + large-scale code removal and addition operations should be carried + out. We'll post something to committers just as soon as we finally + flesh it out to our mutual satisfaction but, in a nutshell, it + basically just insists that people need to be warned before such + changes happen and that the owner of a given body of code should be + given first say as to whether or not it's time to kill it in the name + of obsolescence or redundancy. Finally, we are looking at the general + issue of communication inside and outside core and the question of + whether or not to bring in some new member(s) at this time. That + discussion is ongoing and I'll do my best to keep everyone up to date + on that as things progress.</p> + + <h2>Release numbering:</h2> + + <p>Other decisions on the horizon concern returning to our former + practice of using "major" version numbers for branches and "minor" + numbers for releases, the revision number field only being used to + denote point-releases which were done for some reason significant + enough to merit such a special release. This means that the next + release will be 3.1, not 3.0.1, and the new branch will be 4.0-current + instead of 3.1-current. Is this just a marketing ploy? No, it's not, + though marketing has indeed been a frequent casualty of our current + numbering scheme.</p> + + <p>We have frequently made fairly large changes between our "point + releases", jumps like 2.2.5->2.2.6 and 2.2.6->2.2.7 being a lot bigger + than most folks gave them credit for given that it was just one little + revision number being changed. This one simple facet of human nature + reduced the effectiveness of these releases and under-sold the work + being done by our developers to substantially improve <em>every</em> + release we do, regardless of which branch it's on.</p> + + <p>This is not a trend which seems to be reversing itself and so I feel + quite safe in saying that 3.1 will be a "full release" over 3.0 in its + own right and not merely the "3.0.1" which conveys such a different + impression. It's also very important to note that since our branches + seem to typically last from 12-18 months these days, no matter what we + try in attempting to kill a branch earlier, a major version bump (4.0) + is entirely merited for something which won't see full release status + until sometime in the year 2000. This will make the marketing people + happy since they won't have such an uphill battle on number perception + and it will make the users happy since they'll get a clearer picture + of what changed in, say, 3.1 to 3.2 vs 3.1 to 3.1.1 (which might be an + important security update). It will also make this particular + developer happy since I'll have the revision number space back again + for doing point releases. It's a win and so we're going to do it. + 3.0.1 is dead, long live 3.1! :)</p> + + <h2>Technology:</h2> + + <p>This last year also saw a successful transition to ELF from a.out + format and a new kernel loadable module scheme which allows modules to + be read in without a runtime dependency on /usr/bin/ld. We also got a + new boot loader (with a forth interpreter!) to aggregate a "kernel" at + boot time. These are both powerful new mechanisms and, coupled with + some new stuff which will be coming in 1999, should give us a far more + dynamic and extensible system than we've ever had before.</p> + + <p>Not to be overlooked is also our new SCSI CAM system, giving us more + robust behavior with large drive arrays and supporting more of the + high-end SCSI controllers, or the support for multiple processors on + the x86. We made considerable progress all across the board with the + release of 3.0, finally reaching a point with the DEC Alpha + architecture port where people starting worrying more about the + packages collection than they did about working kernels or a /usr/src + which built. That represents considerable progress towards "genuine + usefulness" and I hope that 1999 will see a fully desktop capable + release of FreeBSD/axp (to say nothing of a server capable one), + various difficulties with X server technology making the Alpha desktop + a unique milestone in its own right, especially if it's on an ARC or + AlphaBIOS machine. 1999 may also see the early release of a SPARC + port, though it's still far too early to say anything more definite + than that. Join the <a + href="mailto:sparc@FreeBSD.org">sparc@FreeBSD.org</a> mailing list if + you want to follow these efforts.</p> + + <p>IPv6 and IPSec were also hotly debated topics in 1998, FreeBSD's + refusal to back any specific implementation being cited by many as an + example of core's over-conservatism in action. Happily for everyone, + our wait-and-see attitude proved to be the right one when the two + major "competing" groups, KAME and INRIA, finally agreed to merge + their implementations. We have, in turn, committed to adopting this + merged implementation and have several people from the KAME/INRIA + groups on the FreeBSD development team who will be importing and + maintaining this code as it becomes available.</p> + + <p>There is also substantial work underway with the VM system and the + filesystem code, much of which is either being tested quietly in small + groups (Dillon/Dyson/Greenman) or is awaiting the 4.0 branch event, + still scheduled for January 15th, 1999. In other areas, we have + Kazu's very welcome total redesign of the console driver coming into + -current along with USB support, courtesy of Nick Hibma and others. + This is just to name a few of the projects underway and I don't mean + to slight anyone by not mentioning theirs directly, these are just 3 + ongoing projects right off the top of my head. We seem to be gaining + a lot of technical momentum, and that's great, just so long as we can + also keep our heads during the times where not everyone is in total + agreement about which technical direction to take.</p> + + <h2>Tech support:</h2> + + <p>A point which should also be obvious to everyone yet still somehow + requires frequent reinforcement is the fact that we need to maintain + participation in this project as something which is also + <em>enjoyable</em> for the developer/participants or they will just as + quickly go away again and stop giving each and every one of us the + benefit of their volunteer labor (on which a dollar value could not + even be put). This is something which each and every one of our + users needs to be aware of, at least somewhere in the back of their + minds, for those times when they're tempted to start thinking of + FreeBSD as just another shrink-wrap solution from Software, + Inc. and start treating project members like personal employees. + Those looking for actual FreeBSD employees should send mail to + <a href="mailto:jobs@FreeBSD.org">jobs@FreeBSD.org</a> and indicate how + much money they're willing to pay, otherwise don't do it.</p> + + <p>I don't mean to come across so harshly here that people don't even + bother asking us for help, I'm simply saying that those users who + avail themselves of the various FreeBSD volunteer tech support + mechanisms out there (mail, news, irc, etc) should always understand + that asking another perfect stranger for help is just not much + different from asking a random person on the street for a dollar. If + you want to get free handouts, you'd better at the very least learn to + ask politely and when to take "no" for an answer! :-) I've seen a lot + of abuse of the various tech support forum volunteers this last year + and it frankly sucks. People just need to be more considerate and + stop regarding free tech support as a god-given right rather than a + very special privilege. If you want on-demand tech support, go to + www.freebsdmall.com and order yourself a tech support contract. You + get what you pay for! :)</p> + + <h2>Looking forward:</h2> + + <p>What do I see ahead for 1999? Well, assuming that we don't all vanish + in some pre-millennial holocaust, I see more interesting new features, + improved marketing, more commercial interest, more magazine articles + and press attention, basically more of the same if we can just try to + stay reasonably well focused on what we need to do and not get + distracted into chasing weird desktop dreams or suddenly become overly + minimalist or kitchen-sink biased in /usr/src, continuing to chart the + middle course we're more famous for. The FreeBSD core team, one year + older and hopefully a little wiser, needs to continue keeping a light + but steady hand on the tiller, relying on our developers as usual to + provide much of the actual motive force behind FreeBSD.</p> + + <p>Our users also need to become more involved and I'm hoping that 1999 + will be the year when a lot more local user groups and other self-help + type of organizations are formed. The Handbook and FAQ are documents + which are getting better, hopefully another trend we'll see continue + into 1999 as Nik Clayton, our fearless new Documentation Project + leader, continues at the helm. We still have to remember, however, + that for many users the handbook and FAQ docs are just not enough.</p> + + <p>Linux has succeeded largely because of a large grass-roots support and + evangelism network which allows it to reach such people and + communicate the message to them. If FreeBSD's own users want to see + FreeBSD doing better against whomever they most perceive as its + competition, and 1998 was certainly a year where I heard a lot of + complaining about this, then they're going to simply have to get off + their collective duffs and put in more of this kind of work. When was + the last time a bunch of FreeBSD users got together to hand out + FreeBSD literature at a Microsoft product launch, for example, or held + an install-a-thon at a local computer show?</p> + + <p>The Linux folks do things like that all the time, apparently, whereas + only a very few die-hard FreeBSD users currently do it now, so why not + help these people out? Join the <a + href="mailto:advocacy@FreeBSD.org">advocacy@FreeBSD.org</a> mailing + list and discuss your plans there so that others with more enthusiasm + than ideas can also learn from and perhaps help you with yours. Write + short articles for the new advocacy sites like <a + href="http://www.daemonnews.org/">www.daemonnews.org</a> or <a + href="http://www.freebsdrocks.com/">www.freebsdrocks.com</a> and help + promote the success of BSD evangelical publications.</p> + + <p>Phrases like "this is your FreeBSD" and "it all depends on you" may + seem shop-worn and trite, but they're also unfortunately still true + when there's so few of us and so many of you. If FreeBSD is to + <em>really</em> continue to succeed in 1999, it will only be with + substantial user participation and that means you, users! Start a local + user group, donate some of your older CD releases to the local library, + try and convince a local small business or ISP to use FreeBSD, these are + just a few of the many things that can be done if you're truly + interested in putting some energy into FreeBSD and ideas for what to do + will be the least of your worries if you're truly motivated.</p> + + <p>Executive Summary: 1999, rah rah rah, let's do it! :)</p> + + &footer; + </body> +</html> diff --git a/en_US.ISO8859-1/htdocs/news/status/Makefile b/en_US.ISO8859-1/htdocs/news/status/Makefile new file mode 100644 index 0000000000..b3bed889b4 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/Makefile @@ -0,0 +1,66 @@ +# $FreeBSD: www/en/news/status/Makefile,v 1.57 2012/01/27 10:00:58 danger Exp $ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +DOCS= status.sgml + +XMLDOCS= report-2001-06 +XMLDOCS+= report-2001-07 +XMLDOCS+= report-2001-08 +XMLDOCS+= report-2001-09 +XMLDOCS+= report-2001-11 +XMLDOCS+= report-2001-12-2002-01 +XMLDOCS+= report-2002-02-2002-04 +XMLDOCS+= report-2002-05-2002-06 +XMLDOCS+= report-2002-07-2002-08 +XMLDOCS+= report-2002-09-2002-10 +XMLDOCS+= report-2002-11-2002-12 +XMLDOCS+= report-2003-01-2003-02 +XMLDOCS+= report-2003-03-2003-09 +XMLDOCS+= report-2003-10-2003-12 +XMLDOCS+= report-2004-01-2004-02 +XMLDOCS+= report-2004-03-2004-04 +XMLDOCS+= report-2004-05-2004-06 +XMLDOCS+= report-2004-07-2004-12 +XMLDOCS+= report-2005-01-2005-03 +XMLDOCS+= report-2005-03-2005-06 +XMLDOCS+= report-2005-07-2005-10 +XMLDOCS+= report-2005-10-2005-12 +XMLDOCS+= report-2006-01-2006-03 +XMLDOCS+= report-2006-04-2006-06 +XMLDOCS+= report-2006-06-2006-10 +XMLDOCS+= report-2006-10-2006-12 +XMLDOCS+= report-2007-01-2007-03 +XMLDOCS+= report-2007-04-2007-06 +XMLDOCS+= report-2007-07-2007-10 +XMLDOCS+= report-2007-10-2007-12 +XMLDOCS+= report-2008-01-2008-03 +XMLDOCS+= report-2008-04-2008-06 +XMLDOCS+= report-2008-07-2008-09 +XMLDOCS+= report-2008-10-2008-12 +XMLDOCS+= report-2009-01-2009-03 +XMLDOCS+= report-2009-04-2009-09 +XMLDOCS+= report-2009-10-2009-12 +XMLDOCS+= report-2010-01-2010-03 +XMLDOCS+= report-2010-04-2010-06 +XMLDOCS+= report-2010-07-2010-09 +XMLDOCS+= report-2010-10-2010-12 +XMLDOCS+= report-2011-01-2011-03 +XMLDOCS+= report-2011-04-2011-06 +XMLDOCS+= report-2011-07-2011-09 +XMLDOCS+= report-2011-10-2011-12 +XMLDOCS+= report-2012-01-2012-03 + +XSLT.DEFAULT= report.xsl + +# Install a sample <project> entry. +DATA= report-sample.xml + +INDEXLINK= status.html + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/news/status/README b/en_US.ISO8859-1/htdocs/news/status/README new file mode 100644 index 0000000000..cb58ad8108 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/README @@ -0,0 +1,156 @@ +Compiling status reports - best practices + +1) Call for reports + - Are usually sent to freebsd-hackers@ CC freebsd-current@ as the lists + with the most usual suspects for submitting reports. Forward to + developers@ as well. Also ping individuals which are known to have + something cooking. + - The xml-template is at: + http://www.freebsd.org/news/status/report-sample.xml and the generator + CGI at: http://www.freebsd.org/cgi/monthly.cgi at the time of this + writing. Make sure to keep them up to date with regard to categories + to pick from and place them prominently in the CFR - otherwise people + submit plain text reports and you have to format them yourself. + +2) In the past we usually had to extend the deadline by a week in order to + get everybody to report. Starting early with kind reminders seems to + help ;) + +3) The following groups have written very nice reports for the last rounds: + portmgr@, secteam@, re@ and deb@ for the FreeBSD Foundation. Various + conference organizers - depending on the season: BSDCan (info@bsdcan.org) + May, EuroBSDCon (info@eurobsdcon.org) Sept, AsiaBSDCon + (secretary@asiabsdcon.org) March. Our readers seem to value + these reports, so we should try to get them in if at all possible. + +4) Putting it all together: + - Copy and paste all reports in a single .xml file and use tidy(1) to get + it well formatted. Usually <url>'s without a description are missing + the closing "/>" which is the cause for most of the errors you will + encounter. Sometimes other closing tags are missing. + - Invoking tidy with the following options seems to cause the fewest + problems: tidy -xml -i -wrap 74 -latin1 -preserve + - Some special characters still break with that - noticed when sos@ + submits a report. + - Remove empty "<help></help>" sections, they cause a strange looking + newline. + - The <body> part usually needs a hand to make it proper html. Use <a + href=""> here, not <url>. + - Lists come out best if you close the <p> before and start a new one + after, like: + ... blabla:</p> + <ul> + <li>some item</li> + </ul> + <p>Some more blabla ... + +5) After the a couple iterations of the above, wrap the whole thing in a + report template: + +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status +Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/README,v 1.5 2007/10/08 16:54:13 brd Exp $ --> +<report> + <date> + <month>July-September</month> + + <year>2006</year> + </date> + + <section> + <title>Introduction</title> + + <p>SUMMARY GOES HERE</p> + + <p>Thanks to all the reporters for the excellent work! We hope you + enjoy reading.</p> + </section> + + <category> + <name>soc</name> + + <description>Google Summer of Code</description> + </category> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>team</name> + + <description>FreeBSD Team Reports</description> + </category> + + <category> + <name>net</name> + + <description>Network Infrastructure</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <category> + <name>bin</name> + + <description>Userland Programs</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> +</report> + + Categories are subject to change obviously. They come out in the order + as stated in the report. After another round of tidy(1) try to balance + the categories. Put things where they belong best, retire categories + that don't fill up, etc. Adding it to your local build and looking at + the html helps. Make sure you have an up-to-date www and doc tree. + +6) Sending it out: + - Just prior to committing, build the html locally. + - Extract a text version: lynx -dump -nolist report.html > report.txt + - Prettify. + - Send out To: hackers, CC: current, stable. New email to: announce@ this + one needs to be approved. Find somebody who can do that before you + start. + - Commit. Also update the next due date in status.sgml and link to the + new report. + - Add a news entry to www/share/sgml/news.xml. Template: + <event> + <title>June-October, 2006 Status Report</title> + + <p>The June-October, 2006 Status Report is <a + href="&base;/news/status/report-2006-06-2006-10.html">now + available</a> with 49 entries.</p> + </event> + +7) Repeat. diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2001-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2001-06.xml new file mode 100644 index 0000000000..5027dc556b --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2001-06.xml @@ -0,0 +1,830 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2001-06.xml,v 1.8 2006/08/19 21:20:40 hrs Exp $ --> + +<report> + <date> + <month>June</month> + + <year>2001</year> + </date> + + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD: www/en/news/status/report-2001-06.xml,v 1.8 2006/08/19 21:20:40 hrs Exp $ + </cvs:keyword> + </cvs:keywords> + + <section> + <title>Introduction</title> + + <p>One of the benefits of the FreeBSD development model is a focus + on centralized design and implementation, in which the operating + system is maintained in a central repository, and discussed on + centrally maintained lists. This allows for a high level of + coordination between authors of various components of the system, + and allows policies to be enforced over the entire system, covering + issues ranging from architecture to style. However, as the FreeBSD + developer community has grown, and the rate of both mailing list + traffic and tree modifications has increased, making it difficult + even for the most dedicated developer to remain on top of all the + work going on in the tree.</p> + + <p>The FreeBSD Monthly Development Status Report attempts to + address this problem by providing a vehicle that allows developers + to make the broader community aware of their on-going work on + FreeBSD, both in and out of the central source repository. This is + the first issue, and as such is an experiment. For each project and + sub-project, a one paragraph summary is included, indicating + progress since the last summary (in this case, simply recent + progress, as there have been no prior summaries).</p> + + <p>This status report may be reproduced in whole or in part, as + long as the source is clearly identified and appropriate credit + given.</p> + </section> + + <section> + <title>Future Editions</title> + + <p>Assuming there is some positive feedback on this idea, and that + future submissions get made such that there is content for future + issues, the goal is to release a development status report once a + month. As such, the next deadline will be July 31, 2001, with a + scheduled publication date in the first week of August. This will + put the status report on a schedule in line with the calendar, as + well as providing a little over a month until the next deadline, + which will include a number of pertinent events, including the + Annual USENIX Technical Conference in Boston, MA. Submissions + should be e-mailed to:</p> + + <blockquote> + <a href="mailto:robert+freebsd.monthly@cyrus.watson.org"> + robert+freebsd.monthly@cyrus.watson.org</a> + </blockquote> + + <p>Many submitters will want to wait until the last week of July so + as to provide the most up-to-date status report; however, + submissions will be accepted at any time prior to that date.</p> + + <p> + <i>-- Robert Watson < + <a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a> + + ></i> + </p> + </section> + + <project> + <title>Binary Updater Project</title> + + <contact> + <person> + <name> + <given>Eric</given> + + <common>Melville</common> + </name> + + <email>eric@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Murray</given> + + <common>Stokely</common> + </name> + + <email>murray@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~murray/updater.html" /> + </links> + + <body> + <p>The FreeBSD Binary Updater Project aims to provide a secure + mechanism for the distribution of binary updates for FreeBSD. + This project is complementary to the Open Packages and libh + efforts and there should be very little overlap with those + projects. The system uses a client / server mechanism that allows + clients to install any known "profile" or release of FreeBSD over + the network. Where a specific profile might contain a specific + set of FreeBSD software to install, additional packages, and + configuration actions that make it more ideal for a specific + environment (ie FreeBSD 4.3 Secure Web Server Profile)</p> + + <p>The system can currently be used to install a FreeBSD system + or perform the most simple of upgrades but many features are + absent. In particular, the client is in its infancy and much work + remains to be done. We need additional developers so please get + in touch with us at + <a href="mailto:updater@osd.bsdi.com">updater@osd.bsdi.com</a> + + if you are interested in spending some cycles on this.</p> + </body> + </project> + + <project> + <title>Problem Reports</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://phk.freebsd.dk/Gnats/" /> + </links> + + <body> + <p>Poul-Henning Kamp kicked off a drive to get our GNATS PR + database cleaned up so the wheat can be sorted from the chaff. + Progress is good, but there is still a lot of work to do. Give a + hand if you can. Remember: every unhandled PR is a pissed off + contributor or user.</p> + </body> + </project> + + <project> + <title>CVSROOT script rewrite/tidy</title> + + <contact> + <person> + <name> + <given>Josef</given> + + <common>Karthauser</common> + </name> + + <email>joe@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>I'm in the process of rewriting the CVSROOT/scripts to make + them more clean and configurable. A lot of other projects also + use these and so it makes sense to make them as easy to use in + other environments as possible.</p> + + <p>Status: work in progress. There is now a configuration file, + but not all the scripts use it yet.</p> + </body> + </project> + + <project> + <title>DEVFS</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work is progressing on implementing true cloning devices in + DEVFS. Brian Somers and Poul-Henning Kamp are working to make + if_tun the first truly cloning driver in the system. Next will be + the pty driver and the bpf driver.</p> + + <p>From July 1st DEVFS will be standard in -current.</p> + </body> + </project> + + <project> + <title>digi driver</title> + + <contact> + <person> + <name> + <given>Brian</given> + + <common>Somers</common> + </name> + + <email>brian@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Added the digi driver. Initial work was done by John Prince + <johnp@knight-trosoft.com>, but all the modular stuff was + done by me and initial work on supporting Xe and Xi cards (ala + dgb) was done by me. I'm now awaiting an Xe card being sent from + joerg@ (almost a donation) so that I can get that side of things + working properly.</p> + </body> + </project> + + <project> + <title>Diskcheckd</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://phantom.cris.net/freebsd/projects/viewproj.php?p_id=15" /> + </links> + + <body> + <p>Ben Smithurst has written a "diskcheckd" daemon which will + read all sectors on the disks over a configured period. With + recent increases in disksizes it is by no means a given that disk + read errors will be discovered before they are fatal. This daemon + will hopefully result in the drive firmware being able to + relocate bad sectors before they become unreadable. This code is + now committed to 5.0-CURRENT.</p> + </body> + </project> + + <project> + <title>if_fxp driver</title> + + <contact> + <person> + <name> + <given>Jonathan</given> + + <common>Lemon</common> + </name> + + <email>jlemon@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>In the last month (May-June), the new fxp driver was brought + into -stable. This new driver uses the common MII code, so + support for new PHYs is easy to add. Support for the new Intel + 82562 chips was added. The driver was updated to add VLAN support + and a workaround for a bug affecting Intel 815-based boards.</p> + </body> + </project> + + <project> + <title>Java Project</title> + + <contact> + <person> + <name> + <given>Greg</given> + + <common>Lewis</common> + </name> + + <email>glewis@eyesbeyond.com</email> + </person> + </contact> + + <body> + <p>The FreeBSD Java Project has continued its "behind the scenes" + work over the last month. Progress was made both technically, + with the help of Bill Huey (of Wind River), on a port of JDK + 1.3.1 and legally, with Nate Williams continuing negotiations + with Sun on a mutually acceptable license to release a binary + Java 2 SDK under. The JDK 1.2.2 port has also seen some + development, with a new patchset likely to be released soon which + includes JPDA and NetBSD support (the latter courtesy of Scott + Bartram).</p> + </body> + </project> + + <project> + <title>Kernel Graphics Interface port</title> + + <contact> + <person> + <name> + <given>Nicolas</given> + + <common>Souchu</common> + </name> + + <email>nsouch@fr.alcove.com</email> + </person> + </contact> + + <links> + <url href="http://kgi.sourceforge.net/" /> + </links> + + <body> + <p>The Kernel Graphics Interface project has worked for several + years to provide a framework for graphic drivers under Linux + receiving input from other groups like the UDI project. Currently + the KGI core implementation is quite settled, as is the driver + coding model as a whole. Work is being done to newbussify KGI and + produce a kld, as part of a future redesign of the graphics + subsystem in FreeBSD. KGI will be an alternative for graphic card + producers that don't accept the XFree86 model of userland graphic + adapters and will also provide accelerated support for any other + graphic alternative.</p> + </body> + </project> + + <project> + <title>libh Project</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Langer</common> + </name> + + <email>alex@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Nathan</given> + + <common>Ahlstrom</common> + </name> + + <email>nra@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~alex/libh/" /> + </links> + + <body> + <p>The libh project is a next generation sysinstall. It is + written in C++ using QT for its graphical frontend and tvision + for its console support. The menus are scriptable via an embedded + tcl interpreter. It has been growing functionality quite a bit + lately, including a new disklabel editor. Current work is on + installation scripts for CDROM, FTP, ... installs as well as a + fully functional standalone disk-partition and label editor. The + GUI API was extended a little and many bugs were fixed. There + seems to be some interest in i18n work.</p> + </body> + </project> + + <project> + <title>Mount(2) API</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Maxime Henrion is working on implementing a new and more + extensible mount(2) systemcall, mainly to overcome the 32 bits + for mountoptions limit, secondary goal to make it possible to + mount filesystems from inside the kernel.</p> + </body> + </project> + + <project> + <title>OLDCARD pccard implementation</title> + + <contact> + <person> + <name> + <given>Warner</given> + + <common>Losh</common> + </name> + + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>In the last two months, the OLDCARD pccard implementation was + rototilled to within an inch of its life. Many new pci cardbus + bridges were added. Power handling was improved. PCI Card cardbus + bridges are nearly supported and should be committed in early + June to the tree. This will likely be the last major work done on + OLDCARD. After pci cards are supported, work will shift to + improving NEWCARD.</p> + </body> + </project> + + <project> + <title>PowerPC Port</title> + + <contact> + <person> + <name> + <given>Benno</given> + + <common>Rice</common> + </name> + + <email>benno@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The PowerPC port is proceeding well. All seems to be working + in pmap.c after a number of problems encountered where FreeBSD + passes a vm_page_t to a NetBSD-derived function that expects a + vm_offset_t. Then after debugging the atomic operations code, I'm + now at the point where VM appears to be initialized and it's now + hanging while in sys/kern/kern_malloc.c:kmeminit(). Progress + continues. =)</p> + </body> + </project> + + <project> + <title>PPP</title> + + <contact> + <person> + <name> + <given>Brian</given> + + <common>Somers</common> + </name> + + <email>brian@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Developing full MPPE support for Andre Opperman @ Monzoon in + Switzerland. Work is now complete and will eventually be brought + into -current, but no dates are yet known.</p> + </body> + </project> + + <project> + <title>pseudofs</title> + + <contact> + <person> + <name> + <given>Dag-Erling</given> + + <common>Smorgrav</common> + </name> + + <email>des@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Pseudofs is a framework for pseudo-filesystems, like procfs + and linprocfs. The goal of pseudofs is twofold:</p> + + <ul> + <li>eliminate code duplication between (and within) procfs and + linprocfs</li> + + <li>isolate procfs and linprocfs from the complexities of the + vfs system to simplify maintenance and further + development.</li> + </ul> + + <p>Pseudofs has reached the point where it is sufficiently + functional and stable that linprocfs has been almost fully + reimplemented on top of it; the only bit that's missing is the + proc/<pid>/mem file.</p> + + <p>The primary to-do item for pseudofs right now is to add + support for writeable files (which are required for procfs, and + are quite a bit less trivial to handle than read-only files). In + addition, pseudofs needs either generic support for raw + (non-sbuf'ed, possibly mmap'able) files, or failing that, + special-case code to handle proc/<pid>/mem.</p> + </body> + </project> + + <project> + <title>RELNOTESng</title> + + <contact> + <person> + <name> + <given>Bruce</given> + + <common>A. Mah</common> + </name> + + <email>bmah@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~bmah/relnotes/" /> + </links> + + <body> + <p>RELNOTESng is the name I've given to the rewrite of the *.TXT + files that typically accompany a FreeBSD release. The information + from these files (which include, among other things, the release + notes and the supported hardware list) have been reorganized and + converted to SGML. This helps us produce the documentation in + various formats, as well as facilitating the maintenance of + documentation for multiple architectures. This work was recently + committed to -CURRENT, and I intend to MFC it to 4-STABLE before + 4.4-RELEASE.</p> + </body> + </project> + + <project> + <title>SMPng Project</title> + + <contact> + <person> + <name> + <given>John</given> + + <common>Baldwin</common> + </name> + + <email>jhb@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Jake</given> + + <common>Burkholder</common> + </name> + + <email>jake@FreeBSD.org</email> + </person> + + <person> + <name> + <given>SMP</given> + + <common>Mailing list</common> + </name> + + <email>smp@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~jasone/smp/" /> + </links> + + <body> + <p>The SMPng project aims to provide multithreaded support for + the FreeBSD kernel. Currently the kernel still runs almost + exclusively under the Giant kernel lock. Recently, progress has + been made in locking the process group and session structures as + well as file descriptors by Seigo Tanimura-san. Alfred Perlstein + has also added in a giant lock around the entire virtual memory + (VM) subsystem which will eventually be split up into several + smaller locks. The locking of the VM subsystem has proved tricky, + and some of the current effort is focused on finding and fixing a + few remaining bugs in on the alpha architecture.</p> + </body> + </project> + + <project> + <title>SMPng mbuf allocator</title> + + <contact> + <person> + <name> + <given>Bosko</given> + + <common>Milekic</common> + </name> + + <email>bmilekic@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~bmilekic/code/mb_slab/" /> + </links> + + <body> + <p>mb_alloc is a new specialized allocator for mbufs and mbuf + clusters. Presently, it offers various important advantages over + the old (status quo) mbuf allocator, particularly for MP + machines. Additionally, it is designed with the possibility of + future enhancements in mind.</p> + + <p>Presently in initial review & testing stages, most of the + code is already written.</p> + </body> + </project> + + <project> + <title>Sparc64 Port</title> + + <contact> + <person> + <name> + <given>Jake</given> + + <common>Burkholder</common> + </name> + + <email>jake@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work has (re)started on a port of FreeBSD to the UltraSPARC + architecture, specifically targeting PCI based workstations. Jake + Burkholder will be porting the kernel, and Ade Lovett has + expressed an interest in working on userland. Recent work on the + project includes:</p> + + <ul> + <li>built a gnu cross toolchain targeting sparc64</li> + + <li>obtained remote access to an ultra 5 development machine + (thanks to emmy)</li> + + <li>developed a minimal set of headers and source files to + allow the kernel to be compiled and linked</li> + + <li>implemented a mini-loader which relocates the kernel, maps + it into the tlbs and calls it</li> + + <li>nabbed Benno Rice's openfirmware console driver which + allows printf and panic to work</li> + </ul> + + <p>At this point the kernel can be net-booted and prints the + FreeBSD copyright before calling code that is not yet + implemented. I am currently working on a design for the pmap + module and plan to begin implementation in the next few days.</p> + </body> + </project> + + <project> + <title>TrustedBSD</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/" /> + </links> + + <body> + <p>The TrustedBSD Project seeks to improve the security of the + FreeBSD operating system by adding new security features, many + derived from common trusted operating system requirements. This + includes Access Control Lists (ACLs), Fine-grained Event Logging + (Audit), Fine-grained Privileges (Capabilities), Mandatory Access + Control (MAC), and other architecture features, including file + system extended attributes, and improved object labeling.</p> + + <p>Individual feature status reports are documented separately + below; in general, basic features (such as EAs, ACLs, and kernel + support for Capabilities) will be initially available in + 5.0-RELEASE, conditional on specific kernel options. A + performance-enhanced version of EAs is currently being targeted + at 6.0-RELEASE, along with an integrated capability-aware + userland, and MAC support.</p> + </body> + </project> + + <project> + <title>TrustedBSD: ACLs</title> + + <contact> + <person> + <name> + <given>Chris</given> + + <common>D. Faulhaber</common> + </name> + + <email>jedgar@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Patches are now available to add ACL support to cp(1) and + mv(1) along with preliminary support for install(1). Ilmar's i18n + patches for getfacl(1) and setfacl(1) need to be updated for the + last set of changes and committed. Some other functional + improvements are also in the pipeline.</p> + </body> + </project> + + <project> + <title>TrustedBSD Capabilities</title> + + <contact> + <person> + <name> + <given>Thomas</given> + + <common>Moestl</common> + </name> + + <email>tmm@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The kernel part of the capability implementation is mostly + finished; all uses of suser() and suser_xxx() and nearly all + comparisons of uid's with 0 have been converted to use the newly + introduced cap_check() call. Some details still need + clarification. More documentation for this needs to be done.</p> + + <p>POSIX.2c-compatible getfcap and setfcap programs have been + written. Experimental capability support in su(1), login(1), + install(1) and bsd.prog.mk is being tested.</p> + + <p>Support for capabilities, ACL's, capabilities and MAC labels + in tar(1) is being developed; only the capability part is tested + right now. Generic support for extended attributes is planned, + this will require extensions to the current EA interface, which + are written and will probably be committed to -CURRENT in a few + weeks. A port of these features to pax(1) is planned.</p> + </body> + </project> + + <project> + <title>TrustedBSD MAC and Object Labeling</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/" /> + </links> + + <body> + <p>An initial prototype of a Mandatory Access Control + implementation was completed earlier this year, supporting + Multi-Level Security, Biba Integrity protection, and a more + general jail-based access control model. Based on that + implementation, I'm now in the process of improving the FreeBSD + security abstractions to simplify both the implementation and + integration of MAC support, as well as increase the number of + kernel objects protected by both discretionary and mandatory + protection schemes. Generic object labeling introduces a + structure not dissimilar in properties to the kernel ucred + structure, only it is intended to be associated with kernel + objects, rather than kernel subjects, permitting the creation of + generic security protection routines for objects. This would + allow the easy extension of procfs and devfs to support ACLs and + MAC, for example. A prototype is underway, with compiling and + running code and simple protections now associated with + sysctl's.</p> + </body> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2001-07.xml b/en_US.ISO8859-1/htdocs/news/status/report-2001-07.xml new file mode 100644 index 0000000000..1d2202a6d4 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2001-07.xml @@ -0,0 +1,1206 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2001-07.xml,v 1.9 2007/04/11 04:11:09 brd Exp $ --> + +<report> + <date> + <month>July</month> + + <year>2001</year> + </date> + + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD: www/en/news/status/report-2001-07.xml,v 1.9 2007/04/11 04:11:09 brd Exp $ + </cvs:keyword> + </cvs:keywords> + + <section> + <title>Introduction</title> + + <p>Last month's status report was apparently a great success: I + received countless e-mails with comments, questions, and + suggestions. I've tried to incorporate any suggestions and address + any problems from these e-mails in this month's report, which + captures a far more extensive snapshot of FreeBSD activity in the + last month. Unlike last month's report, it does a better job of + reflecting non-development activity, such as on-going conference + planning, documentation, and so on. This is a trend I hope to see + improve in future months as well.</p> + + <p>On the topic of conferences, in the future I'd like to report + more on publication activities relating to FreeBSD, including + online journals with articles relating to FreeBSD, paper journals, + conference papers, and so on. Likewise, I would be interested in + including references to Call for Papers relating to FreeBSD. I'll + take this opportunity to plug both registration and paper + submission for BSDCon Europe in November, which has status included + in this report, and for the general BSD Conference being hosted by + USENIX in February. Your attendance and submissions make these + conferences "happen", and promote FreeBSD as a platform for new + research, feature development, and application products. Work of + extremely high calibre is performed on FreeBSD, and we need to get + the word out.</p> + </section> + + <section> + <title>Submission for Future Editions</title> + + <p>Next month, we're maintaining much the same submission + requirements: reports should be one or two paragraphs long, sent by + e-mail, and approximate the layout of the entries this month + (Project, Contact, URL, and text). I'll send out reminders again + over the week before the deadline, with more specific instructions. + An area where I'd like to explore improvement lies in the + coordination of related status reports for larger projects, such as + new architectural work or platform ports. This might even have the + effect of encouraging communication within these projects :-). I'd + like to continue to focus on pulling in a broader range of groups + and their activities, including the Security Officer, Release + Engineer, and Core Team.</p> + + <p> + <i>-- Robert Watson < + <a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a> + + ></i> + </p> + </section> + + <project> + <title>ACPI</title> + + <contact> + <person> + <name> + <given>Mike</given> + + <common>Smith</common> + </name> + + <email>msmith@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>ACPI (Advanced Configuration and Power Interface) is an + industry standard which obsoletes APM, Intel MPS, PnPBIOS, and + other Intel PC firmware interface standards. It is also used on + the IA64 platform. More information on ACPI is available at</p> + + <a href="http://developer.intel.com/technology/iapc/acpi"> + http://developer.intel.com/technology/iapc/acpi</a> + + <p>The FreeBSD ACPI subsystem project is based heavily on the + Intel ACPI Component Architecture. This status report outlines + the current state of the project; future updates will focus on + changes as they occur.</p> + + <p>The Intel ACPI interpreter is fully integrated, although bugs + are still coming out of the woodwork occasionally.</p> + + <ul> + <li>PCI bus detection and interrupt routing are functional, but + power management interaction will require work on the core PCI + subsystem.</li> + + <li>Non-PCI motherboard peripheral probing is implemented, but + believed to have problems on some systems.</li> + + <li>A power policy manager has been implemented. The initial + policy manager has two modes, "performance" and "economy".</li> + + <li>CPU speed throttling is integrated with the platform power + policy.</li> + + <li>System thermal monitoring is implemented, but fan control + is believed to have problems.</li> + + <li>Pushbutton suspend and power-off is implemented.</li> + + <li>System timekeeping using the ACPI timer is supported.</li> + + <li>Battery status monitoring is implemented.</li> + </ul> + + <p>Work is ongoing in the following areas:</p> + + <ul> + <li>System suspend and resume.</li> + + <li>Timekeeper accuracy/reliability.</li> + + <li>Power profiles.</li> + + <li>User-level management interfaces.</li> + + <li>PCI power management.</li> + + <li>Bug-hunting.</li> + </ul> + </body> + </project> + + <project> + <title>ARM Port</title> + + <contact> + <person> + <name> + <given>Stephane</given> + + <common>Potvin</common> + </name> + + <email>septovin@videotron.ca</email> + </person> + </contact> + + <body> + <p>The ARM port is currently going pretty well. The kernel is + compiling and is able to boot to the point where it panics trying + to initialize the network subsystem. The current reference + platform is the Netwinder but this may change as many people + expressed interest in a more broadly available platform. Things + that need to be done before it can get further includes adding + footbridge, timer and interrupt supports. The pmap module is not + completed yet either.</p> + </body> + </project> + + <project> + <title>BIND 9</title> + + <contact> + <person> + <name>Doug Barton</name> + + <email>dougb@FreeBSD.org</email> + </person> + + <person> + <name>Jeroen Ruigrok</name> + + <email>asmodai@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Now that BIND 8.2.4 is finally imported the time has come to + look at getting BIND 9 imported into CURRENT. The current idea is + to have it imported alongside BIND 8 so that people can play with + either one until all import problems have been taken care of and + people have tested it a bit.</p> + </body> + </project> + + <project> + <title>binup</title> + + <contact> + <person> + <name>Eric Melville</name> + + <email>eric@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Although gaining a new name, the project has been at a + standstill due to both resource availability during the move + between BSDi and Wind River, and other commitments of the + developers. The project should obtain an official mailing list, + as well as return to an active state after the dust settles.</p> + </body> + </project> + + <project> + <title>BSDCon Europe</title> + + <links> + <url href="http://www.bsdconeurope.org" /> + </links> + + <contact> + <person> + <name>Paul Richards</name> + + <email>paul@freebsd-services.co.uk</email> + </person> + + <person> + <name>Josef Karthauser</name> + + <email>joe@tao.org.uk</email> + </person> + </contact> + + <body> + <p>The conference will take place at the Thistle Hotel, Brighton, + UK from 9-11 November 2001.</p> + + <p>The aim of the conference is to provide a focal point for + European users and developers of all the BSD derived operating + systems. The format will be similar to other conferences, with 2 + days of technical sessions over the Saturday and Sunday.</p> + + <p>We'll be finalizing the schedule towards the end of the month + and anybody who is interested in doing a talk should contact us + ASAP. There are no restrictions on the use of talks; if it's been + done before we may still be interested in having it presented to + an European audience, and we make no claims to the talks so + speakers are free to present the talks again at other + conferences.</p> + + <p>We're also still looking for sponsors.</p> + + <p>We had 80 pre-registrations in the first week so we're + expecting a good turnout.</p> + </body> + </project> + + <project> + <title>CAM</title> + + <contact> + <person> + <name>Matthew Jacob</name> + + <email>mjacob@FreeBSD.org</email> + </person> + + <person> + <name>Justin Gibbs</name> + + <email>gibbs@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The new CAM transport code is starting to get supported in + more HBAs and to get refined so that it does the intended + per-protocol support. No progress on doing any SMPng work for CAM + has been made yet. This is a fairly high priority.</p> + </body> + </project> + + <project> + <title>Problem Reports</title> + + <links> + <url href="http://phk.freebsd.dk/Gnats/" /> + </links> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Thanks to various outstanding individual efforts, we are now + down to just below 2300 open bug-reports. This means that we have + fought our way back to the level we had around march 2000.</p> + </body> + </project> + + <project> + <title>Documentation Project</title> + + <links> + <url href="http://www.FreeBSD.org/docs.html" /> + + <url href="http://www.FreeBSD.org/docproj/index.html" /> + </links> + + <contact> + <person> + <name>Documentation Project</name> + + <email>doc@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work continues (in large part sponsored by WRS) on updating + the Handbook ready for the second print edition. There has been a + flurry of activity in this area recently, and the ToDo list can + be seen at</p> + + <p> + <a href="http://www.FreeBSD.org/docproj/handbook.html"> + http://www.FreeBSD.org/docproj/handbook.html</a> + </p> + + <p>Dima and others are doing a stellar job of keeping up with the + steady flow of incoming PRs relating to the documentation + project.</p> + + <p>The Developers' Handbook,</p> + + <p> + <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/developers-handbook/index.html"> + http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/developers-handbook/index.html</a> + </p> + + <p>is a year old; it contains a wealth of useful content for + developers developing on, or for, FreeBSD. As ever, more + contributions are always required, not only for the developers' + handbook, but for all of the FreeBSD documentation set.</p> + </body> + </project> + + <project> + <title>Fibre Channel Support</title> + + <contact> + <person> + <name>Matthew Jacob</name> + + <email>mjacob@feral.com</email> + </person> + </contact> + + <body> + <p>The basic design hasn't changed and this project mainly is in + the phase of continued hardening and test case development. The + next major feature will be to fully integrate into the new CAM + TRAN code and to fully support on the fly device addition and + removal. The only HBA supported is QLogic at this time. Future + support for the QLogic line is planned to have 2300 (2Gb) and IP + support before October.</p> + </body> + </project> + + <project> + <title>Hardware Watchpoints in the Kernel Debugger</title> + + <contact> + <person> + <name>Brian Dean</name> + + <email>bsd@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Hardware watchpoints are now available for kernel debugging on + the IA32 (i386) architecture. One can now set hardware + watchpoints using the new ddb command 'hwatch', which is + analogous to the existing 'watch' command. Alternatively, if + greater flexibility is required, direct access to the debug + registers is available using the ddb 'set' command which allows + complete control over the processor hardware debug facilities. + Hardware watchpoints are very useful in tracking down those + elusive memory overwrite bugs in the kernel. Hardware watchpoints + can even be used to set a code breakpoint in ROM, which is + commonly found in embedded systems.</p> + </body> + </project> + + <project> + <title>ifconfig support for IEEE 802.11 wireless devices</title> + + <contact> + <person> + <name>Brooks Davis</name> + + <email>brooks@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Support for configuring IEEE 802.11 wireless devices via + ifconfig has been committed to -current and -stable. It contains + most of the functionality needed to configure an wireless device. + Some missing features are being worked on including integrated + support for DHCP so a single entry in /etc/rc.conf can be used to + fully configure a wireless device on a DHCP lan and setting the + CTS/RTS threshold. Currently the an(4) and wi(4) drivers are + supported in -current and -stable with the awi(4) device + supported in -current. Further work is needed to support + Frequency Hopping devices such as ray(4).</p> + </body> + </project> + + <project> + <title>jailNG</title> + + <contact> + <person> + <name>Robert Watson</name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>jailNG is a from-scratch rewrite of the popular jail(8) + service, focusing on improved management functions, as well as + more fine-grained configurability. An initial prototype has been + written, based on explicitly named and configured jails, and work + is proceeding on userland integration. Currently, it's not clear + if the timeline for this will be 5.0-RELEASE, or 5.1-RELEASE.</p> + </body> + </project> + + <project> + <title>FreeBSD Java Project</title> + + <links> + <url href="http://www.FreeBSD.org/java/" /> + </links> + + <contact> + <person> + <name>Greg Lewis</name> + + <email>glewis@eyesbeyond.com</email> + </person> + </contact> + + <body> + <p>The main development in the FreeBSD Java Project over the last + month was the release of an initial "Developers Only" patchset + for the JDK 1.3.1. Since that release progress had been made + towards a much more usable alpha quality patchset which is + likely to be turned into a port, as per the current JDK 1.2.2 + patchset. This new patchset will feature a number of bugfixes, + which essentially get the JDK to a working state for early + adopters, and an initial implementation of "native threads" based + on FreeBSD's userland pthreads. Unfortunately this implementation + isn't fully functional, but is included in the hope of + getting more eyeballs on the code (particularly experienced + pthread programmers). We'd also like to welcome Fuyuhiko + Maruyama-san as a new committer, the usual punishment for too + many good patches.</p> + </body> + </project> + + <project> + <title>jpman project</title> + + <links> + <url href="http://www.jp.FreeBSD.org/man-jp/" /> + </links> + + <contact> + <person> + <name>Japanese Man Page Project</name> + + <email>man-jp@jp.FreeBSD.org</email> + </person> + </contact> + + <body> + <p>We have been working to provide Japanese version of FreeBSD + online manuals, since 1996. Currently, RELENG_4 manuals are + based. Translated versions are placed on doc/ja_JP.eucJP/man and + provided to users using ports/japanese/man-doc. Also, we discuss + about related commands (e.g. ports/japanese/man and + ports/japanese/groff).</p> + </body> + </project> + + <project> + <title>Kernel Summit - Usenix 2001</title> + + <links> + <url href="http://www.FreeBSD.org/~jhb/summit/usenix01/" /> + </links> + + <contact> + <person> + <name>John Baldwin</name> + + <email>jhb@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The first FreeBSD kernel summit meeting was held June 29-30, + 2001 in Boston, MA at the Usenix 2001 Annual Technical + Conference. Links to a variety of files are posted on the web + site.</p> + + <p>Note: I (jhb) am still working on writing up a general summary + of the meeting. When that is completed it will be posted here and + mailed to the -hackers mailing list.</p> + </body> + </project> + + <project> + <title>KSE threading the kernel</title> + + <links> + <url href="http://people.FreeBSD.org/~jasone/kse/" /> + </links> + + <contact> + <person> + <name>Julian Elischer</name> + + <email>julian@elischer.org</email> + </person> + </contact> + + <body> + <p>I'm working on multithreading the kernel. So far I have over + 400KB of diffs relative to today's -current (I'm keeping my tree + updated with changes as they occur rather than get hit with a big + update at the end).</p> + + <p>I have split the proc structure and am changing most of the + kernel to pass around a thread identifier instead of a proc + structure.</p> + + <p>The following interfaces have been changed so far:</p> + + <ul> + <li>device devsw entries</li> + + <li>vfs calls</li> + + <li>mutexes</li> + + <li>events</li> + + <li>system calls</li> + + <li>scheduler</li> + + <li>+ a lot of code in between.</li> + </ul> + + <p>I have still a lot of work to go with a lot of "dumb editing" + (s/struct proc \*p/struct thread \*td/) usually I change a few + items and then fix everything that breaks when I try compile it. + I'd like to check it in on a branch so others can help the + editing but haven't worked out the best way to do it yet.</p> + + <p>I have implemented changes to the scheduler so that KSE's are + scheduled instead of processes, and threads sleep, letting the + KSE pick up a new thread. but it's not anywhere ready yet (heck + it doesn't compile yet :-)</p> + + <p>Note that I have not yet updated the document listed above.. + everywhere it mentions "ksec" or "KSE-context", the code uses the + word "thread". I will update it soon as Jason has sent me the + source.</p> + </body> + </project> + + <project> + <title>FreeBSD Monthly Development Status Reports</title> + + <links> + <url href="http://www.FreeBSD.org/news/status/" /> + </links> + + <contact> + <person> + <name>Robert Watson</name> + + <email>rwatson@FreeBSD.org></email> + </person> + + <person> + <name>Chris Costello</name> + + <email>chris@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The FreeBSD Monthly Development Status Report aims to keep + users and developers up-to-date on the latest goings-on in the + FreeBSD project by providing summaries of each project and its + status. At the time of this writing, the July 2001 status report + is being prepared and is very near release. The FreeBSD Web site + now has a Status Reports section, which, when the July 2001 + report is released, will be updated to include a link to an + HTML-ified version.</p> + </body> + </project> + + <project> + <title>NetBSD rc.d port</title> + + <links> + <url href="http://groups.yahoo.com/group/FreeBSD-rc" /> + </links> + + <contact> + <person> + <name>Doug Barton</name> + + <email>dougb@FreeBSD.org</email> + </person> + + <person> + <name>Sheldon Hearn</name> + + <email>sheldonh@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The NetBSD rc.d port aims to improve the FreeBSD startup + process by porting Luke Mewburn's rc.d work from NetBSD to + FreeBSD. This will score FreeBSD startup and shutdown + dependencies without losing the traditional and much loved + monolithic configuration filesystem.</p> + + <p>Luke Mewburn's USENIX paper and slides on the system as + implemented in NetBSD are available here:</p> + + <p> + <a href="http://groups.yahoo.com/group/FreeBSD-rc/message/3"> + http://groups.yahoo.com/group/FreeBSD-rc/message/3</a> + </p> + + <p>Interested parties are urged to study this material before + joining the discussion list.</p> + + <p>The intention at this stage is to decide on an approach that + will ensure that the differences between the NetBSD rc.d system + and the system as ported to FreeBSD will be kept to a minimum. + This will probably involve discussions with Luke around those + areas of the system that are identified as areas for potential + improvement.</p> + </body> + </project> + + <project> + <title>Netgraph ATM</title> + + <contact> + <person> + <name>Hartmut Brandt</name> + + <email>brandt@fokus.gmd.de</email> + </person> + </contact> + + <body> + <p>The goal of this project is the implementation of ATM + signalling and other ATM protocols by means of the netgraph(4) + framework. This should provide an easily extensible architecture + for using ATM on FreeBSD. Currently the full UNI4.0 stack (except + for the LIJ capability) has been implemented, including ILMI and + a first version of the ATM Forum API for UNI. An implementation + of Classical IP over ATM is also available. Drivers have been + implemented for the Fore PCA200E and Fore HE-155 cards.</p> + </body> + </project> + + <project> + <title>network device cloning</title> + + <contact> + <person> + <name>Brooks Davis</name> + + <email>brooks@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Network device cloning support has been imported from NetBSD. + This allows virtual devices to be allocated on demand rather then + being statically allocated at compile time. Our implementation + differs slightly from that of NetBSD's in that we allow both the + creation of specific devices (i.e. gif0) and arbitrary devices + instead of just allowing specific devices. Currently, the only + device in the tree which has been converted is the gif(4) device + which has been converted in both -current and -stable. Work is + ongoing to convert all other virtual network devices with work in + progress on faith, stf, and vlan interfaces. In general this + conversion is accompanied by appropriate modifications to make + these devices fully modular.</p> + </body> + </project> + + <project> + <title>Next Generation POSIX threads (NGPT)</title> + + <links> + <url + href="http://oss.software.ibm.com/developerworks/opensource/pthreads/" /> + </links> + + <contact> + <person> + <name>Arun Sharma</name> + + <email>arun@sharma.dhs.org</email> + </person> + </contact> + + <body> + <h4>Porting NGPT (next generation pthreads) to FreeBSD</h4> + + <p>NGPT is an effort led by IBM engineers to implement MxN + threads (also known as many user threads to one kernel thread + mapping) on Linux. I have ported it to FreeBSD to use + rfork(2).</p> + + <p>The port is right here:</p> + + <p> + <a href="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=29239"> + http://www.FreeBSD.org/cgi/query-pr.cgi?pr=29239</a> + </p> + </body> + </project> + + <project> + <title>OLDCARD upgrade to support PCI cards</title> + + <links> + <url href="http://people.FreeBSD.org/~imp/oldcard-status.html" /> + </links> + + <contact> + <person> + <name>Warner Losh</name> + + <email>imp@village.org</email> + </person> + </contact> + + <body> + <p> + <i>Funded by: Monzoon Networking, LLC</i> + </p> + + <p>This month has been a month of conventration and + consolidation. Much of the changes from current have been + migrating into stable. I've improved power support, + suspend/resume interactions, interrupt handling, and ability to + work after windows/NEWCARD has run. Interrupt routing continues + to be a locking issue for a complete MFC. Current patches are + available at the above website. I'm racing to get this done + before 4.4 is released.</p> + </body> + </project> + + <project> + <title>Open Runtime Platform (ORP)</title> + + <links> + <url href="http://www.intel.com/research/mrl/orp/" /> + </links> + + <contact> + <person> + <name>Arun Sharma</name> + + <email>arun@sharmas.dhs.org</email> + </person> + + <person> + <name>eGroups: ORP</name> + + <email>orp@egroups.com</email> + </person> + </contact> + + <body> + <p>Information on Intel ORP - a BSD licensed Java VM is right + here:</p> + + <p> + <a href="http://www.intel.com/research/mrl/orp/"> + http://www.intel.com/research/mrl/orp/</a> + </p> + + <p>A FreeBSD patch has been tested to work with NGPT and + submitted to the ORP project. The patch is available here:</p> + + <p> + <a + href="http://www.sharma-home.net/~adsharma/projects/orp/orp-freebsd-1.0.5.patch.txt.gz"> + http://www.sharma-home.net/~adsharma/projects/orp/orp-freebsd-1.0.5.patch.txt.gz</a> + </p> + + <p>There are some issues to be ironed out to make it work with + FreeBSD's default (user level) pthread implementation.</p> + </body> + </project> + + <project> + <title>OpenPackages</title> + + <links> + <url href="http://openpackages.org/" /> + </links> + + <body> + <p>OpenPackages intends to create a software packaging system + that will allow third-party programs to be installed, without + operating system dependent changes, on as many platforms as are + feasible. OpenPackages was originally based on code from the BSD + ports systems, and has been improved and extended by developers + of many heritages.</p> + + <p>The OpenPackages Project is pleased to release the Milestone 2 + codebase. This release contains a working package building system + and a single test package. OP currently is known to build on + certain instances of the following operating systems: FreeBSD, + HP/UX, IRIX, Linux (Debian, Red Hat, Suse, Mandrake, TurboLinux, + Caldera, etc.), NetBSD, OpenBSD, Solaris</p> + </body> + </project> + + <project> + <title>PAM</title> + + <contact> + <person> + <name>Mark R V Murray</name> + + <email>mark@grondar.za</email> + </person> + </contact> + + <body> + <p>(First report)</p> + + <p>Large cleanup and extension of FreeBSD PAM modules. All + modules are to be documented, consistent in style (style(9) used) + and as complete as possible WRT functionality. Mostly done.</p> + </body> + </project> + + <project> + <title>PowerPC Port</title> + + <contact> + <person> + <name>Benno Rice</name> + + <email>benno@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>We now have the rudiments of device support. We have a nexus + driver for OpenFirmware machines, along with support for the + Apple UniNorth PCI/AGP host bridge. I'm currently trying to get + the USB hardware working so that I can get closer to having a + console driver independent of OpenFirmware, then I'll be trying + to get the system to get to single-user mode using NFS.</p> + </body> + </project> + + <project> + <title>PPP IPv6 Support</title> + + <contact> + <person> + <name>Brian Somers</name> + + <email>brian@freebsd-services.com</email> + </person> + </contact> + + <body> + <p>Work has begun, but nothing has yet been committed. The NCP + addresses used by ppp have been abstracted and initial support + has been added to the filter set for ipv6 addresses. NCP + negotiation hasn't yet been started.</p> + </body> + </project> + + <project> + <title>Porting ppp to hurd & linux</title> + + <contact> + <person> + <name>Brian Somers</name> + + <email>brian@Awfulhak.org</email> + </person> + </contact> + + <body> + <p>Patches have been submitted to get ppp working under HURD, and + mostly under Linux. There are GPL copyright problems that need to + be addressed.</p> + </body> + </project> + + <project> + <title>pppoed</title> + + <contact> + <person> + <name>Brian Somers</name> + + <email>brian@freebsd-services.com</email> + </person> + </contact> + + <body> + <p>Making pppoed function in a production environment. Most of + the work is complete and committed. Additional work includes + adding a -l option where ``-l label'' is shorthand for ``-e exec + ppp -direct label'' and discovering why rogue child processes are + being left around.</p> + </body> + </project> + + <project> + <title>PRFW - Hooks within the FreeBSD kernel</title> + + <contact> + <person> + <name>Evan Sarmiento</name> + + <email>ems@open-root.org</email> + </person> + </contact> + + <body> + <p>PRFW is a set of hooks which I have integrated into the + FreeBSD kernel. This allows modules to easily intercept system + calls with less overhead. It also supports per-pid restrictions, + which means, one process may not be able to use X function in Y + manner, but another process may.</p> + + <p>Progress: I was working on this in 4.3-RELEASE, but now I'm + merging it into current. I will be submitting a patch to the + mailing lists in about a week.</p> + </body> + </project> + + <project> + <title>SCSI Tape Support</title> + + <contact> + <person> + <name>Matthew Jacob</name> + + <email>mjacob@feral.com</email> + </person> + </contact> + + <body> + <p>This driver is currently not working well under -current and + is undergoing some work at this time. No major design or feature + changes are planned. There was some notion of adding TapeAlert + support, but HP supports that as a binary product via a user + library and it was felt that it'd be more politically prudent to + leave it alone.</p> + </body> + </project> + + <project> + <title>SMPng</title> + + <contact> + <person> + <name>Peter Wemm</name> + + <email>peter@FreeBSD.org</email> + </person> + + <person> + <name>John Baldwin</name> + + <email>jhb@FreeBSD.org</email> + </person> + </contact> + + <body> + <h4>Development</h4> + + <p>In the 'smpng' p4 branch there is code to make the ast() + function loop to close the race when an AST is triggered while we + are handling previously triggered AST's.</p> + + <p>In the 'jhb_preemption' p4 branch work is being done to make + the kernel fully preemptive. It is reportedly stable on UP x86, + but SMP x86 locks up, UP alpha has problems during shutdown and + can recurse indefinitely until it exhausts its stack.</p> + + <h4>Management</h4> + + <p>We are using a perforce repository for live development work, + which can track multiple separate long-lived works-in-progress + and collaborate between multiple developers at the same time on + the same change set.</p> + + <p>FreeBSD-current is being imported into p4 hourly, for easy + tracking of the moving -current tree.</p> + + <p>I haven't written up a good primer yet, but we're able to open + this up to the general developer community. NEWCARD work looks + like it will be done here too. Perforce is ideal for tracking + this sort of long-lived project without having to resort to + passing patches around.</p> + + <p>KSE work is now being checked into a kse p4 branch - thanks + Julian!</p> + + <p>KSE work is focusing on getting the main API changes into the + base tree well before 5.0.</p> + </body> + </project> + + <project> + <title>SMPng mbuf allocator</title> + + <links> + <url href="http://people.FreeBSD.org/~bmilekic/code/mb_slab/" /> + </links> + + <contact> + <person> + <name>Bosko Milekic</name> + + <email>bmilekic@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>mb_alloc is a specialized allocator for mbufs and mbuf + clusters. It offers various important advantages over the old + mbuf allocator, particularly for MP machines. Additionally, it + is designed with the possibility of important future + enhancements in mind.</p> + + <p>The mb_alloc code has been committed to -CURRENT a month ago + and appears to be holding up well. Prior to committing it, + preliminary performance measurements were done merely to ensure + that it is not significantly worse than the old allocator, even + with Giant still in place. Results were promising + <a + href="http://people.FreeBSD.org/~bmilekic/code/mb_alloc/results.html"> + [http://people.FreeBSD.org/~bmilekic/code/mb_alloc/results.html]</a> + + - also see jlemon's results (link at the bottom of accompanying + text). Since the commit, Matt Jacob has provided useful feedback + and bugfixes. Work is now being done to re-enable mbtypes + statistics and make appropriate changes to netstat(1) and + systat(1).</p> + </body> + </project> + + <project> + <title>sparc64 port</title> + + <contact> + <person> + <name>Jake Burkholder</name> + + <email>jake@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The sparc64 port has been committed to the FreeBSD repository. + As such further development will occur in cvs, rather than as a + separately maintained patch set. Significant progress has been + made since the last status report, including; support for kernel + debugging with ddb, much more complete pmap support, support for + context switching and process creation, and filling out of + important machine dependent data structures. Thomas Moestl has + shown a strong interest in working on the port and is in the + process of implementing support for saving and restoring a + process's floating point context. I look forward to working with + him and any other developers that happen to fall out of the wood + works.</p> + </body> + </project> + + <project> + <title>FreeBSD/sparc64 kernel loader</title> + + <contact> + <person> + <name>Robert Drehmel</name> + + <email>robert@ferrari.de</email> + </person> + </contact> + + <body> + <p>The sparc64 loader is functional enough to boot an ELF binary + from an UFS filesystem using the existent openfirmware library, + which has been revised to work flawlessly on 32-bit and 64-bit + architectures. Support for netbooting and modules will be + implemented next, followed by a better openfirmware mapping + strategy.</p> + </body> + </project> + + <project> + <title>SYN cache implementation for FreeBSD</title> + + <contact> + <person> + <name>Jonathan Lemon</name> + + <email>jlemon@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>This project brings a SYN cache implementation to FreeBSD, in + order to make it more robust to DoS attacks. A SYN cookie + approach was considered, but ultimately rejected because it does + not conform to the TCP protocol. The SYN cache will work with + T/TCP, IPV6 and IPSEC, and the size of each cache element is + currently is less than 1/5th the size of a normal TCP control + block.</p> + </body> + </project> + + <project> + <title>TrustedBSD Project</title> + + <links> + <url href="http://www.TrustedBSD.org/" /> + </links> + + <contact> + <person> + <name>Robert Watson</name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>It's been a busy month, with a number of relevant news items. + Not least important is that NAI Labs was awarded a $1.2M contract + from the US Defense Advanced Research Projects Agency (DARPA) to + work on a variety of components relevant to the TrustedBSD + Project, including support for pluggable security models, and + supporting features such as improving the extended attributes + implementation, simple crypto support for swap and filesystems, + documentation, and much more.</p> + + <p>On the features side, progress continues on Mandatory Access + Control, object labeling, and improving the consistency of kernel + access control mechanisms--in particular, with regard to + inter-process authorization and credential management. Work has + begun on porting LOMAC, NAI Labs' Low-Watermark Mandatory Access + Control scheme, from Linux to FreeBSD, and it has been + re-licensed under a BSD license. We hope to have an initial port + complete in time for 5.0-RELEASE later this year.</p> + </body> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2001-08.xml b/en_US.ISO8859-1/htdocs/news/status/report-2001-08.xml new file mode 100644 index 0000000000..c568aa5dbb --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2001-08.xml @@ -0,0 +1,1523 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2001-08.xml,v 1.7 2006/08/19 21:20:39 hrs Exp $ --> + +<report> + <date> + <month>August</month> + + <year>2001</year> + </date> + + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD: www/en/news/status/report-2001-08.xml,v 1.7 2006/08/19 21:20:39 hrs Exp $ + </cvs:keyword> + </cvs:keywords> + + <section> + <title>Introduction</title> + + <p>The FreeBSD Project made substantial progress in the month of + August, 2001, both on continuing the development of the RELENG_4 + line (4.x-STABLE and 4.x-RELEASE), and on 5.0-CURRENT, the main + development branch. During this month, the decision was made to + push the release of 5.0-CURRENT back so that KSE (support for + fine-grained user threads) could be completed in time for the + release, rather than postponing that support for 6.0. As such, the + lifespan of the RELENG_4 line will be extended, with new features + continuing to be backported to that branch. 4.4-RELEASE went into + final beta during this month, and will also be available + shortly.</p> + + <p>This month's edition of the status report has been written with + the assistance of Nik Clayton and Chris Costello.</p> + </section> + + <section> + <title>Future submissions</title> + + <p>For next month, the submission procedures remain the same: + reports should be between one and two paragraphs long, sent by + e-mail, and in a format approximately that of this month's + submissions (Project, Contact, URL, and text). Reminders will be + mailed to the hackers@FreeBSD.org and developers@FreeBSD.org + mailing lists at least a week before the deadline; complete + submission instructions may be found in those reminders.</p> + + <p>-- Robert Watson</p> + </section> + + <project> + <title>Fibre Channel Support</title> + + <contact> + <person> + <name> + <given>Matthew</given> + + <common>Jacob</common> + </name> + + <email>mjacob@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.feral.com/isp.html" /> + </links> + + <body> + <p>2 Gigabit support was integrated on 8/31/2001 (QLogic + 2300/2312 cards). Because of the author's shrinking time + commitment for FreeBSD, the previously planned "next step" which + would have been more complete new CAM Transport integration is + now probably just the addition of an FC-IP adjunct (as this can + benefit many platforms simultaneously).</p> + </body> + </project> + + <project> + <title>SCSI Tape Support</title> + + <contact> + <person> + <name> + <given>Matthew</given> + + <common>Jacob</common> + </name> + + <email>mjacob@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>A major update to error handling was done on 8/28/2001 which + should correct most of the EOM detection problems that have been + around for a while. There are several things to fix. The + principle thing to fix next is the establishment of a loader(8) + mediated device quirks method.</p> + </body> + </project> + + <project> + <title>CAM</title> + + <contact> + <person> + <name> + <given>Matthew</given> + + <common>Jacob</common> + </name> + + <email>mjacob@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Justin</given> + + <common>Gibbs</common> + </name> + + <email>gibbs@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Kenneth</given> + + <common>Merry</common> + </name> + + <email>ken@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>No change since last status. Some discussion amongst all of us + occurred, but lack of time and commitment to FreeBSD has meant + little has actually been committed to the tree. SMPng work will + be left to those who seem to have a notion about what needs to be + done.</p> + </body> + </project> + + <project> + <title>Intel Gigabit Ethernet</title> + + <contact> + <person> + <name> + <given>Matthew</given> + + <common>Jacob</common> + </name> + + <email>mjacob@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>No new status to report. This driver will be worked on again + soon and cleaned up to work better.</p> + </body> + </project> + + <project> + <title>KSE</title> + + <contact> + <person> + <name> + <given>Julian</given> + + <common>Elischer</common> + </name> + + <email>julian@elischer.org</email> + </person> + + <person> + <name> + <given>Peter</given> + + <common>Wemm</common> + </name> + + <email>peter@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Matt</given> + + <common>Dillon</common> + </name> + + <email>dillon@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work in adding supporting infrastructure to the kernel for KSE + threading support has reached "milestone 2".</p> + + <p>Milestone 2 is where the kernel source consistently refers to + its resources in terms of per-thread and per-process resources, + in the way that it will need to when there are > 1 threads per + process, but the LOGICAL changes to such things as the scheduler, + and fork and exit, have not yet been made to allow more than one + thread to be created. (nor have new threading syscalls been added + yet). This is an important milestone as it represents the last + point where the kernel has only "mechanical" changes. To go + further we must start adding new algorithms and functions.</p> + + <p>The kernel for milestone 2 is reliable and has no noticeable + performance degradations when compared to a matching -current + kernel. (the differences are less than the margin of error, so + that sometimes the new kernel actually fractionally beats the + unaltered kernel).</p> + + <p>We hope that by the time this is published, the KSE patches + will have been committed. The Major effect for most developers + will be only that the device driver interface requires a 'thread' + pointer instead of a Proc pointer in the open, close and ioctl + entrypoints.</p> + + <p>I'm sure there will be small teething problems but we are not + expecting great problems at the commit.</p> + </body> + </project> + + <project> + <title>FreeBSD core-secretary</title> + + <contact> + <person> + <name> + <given>Alan</given> + + <common>Clegg</common> + </name> + + <email>abc@FreeBSD.org</email> + </person> + + <person> + <email>core-secretary@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The position of Core Secretary was filled by Alan Clegg + <abc@FreeBSD.org> The first core-secretary report should be + available the second week in September and will cover the issues + discussed by core during August 2001.</p> + </body> + </project> + + <project> + <title>FreeBSD PAM</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Murray</common> + </name> + + <email>markm@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Development is continuing; pam_unix has gained the ability to + change passwords, login(1) has had PAM made compulsory (and is + going to have more PAM-capable features handed over to PAM).</p> + </body> + </project> + + <project> + <title>Netgraph ATM</title> + + <contact> + <person> + <name> + <given>Hartmut</given> + + <common>Brandt</common> + </name> + + <email>brandt@fokus.gmd.de</email> + </person> + </contact> + + <body> + <p>The ATM stack has been tested with a number of FreeBSD + machines and a Marconi ATM switch and seems to be quite stable + running CLIP. Multi port support for the native ATM API has been + implemented but needs some testing.</p> + </body> + </project> + + <project> + <title>PRFW - hooks for the FreeBSD kernel</title> + + <contact> + <person> + <name> + <given>Evan</given> + + <common>Sarmiento</common> + </name> + + <email>ems@open-root.org</email> + </person> + </contact> + + <links> + <url href="http://www.freesoftware.fsf.org/jailuser" /> + </links> + + <body> + <p>PRFW is a set of hooks for the FreeBSD kernel. It allows users + to insert code into system calls, for such purposes as creating + extended security features. Last week, PRFW reached 0.1.0, with + many bugfixes and cleaning. I urge anyone who is interested to + please visit the site, join the mailing list. Also take a peek at + lsm.immunix.org, the Linux hooks. It will be a good contrast.</p> + </body> + </project> + + <project> + <title>CVSROOT script rewrite/tidy</title> + + <contact> + <person> + <name> + <given>Josef</given> + + <common>Karthauser</common> + </name> + + <email>joe@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work is still progressing to make all of the perl scripts run + using perl's 'strict' mode, and to migrate all FreeBSD specific + options into the configuration file (CVSROOT/cfg.pm). I'll be + looking for help soon to write a guide on how to make use of + these scripts for use in your own repository. Anyone interested + in helping should contact me at the above email address.</p> + </body> + </project> + + <project> + <title>PPP IPv6 Support</title> + + <contact> + <person> + <name> + <given>Brian</given> + + <common>Somers</common> + </name> + + <email>brian@freebsd-services.com</email> + </person> + </contact> + + <body> + <p>The software has been committed to -current and seems + functional. Outstanding issues include dealing with IPV6CP events + (linkup & linkdown scripts) and allocating site-local and + global addresses (currently, ``iface add'' is the only way to + actually use the link).</p> + </body> + </project> + + <project> + <title>Porting ppp to hurd & linux</title> + + <contact> + <person> + <name> + <given>Brian</given> + + <common>Somers</common> + </name> + + <email>brian@freebsd-services.com</email> + </person> + </contact> + + <body> + <p>Status is unchanged since last month. Patches have been + submitted to get ppp working under HURD, and mostly under Linux. + There are GPL copyright problems that need to be addressed. Many + conflicts are expected after the commit of IPv6 support in + ppp.</p> + </body> + </project> + + <project> + <title>pppoed</title> + + <contact> + <person> + <name> + <given>Brian</given> + + <common>Somers</common> + </name> + + <email>brian@freebsd-services.com</email> + </person> + </contact> + + <body> + <p>Making pppoed function in a production environment. All known + problems have been fixed and committed.</p> + </body> + </project> + + <project> + <title>pppoa</title> + + <contact> + <person> + <name> + <given>Brian</given> + + <common>Somers</common> + </name> + + <email>brian@freebsd-services.com</email> + </person> + </contact> + + <body> + <p>I looked at bringing PPPoA into the base system, but could not + because of an overly restrictive distribution license on the + Alcatel Speedtouch modem firmware. It has been committed as a + port instead and is running live at a FreeBSD Services client + site.</p> + </body> + </project> + + <project> + <title>OLDCARD improvements</title> + + <contact> + <person> + <name> + <given>Warner</given> + + <common>Losh</common> + </name> + + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The OLDCARD improvements have been completed, except for a few + edge cases for older laptops with CL-PD6729/30 chips and some pci + bios issues. Some minor work will continue, but after 4.4R is + released, only a few remaining bugs will be fixed before the + author moves on to greener fields of NEWCARD development.</p> + </body> + </project> + + <project> + <title>jpman project</title> + + <contact> + <person> + <name> + <given>Kazuo</given> + + <common>Horikawa</common> + </name> + + <email>horikawa@psinet.com</email> + </person> + + <person> + <email>man-jp@jp.FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.jp.FreeBSD.org/man-jp/" /> + </links> + + <body> + <p>Targeting 4.4-RELEASE, one team has been translating newly + MFC'ed section [125678] manpages. The other team has been + updating section 3 since May and one third (1/3) is finished. The + port ja-groff is updated to be groff-1.17.2 based, and now it has + the same functionality as base system does. The port ja-man is + updated to have the search capability under an architecture + subdirectory, as base system does. The doc/ja_JP.eucJP/man + hierarchy update (adding architecture subdirectories) is planned + after 4.4-RELEASE.</p> + </body> + </project> + + <project> + <title>ARM port</title> + + <contact> + <person> + <name> + <given>Stephane</given> + + <common>Potvin</common> + </name> + + <email>sepotvin@videotron.ca</email> + </person> + </contact> + + <links> + <url href="http://pages.infinit.net/sepotvin/" /> + </links> + + <body> + <p>Basic footbridge support is now functional and the kernel is + now able to probe the pci bus. Access primitives for the bus are + still missing so I can't attach any drivers yet.</p> + </body> + </project> + + <project> + <title>SYN cache implementation for FreeBSD</title> + + <contact> + <person> + <name> + <given>Jonathan</given> + + <common>Lemon</common> + </name> + + <email>jlemon@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The syncache implementation is completed, and currently under + testing and review. The code should be committed to -current in + the near future, and a patchset for -stable made available.</p> + </body> + </project> + + <project> + <title>Compressed TCP state</title> + + <contact> + <person> + <name> + <given>Jonathan</given> + + <common>Lemon</common> + </name> + + <email>jlemon@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>State information for TCP connections is primarily kept in the + TCP/IP control blocks in the kernel. Not all of the TCP states + make use of the entire structure, and significant memory savings + can be had by using a cut-down version of the state in some + cases. The first phase of this project will address connections + that are in the TIME_WAIT state by moving them into a smaller + structure.</p> + + <p>This project has completed the initial research and rough + design phases, with actual code development starting + immediately.</p> + </body> + </project> + + <project> + <title>Network SMP locking</title> + + <contact> + <person> + <name> + <given>Jonathan</given> + + <common>Lemon</common> + </name> + + <email>jlemon@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>For 5.0, the goal is for the network stack to run without the + Giant lock. Initial development in this area may focus on + partitioning the code and data structures into distinct areas of + responsibilities. A first pass of locking may involve using a + several smaller mini-giant code locks in order to reduce the + problem to a manageable size.</p> + + <p>Progress for this month includes the creation of a perforce + repository to officially track the locking changes, and the + initial submission of locks for the &ifnet list. Some code + cleanup has also been done to the main tree in order to better + support future locking additions.</p> + </body> + </project> + + <project> + <title>Network device nodes</title> + + <contact> + <person> + <name> + <given>Jonathan</given> + + <common>Lemon</common> + </name> + + <email>jlemon@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Currently, all network devices (fxp0, lo0, etc) exist in their + own namespace, and are accessed through a socket interface. This + project creates device nodes in /dev for network devices, and + allows control and access in that fashion.</p> + + <p>This is experimental work, and suggestions for APIs and + functionality are strongly encouraged and welcomed. In is not + clear whether it will be possible (or desirable) to provide the + exact same set of operations that can be done through the socket + interface.</p> + + <p>Benefits of approach include the fact that a kqueue filter can + be attached to a network device for monitoring purposes. Initial + code exists to send a kq event whenever the network link status + changes. Other benefits may include better access control by + using filesystem ACLs to control access to the device.</p> + </body> + </project> + + <project> + <title>RELNOTESng</title> + + <contact> + <person> + <name> + <given>Bruce</given> + + <common>Mah</common> + </name> + + <email>bmah@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~bmah/relnotes/" /> + </links> + + <body> + <p>RELNOTESng, the DocBook-ified set of release documentation + files, has been merged to the RELENG_4 branch. 4.4-RELEASE will + be the first release of FreeBSD with the new-style release notes, + hardware list, etc. Some of these documents are being translated + by the Japanese and Russian translation teams.</p> + + <p>Snapshots of RELNOTESng for CURRENT and 4-STABLE in HTML, + text, and PDF are available at the above URL and are updated + irregularly but frequently. Dima Dorfman <dd@FreeBSD.org> + and Nik Clayton <nik@FreeBSD.org> have been working to have + automatically-generated snapshots on the main FreeBSD web + site.</p> + + <p>On my TODO list: 1) Resynchronize the FreeBSD installation + document with the installation chapter in the Handbook. 2) Update + the hardware lists (with particular emphasis on PCCARD and USB + devices). 3) Update the infrastructure to allow the + architecture-dependent parts of RELNOTESng to scale to more + hardware platforms.</p> + </body> + </project> + + <project> + <title>FreeBSD/sparc64 port</title> + + <contact> + <person> + <name> + <given>Jake</given> + + <common>Burkholder</common> + </name> + + <email>jake@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Thomas</given> + + <common>Moestl</common> + </name> + + <email>tmm@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Robert</given> + + <common>Drehmel</common> + </name> + + <email>robert@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Sparc64 development is still continuing rapidly and we're + making some excellent progress. Of note, some problems with the + way the pmap module implements copy-on-write mappings have been + fixed and fork() now works as expected, support for signals has + been added, and the port has been updated for KSE in the perforce + repository. Thomas Moestl has begun work on pci bus support, and + a basic nexus bus for sparc64 has been written. The driver for + the Sun `Psycho' and `Sabre' UPA-to-PCI bridges and associated + code has been ported from NetBSD (the Sabre is the on-chip + version found in the UltraSparc IIi and IIe). PCI configuration, + I/O and memory space accesses do already work, as well as + interrupt assignment and delivery for devices attached directly + to the bridge, and the first PCI device drivers can attach and + seem to work mostly. Interrupt routing and busdma support still + need much work.</p> + </body> + </project> + + <project> + <title>Documentation Project</title> + + <contact> + <person> + <name> + <given>Nik</given> + + <common>Clayton</common> + </name> + + <email>nik@FreeBSD.org</email> + </person> + + <person> + <name> + <common>Documentation Project</common> + </name> + + <email>doc@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/docs.html" /> + + <url href="http://www.FreeBSD.org/docproj/index.html" /> + </links> + + <body> + <p>The Handbook has been the main focus of activity this month. + Due to go to the printers on the 15th a vast amount of new + content has been submitted and committed. This includes a + complete rewrite of the "Installing FreeBSD", which massively + expands the amount of information available to people new to + FreeBSD. It even includes screenshots.</p> + + <p> + <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html"> + http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html</a> + </p> + + <p>Comments, and contributions are, of course, welcome.</p> + </body> + </project> + + <project> + <title>IP Multicast Routing support</title> + + <contact> + <person> + <name> + <given>Bill</given> + + <common>Fenner</common> + </name> + + <email>fenner@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>FreeBSD's IP Multicast Routing support was recently updated in + several ways. One big change is that it's now able to be loaded + as a KLD instead of statically compiled into the kernel; this is + especially useful for experimentation or updating of an existing + system. It also now coexists nicely with the kernel IP + encapsulation infrastructure, so that multicast tunnels can + better coexist with MobileIP, certain IPSec tunnels and generic + IPv4-in-IPv4 tunnels.</p> + </body> + </project> + + <project> + <title>Mbuf SMPng allocator</title> + + <contact> + <person> + <name> + <given>Bosko</given> + + <common>Milekic</common> + </name> + + <email>bmilekic@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~bmilekic/code/mb_slab/" /> + </links> + + <body> + <p>The allocator appears to be stable. Mbtypes statistics have + been re-activated thanks, in part, to Jiangyi Liu + <jyliu@163.net> although the diff has not yet been + committed (I'm just in the process of cleaning it up a little and + final testing). More work to come: cleanups, follow TODO from the + original commit, and perhaps an eventual generalization of the + allocator for various network-related allocations (in a more + distant future).</p> + </body> + </project> + + <project> + <title>RAIDframe for FreeBSD</title> + + <contact> + <person> + <name> + <given>Scott</given> + + <common>Long</common> + </name> + + <email>scottl@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~scottl/rf" /> + </links> + + <body> + <p>After two months of little progress, RAIDframe work is gearing + up again. The port to -stable has some known bugs but is fairly + stable. The port to -current was recently completed and patches + will be released soon. RAIDframe is a multi-platform RAID + subsystem designed at CMU. This is a port of the NetBSD version + by Greg Oster.</p> + </body> + </project> + + <project> + <title>aac driver</title> + + <contact> + <person> + <name> + <given>Scott</given> + + <common>Long</common> + </name> + + <email>scottl@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~scottl/aac" /> + </links> + + <body> + <p>The aac driver has been given a lot of attention lately and is + now nearly feature complete. Changes include crashdump support, + correct handling of controller initiated commands, and more + complete management interface support. The Linux RAID management + tool available from Dell and HP now fully works; a FreeBSD native + version of the tool is also in the works. These changes have been + checked into -current, and will appear in -stable once 4.4 has + been released.</p> + </body> + </project> + + <project> + <title>Problem Reports</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://phk.freebsd.dk/Gnats/" /> + </links> + + <body> + <p>We are making some progress, we are now down to 2170 open PR's + down from an all time high of 3270 just 3 months ago. The aim is + still to get rid of all the dead-wood in the PR database so only + relevant PRs in the database. A big thanks from me to the people + who have made this happen!</p> + </body> + </project> + + <project> + <title>network device cloning</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Support for cloning vlan devices via ifconfig has been + committed to -current and will be MFC'd after further testing. + Additionally, Maksim Yevmenkin submitted code to allow cloning of + tap and vmnet devices on devfs systems. Code for faith and stf + should be committed shortly.</p> + </body> + </project> + + <project> + <title>ia64 Port</title> + + <contact> + <person> + <name> + <given>Doug</given> + + <common>Rabson</common> + </name> + + <email>dfr@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Current status is that the ia64 kernel builds and runs in a + simulator environment up to single user mode and has been tested + lightly in that environment. My current focus is on completing + the ia64 loader so that I can start to get kernels working on the + real hardware. The loader is coming along well and I expect to be + able to load kernels (but not necessary execute them) soon.</p> + </body> + </project> + + <project> + <title>libh Project</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Langer</common> + </name> + + <email>alex@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Nathan</given> + + <common>Ahistrom</common> + </name> + + <email>nra@FreeBSd.org</email> + </person> + </contact> + + <body> + <p>I have access to the libh CVS repo again and am testing a new, + OBJDIR capable build structure at the moment. Done that, I'm + going to continue testing the package library and implement the + missing functionality. Currently, import of libh into the base + system is under discussion (arch mailinglist). Now that + 5.0-RELEASE has been shifted, I want 5.0 ship with a libh + installer and package system. We can really need people who are + good in C++, are able to understand what the current + implementation does and also feel that working on libh is fun and + thus are willing to help.</p> + </body> + </project> + + <project> + <title>GNOME Desktop for FreeBSD</title> + + <contact> + <person> + <name> + <given>Maxim</given> + + <common>Sobolev</common> + </name> + + <email>sobomax@FreeBSD.org</email> + </person> + + <person> + <name> + <common>FreeBSD GNOME Team</common> + </name> + + <email>gnome@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Getting GNOME Fifth-Toe metaport ready for 4.4-RELEASE was the + main focus of activity this month. In the process many components + were updated, many bugs were tracked down and solved, which + allowed to make this 97-component meta-package building and + working properly.</p> + + <p>Next month the project will be focused on organizing work of + the FreeBSD GNOME Team as well as on attempts to increase amount + of people participating in the team (anybody who is willing to + participate is welcome to drop a note to gnome@FreeBSD with a + short explanation of how he/she could help).</p> + </body> + </project> + + <project> + <title>fbsd-nvdriver</title> + + <contact> + <person> + <name> + <given>Erik</given> + + <common>Greenwald</common> + </name> + + <email>erik@floatingmind.com</email> + </person> + + <person> + <name> + <given>Joel</given> + + <common>Willson</common> + </name> + + <email>siigorny@linuxsveeden.borkborkbork</email> + </person> + </contact> + + <links> + <url href="http://fbsd-nvdriver.sourceforge.net" /> + </links> + + <body> + <p>NVIDIA Corporation releases Linux drivers by using a + combination of binary object files and source (under a + constrictive license). The FreeBSD NVIDIA driver project aimed to + completely replace the source component of the driver using code + targeting FreeBSD 4.3 and released under the BSD license. The + binary module provided is supposedly the same module used on + Windows, BeOS, and OS/2, so it should be portable between + different i80x86 based OS's.</p> + + <p>The project is currently on indefinite hold. Our contact at + NVIDIA seemed enthusiastic about the project, and was fairly + quick about returning email, but when we discovered issues that + prevented porting without changes to the binary component or + error codes we needed deciphered, Nick (the contact) said he'd + look into it and never got back. The first major problem was the + ioctl interface, the NVIDIA driver passes a pointer and depends + on the kernel side to copyout the right amount, where FreeBSD + expect the parameters to be correct and the copyout is performed + by the subsystem. This was worked around using Dave Rufinos + "ioctl tunnel" idea. After that, we found that X refused to load + and traced it down to an ioctl defined in the binary component + erroring. We cannot tell what that ioctl is, were told that we + could not sign an NDA for source to that component, and have been + waiting a month for Nick to "look into it". Therefore progress is + impossible (without breaking the license) and we believe that the + flaws make the driver unportable to any *nix other than + Linux.</p> + </body> + </project> + + <project> + <title>FreeBSD Release Engineering</title> + + <contact> + <person> + <name> + <common>FreeBSD Release Engineer Team</common> + </name> + + <email>re@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The FreeBSD release engineering process for FreeBSD 4.4 + started to ramp up around August 1st when the "code slush" took + affect. During this time all commits to the RELENG_4 branch were + reviewed by re@FreeBSD.org (over 250 code snippets had to be + reviewed). After the first release candidate on August 15th, all + submissions were scrutinized under a more strict potential risk + vs benefit curve. The best way to help get involved with the + release engineering process is to simply follow the low volume + freebsd-qa mailing list, help out with the neverending supply of + PRs related to our installation tools (sysinstall), or to work on + a possible next-generation replacement for our installation + technology, such as the libh or OpenPackages projects.</p> + + <p>Many companies donated equipment, network access, or paychecks + to finance these activities. Including Compaq, Yahoo!, Wind River + Systems, and many more.</p> + </body> + </project> + + <project> + <title>Improved TCP Initial Sequence Numbers</title> + + <contact> + <person> + <name> + <given>Mike</given> + + <common>Silbersack</common> + </name> + + <email>silby@silby.com</email> + </person> + </contact> + + <body> + <p>In mid March, 2001, Tim Newsham of Guardent identified an + attack possible against the initial sequence number generation + scheme of FreeBSD (and other OSes.) In order to guard against + this threat, a randomized sequence number generation scheme was + ported over from OpenBSD and included in 4.3-release. + Unfortunately, non-monotonic generation was found to cause major + problems with applications which initiate continuous, rapid + connections to a single host.</p> + + <p>In order to restore proper operation under such circumstances + while still providing strong resistance against sequence number + prediction, FreeBSD 4.4 uses the algorithm specified in RFC 1948. + This algorithm hashes together host and port information with a + piece of secret data to generate a unique sequence number space + for each connection. As a result, outgoing initial sequence + numbers are again monotonic, but also unguessable by an + attacker.</p> + </body> + </project> + + <project> + <title>LOMAC</title> + + <contact> + <person> + <name> + <given>Brian</given> + + <common>Feldman</common> + </name> + + <email>green@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The port of LOMAC to FreeBSD is progressing well, and already + has a very high level of stability (no known outstanding bugs!). + Aspects which have already been implemented include a stacking + filesystem overlay with fully-functional access controls (for + files and directories) based on path names, access controls for + sending signals, and file-backed-memory revocation for + processes.</p> + </body> + </project> + + <project> + <title>SMPng</title> + + <contact> + <person> + <name> + <given>John</given> + + <common>Baldwin</common> + </name> + + <email>jhb@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Peter</given> + + <common>Wemm</common> + </name> + + <email>wemm@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~jasone/smp/" /> + </links> + + <body> + <p>Updates to things from last month: + <ul> + <li>The ast() fixes were committed last month.</li> + + <li>The work on the preemptive kernel is stalled for the time + being. It is still unstable on Alpha and SMP systems.</li> + </ul> + </p> + + <p>New stuff since last month: + <ul> + <li>sx locks now support upgrades and downgrades.</li> + + <li>Witness now supports lock upgrades and downgrades.</li> + + <li>Jason Evans has committed a semaphore implementation.</li> + + <li>Matt Dillon has pushed Giant down into all of the + syscalls.</li> + + <li>John Baldwin has been working on proc locking in a p4 + 'jhb_proc' branch.</li> + + <li>John is also currently working on making the ktrace code + use a work thread to asynchronously write trace data out to the + trace file. This will make ktrace safe almost completely MP + safe with the exception that a few ktrace events need Giant in + order to call malloc(9) and that ktrgenio() is still + synchronous. Specifically, however, ktrpsig(), ktrsysret(), and + ktrcsw() no longer need Giant.</li> + + <li>Jonathan Lemon has started work on locking the network + stack in a p4 'netlock' branch.</li> + </ul> + </p> + </body> + </project> + + <project> + <title>FreeBSD Java Project</title> + + <contact> + <person> + <name> + <given>Greg</given> + + <common>Lewis</common> + </name> + + <email>glewis@eyesbeyond.com</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/java/" /> + </links> + + <body> + <p>Most of the work this month has focused on development of the + native JDK 1.3.1 patchset. The 3rd patchset is out and has been + accompanied with the creation of a FreeBSD "port". This has + allowed early adopters much easier access to the code and + naturally resulted in a number of bugs being found. Development + work has mostly focused on fixing these problems and the project + is now set to release fourth patchset over the weekend, which + should see the JDK in a reasonably usable state. One of the big + challenges left is producing a working HotSpot JVM, which looks + like it will require some heavy hacking.</p> + + <p>We also welcome OpenBSD's Heikki Korpela to the porting team + :)</p> + </body> + </project> + + <project> + <title>floppy driver overhaul</title> + + <contact> + <person> + <name> + <given>Joerg</given> + + <common>Wunsch</common> + </name> + + <email>j@uriah.heep.sax.de</email> + </person> + </contact> + + <body> + <p>As part of some ongoing development activity, the floppy + driver (fdc(4)) enjoyed some overhaul in the past which is part + of an ongoing process. Automatic density selection will come + next, something i meant to implement for years now. As part of + that, the entire density selection stuff has been rewritten. 2.88 + MB floppies are on the wishlist as well, but I need a working + 2.88 drive before attempting to implement that.</p> + </body> + </project> + + <project> + <title>sppp(4) merge</title> + + <contact> + <person> + <name> + <given>Joerg</given> + + <common>Wunsch</common> + </name> + + <email>j@uriah.heep.sax.de</email> + </person> + </contact> + + <body> + <p>sppp(4) should be merged with the ISDN4BSD offspring variant. + This will merge some features and bugfixes from the i4b branch + (like VJ compression), and eventually end up in a single sppp(4) + in the tree. While being at that, incorporating many changes and + bugfixes from NetBSD is considered as well.</p> + </body> + </project> + + <project> + <title>KAME</title> + + <contact> + <person> + <name> + <given>Munechika</given> + + <common>Sumikawa</common> + </name> + + <email>sumikawa@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.kame.net/" /> + </links> + + <body> + <p>The KAME project (http://www.kame.net/) has merged its IPv6 + and IPsec implementation as of July 2001 to FreeBSD CURRENT and + STABLE, in cooperation with some contributors of the project. The + latest code includes a number of bug fixes, has been fully tested + in FreeBSD STABLE, and will appear in FreeBSD 4.4 RELEASE. Thus, + the new RELEASE version will be quite stable in terms of IPv6 and + IPsec.</p> + + <p>The project has assigned a talented guy to be responsible for + merge from KAME to FreeBSD, so future merge efforts will be + smoother.</p> + </body> + </project> + + <project> + <title>TrustedBSD</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/" /> + </links> + + <body> + <p>The TrustedBSD project continues to move ahead, with progress + made in the ACL, Capability, and MAC implementations. In + addition, support from DARPA is permitting new work to improve + the extended attribute code, improve security abstractions, and + work on security documentation. Due to the push-back of the + FreeBSD 5.0 release, it should now be possible to include a + complete MAC implementation in that release. Specific status + reports appear for components where substantial progress is being + made.</p> + </body> + </project> + + <project> + <title>TrustedBSD Capabilities</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Thomas</given> + + <common>Moestl</common> + </name> + + <email>tmm@FreeBSD.org</email> + </person> + + <person> + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <body> + <p>Capabilities support is currently being committed to the base + FreeBSD tree--userland libraries are now fully committed, and + kernel infrastructure is being integrated.</p> + </body> + </project> + + <project> + <title>BSDCon Europe</title> + + <contact> + <person> + <name> + <given>Paul</given> + + <common>Richards</common> + </name> + + <email>paul@freebsd-services.com</email> + </person> + </contact> + + <body> + <p>Planning for BSDCon Europe is going well. We're still + accepting proposals for talks but the schedule is starting to + fill up so we may not be for much longer.</p> + + <p>An update of the site that includes accommodation information, + a preliminary schedule, a list of speakers and an online payment + page will be launched on Wednesday 19 September.</p> + + <p>The fee will be £150 for individuals and £250 for + corporations. The individual pricing is valid only until the end + of September, the price will rise to £200 for October and + late registrations in November will be £250.</p> + + <p>The updated website will include a list of sponsorship + options, we're still looking for more sponsorship.</p> + </body> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2001-09.xml b/en_US.ISO8859-1/htdocs/news/status/report-2001-09.xml new file mode 100644 index 0000000000..b362052309 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2001-09.xml @@ -0,0 +1,948 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2001-09.xml,v 1.4 2006/08/19 21:20:40 hrs Exp $ --> + +<report> + <date> + <month>September</month> + + <year>2001</year> + </date> + + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" + version="1.0"> + <cvs:keyword name="freebsd">$FreeBSD: www/en/news/status/report-2001-09.xml,v 1.4 2006/08/19 21:20:40 hrs Exp $</cvs:keyword> + </cvs:keywords> + + <section> + <title>Introduction</title> + + <p>In the month of September, the FreeBSD Project continued its + investment in long-term projects, including continuing work on a + fine-grained SMP implementation, support for Kernel Schedulable + Entities (KSE) supporting highly efficient threading, and + broadening support for modern hardware platforms, including Intel's + new IA64 architecture, UltraSparc, and PowerPC. Additional focus + was placed on the release process, including work on the release + notes infrastructure, support for DVD releases, and work on a + binary updating tool.</p> + + <p>Due to the delay in getting the September report out the door, + the November status report will also cover October. During the + month of November, we look forward to BSDCon Europe, the first such + event outside the continental United States. The USENIX conference + paper submission deadlines are also in November, and FreeBSD users + and developers are encouraged to submit to the general and FREENIX + tracks. Please see www.usenix.org for more information.</p> + </section> + + <project> + <title>PRFW</title> + + <contact> + <person> + <name> + <given>Evan</given> + + <common>Sarmiento</common> + </name> + + <email>evms@csa.bu.edu</email> + </person> + </contact> + + <links> + <url href="http://www.freesoftware.fsf.org/jailuser/" /> + </links> + + <body> + <p>PRFW provides hooks in the FreeBSD kernel, allowing users to + insert their own checks in system calls and various kernel + functions. PRFW is nearing 0.5, which will incorporate numerous + structural changes such as, much faster per-process hooks, kernel + function hooks, plus, a new way of adding hooks which would + enable users to reference hooks by a string.</p> + </body> + </project> + + <project> + <title>FreeBSD libh Project</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Langer</common> + </name> + + <email>alex@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Nathan</given> + + <common>Ahlstrom</common> + </name> + + <email>nra@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/libh.html" /> + </links> + + <body> + <p>The build process is now creating four different versions of + the libs, which include support for TVision, Qt, both or none. I + created some first packages from existing ports and installed + those libh packages on my system only using libh's tools, + including registering all the files in the package database, + recording their checksums etc. Patches to the disk editor have + been submitted, which include functionality to write the changes + in the fdisk part and initial support for a disk label editor. + We'll soon have a new committer.</p> + </body> + </project> + + <project> + <title>RELNOTESng</title> + + <contact> + <person> + <name> + <given>Bruce A.</given> + + <common>Mah</common> + </name> + + <email>bmah@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~bmah/relnotes/" /> + </links> + + <body> + <p>FreeBSD 4.4-RELEASE was the first release of FreeBSD with its + new-style release documentation. Both English and Japanese + versions of these documents were created. Regularly-built + snapshots of -CURRENT and 4-STABLE release documentation are now + available on the Web site, but they require a little HTML + infrastructure to make them viewer-friendly. I intend to continue + updating my snapshot site at the URL above, at least for a little + while.</p> + + <p>Call for help: The hardware compatibility lists need to be + updated in the areas of the Alpha architecture, USB devices, and + PCCARD devices. I'm looking for volunteers to help; interested + parties should contact me at the email address above. DocBook + experience is not required; familiarity with the hardware above + would be very helpful.</p> + </body> + </project> + + <project> + <title>Fibre Channel Support</title> + + <contact> + <person> + <name> + <given>Matthew</given> + + <common>Jacob</common> + </name> + + <email>mjacob@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.feral.com/isp.html" /> + </links> + + <body> + <p>Bug fixing and move to -STABLE of 2Gb support.</p> + </body> + </project> + + <project> + <title>Intel Gigabit Ethernet</title> + + <contact> + <person> + <name> + <given>Matthew</given> + + <common>Jacob</common> + </name> + + <email>mjacob@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Quite a lot of cleanup of this driver. Bug fixes and some + performance enhancements. However, this driver is likely to be + removed shortly and replaced by one from Intel itself.</p> + </body> + </project> + + <project> + <title>TIRPC</title> + + <contact> + <person> + <name> + <given>Martin</given> + + <common>Blapp</common> + </name> + + <email>mb@imp.ch</email> + </person> + </contact> + + <links> + <url href="http://www.attic.ch/tirpc.html" /> + </links> + + <body> + <p>As you know, in march 2001 the version 2.3 of TIRPC has been + committed together with many userland changes. Alfred Perlstein + and Ian Dowse have helped me a lot with the porting effort and if + I had problems with understanding the code.</p> + + <p>Most bugs are now fixed, some remaining areas to fix are + secure RPC (keyserv) and unix domain support. I've patches for + these area available. Ian Dowse fixed a lot of outstanding bugs + in the rpcbind binary itself. Thank you Ian !</p> + + <p>The plan is now to migrate slowly towards TIRPC 2.8, which is + threadsafe for the server- and clientside. One first patch I've + made available on my URL. TIRPC 2.8 is licensed under the "Sun + Standards License Version 1.0" and we have to add some license + lines and the license itself to all modified files.</p> + + <p>A example is timed_clnt_create.diff which can be found on the + homepage.</p> + </body> + </project> + + <project> + <title>binup</title> + + <contact> + <person> + <name> + <given>Eric</given> + + <common>Melville</common> + </name> + + <email>eric@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Murray</given> + + <common>Stokely</common> + </name> + + <email>murray@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/updater.html" /> + </links> + + <body> + <p>The project has gained a mailing list, + freebsd-binup@FreeBSD.org - and the source tree has been moved + into the projects/ directory in the FreeBSD CVS repository. + Current work is focusing on extending the FreeBSD package + framework, and the client library should be rewritten and + completed by the end of the year.</p> + + <p>TODO: make the projects/ hierarchy into a cvsup distribution + and add it to cvs-all. Then update distrib.self.</p> + </body> + </project> + + <project> + <title>Porting ppp to hurd & linux</title> + + <contact> + <person> + <name> + <given>Brian</given> + + <common>Somers</common> + </name> + + <email>brian@freebsd-services.com</email> + </person> + </contact> + + <body> + <p>Status is unchanged since last month. Patches have been + submitted to get ppp working under HURD, and mostly under Linux. + There are GPL copyright problems that need to be addressed. Many + conflicts are expected after the commit of IPv6 support in + ppp.</p> + </body> + </project> + + <project> + <title>PPP IPv6 Support</title> + + <contact> + <person> + <name> + <given>Brian</given> + + <common>Somers</common> + </name> + + <email>brian@freebsd-services.com</email> + </person> + </contact> + + <body> + <p>The software has been committed to -current and seems + functional. Outstanding issues include dealing with IPV6CP events + (linkup & linkdown scripts) and allocating site-local and + global addresses (currently, ``iface add'' is the only way to + actually use the link). A bug exists in -stable (running the + not-yet-MFC'd ppp code) whereby routing entries are disappearing + after a time (around 12 or 24 hours). No further details are yet + available.</p> + </body> + </project> + + <project> + <title>FreeBSD DVD generation</title> + + <contact> + <person> + <name> + <given>Brian</given> + + <common>Somers</common> + </name> + + <email>brian@freebsd-services.com</email> + </person> + </contact> + + <body> + <p>A two disc set has been mastered and sent for pressing. There + are a few surprises with this release - details will be given in + the official announcement (at BSDConEurope).</p> + </body> + </project> + + <project> + <title>Netgraph ATM</title> + + <contact> + <person> + <name> + <given>Harti</given> + + <common>Brandt</common> + </name> + + <email>brandt@fokus.gmd.de</email> + </person> + </contact> + + <body> + <p>ATM-Forum LAN-emulation version 2.0 without support for QoS + has been implemented and tested. The ILMI daemon has been + modularized into a general mini-SNMP daemon, an ILMI module and a + not yet finished IPOA (IP over ATM) module.</p> + </body> + </project> + + <project> + <title>jpman project</title> + + <contact> + <person> + <email>man-jp@jp.FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.jp.FreeBSD.org/man-jp/" /> + </links> + + <body> + <p>We have finished updating section [125678] manpages to + 4.4-RELEASE based, 1 week after 4.4-RELEASE is announced. To + finish this update, OKAZAKI Tetsurou has imported Ex/Rv macro + support on ja-groff-1.17.2_1. SUZUKI Koichi did most Ex/Rv + changes on Japanese manpages. He also find some issues of these + macro usage on some original manpages and filed a PR. For + post-4.4-RELEASE, now we target 4.5-RELEASE. Section 3 update is + also in progress.</p> + </body> + </project> + + <project> + <title>New Mount(2) API</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Maxime</given> + + <common>Henrion</common> + </name> + + <email>mux@qualys.com</email> + </person> + </contact> + + <body> + <p>We've made some good progress now, and the new nmount(2) + syscall is nearly finished. There is still some work to do to + have a working kernel_mount() and to convert all filesystems to + use this new API for their VFS_MOUNT() functions.</p> + </body> + </project> + + <project> + <title>FreeBSD/sparc64 port</title> + + <contact> + <person> + <name> + <given>Jake</given> + + <common>Burkholder</common> + </name> + + <email>jake@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Thomas</given> + + <common>Moestl</common> + </name> + + <email>tmm@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>I am pleased to announce that as of 1 AM Friday October 19th, + the sparc64 port boots to single user mode. A few binaries from + the base system have been built and verified to work properly. + Much of this work is still in review for commit, but will be + integrated into the cvs tree as soon as possible. EBus support + has been ported from NetBSD, and ISA support has been written. + The PCI host bridge code has stabilized, and busdma seems to work + correctly now. The sio driver has had EBus support added, and the + ATA driver has been modified so that it works on big-endian + systems and uses the busdma API. With these changes, a root file + system can now be successfully mounted from ATA disks on sparc64, + even in DMA mode. The gem driver, which supports Sun GEM and ERI + and Apple GMAC and GMAC2 ethernet adaptor, has been ported from + NetBSD but has not yet had sufficient testing.</p> + </body> + </project> + + <project> + <title>SYN cache implementation for FreeBSD</title> + + <contact> + <person> + <name> + <given>Jonathan</given> + + <common>Lemon</common> + </name> + + <email>jlemon@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>No new status to report, the code is still waiting to be + committed. It is likely that this code will be expanded to + include syn cookies as a further fallback mechanism.</p> + </body> + </project> + + <project> + <title>Compressed TCP state</title> + + <contact> + <person> + <name> + <given>Jonathan</given> + + <common>Lemon</common> + </name> + + <email>jlemon@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Development on this project has been slowed, pending the + commit of the syncache code, as this builds on part of that + work.</p> + </body> + </project> + + <project> + <title>Network SMP locking</title> + + <contact> + <person> + <name> + <given>Jonathan</given> + + <common>Lemon</common> + </name> + + <email>jlemon@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Not much progress has been made this month, with other + projects occupying most of my time. However, reviewing all the + code and data structures had a side benefit; a hash table for + inet addresses has been added. This will significantly speed up + interface address lookups in the case where there are a larger + number of interface aliases.</p> + </body> + </project> + + <project> + <title>Multiple console support</title> + + <contact> + <person> + <name> + <given>Jonathan</given> + + <common>Lemon</common> + </name> + + <email>jlemon@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Currently, a single device may act as a console at any time, + which requires the user to choose the console device at boot + time. With the upcoming network console support, it is desirable + to allow multiple console devices which behave identically, and + to alter consoles while the kernel is running.</p> + + <p>The code is completed, and needs some final polishing to clean + up the rough edges. Console output can be sent to both syscons + and sio, (as well as the network) and when in ddb, input can be + taken from any input source. A small control program allows + adding and removing consoles on the fly.</p> + </body> + </project> + + <project> + <title>Network console</title> + + <contact> + <person> + <name> + <given>Jonathan</given> + + <common>Lemon</common> + </name> + + <email>jlemon@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>This project's goal is to add low level network functionality + to FreeBSD. The initial target is to make a network console + available for remote debugging with ddb or gdb. A secondary + target is to utilize the code to perform network crash dumps. The + design assumes that the network card and driver are working, but + does not rely on other parts of the kernel.</p> + + <p>Initial development has been fairly rapid, and a minimal + TCP/IP stack has been written. It is currently possible to telnet + to a machine which is at the ddb> prompt and interact with the + debugger.</p> + </body> + </project> + + <project> + <title>Network device nodes</title> + + <contact> + <person> + <name> + <given>Jonathan</given> + + <common>Lemon</common> + </name> + + <email>jlemon@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Network devices now support aliases in the form of /dev/netN, + where N is the interface index. Devices may be wired down to a + specific index number by entries in /boot/device.hints of + either:</p> + + <p>hint.net.<ifindex>.dev="devname" + hint.net.<ifindex>.ether="ethernet address"</p> + + <p>Additionally, ifconfig has been updated so that it will accept + the alias name when configuring a device.</p> + </body> + </project> + + <project> + <title>Intel Gigabit driver</title> + + <contact> + <person> + <name> + <given>Jonathan</given> + + <common>Lemon</common> + </name> + + <email>jlemon@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The gx driver has finally been committed to the tree. The + driver provides support for the Intel PRO/1000 cards, both fiber + and copper variants. The driver supports VLAN tagging and TCP/IP + checksum offload.</p> + </body> + </project> + + <project> + <title>KSE</title> + + <contact> + <person> + <email>julian@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~jasone/kse/" /> + + <url href="http://www.FreeBSD.org/~julian" /> + </links> + + <body> + <p>In the last month, not a lot has happened other than settling + in of the big August commit. Largely due to me having a sudden + increased workload at work, and a need for increased time to be + spent elsewhere. However some design work has proceeded. The API + has firmed up somewhat and several people have been reading + through what has been done already in order to be able to help in + the next phase.</p> + + <p>Milestone 3 will be to have the ability to generate and remove + multiple threads/KSEs per process. Milestone 3 will NOT require + that doing so will be safe. (especially in SMP systems), i.e. + locking issues will not be fully addressed, so while some testing + will be possible, it will not be possible to actually run in this + mode with any load.</p> + + <p>This will require allocators and destructors for the new + structures. Creation of the syscalls. Generation of an accurate + written API for the userland crew. Writing of the upcall launch + code. Production of a userland test program (not a full thread + scheduler). Resolution of some of the more glaring + incompatibilities (e.g. the scheduler) in a backwards compatible + manner. (i.e. if there are no multi threaded processes on a + system it should behave the same as now (and be as + reliable)).</p> + + <p>Criteria for knowing when we have reached Milestone 3 is the + ability for a simple process on an unloaded system to perform a + series of blocking syscalls reliably. e.g. open 2 sockets, and + send data on one, after having done a read on another, and then + 'respond' in like manner..</p> + </body> + </project> + + <project> + <title>PowerPC Port</title> + + <contact> + <person> + <name> + <given>Benno</given> + + <common>Rice</common> + </name> + + <email>benno@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>There have been a few major successes in the PowerPC port this + month. Mark Peek has succeeded in getting the FreeBSD/PowerPC + kernel cross compiled on FreeBSD and booting under the PSIM + simulator (now in /usr/ports/emulators/psim-freebsd). I have + succeeded in getting the FreeBSD loader to load and execute + kernels using the OpenFirmware found on Apple Macintosh hardware. + Mark is now working on completing some of the startup and pmap + code, while I am taking advantage of the simulator to work on + some interrupt and device issues.</p> + </body> + </project> + + <project> + <title>FreeBSD Java Project</title> + + <contact> + <person> + <name> + <given>Greg</given> + + <common>Lewis</common> + </name> + + <email>glewis@eyesbeyond.com</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/java/">Official FreeBSD Java + Project site.</url> + </links> + + <body> + <p>The project has moved forward on JDK 1.3.1 development this + month, with the release of two more patchsets. The team is + reasonably confident that the latest patchset is a stable release + of the core JDK 1.3.1 tools and classes, when the default "green" + threads subsystem is used. This is mostly thanks to hard work by + Fuyuhiko Maruyama to stabilize and fix the code. Bill Huey has + also been progressing with his work on the "native" threads + subsystem, although this hasn't yet reached the stability of + "green" threads. Another (arguably the) major highlight of the + latest patchset was the integration of NetBSD support by Scott + Bartram and Alistair Crooks (the latter of NetBSD packages fame). + Hopefully OpenBSD support will follow, making it truly a united + BSD Java Project.</p> + </body> + </project> + + <project> + <title>Improving FreeBSD startup scripts</title> + + <contact> + <person> + <name> + <given>Doug</given> + + <common>Barton</common> + </name> + + <email>DougB@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gordon</given> + + <common>Tetlow</common> + </name> + + <email>gordont@gnf.org</email> + </person> + </contact> + + <links> + <url href="http://groups.yahoo.com/group/FreeBSD-rc/">Improving + FreeBSD startup scripts</url> + + <url href="http://www.cs.rmit.edu.au/~lukem/bibliography.html"> + Luke Mewburn's papers</url> + + <url href="http://www.netbsd.org/Documentation/rc/">NetBSD + Initialization and Services Control</url> + </links> + + <body> + <p>This group is for discussion about the startup scripts in + FreeBSD, primarily the scripts in /etc/rc*. Primary focus will be + on improvements and importation of NetBSD's excellent work on + this topic.</p> + + <p>Alright folks, I finally got off my butt last night and put + together a roadmap for the migration to the new rc.d init scripts + that were imported from NetBSD a long time ago and just sat in + the tree.</p> + + <p>M1 (Patch included) + <br /> + + Setup infrastructure + <br /> + + Make rcorder compile + <br /> + + Hook rc.subr into the distribution (and mergemaster) + <br /> + + Hook rcorder into the world + <br /> + + Add toggle in rc.conf to switch between rc_ng and current boot + scripts</p> + + <p>M2 + <br /> + + Get FreeBSD to boot with the new boot scripts + <br /> + + Rewrite the /etc/rc.d scripts to work with FreeBSD</p> + + <p>M3 + <br /> + + Add some FreeBSD specific support into rc.subr</p> + + <p>M4 + <br /> + + Add true dependency checking to the infrastructure so that + starting nfsd will start mountd and rpcbind + <br /> + + add support into rc.subr + <br /> + + Add dependencies into rc.d scripts</p> + + <p>I'd like a couple of people to take a look at this and then + I'll submit a pr for it if there aren't too many objections. I'm + expecting M2 to run into quite a bikeshed, but hey, I got my nice + shiny asbestos back from the cleaners.</p> + </body> + </project> + + <project> + <title>FreeBSD C99/POSIX Conformance Project</title> + + <contact> + <person> + <name> + <given>Mike</given> + + <common>Barcroft</common> + </name> + + <email>mike@FreeBSD.org</email> + </person> + + <person> + <name> + <common>FreeBSD-Standards Mailing List</common> + </name> + + <email>freebsd-standards@bostonradio.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~mike/c99/" /> + </links> + + <body> + <p>The FreeBSD C99/POSIX Conformance Project aims to implement + all requirements of the C99 Standard and the latest 1003.1-200x + POSIX draft (currently Draft 7). In cases where aspects of the + standard cannot be followed, those aspects will be documented in + the c99(7) or posix(7) manuals. It is also an aim of this project + to implement regression tests to ensure correctness whenever + possible.</p> + + <p>Patches that implement the <stdint.h> and + <inttypes.h> headers, and modifications to printf(3) have + been developed and will be committed shortly. They will allow us + to use some of the new types C99 introduces, such as intmax_t and + the printf(3) conversion specifier "%j".</p> + </body> + </project> + + <project> + <title>SMPng Status Report</title> + + <contact> + <person> + <name> + <given>John</given> + + <common>Baldwin</common> + </name> + + <email>jhb@FreeBSD.org</email> + </person> + + <person> + <email>smp@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~jasone/smp/" /> + </links> + + <body> + <p>Some progress has been made on the proc locking this month. + Also, a new LOCK_DEBUG macro was defined to allow some locking + infrastructure to be more efficient. Kernels now only include the + filenames of files calling mutex, sx, or semaphore lock + operations if the filenames are needed. Also, mutex operations + are no longer inlined if any debugging options are turned on. The + ucred API was also overhauled to be more locking friendly. A + group has also started investigating the tty subsystem to design + and possibly implement a locking strategy.</p> + </body> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2001-11.xml b/en_US.ISO8859-1/htdocs/news/status/report-2001-11.xml new file mode 100644 index 0000000000..09fc206315 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2001-11.xml @@ -0,0 +1,1029 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2001-11.xml,v 1.4 2006/08/19 21:20:40 hrs Exp $ --> + +<report> + <date> + <month>November</month> + + <year>2001</year> + </date> + + <section> + <title>Introduction</title> + + <p>This months report covers activity during the second half of + October, and the month of November. During these months, + substantial work was performed to improve system performance and + stability, in particular addressing concerns regarding regressions + in network performance for the TCP protocol, and via the + introduction of polled network device driver support. Work + continues on long-term architectural projects for 5.0, including + KSEs, NEWCARD, and TrustedBSD, as well as the cleaning up of + long-standing problems in FreeBSD, such as PAM integration. + Administrative changes are also documented, including work to + redefine and formalize the release engineering process, and the + approval of a new portmgr group which will administer the ports + collection.</p> + + <p>FreeBSD users and developers are strongly encouraged to attend + the USENIX BSD Conference in February of next year; it is expected + that this will be a useful forum both for learning about FreeBSD + and on-going work, as well as providing an opportunity for + developers to work more closely and act as a vehicle for discussion + and round-the-clock hacking. More information is available at the + USENIX web site.</p> + + <p>Robert Watson</p> + </section> + + <project> + <title>TCP Performance Improvements</title> + + <contact> + <person> + <name> + <given>Matthew</given> + + <common>Dillon</common> + </name> + + <email>dillon@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>A number of serious TCP bugs effecting throughput snuck into + the system over the last few releases and have finally been + fixed. TCP performance should be greatly improved for a number of + cases, including TCP/NFS.</p> + </body> + </project> + + <project> + <title>Intel Gigabit Driver: wx desupported</title> + + <contact> + <person> + <name> + <given>Matthew</given> + + <common>Jacob</common> + </name> + + <email>mjacob@feral.com</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The wx driver is desupported and removed from -current. No + further support for wx in -stable is planned. Newer and better + drivers are now in the tree.</p> + </body> + </project> + + <project> + <title>Fibre Channel Support</title> + + <contact> + <person> + <name> + <given>Matthew</given> + + <common>Jacob</common> + </name> + + <email>mjacob@feral.com</email> + </person> + </contact> + + <links> + <url href="http://www.feral.com/isp.html">Qlogic ISP Host Adapter + Software</url> + </links> + + <body> + <p>Ongoing bug fixes. Work is underway, to be integrated shortly, + that makes the cross platform endian support easier and will + prepare the FreeBSD version for eventual sparc64 and PowerPC + usage.</p> + </body> + </project> + + <project> + <title>TrustedBSD Audit</title> + + <contact> + <person> + <name> + <given>John</given> + + <common>Doe</common> + </name> + + <email>trustedbsd-audit@trustedbsd.org</email> + </person> + </contact> + + <links> + <!-- We don't really have any --> + <url href="http://www.TrustedBSD.org/">TrustedBSD Project + Homepage</url> + </links> + + <body> + <p>Currently, we are exploring a variety of strategies to learn + about the implementation and performance issues in order to have + a solid design. One of our main goals will be to use a + standardized interface to the system, whether it be POSIX.1e, or + another of the other standards, because as they say "Standards + are great because you have so many to choose from." Hopefully + within the next month or so, we will populate the perforce + TrustedBSD tree with an agreed upon framework that is ready for + serious final work.</p> + </body> + </project> + + <project> + <title>Pluggable Authentication Modules</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Murray</common> + </name> + + <email>markm@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Dag-Erling</given> + + <common>Smørgrav</common> + </name> + + <email>des@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~des/diary/2001.html" /> + </links> + + <body> + <p>On the code side, a number of libpam bugs have been fixed; a + new PAM module, + <tt>pam_self(8)</tt> + + , has been written; and preparations have been made for + the transition from + <tt>/etc/pam.conf</tt> + + to + <tt>/etc/pam.d</tt> + + .</p> + + <p>On the documentation side, new manual pages have been written + for + <tt>pam_ssh(8)</tt> + + , + <tt>pam_get_item(3)</tt> + + and + <tt>pam_set_item(3)</tt> + + , and work has started on a longer article about PAM which is + expected to be finished by the end of the year.</p> + + <p>A lot of work still remains to be done to integrate PAM more + tightly with the FreeBSD base system—particularly the + <tt>passwd(1)</tt> + + , + <tt>chpass(1)</tt> + + etc. utilities—and ports collection.</p> + </body> + </project> + + <project> + <title>Status Report: mb_alloc (-CURRENT mbuf allocator)</title> + + <contact> + <person> + <name> + <given>Bosko</given> + + <common>Milekic</common> + </name> + + <email>bmilekic@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~bmilekic/code/mb_alloc/">Code + Dump and Preliminary Results</url> + </links> + + <body> + <p>Presently re-style(9)ing mbuf code with the help of Bruce + (bde). The next larger step is approaching: to better + performance, as initially planned, not have reference counters + for clusters allocated separately via malloc(9). Rather, use some + of the [unused] space at the end of each cluster as a counter; + since this space is totally unused and since ref. counter + <--> mbuf cluster is a one-to-one relationship, this is + most convenient.</p> + </body> + </project> + + <project> + <title>FreeBSD 4.5 Release Engineering</title> + + <contact> + <person> + <name> + <given>Murray</given> + + <common>Stokely</common> + </name> + + <email>murray@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/internal/releng.html">FreeBSD + Release Engineering.</url> + + <url href="http://www.FreeBSD.org/internal/releng45.html">FreeBSD + 4.5 Release Process / Schedule.</url> + </links> + + <body> + <p>Release engineering activities for FreeBSD 4.5 have begun. An + overview of the entire process has been added to the FreeBSD web + site, along with a specific schedule for 4.5. The code freeze is + scheduled to start on December 20. The team responsible for + responding to MFC requests sent to re@FreeBSD.org for this + release is: Murray Stokely, Robert Watson, and John Baldwin. Some + of our many goals for this release include closing more + installation-related problem reports, being more conservative + with our approval of changes during the code freeze, and + continuing to document the entire process. For suggestions or + questions about FreeBSD 4.5 release activities, please subscribe + to the public freebsd-qa@FreeBSD.org mailing list.</p> + </body> + </project> + + <project> + <title>Web site conversion to XML</title> + + <contact> + <person> + <name> + <given>Nik</given> + + <common>Clayton</common> + </name> + + <email>nik@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work is (slowly) progressing on converting the web site to use + pages marked up in a simple XML schema, and then generating HTML + and other output formats using XSLT style sheets. The work so far + can be tested by doing "cvs checkout -r XML_XSL_XP www" and then + "cd www/en; make index.html". Take a look at index.page in the + same directory to see the source XML. The CVS logs for index.page + contain detailed instructions explaining how index.page was + generated from its earlier form.</p> + </body> + </project> + + <project> + <title>FreeBSD in Bulgarian</title> + + <contact> + <person> + <name> + <given>Peter</given> + + <common>Pentchev</common> + </name> + + <email>roam@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD-bg.ringlet.net/" /> + + <url href="http://people.FreeBSD.org/~roam/bg/" /> + </links> + + <body> + <p>The FreeBSD in Bulgarian project aims to bring a more + comfortable working environment to Bulgarian users of the FreeBSD + OS. This includes, but is not limited to, font, keymap and locale + support, translation of the FreeBSD documentation into Bulgarian, + local user groups and various forms of on-line help channels and + discussion forums to help Bulgarians adopt and use FreeBSD.</p> + + <p>Bulgarian locale support has been committed to FreeBSD + 5.0-CURRENT (and later merged into 4.x-STABLE on December 10th). + A local CVS repository for the translation of the FreeBSD + documentation into Bulgarian has been created.</p> + </body> + </project> + + <project> + <title>New mount(2) API</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Maxime</given> + + <common>Henrion</common> + </name> + + <email>mux@qualys.com</email> + </person> + </contact> + + <links> + <url href="http://www.sneakerz.org/~mux/mount.diff" /> + </links> + + <body> + <p>There is now some code ready for the new mount API, which has + to be reviewed and tested. If it is adopted, we will probably + start converting all the filesystems, as well as other code in + the kernel, to make them use it. If you want to play with it, the + patch is available at the above URL.</p> + </body> + </project> + + <project> + <title>Network interface cloning and modularity</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Support for VLAN cloning has been merged from current and will + ship with 4.5-RELEASE. Additionally, new rc.conf support for + cloning interfaces at boot has been MFD'd. Work is ongoing to MFC + stf and faith cloning as well as adding cloning for ppp devices + and enhancing VLAN modularity.</p> + </body> + </project> + + <project> + <title>Device Polling</title> + + <contact> + <person> + <name> + <given>Luigi</given> + + <common>Rizzo</common> + </name> + + <email>luigi@iet.unipi.it</email> + </person> + </contact> + + <links> + <url href="http://info.iet.unipi.it/~luigi/polling/">Web page + with code and detailed description.</url> + </links> + + <body> + <p>This work uses a mixed interrupt-polling architecture to + handle network device drivers, giving the system substantial + improvements in terms of stability and robustness to overloads, + as well as the ability to control the sharing of CPU between + network-related kernel processing and other user/kernel tasks. + Last not least, you might even see a moderate (up to 20-30%, + machine dependent) performance improvement.</p> + </body> + </project> + + <project> + <title>RELNOTESng</title> + + <contact> + <person> + <name> + <given>Bruce</given> + + <common>Mah</common> + </name> + + <email>bmah@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~bmah/relnotes/" /> + + <url href="http://www.FreeBSD.org/relnotes.html" /> + </links> + + <body> + <p>I've been working on making the Hardware Notes less + i386-centric. This will be especially important for -CURRENT as + the ia64 and sparc ports reach maturity; most of this work should + be completed in time to be MFC-ed for FreeBSD 4.5-RELEASE. I + encourage any interested parties to review the release + documentation and send me comments or patches.</p> + </body> + </project> + + <project> + <title>FreeBSD NVIDIA Driver Port</title> + + <contact> + <person> + <name> + <given>Matthew</given> + + <middle>N.</middle> + + <common>Dodd</common> + </name> + + <email>mdodd@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="ftp://ftp.jurai.net/users/winter/nvidia/NEWS">News and + Status.</url> + + <url href="ftp://ftp.jurai.net/users/winter/nvidia/">FTP + directory.</url> + </links> + + <body> + <p>The port of the driver is around 90% feature complete. AGP + support and "Registry" support via sysctl need to be + finished/implemented. The NVIDIA guys are working on a build of + the X11 libs and extensions for FreeBSD; once this is done + hardware accelerated direct rendering should work. The previous + version this driver is no longer available. I'm planning on + making a snapshot of my code once I chase out a few more + bugs.</p> + + <p>Please note that development is taking place under -CURRENT + right now; a port to -STABLE will be available at some later + time.</p> + </body> + </project> + + <project> + <title>jp.FreeBSD.org daily SNAPSHOTs project</title> + + <contact> + <person> + <name> + <given>Makoto</given> + + <common>Matsushita</common> + </name> + + <email>matusita@jp.FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://snapshots.jp.FreeBSD.org/">Project + Webpage</url> + + <url + href="ftp://snapshots.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386/"> + Anonymous FTP</url> + </links> + + <body> + <p>jp.FreeBSD.org daily SNAPSHOTs project is yet another + snapshots server that provides latest 4-stable and 5-current + distribution. You also find installable ISO image, live + filesystem, HTMLed source code with search engine, and more; + please check project webpage for more details.</p> + </body> + </project> + + <project> + <title>UDF Filesystem</title> + + <contact> + <person> + <name> + <given>Scott</given> + + <common>Long</common> + </name> + + <email>scottl@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~scottl/udf">UDF + Filesystem.</url> + </links> + + <body> + <p>Modest gains have been made on the UDF filesystem since the + last report. Reading of files from DVD-ROM now works (and is + fast, according to some reports), and there is preliminary + support for reading from CD-RW media. The CD-RW support has only + been tested against CD's created with Adaptec/ Roxio DirectCD, + and much, much more testing is needed. Once this support is + solid, I plan to check it into the tree and start work on making + the filesystem writable.</p> + </body> + </project> + + <project> + <title>NEWCARD/OLDCARD Status report</title> + + <contact> + <person> + <name> + <given>Warner</given> + + <common>Losh</common> + </name> + + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Not much to report. A number of minor bugs in OLDCARD have + been corrected. A larger number of machines now work. Additional + work on ToPIC support has been committed, but continued lack of a + suitable ToPIC machine has left the author unable to do much + work. A few stubborn machines still need to be supported (the + author has an example of one such machine, so there is hope for + it being fixed. Some pci related issues remain for both OLDCARD + and NEWCARD.</p> + + <p>NEWCARD work is ramping up, while OLDCARD work is ramping + down. A number of things remain to be done for NEWCARD, including + suspend/ resume support, generic device arrival/removal daemon + and hopefully automatic loading of drivers. A number of current + pccard drivers still need to be converted to NEWBUS. Several + Chipset issues remain, as does the merging of isa pccard bridge + code with the pccbb code.</p> + </body> + </project> + + <project> + <title>GEOM - generalized block storage manipulation</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~phk/Geom/">Old concept paper + here.</url> + </links> + + <body> + <p>This project is now finally underway, thanks to DARPA and NAI + getting a sponsorship lined up. The infrastructure code and data + structures are currently taking form inside a userland simulation + harness.</p> + </body> + </project> + + <project> + <title>jpman project</title> + + <contact> + <person> + <name> + <given>Kazuo</given> + + <common>Horikawa</common> + </name> + + <email>horikawa@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.jp.FreeBSD.org/man-jp/">User and developer + information (in Japanese).</url> + </links> + + <body> + <p>Targeting 4.5-RELEASE, we continued to revising + doc/ja_JP.eucJP/man/man[1256789] to catch up with RELENG_4. + Section 3 updating has 45% finished.</p> + </body> + </project> + + <project> + <title>LOMAC Status Report</title> + + <contact> + <person> + <name> + <given>Brian</given> + + <common>Feldman</common> + </name> + + <email>green@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://opensource.nailabs.com/lomac/">NAI Labs' LOMAC + page</url> + </links> + + <body> + <p>A FreeBSD -CURRENT snapshot with LOMAC is currently being + prepared, with aid of Perforce on the "green_lomac" branch. Very + soon there should be a working demonstration installation CD of + FreeBSD with LOMAC, including the ability to enable LOMAC in + rc.conf with sysinstall, being a legitimate "out-of-the-box" + FreeBSD experience. Actual release build is pending debugging + issues with program start-up (especially xdm).</p> + </body> + </project> + + <project> + <title>ATA Project Status Report</title> + + <contact> + <person> + <name> + <given>Søren Schmidt</given> + </name> + + <email>sos@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work is underways to support failing mirror disks better and + handle hotswapping in a new replacement disk and have it rebuild + automagically.</p> + + <p>Support for the Promise TX4 is now working in my lab, seems + they did the PCI-PCI bridging in the not so obvious way.</p> + + <p>Plans are in the works to backport the -current ATA driver to + -stable with hotswap and the works. Now that -current is delayed + I'm working on ways to give me time to get this done, since I've + had lots of requests lately and we really can't let down our + customers :).</p> + + <p>SMART support is being worked on, but no timelines yet.</p> + + <p>Although not strictly ATA, Promise has equipped me with a + couple SuperTrak sx6000 RAID controllers, they take 6 ATA disks + and does RAID0-5 in hardware. I have done a driver (its an I2O + device) for both -current and -stable and it works beautifully with + hotswap the works. It will enter the tree when it is more mature, + and I have an agreement with Promise on how we handle userland + control util etc. BTW it seems it can also be used as a normal 6 + channel PCI ATA controller, a bit on the expensive side + maybe...</p> + </body> + </project> + + <project> + <title>Revised {mode,log}page support for camcontrol</title> + + <contact> + <person> + <name> + <given>Kelly</given> + + <common>Yancey</common> + </name> + + <email>kbyanc@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Extending camcontrol's page definition file format to include + both modepage and logpage definitions; adding support to + camcontrol to query and reset log page parameters. Consideration + is being made to possibly include support for diagnostic and + vital product data pages, but that is outside the current project + scope. New page definition file format includes capability to + conditionally include page definitions based on SCSI INQUIRY + results allowing vendor-specific pages to be described also. + Approximately 80% complete.</p> + </body> + </project> + + <project> + <title>FreeBSD C99 & POSIX Conformance Project</title> + + <contact> + <person> + <name> + <given>Mike</given> + + <common>Barcroft</common> + </name> + + <email>mike@FreeBSD.org</email> + </person> + + <person> + <name> + <common>FreeBSD-Standards Mailing List</common> + </name> + + <email>standards@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~mike/c99/" /> + </links> + + <body> + <p>Work on the FreeBSD C99 & POSIX Conformance Project is + progressing nicely. Since the last status report, two new headers + have been added [<stdint.h> and <inttypes.h>], + several new functions implemented [atoll(3), imaxabs(3), + imaxdiv(3), llabs(3), lldiv(3), strerror_r(3), strtoimax(3), and + strtoumax(3)], and changes to assert(3) and printf(3) were made + to support C99. More printf(3) changes are in the works to + support the remaining C99 and POSIX requirements. Additionally, + research was done into our POSIX Utility conformance and a list + of tasks was derived from that research.</p> + + <p>Several other interesting events occurred during November and + the beginning of December. The project mailing list was moved to + the FreeBSD.org domain, and is now available at + standards@FreeBSD.org. On December 6, 2001, the IEEE Standards + Board approved the Austin Group Specification as IEEE Std + 1003.1-2001, thus making the work we're doing ever more + important.</p> + </body> + </project> + + <project> + <title>Improving FreeBSD startup scripts</title> + + <contact> + <person> + <name> + <given>Doug Barton</given> + + <common>Committer</common> + </name> + + <email>DougB@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gordon Tetlow</given> + + <common>Contributor</common> + </name> + + <email>gordont@gnf.org</email> + </person> + </contact> + + <links> + <url href="http://groups.yahoo.com/group/FreeBSD-rc/">Improving + FreeBSD startup scripts</url> + + <url href="http://www.cs.rmit.edu.au/~lukem/bibliography.html"> + Luke Mewburn's papers</url> + + <url href="http://www.netbsd.org/Documentation/rc/">NetBSD + Initialization and Services Control</url> + </links> + + <body><-- from http://groups.yahoo.com/group/FreeBSD-rc/ --> + <p>This group is for discussion about the startup scripts in + FreeBSD, primarily the scripts in /etc/rc*. Primary focus will be + on improvements and importation of NetBSD's excellent work on this + topic.</p> + + <-- from Gordon Tetlow's ranting --> + <p>Due to personal commitments by the folks working on this project + we have been unable to spend much time porting the rc.d + infrastructure into the FreeBSD boot framework.</p> + + <p>Currently, the system will boot (with a little fudging) just + before network utilization. There are patches floating around for + this (see the -arch list from September).</p> + </body> + </project> + + <project> + <title>KSEs</title> + + <contact> + <person> + <name> + <given>Julian</given> + + <common>Elischer</common> + </name> + + <email>julian@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~julian/">My web-page with + links</url> + + <url href="http://www.FreeBSD.org/~jasone/kse/">Jason Evans' KSE + page.</url> + + </links> + + <body> + <p>I have been working behind the scenes on design rather than + programming for this last month. I have been working however in + the p4 tree to make the system run with the thread structure NOT + a part of the proc structure (a prerequisite for threading)</p> + </body> + </project> + + <project> + <title>Ports Manager Team (portmgr)</title> + + <contact> + <person> + <name> + <given>Will</given> + + <common>Andrews</common> + </name> + + <email>will@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://bento.FreeBSD.org/">Ports build cluster</url> + </links> + + <body> + <p>After a discussion with the Core Team about our status + regarding the ports collection, we heard from them that they'd + decided to recognize us as the final authority for approving + ports committers. We've spent the last few weeks working on our + ports build cluster (see the link) and trying to find ways to + improve it for the ports development community. We've also + handled a few minor issues in the ports collection.</p> + </body> + </project> + + <project> + <title>TrustedBSD Project</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/">TrustedBSD Home Page</url> + </links> + + <body> + <p>The TrustedBSD Project continued focusing development efforts + on fine-grained Capabilities and Mandatory Access Control this + month. Kernel support for capabilities is essentially complete, + and efforts are underway to adapt userland applications to use + Capabilities. The login process has been updated to allow users + to run with additional privilege based on /etc/capabilities. The + MAC implementation work has also been active, with improved + support for the labeling of IPC objects, including better + integration into the network stack. Both development trees have + been updated to work with recent KSE-related developments, as + well as exist more happily in a fine-grained SMP kernel. Initial + audit-related work appears in a separate entry.</p> + + <p>Development of TrustedBSD source code was moved to the FreeBSD + Perforce repository, permitting better source code management. As + such, the TrustedBSD development trees will now be available via + cvsup.</p> + </body> + </project> + + <project> + <title>SMPng Status Report</title> + + <contact> + <person> + <name> + <given>John</given> + + <common>Baldwin</common> + </name> + + <email>jhb@FreeBSD.org</email> + </person> + + <person> + <email>smp@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/smp/" /> + </links> + + <body> + <p>October ended up being a bit busier than November for + SMPng. During October, Peter Wemm finally finished the + ambitious task of unwinding all the macros in NFS and + splitting it up into two halves: client and server. Andrew + Reiter also submitted some code to add locks to taskqueues, + and the folks working on the TTY subsystem designed the + locking strategy they will be using. Per-thread ucred + references were also added for user traps and syscalls. Once + the necessary locking on the process ucred references is + committed, this will allow kernel code to access the + credentials of the current thread without needing locks while + also ensuring that a thread has constant credentials for the + lifetime of a syscall. November only saw a few small bug fixes + unfortunately, but December is already shaping up to be a very + active month, so next month's report should be a bit more + interesting.</p> + + <p>In non-coding news, the website for the SMPng project has + moved from its old location to the new location above. Also, + I have completed a paper I am presenting for BSDCon regarding + the SMPng project. The paper will be available in the + conference proceedings and will be available online after the + conference as well.</p> + </body> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2001-12-2002-01.xml b/en_US.ISO8859-1/htdocs/news/status/report-2001-12-2002-01.xml new file mode 100644 index 0000000000..5bb87125be --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2001-12-2002-01.xml @@ -0,0 +1,721 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2001-12-2002-01.xml,v 1.8 2006/08/19 21:20:39 hrs Exp $ --> + +<report> + <date> + <month>December 2001 - January 2002</month> + + <year></year> <!-- XXX --> + </date> + + <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> + <cvs:keyword name="freebsd"> + $FreeBSD: www/en/news/status/report-2001-12-2002-01.xml,v 1.8 2006/08/19 21:20:39 hrs Exp $ + </cvs:keyword> + </cvs:keywords> + + <section> + <title>Introduction</title> + + <p>This bi-monthly report covers development activities on the FreeBSD + Project for December 2001 and January 2002. A variety of + accomplishments have been made over the last couple of months, + including strong progress relating to the KSE project, which + brings Scheduler Activations to the FreeBSD kernel, as well + as less visible infrastructure projects such as improvements + to the mount interface, PAM integration work, and translation + efforts. Shortly following the deadline for this status + report, the BSD Conference and FreeBSD Developer Summit were + held, and will be covered in the next bi-monthly report at + the end of March. Plans are already under way for the USENIX + Annual Technical Conference in Monterey, CA, later this year, + and all and sundry are encouraged to attend to get further + insight in FreeBSD development.</p> + + <p>Robert Watson</p> + </section> + + + <project> + <title>USB stack maintenance</title> + + <contact> + <person> + <name> + <given>Josef</given> + + <common>Karthauser</common> + </name> + + <email>joe@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>I've been working to integrate recent improvements in the + NetBSD usb stack to FreeBSD -current. Both NetBSD and OpenBSD + currently share the same source, as FreeBSD did too at once point + before it diverged. The goal is to get back to that state, but + there are many improvements on both sides that need to be merged + before this is complete.</p> + + <p>I'm currently looking for someone to help maintain usb in + -stable. Please let me know if you're interested.</p> + </body> + </project> + + <project> + <title>TrustedBSD ACLs</title> + + <contact> + <person> + <name> + <given>Chris</given> + + <common>Faulhaber</common> + </name> + + <email>jedgar@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.fxp.org/jedgar/ACL/"> + </url> + </links> + + <body> + <p>Patches for cp(1), ls(1), and mv(1) to bring in + POSIX.1e-compliant Access Control List support have been updated + to patch against builds of -CURRENT. Other system utilities are + currently being evaluated for ACL support including install(1) + (patch available) and mtree(8). Work is in progress to verify the + native getfacl(1), setfacl(1), and other utilities build and work + correctly on other ACL-enabled systems (e.g. Linux w/ACL patches) + and to help verify POSIX-compliance of the continuing TrustedBSD + work along with other systems. Finally, experimental Perl and PHP + modules are available allowing limited access to native ACLs for + languages other than C.</p> + </body> + </project> + + <project> + <title>Bluetooth stack for FreeBSD (Netgraph + implementation)</title> + + <contact> + <person> + <name> + <given>Maksim</given> + + <common>Yevmenkin</common> + </name> + + <email>m_evmenkin@yahoo.com</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The project is making progress. The goal is to design and + implement Host Controller Interface (HCI) and Link Layer Control + and Adaptation Protocol (L2CAP) layers using Netgraph framework. + More distant goal is to write support for Service Discovery + Protocol (SDP) and RFCOMM protocol (Serial port emulation over + Bluetooth link) . All information was obtained from Bluetooth + Specification Book v1.1.</p> + + <p>Project status: In progress. 1) Design: mostly complete, there + are some minor issues to be resolved. 2) Implementation: Kernel - + HCI and L2CAP Netgraph nodes have been implemented; 3) User space + (API, library, utilities) - in progress. 4) Testing: In progress. + I do not have real Bluetooth hardware at this point, so i wrote + some tools that allow me to test the code. Some of them will be + used as foundation for future user space utilities.</p> + + <p>Issues: 1) Bluetooth hardware; I do not have real Bluetooth + hardware, so if people can donate hardware/specs it would be + great. I promise to write all required drivers and make them + available. I also promise to return hardware/specs on first + request. 2) Project name; I would like to see the name that + reflects the following: it is a Bluetooth stack, implementation + is for FreeBSD and implementation is based on Netgraph + framework</p> + </body> + </project> + + <project> + <title>"GEOM" - generalized block storage manipulation</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~phk/Geom/">Old concept paper + here.</url> + </links> + + <body> + <p>This project is now finally underway, thanks to DARPA and NAI + getting a sponsorship lined up. The infrastructure code and data + structures are currently taking form inside a userland simulation + harness. Basic MBR and BSD methods have been written and device + attach/taste/dettach algorithms been implemented and + validated.</p> + </body> + </project> + + <project> + <title>jp.FreeBSD.org daily SNAPSHOTs project</title> + + <contact> + <person> + <name> + <given>Makoto</given> + + <common>Matsushita</common> + </name> + + <email>matusita@jp.FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://snapshots.jp.FreeBSD.org/">Project + Webpage</url> + + <url href="http://www.jp.FreeBSD.org/snapshots/notes.html"> + SNAPSHOTs Notes (in Japanese)</url> + </links> + + <body> + <p>I've update OS of buildboxes to the latest FreeBSD 5-current + and 4-stable. Everything goes fine. From January 2002, I've + started a webzine, SNAPSHOTS Notes (only Japanese version is + available). SNAPSHOTs Notes pickups tips and information + especially for the people living with FreeBSD 5-current/4-stable. + Article or idea for SNAPSHOTs notes are always welcome (you don't + need to write in Japanese :-).</p> + </body> + </project> + + <project> + <title>TrustedBSD Audit</title> + + <contact> + <person> + <name> + <given>trustedbsd-discuss</given> + </name> + + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/">TrustedBSD project + website</url> + </links> + + <body> + <p>Robert Watson created the TrustedBSD audit perforce tree, + which is a branch from the TrustedBSD base tree, in order to + start pushing development efforts towards using a revision + control system. Andrew Reiter started to merge in some framework + related code for generation of audit records, enqueueing writes, + and handling data writing. There is a great deal of work to be + done with updates and discussion on the + trustedbsd-discuss@TrustedBSD.org mailing list.</p> + </body> + </project> + + <project> + <title>KSE Status Report</title> + + <contact> + <person> + <name> + <given>Julian</given> + + <common>Elischer</common> + </name> + + <email>julian@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~julian/">Links from + here.</url> + + <url href="http://www.FreeBSD.org/~jasone/kse/">Links from + here.</url> + </links> + + <body> + <p>The KSE project (an attempt to support scalable thread in + FreeBSD using kernel support), has reached What I call "milestone + 3". At this milestone it is possible to run a multithreaded + program on a single CPU but with full concurrency of threads on + that CPU. In other words the kernel supports the fact that one + thread can block by allowing another thread to run in its place. + A test program that demonstrates this is available at the above + website.</p> + + <p>Milestone 4 will be to allow threads from the same program to + run on multiple CPUs but may require more input from the SMPng + project. I am at the moment (Feb 6) getting ready to commit a + first set of changes for milestone 3, that have no real effect + but serve to drastically reduce the complexity of the remaining + diff so that others can read it more easily. After changes to + libkvm to support this diff have been added it should be possible + to run 'ps' and look at multiple threads in a treaded process. I + will be demonstrating KSE/M3 at BSDcon.</p> + </body> + </project> + + <project> + <title>Netgraph ATM</title> + + <contact> + <person> + <name> + <given>Harti</given> + + <common>Brandt</common> + </name> + + <email>brandt@fokus.gmd.de</email> + </person> + </contact> + + <links> + <url + href="ftp://ftp.fokus.gmd.de/pub/cc/cats/usr/harti/ngatm/" /> + </links> + + <body> + <p>The Netgraph ATM package has been split into a number of + smaller packages: bsnmp is a general-purpose SNMP daemon with + support for loadable modules. Two modules come with it: one + implementing the standard network-interface and IP related parts + of MIB-2 and one for interfacing other modules to the NetGraph + sub-system. ngatmbase contains the drivers for the ATM hardware, + the ng_atm netgraph type and a few test tools. This package + allows one to use ATM PVCs. It should be possible, for example, + to do PPP over ATM with this package. Both bsnmp and ngatmbase + are available in version 1.0 under the link above. Two other + modules will be released in February: ngatmsig containing the + UNI-4.0 signalling stack as netgraph nodes and ngatmip containing + CLIP and LANE-2.0.</p> + </body> + </project> + + <project> + <title>FreeBSD C99 & POSIX Conformance Project</title> + + <contact> + <person> + <name> + <given>Mike</given> + + <common>Barcroft</common> + </name> + + <email>mike@FreeBSD.org</email> + </person> + + <person> + <name> + <common>FreeBSD-Standards Mailing List</common> + </name> + + <email>standards@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~mike/c99/" /> + </links> + + <body> + <p>A significant amount of progress was made in December and + January, particularly in the area of utility conformance. Several + utilities were updated to conform to SUSv3, they include: at(1), + mailx(1), pwd(1), split(1), and uudecode(1). Several patches have + been submitted to increase conformance in other utilities, they + include: fold(1), patch(1), m4(1), nice(1), pr(1), renice(1), + wc(1), and xargs(1). These are in the process of being reviewed + and committed. Two new utilities have been written, specifically + pathchk(1) and tabs(1). These are also being reviewed and will be + committed shortly.</p> + + <p>A patch which implements most of the requirements of scanf(3) is + being reviewed and is expected to be committed shortly. This will + allow us to MFC a number of new functions and headers. + Additionally, work has started on wide string and complex number + support.</p> + </body> + </project> + + <project> + <title>jpman project</title> + + <contact> + <person> + <name> + <given>Kazuo</given> + + <common>Horikawa</common> + </name> + + <email>horikawa@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.jp.FreeBSD.org/man-jp/">jpman project (in + Japanese)</url> + </links> + + <body> + <p>For 4.5-RELEASE, port ja-man-doc-4.5.tgz is in sync with base + system except for OpenSSH pages (OpenSSH 2.3 based instead of + 2.9) and perl5 pages (jpman project do not maintain). Section 3 + updating has 55% finished.</p> + + <p>OKAZAKI Tetsurou has incorporated changes on base system's + groff into port japanese/groff. MORI Kouji has fixed two bugs of + port japanese/man.</p> + </body> + </project> + + <project> + <title>KAME</title> + + <contact> + <person> + <name> + <given>KAME core team</given> + + <common> + </common> + </name> + + <email>core@kame.net</email> + + <name> + <given>KAME Users Mailing List</given> + + <common> + </common> + </name> + + <email>snap-users@kame.net</email> + </person> + </contact> + + <links> + <url href="http://www.kame.net/" /> + </links> + + <body> + <p>The KAME project is currently focusing on the scoped + addressing architecture, the advanced API implementation, NATPT + and the mobile ipv6 implementation. Though these stuffs are not + stable enough to be merge into the FreeBSD tree, you can get and + try them from the above URL.</p> + </body> + </project> + + <project> + <title>FreeBSD in Bulgarian</title> + + <contact> + <person> + <name> + <given>Peter</given> + + <common>Pentchev</common> + </name> + + <email>roam@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD-bg.ringlet.net/" /> + + <url href="http://people.FreeBSD.org/~roam/bg/" /> + </links> + + <body> + <p>The FreeBSD in Bulgarian project aims to bring a more + comfortable working environment to Bulgarian users of the FreeBSD + OS. This includes, but is not limited to, font, keymap and locale + support, translation of the FreeBSD documentation into Bulgarian, + local user groups and various forms of on-line help channels and + discussion forums to help Bulgarians adopt and use FreeBSD.</p> + + <p>A guide for using FreeBSD with Bulgarian settings has been put + up on the project's website. The CVS repository will be made + public shortly, linked to on the URL's above.</p> + + <p>An independent project for making FreeBSD easier to use by + Bulgarians has appeared, <a + href="http://www.FreeBSD-bg.org/">http://www.FreeBSD-bg.org/</a>. + It also hosts a mailing list for discussions of FreeBSD in + Bulgarian, <a href="mailto:stable@FreeBSD-bg.org"> + stable@FreeBSD-bg.org</a>. For more information about the mailing + list, send an e-mail with "help" in the message body to + <a href="mailto:majordomo@FreeBSD-bg.org"> + majordomo@FreeBSD-bg.org</a>.</p> + </body> + </project> + + <project> + <title>FreeBSD Java Project</title> + + <contact> + <person> + <name> + <given>Greg</given> + + <common>Lewis</common> + </name> + + <email>glewis@eyesbeyond.com</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/java" /> + </links> + + <body> + <p>The past two months have been an exciting time in the FreeBSD + Java Project with the signing of a license between the FreeBSD + Foundation and Sun allowing us access to updated JDK source code + and the Java Compatibility Kit (JCK). This license will also + allow the project to release a binary version of both the JDK and + JRE once JCK testing is complete. Work on this testing is under + way with the project hopeful of being able to make a binary + release in the not too distant future.</p> + + <p>In lieu of the binary release which was hoped for with FreeBSD + 4.5 the project will release an updated source patchset this + weekend. This patchset will feature further work on the FreeBSD + "native" threads subsystem from Bill Huey. Also, thanks to hard + work by Joe Kelsey and Fuyuhiko Maruyama, the patchset will for + the first time feature a working Java browser plugin!</p> + </body> + </project> + + <project> + <title>Revised {mode,log}page support for camcontrol</title> + + <contact> + <person> + <name> + <given>Kelly</given> + + <common>Yancey</common> + </name> + + <email>kbyanc@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Extending camcontrol's page definition file format to include + both modepage and logpage definitions; adding support to + camcontrol to query and reset log page parameters. Consideration + is being made to possibly include support for diagnostic and + vital product data pages, but that is outside the current project + scope. New page definition file format includes capability to + conditionally include page definitions based on SCSI INQUIRY + results allowing vendor-specific pages to be described also. + Approximately 90% complete.</p> + </body> + </project> + + <project> + <title>Pluggable Authentication Modules</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Murray</common> + </name> + + <email>markm@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Dag-Erling</given> + + <common>Smørgrav</common> + </name> + + <email>des@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://openpam.sourceforge.net/">OpenPAM</url> + </links> + + <body> + <p>OpenPAM, a new library intended to replace Linux-PAM in + FreeBSD, has been written and is undergoing integration testing. + It is available for download from the URL listed above.</p> + + <p>In addition to this, a couple of new modules have been written + (pam_lastlog(8), pam_login_access(8)), and the pam_unix(8) module + has been extended to perform most of the tasks normally performed + by login(1), which is now fully PAMified.</p> + + <p>The PAM FDP article has been put on hold until OpenPAM + replaces Linux-PAM in CVS, to avoid wasting effort on soon-to-be + obsolete documentation.</p> + </body> + </project> + + <project> + <title>TrustedBSD MAC Implementation</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/">TrustedBSD Project Web + Site</url> + </links> + + <body> + <p>Substantial progress has been made towards a working MAC + implementation. The focus over the last two months has been + moving from a hard-coded series of MAC policies to a more + flexible implementation. A pluggable policy framework has been + created (and is still under development), supporting Biba, MLS, + TE, a "BSD Extended" model, and a sample mac_none module. Some + modules must be compiled in or loaded prior to boot; others may + be introduced at run-time. Support for networking has improved, + with improved handling of IP fragmentation in IPv4, support for + various pseudo-interfaces such as if_tun and if_tap, improved + integration into userland, NFS-related fixes, moving the VFS + enforcement out of individual filesystems, support for a + 'multilevel' mount flag, support for explicit labeling in procfs + and devfs, addition of an 'extattrctl lsattr' argument to list + EAs on a filesystem, support for label ranges in the Biba and MAC + policies, and much more.</p> + + <p>Targets for the next two months include more universal + enforcement of VFS-related calls, improved support for + alternative ABIs, improved flexibility of in-kernel subject and + object labels, support for IPv6 and IPsec, and improved support + for NFS serving.</p> + + <p>Development continues in the FreeBSD Perforce repository, + which may be accessed using cvsup.</p> + </body> + </project> + + <project> + <title>New mount(2) API</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Maxime</given> + + <common>Henrion</common> + </name> + + <email>mux@sneakerz.org</email> + </person> + </contact> + + <body> + <p>Now that the patch has been mailed to the + freebsd-arch@FreeBSD.org mailing list, and that there were no + objections, the commit will happen soon. Poul is currently + testing it in his own tree. After it has been committed, it will + be time to modify the filesystems in the tree to use VFS_NMOUNT + instead of VFS_MOUNT. Mount(8) will also need some modifications. + Some new manpages -- nmount(2) and kernel_vmount(9) -- are being + created in the meantime.</p> + </body> + </project> + + + <project> + <title>SMPng</title> + + <contact> + <person> + <name> + <given>smp@FreeBSD.org</given> + </name> + + <email>smp@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/smp/">SMPng project + website</url> + </links> + + <body> + <p>Alfred Perlstein committed file descriptor locking code + which was definitely a good push towards trying to lock down + some important pieces of global data. Peter Wemm has made + progress on pmap cleanups for x86 SMP TLB shootdowns. Matt + Dillon and John Baldwin have made progress on getting patches + done for moving accesses to ucred's out from under Giant's + protection. John Baldwin has also made some commits in order + to get the alpha port's SMP working. Matt Dillon has plans + for hunting down fileops locking issues in order to continue + his previous Giant pushdown work.</p> + </body> + </project> + +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2002-02-2002-04.xml b/en_US.ISO8859-1/htdocs/news/status/report-2002-02-2002-04.xml new file mode 100644 index 0000000000..32bfb1f972 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2002-02-2002-04.xml @@ -0,0 +1,1301 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2002-02-2002-04.xml,v 1.12 2006/08/19 21:20:40 hrs Exp $ --> + +<report> + <date> + <month>February - April</month> + <year>2002</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report covers FreeBSD development activities from February, + 2002 through April, 2002. It's been a busy few months -- BSDCon + in San Francisco, the FreeBSD Developer Summit, a first development + preview of 5.0-CURRENT, not to mention lots of progress on the + 5.0 feature set (SMPng, sparc64, GEOM, ... the list goes on).</p> + <p>In the next two months, the USENIX ATC occurs (highly recommended + event for both developers and users), and a number of new software + components will hit the tree, including UFS2 and the TrustedBSD + MAC framework. We'll also complete the elections for the FreeBSD + Core Team, and should have the next Core Team online by the time + the next report rolls around. Stay tuned for more!</p> + <p>Robert Watson</p> + </section> + + <project> + <title>FreeBSD Package-building Cluster</title> + + <contact> + <person> + <name> + <given>Kris</given> + <common>Kennaway</common> + </name> + <email>kris@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Packages are built from the FreeBSD Ports Collection on a + cluster of i386 and alpha machines using scripts available in + /usr/ports/Tools/portbuild/. Over the past few months I have + been cleaning up and extending these scripts to improve + efficiency and allow for greater flexibility in how package + builds are performed. Major improvements so far have been: + cleaning up and modularizing the scripts to avoid code + duplication and reduce the need for ongoing maintenance; + optimizing the build process and making it much more robust + against client machine failure; and allowing package builds to + be restarted if they are interrupted. The i386 package + cluster is currently running FreeBSD 5.0-CURRENT, and it has + proven to be a useful testing ground for exposing kernel bugs, + especially those which only manifest under system load.</p> + + <p>Future plans include the ability to perform incremental + package rebuilds which only build packages that have changed + since the last run. This will allow packages to be made + available on the FTP site within an hour or two of the CVS + commit to the ports collection. We also hope to set up a + sparc64 package cluster in the near future, but this is + contingent on suitable hardware.</p> + </body> + </project> + + <project> + <title>UMA</title> + + <contact> + <person> + <name> + <given>Jeff</given> + <common>Roberson</common> + </name> + + <email>jeff@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>FreeBSD's new kernel memory allocator has been committed to + 5.0. UMA is a slabs derived allocator that supports memory + reclaiming, object caching, type stable storage, and per CPU + free lists for optimal SMP performance. It has both a + malloc(9) interface and a zone style interface for specific + object types. uma(9) will be available shortly.</p> + </body> + </project> + + <project> + <title>Universal Disk Filesystem for FreeBSD</title> + + <contact> + <person> + <name> + <given>Scott</given> + <common>Long</common> + </name> + <email>scottl@FreeBSD.org</email> + </person> + <person> + <name> + <given>Jeroen</given> + <common>Ruigrok</common> + </name> + <email>asmodai@wxs.nl</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~scottl/udf">UDF Homepage.</url> + </links> + + <body> + <p>Read-only support for UDF filesystems was checked into the 5-CURRENT + branch in April. Backporting for 4-STABLE is being conducted by + Jeroen. The next phase is to write a newfs_udf, then move on to + adding write support to the filesystem. I'm still looking for a + volunteer to handle read and write support for write-once media + (e.g. CD-R).</p> + </body> + </project> + + <project> + <title>Zero Copy Sockets</title> + + <contact> + <person> + <name> + <given>Ken</given> + + <common>Merry</common> + </name> + + <email>ken@FreeBSD.org</email> + </person> + </contact> + + <links> + + <url href="http://people.FreeBSD.org/~ken/zero_copy/">Zero copy patches + and information. </url> + </links> + + <body> + <p> I have released a new zero copy sockets snapshot, the first since + November, 2000. The code has been ported up to the latest + -current, and the jumbo code now has mutex protection. Also, zero + copy send and receive can be selectively turned on and off via sysctl + to make it easier to compare performance with and without zero copy. + Reviews and comments are welcome.</p> + </body> + </project> + + <project> + <title>Bluetooth stack for FreeBSD (Netgraph implementation)</title> + + <contact> + <person> + <name> + <given>Maksim</given> + <common>Yevmenkin</common> + </name> + + <email>m_evmenkin@yahoo.com</email> + </person> + </contact> + + <body> + + <p>I'm slowly making progress. The second engineering release is + available for download at + http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020506.tar.gz</p> + + <p>This release includes support for H4 UART transport layer, Host + Controller Interface (HCI), Link Layer Control and Adaptation + Protocol (L2CAP) and Bluetooth sockets layer. It also comes + with several user space utilities that can be used to configure + and test Bluetooth devices.</p> + + <p>I'm currently working on RFCOMM protocol implementation (Serial + port emulation over Bluetooth link). My next goal is to port + Service Discovery Protocol (SDP) implementation from BlueZ + (http://bluez.sf.net). I'm also thinking about adding USB device + support (as soon as i find/buy hardware).</p> + + <p>Issues: 1) Bluetooth hardware; I have couple PC-CARDs that i use + for development and testing purposes, but i'd love to have more. + 2) Time; My regular day job kicked in, so i will be spending more + time doing stuff i'm getting paid for.</p> + + </body> + </project> + + <project> + <title>FreeBSD C99 & POSIX Conformance Project</title> + + <contact> + <person> + <name> + <given>Mike</given> + + <common>Barcroft</common> + </name> + + <email>mike@FreeBSD.org</email> + </person> + <person> + <name> + <common>FreeBSD-Standards Mailing List</common> + </name> + + <email>standards@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/c99/" /> + </links> + + <body> + <p>Since the last status report, two developers working on utility + conformance were given commit access to the FreeBSD CVS repository + to help expedite development. As a result, the following utilities + have been brought up to conformance, they include: csplit(1), + env(1), expr(1), fold(1), join(1), m4(1), mesg(1), paste(1), + patch(1), pr(1), uuencode(1), uuexpand(1), and xargs(1). The + printf(1) utility was brought up to conformance with the 1992 + edition of POSIX.2, with further development planned.</p> + + <p>On the header front, much progress has been made. Specifically, + infrastructure to control visibility of components of a header, based + on the standard requested by an application, has been added to + <sys/cdefs.h>. Some work has been completed on renovating the + way types are defined. This has lead to the creation of + <sys/_types.h>. Further improvements such as the merger of + <machine/ansi.h> and <machine/types.h> are planned. + Additionally, the headers: <strings.h>, <string.h>, and + <sys/un.h> have been made to conform to POSIX.1-2001.</p> + + <p>On the API front, scanf(3) has received support for 5 new length + modifiers (hh, j, ll, t, and z). A patch to implement two + additional conversion specifiers (j and z) has been developed for + printf(9) and is expected to be committed soon.</p> + + <p>In other news, the project's web site has been moved to the main + FreeBSD site. It is now available at the URL at the top of this + status report. Please update your bookmarks.</p> + </body> + </project> + + <project> + <title>Netgraph ATM</title> + + <contact> + <person> + <name> + <given>Harti</given> + + <common>Brandt</common> + </name> + + <email>brandt@fokus.fhg.de</email> + </person> + </contact> + + <links> + + <url href="http://www.fokus.fhg.de/research/cc/cats/employees/hartmut.brandt/ngatm/index.html">Introduction to NgAtm</url> + </links> + + <body> + <p>Version 1.1 for FreeBSD-current is now available. It includes + the SNMP-daemon package bsnmp, the driver package ngatmbase, + the UNI4.0 signaling package ngatmsig and the network emulation + package ngatmnet. NgAtm allows both to build applications running + directly on top of ATM and to use ATM-Forum LAN emulation to + use IP over ATM. Currently we are working on a simple switch module, + that implements the network side signaling and ILMI as well as + simple routing and call admission control.</p> + </body> + </project> + + <project> + <title>GNOME Project</title> + + <contact> + <person> + <name> + <given>Joe</given> + + <common>Marcus</common> + </name> + + <email>marcus@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/gnome">FreeBSD GNOME Project + homepage.</url> + </links> + + <body> + <p>The GNOME project has seen quite a few changes lately. For one, + the author of this update has recently been given "The Bit." + Joe Marcus Clarke now has CVS access, and is working primarily + on the GNOME project. Joe has been closing a good deal of GNOME + PRs, as well as patching some of the existing GNOME 1.4 + components.</p> + + <p>The GNOME 2 porting effort continues on. We have completed porting + of the GNOME 2.0 API, and are 75% complete on porting the full + GNOME 2.0 desktop. When complete, GNOME 1.4 and GNOME 2.0 will + be co-resident in the ports tree. Both APIs can be installed + concurrently in the same PREFIX, but the respective desktops + will remain mutually independent. Maxim Sobolev is working + on adapting bsd.gnome.mk to handle both versions of the desktop + in an elegant fashion.</p> + + <p>Not to be left out, the existing GNOME 1.4 components have received + numerous updates to keep them in sync with the stable distfiles + on gnome.org. We have seen many "1.0" milestone releases including + the most recent AbiWord 1.0.0. In the next few weeks, we will be + making sure all the GNOME 1.4 components build correct packages + on bento so that GNOME 1.4 will be on the 4.6-RELEASE CD.</p> + </body> + </project> + + <project> + <title>FreeBSD/KGI</title> + + <contact> + <person> + <name> + <given>Nicholas</given> + + <common>Souchu</common> + </name> + + <email>nsouch@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~nsouch/ggiport.html" /> + </links> + + <body> + <p> FreeBSD/KGI started last year after the port of GGI to VGL. + KGI (Kernel Graphic Interface) is a kernel infrastructure providing user + applications with access to hardware graphic resources (dma, + irqs, mmio). KGI is already available under Linux as a separate + project. The FreeBSD/KGI project aims at integrating KGI + in the FreeBSD kernel. Mostly a port for now, but optimized for + FreeBSD in the future. Currently FreeBSD/KGI is under development + and the code is only available for reading, compiling but not running. + More interesting are design hints found at the project URL.</p> + + </body> + </project> + + <project> + <title>Libh</title> + + <contact> + <person> + <name> + <given>Antoine</given> + <common>Beauprş</common> + </name> + + <email>anarcat@anarcat.ath.cx</email> + </person> + <person> + <name> + <given>Alexander</given> + <common>Langer</common> + </name> + + <email>alex@FreeBSD.org</email> + </person> + <person> + <name> + <given>Nathan</given> + <common>Ahlstrom</common> + </name> + + <email>nra@FreeBSD.org</email> + </person> + </contact> + + <links> + + <url href="http://www.FreeBSD.org/projects/libh.html">Main project page.</url> + + </links> + + <body> + <p>We now have a loadable mfsroot floppy. It contains just the + diskeditor (which is really a disk partitioner) which has been + enhanced and is probably in its final form. It's been geared + towards making the newfs(1) and mount(1) steps separate dialogs, so + it reduceed its complexity. A basic fstab class has been + implemented to manipulate /etc/fstab and mountpoint. This might + find a use outside libh, by the way. Libh package format is still + incomplete and somehow buggy, so it's my next target.</p> + + <p>There is a API documentation effort underway with the help of + doxygen(1), so there's now more documentation for people that want + to get started with libh.</p> + + <p>All this lead me to prepare the release of another alpha + preview of libh that will shortly be available in the ports + collection (0.2.2). Also, a new committer (okumoto) has joined the + project (as well as I) and he is currently working on cleaning up + the build system. It's been a few months without news, so this + probably seemed a bit long, but don't worry, we still need your + help to really get this going!</p> + + </body> + </project> + + <project> + <title>jp.FreeBSD.org daily SNAPSHOTs project</title> + <contact> + <person> + <name> + <given>Makoto</given> + <common>Matsushita</common> + </name> + <email>matusita@jp.FreeBSD.org</email> + </person> + </contact> + <links> + <url href="http://snapshots.jp.FreeBSD.org/">Project Webpage</url> + <url href="http://www.jp.FreeBSD.org/snapshots/">Project Webpage (in Japanese)</url> + </links> + <body> + <p>There are several new topics, including: Source Code Tour is now + separated into kernel part and userland part, yet another snapshots + from RELENG_4_x branch (currently 4.5-RELEASE-p4), add several + packages including XFree86 4.x to installation CD-ROM, new + cdboot-only ISO image, fix breakage of duplex.iso, etc. See also + the project webpage for more detail. Also, I have a plan to add + FreeBSD/alpha distribution to this project -- stay tuned.</p> + </body> + </project> + + <project> + <title>KAME</title> + + <contact> + <person> + <name> + <given>Shinsuke</given> + <common>SUZUKI</common> + </name> + + <email>suz@kame.net</email> + </person> + </contact> + + <links> + <url href="http://www.kame.net/">KAME Project Home Page</url> + <url href="http://www.kame.net/roadmap-2002.html">KAME Project Roadmap</url> + </links> + + <body> + <p> KAME Project has been extended until March 2004, and we decided the project + roadmap for these two years. The first one year is for implementation, and the + remaining year is for feedback of our results into other BSD projects (please refer + to the above URL for further detail). + Great change is lack of NAT-PT support due to a lack of human resource, although + KAME snap still contains it as it is.</p> + + <p> SUZUKI Shinsuke (suz@kame.net) has begun working for KAME and FreeBSD merge task in + cooperation with Umemoto-san (ume@FreeBSD.org). + Some of KAME stuff (critical bug fix, newest ports for pim6sd and racoon, etc) + has been merged into 4-stable in this April.</p> + </body> + </project> + + <project> + <title>TrustedBSD Audit</title> + + <contact> + <person> + <name> + <given>Andrew</given> + + <common>Reiter</common> + </name> + <email>arr@FreeBSD.org</email> + </person> + <person> + <name> + <given>TrustedBSD Audit Mailing List</given> + </name> + <email>trustedbsd-audit@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/">TrustedBSD +main web page</url> + </links> + + <body> + <p>Over the past couple of months, progress has pretty much stopped + until very recently. The past few changes to the audit code were + update the usage of zones to UMA zones, cleanup some old cruft, + and start toying with the idea of having an audit write thread + implemented as an ithd. The next step is to decide two realistic + approaches to the where the records will be dumped -- whether that + is to a local disk or fed up to userland and then dealt with. + After that, the goal will be to expand the number of events that + are being audited, while also working in some performance testing + procedures. I will be posting to trustedbsd-audit about the recent + changes shortly.</p> + </body> + </project> + + <project> + <title>TrustedBSD MAC</title> + + <contact> + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + <person> + <name> + <given>TrustedBSD Discussion Mailing List</given> + </name> + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/">TrustedBSD main web page</url> + </links> + + <body> + <p>Over the last three months, there has been a lot of activity + in the TrustedBSD MAC tree. An initial commit of the SEBSD + code (NSA FLASK and SELinux implementation) was made; many + MAC policies previously linked directly to the kernel via + kernel options were moved to kernel modules; the flexibility + of the framework was improved relating to the life cycle of + object labels; additional labeling and access control hooks + were introduced; new policies were introduced to demonstrate + the flexibility of the framework (including a cleanup of + inter-process authorization, additional VFS hooks, improved + support for multilabel filesystems, network booting, IPv6, + IPsec, support for "peer" labels on stream sockets). + Current modules include Biba integrity policy, MLS + confidentiality policy, Type Enforcement, "BSD Extended" + (permitting firewall-like rulesets for filesystem protection), + "ifoff" (limit interface communication by policy), + mac_seeotheruids (limit visibility of processes/etc of other + users), "babyaudit" (a simple audit implementation), and + SEBSD (FLASK/SELinux port).</p> + <p>Over the next month, a final move to completely dynamic + labeling will be made, permitting policies to introduce new + state relating to process credentials, vnodes, sockets, + mounts, interfaces, and mbufs at run-time, allowing a broad + range of flexible label-driven policies to be developed. + In addition, application APIs will be re-designed and + re-implemented so as to better support a fully dynamic + policy framework. We plan to make an initial prototype + patchset available for review in June, with the intent of + committing that patchset in mid-June.</p> + <p>Updated prototype code may be retrieved from the TrustedBSD + CVS trees on cvsup10.FreeBSD.org.</p> + </body> + </project> + + <project> + <title>PAM</title> + + <contact> + <person> + <name> + <given>Mark</given> + <common>Murray</common> + </name> + <email>markm@FreeBSD.org</email> + </person> + <person> + <name> + <given>Dag-Erling</given> + <common>SmŲrgrav</common> + </name> + <email>des@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~des/pam/pam-2002-03.html">March 2002 PAM activity report.</url> + <url href="http://people.FreeBSD.org/~des/pam/pam-2002-04.html">April 2002 PAM activity report.</url> + </links> + + <body> + <p>The painful parts are now completed, with all authentication- + related utilities converted to PAM (except for those cases where + it doesn't make sense, like Kerberos- or OPIE-specific + commands). OpenPAM is complete (except for a few missing man + pages) and seems to work well.</p> + + <p>For more details, see the activity reports linked to above.</p> + </body> + </project> + + <project> + <title>OpenSSH</title> + + <contact> + <person> + <name> + <given>Dag-Erling</given> + <common>SmŲrgrav</common> + </name> + <email>des@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>OpenSSH has been upgraded to 3.1, and the kinks seem to have + been worked out by now. OpenSSH will now use PAM for both ssh1 + and ssh2 authentication.</p> + </body> + </project> + + <project> + <title>KSE</title> + + <contact> + <person> + <name> + <given>Julian</given> + + <common>Elischer</common> + </name> + + <email>julian@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Jonthan</given> + <common>Mini</common> + </name> + <email>mini@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~julian/" /> + <url href="http://www.FreeBSD.org/~jasone/kse/" /> + </links> + + <body> + <p>The KSE project had floundered due to lack of development + time for awhile, but has been picked up recently by + Jonathan Mini. Currently, the main focus is to prepare + the "milestone 3" code for inclusion into -CURRENT.</p> + + <p>The project is still working towards "milestone 4" + (allowing threads from the same process to run on + multiple CPUs), which should be significantly easier + now due to work done by the SMPng project over the past + several months.</p> + + <p>Help could be used in several areas of the project, + especially with porting the libc_r (pthreads) library + to KSE's threading model.</p> + + </body> + </project> + + <project> + <title>NEWCARD</title> + + <contact> + <person> + <name> + <given>Warner</given> + + <common>Losh</common> + </name> + + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>NEWCARD support tried to merge CardBus functions with PCI + functions, but that failed to properly route interrupts. A + branch for the merge was created and will be merged into the + main line at a later date. Too many other things going on in my + life to make much progress.</p> + </body> + </project> + + <project> + <title>Wi Hostap</title> + + <contact> + <person> + <name> + <given>Warner</given> + + <common>Losh</common> + </name> + + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work on the host access point support for the Prism2 and + Prism2.5 based wireless cards has been integrated into the + kernel. This work is largely based on Thomas Skibo's initial + implementation.</p> + </body> + </project> + + <project> + <title>Fibre Channel</title> + <contact> + <person> + <name> + <given>Matthew</given> + <common>Jacob</common> + </name> + <email>mjacob@FreeBSD.org</email> + </person> + </contact> + <links> + + <url href="http://people.FreeBSD.org/~mjacob/fibre_channel.html">Project Status Page.</url> + </links> + + <body> + <p>Continued bug fixing and hardening for this last few months.</p> + <p>Future work will include making target mode work correctly and fast.</p> + <p>The LSI-Logic chipset's MPT Fusion driver is also being evaluated.</p> + </body> + </project> + + <project> + <title>Athlon MTRR Problems</title> + + <contact> + <person> + <name> + <given>David</given> + + <common>Malone</common> + </name> + + <email>dwmalone@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The FreeBSD MTRR code has been made more robust against + unexpected values sometimes found in the Athlon's Memory + Type Range Registers. Problems with these values had prevented + XFree 4.2 running on some motherboards. Experimentation indicates + that these undocumented values may control the mapping of + BIOS/ROMs or have something to do with SMM. If anyone can provide + details of what these values mean, can they + please let me know, so the MTRR code can be completed. </p> + </body> + </project> + + <project> + <title>IPMI Tools for FreeBSD</title> + + <contact> + <person> + <name> + <given>Doug</given> + + <common>White</common> + </name> + + <email>dwhite@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~dwhite/ipmi/" /> + </links> + + <body> + <p>IPMI Tools for FreeBSD is a collection of C and Python + applications and modules for exploring the information available + via the Intelligent Platform Management Interface (IPMI), as + implemented on server motherboards by Intel and HP. IPMI is an + open standard with patent protection for adopters which defines + standard interfaces to on-board management hardware. The + management hardware consists of a CPU, sensors such as temperature + probes and fan speeds, and repositories such as the System Event + Log and Field-Replaceable Unit (FRU) inventory, and other system + information. </p> + + <p>A basic set of tools was recently made available which uses the + KCS and SMIC system interfaces to retrieve the System Event Log, + FRU repository, and system sensors. Additional features are + currently under research. Suggestions for additional features and + programs are greatly appreciated. </p> + + </body> + </project> + + <project> + <title>PowerPC Port</title> + + <contact> + <person> + <name> + <given>Benno</given> + + <common>Rice</common> + </name> + + <email>benno@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://jeamland.net/~benno/powerpc-boot.txt">Current boot +messages.</url> + </links> + + <body> + <p>The PowerPC port is moving ahead. It can now mount a root file system + and exec init, but fails when trying to map init's text segment in. I'm + hoping to have it starting my fake "Hello, world!" init soon, after which + I plan to try and get some libc bits in place so that I can build /bin + and /sbin and try to get to actual single-user.</p> + </body> + </project> + + <project> + <title>jpman project</title> + + <contact> + <person> + <name> + <given>Kazuo</given> + <common>Horikawa</common> + </name> + + <email>horikawa@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.jp.FreeBSD.org/man-jp/"> + jpman project page both for users and developers (in Japanese)</url> + </links> + + <body> + <p>4.5-RELEASE Japanese manpage package, ja-man-doc-4.5.tgz, once + published with OpenSSH 2.3 (as reported by previous status + report) on January 31, is replaced with new package with OpenSSH + 2.9 based manpages on March 3. Since then, we have been + updating Japanese manpages for 4.6-RELEASE. For new translation + and massive update, we have been making a lot of effort.</p> + <p>Continuing section 3 updating has 73% finished.</p> + </body> + </project> + + <project> + <title>"GEOM" - generalized block storage manipulation</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <links> + + <url href="http://www.FreeBSD.org/~phk/Geom/">Old concept paper here.</url> + + </links> + + <body> + <p>The GEOM code has gotten so far that it beats our current code + in some areas while still lacking in others. Work continues on + a generalized interface for "magic data" (boot blocks, disklabels + MBR's etc) manipulation from userland.</p> + <p>With GEOM enabled in the kernel any FreeBSD platform will now + recognize PC style MBR's, i386 disklabels, alpha disklabels, + PC98 extended MBRs and SUN/Solaris style disklabels.</p> + + </body> + </project> + + <project> + <title>FreeBSD ARM Port</title> + <contact> + <person> + <name> + <given>Stephane E.</given> + <common>Potvin</common> + </name> + <email>sepotvin@videotron.ca</email> + </person> + </contact> + <links> + <url href="http://pages.infinit.net/sepotvin" /> + </links> + <body> + <p>Since the last progress report, the initialization code was much + cleaned (thanks to NetBSD's acort32 port) and partial DDB support as + been added. I'm now struggling to put the pmap module into a + working state. The latest patch set only includes the + initialization changes. I did some tries to get what I had so far + working on my iPAQ without much successes (downloading a kernel + over a serial link is way too painful). If anyone has had success in + getting any iPAQ to work as a USB storage device under *BSD please + contact me.</p> + </body> + </project> + + <project> + <title>locking up pcb's in the networking stack</title> + + <contact> + <person> + <name> + <given>Jeffrey</given> + + <common>Hsu</common> + </name> + + <email>hsu@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/smp/" /> + </links> + + <body> + <p>I've been mentoring someone on locking up the protocol control + blocks in the networking stack. She has already finished TCP and + UDP and I'm currently reviewing the patch with her and going over + some networking lock order issues. Locking up raw protocol + interface control blocks follows next.</p> + + </body> + </project> + + <project> + <title>Network interface cloning and modularity</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Support for stf(4), faith(4), and loopback interfaces has been + committed to current. The stf and faith support has been MFC'd. + In current the API has changed to move unit allocation into the + generic cloning code reducing the amount of support code required + in each driver. Code improvements to increase our API + compatibility with NetBSD will be committed soon along with cloning + support for discard interfaces and ppp(4) interfaces.</p> + <p>Thanks to <email>mux@FreeBSD.org</email> for the loopback support + and unit allocation cleanups.</p> + </body> + </project> + + <project> + <title>IA64 Port</title> + + <contact> + <person> + <name> + <given>Peter</given> + <common>Wemm</common> + </name> + <email>peter@FreeBSD.org</email> + </person> + </contact> + + <body> + + <p>IA64 has had a busy few months. Aside from gcc, we are now fully + self hosting on IA64. Doug Rabson has performed his magic and + implemented the execution of 32 bit i386 application binaries + although more work remains to be done to make ld-elf.so.1 happy + with the different underlying page size. We have been using the + i386 perforce binary to do actual development work and submit from + the ia64 systems themselves. Marcel Moolenaar has been working on + SMP and machine-check support. We have been running SMP kernels + amazingly reliably on our development boxes for quite some time now. + syscons is now functional. We have produced a self-booting + run-root-on-cdrom ISO image (idea taken from the sparc64 folks) that + has been used to manually self install an IA64 system from a blank + disk. Aside from a few minor loose ends we now have complete 'make + world' functionality. sysinstall works on ia64. We plan on + producing a semi-respectable boot/install cdrom image shortly.</p> + </body> + </project> + + <project> + <title>GCC 3.1</title> + + <contact> + <person> + <name> + <given>David</given> + <common>O'Brien</common> + </name> + <email>obrien@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>As of Thur May 9th, 2002 FreeBSD 5-CURRENT is now using a GCC 3.1 + prerelease snapshot as the system C compiler. At this time of + cutting over, the compiler is working well on i386, Alpha, Sparc64, + and IA-64 for building world. There is a known problem with our + atomic ops on Alpha that prevents a GCC 3.1 built kernel from + booting.</p> + + <p>Currently the C++ support libraries (libstdc++, et.al.) does not + build and thus prevents the system C++ compiler from being used.</p> + </body> + </project> + + <project> + <title>Release Engineering</title> + + <contact> + <person> + <name> + <common>Release Engineering</common> + </name> + + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/" /> + </links> + + <body> + <p>The release engineering team released FreeBSD <a + href="http://www.FreeBSD.org/releases/5.0R/DP1/announce.html">5.0-DP1</a> + on 8 April 2002. This Developer Preview gives developers and + other interested parties a chance to help test some of the new + features to appear in 5.0-RELEASE. This distribution has known + bugs and areas of instability, and should only be used for + (non-production) testing and development.</p> + + <p>The next releases of FreeBSD will be 4.6-RELEASE (scheduled for + 1 June 2002) and 5.0-DP2 (scheduled for 25 June 2002). + Information on the release schedules and more can be found on + the team's new area on the FreeBSD Web site (see the URL + above).</p> + + <p>Finally, the team has gained two new members: Brian Somers and + Bruce A. Mah.</p> + + </body> + </project> + + <project> + <title>ppp RADIUS/MS-CHAP support</title> + + <contact> + <person> + <name> + <given>Brian</given> + + <common>Somers</common> + </name> + + <email>brian@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>libradius now supports RADIUS vendor attribute extensions and + user-ppp is now capable of doing MS-CHAP authentication via a RADIUS + server. A new net/freeradius port has been created for support of + MS-CHAP in a RADIUS server.</p> + + <p>MS-CHAPv2 support will be added soon.</p> + + <p>The work is sponsored by Monzoon.</p> + </body> + </project> + + <project> + <title>Improving FreeBSD Startup Scripts</title> + + <contact> + <person> + <name> + <given>Doug</given> + <common>Barton</common> + </name> + <email>dougb@FreeBSD.org</email> + </person> + </contact> + + <contact> + <person> + <name> + <given>Mike</given> + <common>Makonnen</common> + </name> + <email>makonnen@pacbell.net</email> + </person> + </contact> + + <contact> + <person> + <name> + <given>Gordon</given> + <common>Tetlow</common> + </name> + <email>gordont@gnf.org</email> + </person> + </contact> + + <links> + <url href="http://home.pacbell.net/makonnen/rcng.html" /> + <url href="http://groups.yahoo.com/group/FreeBSD-rc/" /> + <url href="http://www.mewburn.net/luke/bibliography.html" /> + <url href="http://www.netbsd.org/Documentation/rc/" /> + </links> + + <body> + <p>Mike Makonnen has done quite a bit of excellent work on porting the + scripts from FreeBSD into the NetBSD framework. The next step seems + to be to try to reduce the amount of diffs between our implementation + and the original set from NetBSD.</p> + </body> + </project> + + <project> + <title>SMPng</title> + + <contact> + <person> + <name> + <given>John</given> + + <common>Baldwin</common> + </name> + + <email>jhb@FreeBSD.org</email> + </person> + + <person> + <email>smp@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/smp/" /> + </links> + + <body> + <p>The SMPng project has been picking up steam in the last few + months thankfully. In February, Seigo Tanimura-san committed + the first round of process group and session locking. Alfred + Perlstein also added locking to most of the pipe + implementation. In March, Alfred fixed several problems with + the locking for select() and pushed down Giant some in several + system calls. Andrew Reiter added locking for kernel module + metadata, and Jeff Roberson wrote a new SMP-friendly slab + allocator to replace both the zone allocator and the in-kernel + malloc(). The use of the critical section API was cleaned up + to not be abused as replacements for disabling and enabling + interrupts. Also, Matt Dillon optimized the MD portion of the + critical section code on the i386 architecture. Several other + subsystems were also locked in April as well. See the SMPng + website and todo list for more details.</p> + + <p>Some of the current works in progress include locking for the + kernel linker by Andrew Reiter and light-weight interrupt + threads for the i386 by Bosko Milekic. Seigo Tanimura-san, + Alfred Perlstein, and Jeffrey Hsu are also working on locking + down various pieces of the networking stack. Alan Cox has + started working on fixing the existing locking in the VM + subsystem and moving bits of it out from under Giant. John + Baldwin has written an implementation of turnstiles as well as + adaptive mutexes in the jhb_lock Perforce branch. The + adaptive mutexes appear to be stable on i386, alpha, and + sparc64, but the turnstile code still contains several tricky + lock order reversals. John also plans to commit the + p_canfoo() API change to use td_ucred in the very near future + and then finish the task of making ktrace(4) use a worker + thread.</p> + </body> + </project> + + <project> + <title>New mount(2) API</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + <person> + <name> + <given>Maxime</given> + + <common>Henrion</common> + </name> + + <email>mux@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The patch for the new mount API has now been committed to the + tree. Several filesystems also have been converted to this + new mount API, namely procfs, linprocfs, fdescfs and devfs. + I'm working on converting more filesystems to nmount, and + actually already have UFS done. It has not been committed yet + to avoid conflicting with the UFS2 work, but it should hit the + tree soon. Manpages are still missing at the moment because + I had to modify the API slightly. I hope to have them done + soon now.</p> + </body> + </project> + + <project> + <title>FreeBSD Developer Summit</title> + + <contact> + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/events/2002/bsdcon-devsummit.html" /> + </links> + + <body> + <p>The second FreeBSD Developer Summit, held following the BSD + Conference in San Francisco in February, was a great success. Around + 40 developers attended in person, another five by phone, and many + others by webcast. During a marathon-esque eight hour session, a + variety of development topics were discussed, including adding + inheritance to the KOBJ system, ports to new architectures, + adaptations of the toolchain for new architectures, the GEOM + extensible storage device framework, upcoming changes to the network + stack, TrustedBSD features, KSE, SMPng, and the release engineering + schedule. This event was sponsored by DARPA and NAI Labs, with + webcasting provided by Joe Karthauser, bandwidth provided by Yahoo!. + Planning for future such events is now underway; a summary/transcript + of discussion may be found at the URL above.</p> + </body> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2002-05-2002-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2002-05-2002-06.xml new file mode 100644 index 0000000000..46ca339b4c --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2002-05-2002-06.xml @@ -0,0 +1,1450 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2002-05-2002-06.xml,v 1.7 2006/08/19 21:20:40 hrs Exp $ --> + +<report> + <date> + <month>May - June</month> + <year>2002</year> + </date> + + <section> + <title>Introduction</title> + + <p>May and June were remarkably busy months for the FreeBSD Project-- + FreeBSD developers met in Monterey, CA in June for FreeBSD + Developer Summit III to discuss strategy for the FreeBSD 5.0 + release later this year, for the USENIX Annual Technical + conference and for the FreeBSD BoF. Substantial technical progress + was made on FreeBSD 5.0, and FreeBSD 4.6-RELEASE was cut on the + RELENG_4 branch in June.</p> + <p>The remainder of the summer will continue to be busy. Final + components and features for 5.0-RELEASE will go into the tree, + and the development direction will change from new features + to stability, performance, and production-readiness. With + additional 5.0 development previews late in the summer, we + hope to broaden the tester base for the -CURRENT branch, + and start to get early adopters digging out any potential + problems in their test environments. I encourage both FreeBSD + Developers and FreeBSD Users to give 5.0-DP2 a spin (on a machine + without critical data!) and let us know how it goes. The more + testing that happens before the release, the less fixing we have + to do afterwards!</p> + <p>Robert Watson</p> + + </section> + +<project> + <title>TCP Hostcache</title> +<contact> + <person> + <name> + <given>Andre</given> + <common>Oppermann</common> + </name> + <email>oppermann@pipeline.ch</email> + </person> +</contact> +<body> + <p>The current cache for the TCP metrics is embedded directly into + the routing table route objects. This is highly inefficient as every + route has an empty 56 Byte large metrics structure in it. TCP is the + only consumer (except the MTU and Expiry field) of the structure. A + full view of the Internet routes (110k routes) has more than 6 Mbyte + of unused overhead due to it. The hit rate today is at only approx. + 10% in webserver applications. The TCP hostcache will move this entire + metrics structure from the routing table to the TCP stack. Every entry + is a host entry so a simple hash table is sufficient to keep the + entries. Its implementation is much like the TCP Syncache.</p> + <p>The hostcache is going through testing on our servers and will + be ready for committing in September. The results of the TCP metrics + measurement will be used to tune the cache.</p> +</body> +</project> + +<project> + <title>IP Routing Table Replacement</title> +<contact> + <person> + <name> + <given>Andre</given> + <common>Oppermann</common> + </name> + <email>oppermann@pipeline.ch</email> + </person> + <person> + <name> + <given>Claudio</given> + <common>Jeker</common> + </name> + <email>jeker@n-r-g.com</email> + </person> +</contact> +<body> + <p>The current Patricia Trie routing table in BSD UNIX is not very + efficient and wastes an enormous amount of space for every node (more + than 256 bytes) (A full Internet view of 110k routes takes 33 MByte + of KVM). Another problem are pointers from and to everywhere + in the routing table. This makes replacing the table very hard and + also significantly increases the table maintenance burden (for example + for some kinds of updates the entire PCB has to be searched linearly). + Also this is a heavy burden for SMP locking. The rewrite focuses on + untangling the pointer mess, making the routing table replaceable + and providing a more IP optimized table (5 MByte for 110k routes). + Other new options include policy routing and some structural alignments + in the network stack for clarity, simplicity and flexibility.</p> + <p>The rewritten IP routing table will be ready for committing in + October.</p> +</body> +</project> + +<project> + <title>TCP Metrics Measurement</title> +<contact> + <person> + <name> + <given>Andre</given> + <common>Oppermann</common> + </name> + <email>oppermann@pipeline.ch</email> + </person> + <person> + <name> + <given>Olivier</given> + <common>Mueller</common> + </name> + <email>omueller@8304.ch</email> + </person> +</contact> + <links> + <url href="http://www-t.zhwin.ch/pa02_2/diplomarbeiten2002.pdf"> + Diploma Thesis of ZHWIN students, look for Olivier Mueller and Daniel +Graf</url> + </links> +<body> + <p>These students will analyse the tcpdumps of five major Swiss + newspaper websites which give a representative overview of the + user structure in Switzerland. The nice thing about Switzerland + is that is has a very good mix of Modem/ISDN, leased line, Cable, + ADSL and 3G/GSM/GPRS users. Every Internet access technology is + represented. The goal is to analyze the behavior of all TCP + sessions to the monitored sites. Parameters to be analyzed include + TCP session RTT, RTT variance, in/outbound BDP, MSS changes, flow + control behavior, packet loss, packet retransmit and + timing of HTTP traffic to find optimal TCP parameter caching +method.</p> + <p>If you have any other metrics you think is useful please contact + me so I can put that into the job description for the Students. The + study will be made in September and October.</p> +</body> +</project> + +<project> + <title>NATD rewrite</title> +<contact> + <person> + <name> + <given>Claudio</given> + <common>Jeker</common> + </name> + <email>jeker@n-r-g.com</email> + </person> + <person> + <name> + <given>Andre</given> + <common>Oppermann</common> + </name> + <email>oppermann@pipeline.ch</email> + </person> +</contact> +<body> + <p>The current natd is pretty powerful in translating different kinds + of traffic but not very powerful in configuration. This project + rewrites natd and parts of libalias to give it a configuration set as + powerful and expressive as the ones in ipf (ipnat) and pf. In addition + it'll use kqueue and will support aliasing to multiple IP +addresses.</p> + <p>The rewritten natd will be ready for committing in early +September.</p> +</body> +</project> + +<project> + <title>FreeBSD/ia64</title> + + <contact> + <person> + <name> + <given>Peter</given> + <common>Wemm</common> + </name> + <email>peter@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~peter/ia64/">IA64 project + updates and information.</url> + </links> + + <body> + <p>IA64 has been progressing slowly. We have access to a prototype + 4-way Itaninum2 system from Intel and have managed to get it up and + running to the point of being able to access disk and network with + SMP enabled. We have a big problem with ACPI2.0 and PCI routing + table entries behind pci-pci bridges with no short-term solution + in sight. Various WIP items have been committed to CVS, namely + more complete support for executing 32bit i386 binaries as well + as Marcel Moolenaar's prototype EFI GPT tools.</p> + </body> +</project> + +<project> + <title>Libh Status Report</title> + + <contact> + <person> + <name> + <given>Antoine</given> + + <common>Beaupre</common> + </name> + + <email>antoine@usw4.FreeBSD.org</email> + </person> + </contact> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Langer</common> + </name> + + <email>alex@FreeBSD.org</email> + </person> + </contact> + + <contact> + <person> + <name> + <given>Nathan</given> + + <common>Ahlstrom</common> + </name> + + <email>nra@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/libh.html" /> + <url href="http://usw4.FreeBSD.org/~libh/">libh + new development web page.</url> + <url href="http://usw4.FreeBSD.org/~libh/screenshots"> + First snapshots of the diskeditor in action</url> + </links> + + <body> + <p>Max has been busy cleaning up the user interface dark side, and has + come up with a plan to improve the build system (using an automated + Makefile dependency generator); the UI design and the TCL glue magic + (using Swig). A development page has been created on usw4, publishing + a lot of information about the current project status, a Changelog, + screenshots, documentation, etc. A new listbox widget has been + implemented, making diskeditor look nicer and more usable. The package + system backend is being inspected and redesigned to conform to a standard + that is itself being re-thought. Indeed, the old sysinstall2.txt text has + been SGML-ized and enhanced and now provides a good (although rough) overview + of libh package system. This allowed the document to be enhanced with diagrams + of how different procedures work. We are therefore getting closer to a + real pkgAPI specification document. The package management tools have been + slightly enhanced and should be a bit more usable, and we started committing + regression test suites in the tree, mostly to test and maintain pkg API + conformance.</p> + + <p>So work continues on libh. I plan to take a look at the rhtvision port + to see if it would be better to use it for the tvision backend. I'll keep + on working on the package system to make it really trustworthy, while Max + is continuing his great work on the UI subsystem. I hope to make a new libh + alpha release soon. Note that from now on, libh progress will be published + on the development page.</p> + </body> +</project> + +<project> + <title>OLDCARD</title> + + <contact> + <person> + <name> + <given>Warner</given> + <common>Losh</common> + </name> + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>A major power bug was fixed in oldcard. This caused many +problems for people using PCI interrupts having their machines hang on +boot. This fix has made it into 4.6.1.</p> + + <p>Cardbus power is now used on all cardbus bridges that support +it. This means that we now support 3.3V cards on all cardbus +bridges. Before, we only supported them on some of the bridges +because every bridge uses different 3.3V power control when programmed +through the ExCA registers. Now that we're going through the CardBus +bridge's power control register, 3.3V cards work. In fact, for +CardBus bridges, the so called X.XV and Y.YV cards will work in those +bridges that support them. However, X.XV and Y.YV haven't been +defined yet, and no bridges support them (but the bridge interface +define it). Obviously this latter part is untested.</p> + + <p>CL-PD6722 support has been augmented slightly. Now it is +possible to instruct the driver which type of 3.3V card detection +strategy to use. There are three choices: none, do it like the +CL-PD6710 does it and do it like the CL-PD6722 does it.</p> + + <p>Preliminary support for the CL-PD6729 on a PCI card using PCI +interrupts has been committed. However, it fails for at least one of +the cards like this the author has.</p> + + <p>Client drivers can now ask for the manufacturer and model +number of the card without parsing the CIS directly.</p> + + <p>Except for fixing bugs and updating pccard.conf entries, no +additional work is planned on the OLDCARD system.</p> + </body> +</project> + +<project> + <title>NEWCARD</title> + + <contact> + <person> + <name> + <given>Warner</given> + <common>Losh</common> + </name> + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>A devd daemon, to replace pccardd and usbd, has been designed. +A few minor bugs have been fixed in NEWCARD. NEWCARD is now the +default in -current. There is an experimental pci/cardbus bus code +merge available as a branch which will be merged into current as soon +as it is stable.</p> + +<p>Status: The ed driver, for non-ne2000 clones, is broken and won't +probe. The ata driver won't attach. The sio driver hangs on the +first character. The wi driver is known to work well. Cardbus cards +are generally known to work well, except for some de based cards, +which unfortunately includes the popular Xircom cards. Many systems +fail to work because acpi fails to route interrupts correctly for +non-root pci bridges.</p> + </body> +</project> + +<project> + <title>FreeBSD GNOME Project</title> + + <contact> + <person> + <name> + <given>Joe</given> + + <common>Marcus</common> + </name> + + <email>marcus@FreeBSD.org</email> + </person> + <person> + <name> + <given>Maxim</given> + + <common>Sobolev</common> + </name> + + <email>sobomax@FreeBSD.org</email> + </person> + + </contact> + + <links> + <!-- A hypertext link with a description... --> + <url href="http://www.FreeBSD.org/gnome/">FreeBSD GNOME Project + Homepage.</url> + + </links> + + <body> + <p>Things are going well with the FreeBSD GNOME Project. We have just + finished porting the GNOME 2.0 Final development platform and desktop + to FreeBSD! We hope to be able to make GNOME 2.0 the default for + 5.0-DP2 and 4.7-RELEASE. In the meantime, we're working to port more + GNOME 2.0 applications.</p> + + <p>In order to allow GNOME 1.4.1 applications to work with GNOME 2.0, + we are revamping the GNOME porting infrastructure. GNOME 1.4.1 based + ports are being converted to use the new GNOMENG porting structure. + The specifics of this new system will be written up in the GNOME + porting guide found on the FreeBSD GNOME project homepage.</p> + + </body> +</project> + +<project> + <title>FreeBSD Java Project</title> + + <contact> + <person> + <name> + <given>Greg</given> + <common>Lewis</common> + </name> + + <email>glewis@FreeBSD.org</email> + </person> + </contact> + + <links> + <!-- A hypertext link with a description... --> + <url href="http://www.FreeBSD.org/java/">FreeBSD Java Project</url> + </links> + + <body> + <p> + The BSD Java Porting Team has been making slow but steady progress + on a number of fronts in the last few months. Unfortunately most + of this has occurred behind the scenes, meaning this is a good + opportunity to bring the community up to date. + <ul> + <li>Bill Huey has gotten the Java HotSpot Virtual Machine up and + running on FreeBSD! While dubbing the code of alpha quality, + Bill has been working hard and is able to run major examples + such as the Java 2D demo. This code has hit the repository + and will soon be available.</li> + <li>The port of the 1.4 J2SDK has commenced. The first commits + have gone into the tree, although a first patchset is a + way off yet.</li> + <li>Progress continues with the TCK compliance testing. The + current status has the JDK down to 19 compiler failures + and 183 runtime failures. As we edge closer to compliance + its hoped that example code will be released to allow the + community to pull together through the final few bugs.</li> + <li>A new patchset for JDK 1.3.1 is imminent. This patchset + will include HotSpot for the first time.</li> + </ul> + </p> + </body> +</project> +<project> + <title>KAME Project</title> + + <contact> + <person> + <name> + <given>SUZUKI</given> + + <common>Shinsuke</common> + </name> + + <email>core@kame.net</email> + </person> + </contact> + + <links> + <url href="http://www.kame.net/">KAME Project Web Page</url> + <url href="http://www.interop.jp/eng/exhibition/ipv6_showcase.html">IPv6 Showcase at Network+Interop2002</url> + <url href="http://www.interop.jp/jp/exhibition/ipv6_showcase.html">IPv6 Showcase at Network+Interop2002 (detailed, but in Japanase)</url> + <url href="http://www.sfc.wide.ad.jp/~say/n+i/">Pictures of IPv6 Showcase</url> + </links> + + <body> + <p>I'm afraid KAME Project does not work actively with regard to FreeBSD in these two month, since + we are too busy with the demonstration of our IPv6 implementation at Networld+Interop 2002 Tokyo. + (Thanks to a great effort, the demonstration was quite successful) </p> + + <p>We are aware of netinet6-related bug reports regarding socket handling, fine-grain locking, ip6fw etc. + Regret to say, we could not answer them right now due to the above situation, however we'll discus + these issues internally and determine what to do. </p> + </body> +</project> + +<project> + <title>BSDCon 2003</title> + + <contact> + <person> + <name> + <given>Gregory</given> + <common>Shapiro</common> + </name> + <email>gshapiro@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.usenix.org/events/bsdcon03/cfp/">Call for papers</url> + </links> + +<body> +<p>The BSDCon 2003 Program Committee invites you to contribute original +and innovative papers on topics related to BSD-derived systems and +the Open Source world. Topics of interest include but are not limited +to: +</p> +<ul> + <li> Embedded BSD application development and deployment</li> + <li> Real world experiences using BSD systems</li> + <li> Using BSD in a mixed OS environment</li> + <li> Comparison with non-BSD operating systems; technical, + practical, licensing (GPL vs. BSD)</li> + <li> Tracking open source development on non-BSD systems</li> + <li> BSD on the desktop</li> + <li> I/O subsystem and device driver development</li> + <li> SMP and kernel threads</li> + <li> Kernel enhancements</li> + <li> Internet and networking services</li> + <li> Security</li> + <li> Performance analysis and tuning</li> + <li> System administration</li> + <li> Future of BSD</li> +</ul> +<p> Submissions in the form of extended abstracts are due by April 1, 2003. +Be sure to review the extended abstract expectations before submitting. +Selection will be based on the quality of the written submission and +whether the work is of interest to the community. </p> +<p> We look forward to receiving your submissions! </p> +</body> +</project> + +<project> + + <title>FreeBSD Release Engineering</title> + + <contact> + <person> + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng" /> + </links> + + <body> + + <p>Over the past few months the FreeBSD Release Engineering Team + oversaw a release process that culminated in the release of + FreeBSD 4.6 for the i386 and Alpha architectures on June 15. + The RE team is currently working concurrently on FreeBSD 4.6.1 + and 5.0 DP2. 4.6.1 is a minor point release with an updated SSH + and BIND, fixes for some of the reported ata(4) problems, and + assorted security enhancements that will be detailed in the + release notes. The release engineering activities for 4.6.1 are + taking place on the RELENG_4_6 branch in CVS, while the work on + 5.0 DP2 is taking place in Perforce so as not to disturb ongoing + -CURRENT development. We are still committed to FreeBSD 5.0 on + or around November 15, 2002. For more information about + upcoming release schedules, please see our website above. The + RE team would like to thank Sentex Communications for providing + the release builders with access to a fast i386 build machine. + Compaq also donated a couple of fast Alpha build machines to the + project.</p> + + </body> +</project> + +<project> + <title>Fast IPSEC Status</title> +<contact> +<person> +<name> + <given>Sam</given> + <common>Leffler</common> + </name> + <email>sam@FreeBSD.org</email> + </person> + </contact> +<body> + <p>The main goal of this project is to modify the IPSEC protocols to use +the kernel-level crypto subsystem imported from OpenBSD (see elsewhere). A +secondary goal is to do general performance tuning of the IPSEC +protocols.</p> + <p>Basic functionality is operational for IPv4 protocols. IPv6 support is +coded but not yet tested. Hardware assisted cryptographic operations are +working with good performance improvements. Operation with software-based +cryptographic calculations appears to be at least as good as the existing +implementation. Numerous opportunities for performance improvements have +been identified.</p> + <p>This work is currently being done in the -stable tree. A port to +the -current tree is about to start.</p> + </body> +</project> + +<project> + <title>FreeBSD C99 & POSIX Conformance Project</title> + + <contact> + <person> + <name> + <given>Mike</given> + + <common>Barcroft</common> + </name> + + <email>mike@FreeBSD.org</email> + </person> + <person> + <name> + <common>FreeBSD-Standards Mailing List</common> + </name> + + <email>standards@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/c99/" /> + </links> + + <body> + <p>Since the last status report, the following utilities have been + brought up to conformance (at least to some degree) with POSIX.1-2001, + they include: asa(1), cd(1), compress(1), ctags(1), ls(1), newgrp(1), + nice(1), od(1), pathchk(1), renice(1), tabs(1), tr(1), uniq(1), wc(1), + and who(1). In addition, development is taking place on bringing the + BSD SCCS suite up to date with newer standards.</p> + + <p>On the API front, printf(9) has been given support for the `j' and + 'n' flags, waitpid(2) now supports the WCONTINUED option, and an + implementation of fstatvfs() and statvfs() has been committed. An + implementation of utmpx is in progress, which has an aim to address + some of the major problems with the current utmp. Several headers + have been brought up to conformance with POSIX.1-2001, they include: + <netinet/in.h>, <pwd.h>, <sys/statvfs.h>, and + <sys/wait.h>.</p> + </body> +</project> + +<project> + <title>Hardware Crypto Support Status</title> +<contact> +<person> +<name> + <given>Sam</given> + <common>Leffler</common> + </name> + <email>sam@FreeBSD.org</email> + </person> + </contact> +<body> + <p>The goal of this project is to import the OpenBSD kernel-level crypto +subsystem. This facility provides kernel- and user-level access to hardware +crypto devices for the calculation of cryptographic hashes, ciphers, and +public key operations. The main clients of this facility are the kernel RNG +(/dev/random), network protocols (e.g. IPSEC), and OpenSSL (through the +/dev/crypto device).</p> + <p>The software has been available as a patch against the -stable tree for +about six months. The core crypto support is tested, including device +drivers for the Hifn 7951, and Broadcom 5805, 5820, and 5821 parts. Recent +work has concentrated on fixing device driver bugs, fixing support for Hifn +7811 parts, adding support for public key operations, and adding +flow-control between the crypto layer and device drivers. Future work +includes porting this facility to the -current tree.</p> + </body> +</project> + +<project> + <title>KSE (Kernel schedulable Entity) thread support </title> + + <contact> + <person> + <name> + <given>Julian</given> + + <common>Elischer</common> + </name> + + <email>julian@FreeBSD.org</email> + </person> + <person> + <name> + <given>Dan</given> + + <common>Eischen</common> + </name> + + <email>deischen@FreeBSD.org</email> + </person> + </contact> + + <links> + <!-- A hypertext link with a description... --> + <url href="http://www.freebsd.ord/~julian/">Some info + here.</url> + + </links> + + <body> + <p> + The project took a major step at the beginning of July when + Milestone-III was committed. Milestone-III allows a simple test + program (available at /usr/src/tools/KSE/ksetest/) + to run multiple threads, using kernel support. It does not yet + allow the ability to allow these threads to run on different CPUs + simultaneously. Milestone IV will be to allow this, however + Milestone-III should allow Dan to start (with any interested + parties) to start prototyping the userland part of the + system. Milestone-III is only currently usable on x86, and + does not include some of the + requirements for full thread-control, suspension etc. that + will be required later. </p> + <p> + Before M-IV is started some small tweaking is likely + in the central sources on M-III as we discover issues + as we try to get the userland jumpstarted. These will have no + effect on non-KSE processes, (i.e. all of them :-) and + should not be an issue for other developers. </p> + <p> + A tex/fig->html guru is needed to help maintain the + KSE web page (not mentioned above as it is broken). + </p> + </body> +</project> + + + <project> + <title>SMPng Status Report</title> + + <contact> + <person> + <name> + <given>John</given> + + <common>Baldwin</common> + </name> + + <email>jhb@FreeBSD.org</email> + </person> + + <person> + <email>smp@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/smp/" /> + </links> + + <body> + <p>The SMPng project has continued to make steady progress in + the past two months. Jeff Roberson completed the switch over + to UMA for the general kernel malloc() and free() pushing down + Giant appropriately so that callers of malloc() and free() are + no longer required to hold Giant. Alan Cox continues to clean + up the locking in the VM system pushing down Giant in several + of the VM related system calls. Jeffrey Hsu committed locking + for TCP/IP protocol control blocks in the network stack. John + Baldwin committed the changes to the p_canfoo() API to use + thread credentials for subject threads and added appropriate + locking for the targer process credentials. Support for + adaptive mutexes on SMP systems as well as the new IA32 PAUSE + instruction were also committed in May. The kernel tracing + facility KTRACE also received an overhaul such that the + majority of its work was pushed out into a worker thread + allowing trace points to no longer require Giant. Andrew + Reiter has also been pushing down Giant in several system + calls.</p> + + <p>Bosko continues to work on light-weight interrupt threads + for i386. Most of the bugs in the turnstile code have been + found and fixed; however, the turnstile and preemption + patches have temporarily been put on hold so that more + emphasis can be placed on fixing bugs and making -current + more stable in preparation for 5.0 release in November. + Alan Cox and Andrew Reiter are continuing the work mentioned + above. Jeff Roberson is also working on fixing the current + vnode locking in VFS. Peter Wemm has also started to tackle + TLB issues on SMP in the i386 pmap again as well.</p> + </body> + </project> + +<project> + <title>FreeBSD Security Officer Team</title> + + <contact> + <person> + <name> + <given>Jacques</given> + + <common>Vidrine</common> + </name> + + <email>nectar@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/security"/> + </links> + + <body> + + <p>After an outstanding job serving the project as Security Officer + for over a year, Kris stepped down in January in order to focus more + of his time pursuing his PhD. I offered to attempt to fill the vacant + role.</p> + + <p>This is the first report by the SO Team. Notable events since + the beginning of 2002 follow.</p> + + <p>28 FreeBSD Security Advisories have been issued, 16 of which + were regarding the base system. Of those sixteen, 8 affected only + FreeBSD.</p> + + <p>FreeBSD Security Notices were introduced, and four have been + issued so far. The Security Notices cover issues that are not + regarded as critical enough to warrant a Security Advisory. So far + only Ports Collection issues (i.e. vulnerabilities in optional 3rd + party packages) have been reported in Security Notices. The first + four Security Notices covered 53 individual issues.</p> + + <p>Issues reported to the SO team are now being tracked using a + RequestTracker ticket database.</p> + + <p>The SO team has undergone membership changes, as well as some + changes in internal organization. The membership and organization + has also been made publicly visible on the FreeBSD Security Officer + web page.</p> + + </body> +</project> + +<project> + <title>jpman project</title> + + <contact> + <person> + <name> + <given>Kazuo</given> + <common>Horikawa</common> + </name> + + <email>horikawa@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.jp.FreeBSD.org/man-jp/">jpman project</url> + </links> + + <body> + <p>For 4.6-RELEASE, we announced the package ja-man-doc-4.6.tgz + which is in sync with 4.6-RELEASE base system manual pages + except for perl5 pages (jpman project do not maintain them). + Continuing section 3 updating has 88% finished.</p> + </body> +</project> + +<project> + <title>FreeBSD/KGI Status Report</title> + + <contact> + <person> + <name> + <given>Nicholas</given> + + <common>Souchu</common> + </name> + + <email>nsouch@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~nsouch/ggiport.html"> Project URL</url> + </links> + + <body> + <p>Progression is slow, but the effort is maintained. Most of fb over KGI has been + written in parallel with a KGI display driver based on fb. + DDC/DDC2 is being discussed for Plug & Play monitor support. KGI aims at providing + a generic OS independent interface which would take advantage of FreeBSD I2C (iic(4)) + infrastructure. + </p> + + </body> +</project> + +<project> + <title>UFS2 - Extended attribute and large size support for UFS</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + <person> + <name> + <given>Kirk</given> + <common>Mckusick</common> + </name> + + <email>mckusick@FreeBSD.org</email> + </person> + </contact> + + <body> + <p> + UFS2 is an extension to the well-known UFS filesystem which + using a new inode format adds support for "64bit everywhere" + and later for extended attribute support, in addition to the + current UFS features: soft-updates and snapshots. + </p> + <p> + The basic UFS2 code has been committed and work on the extended + attribute interface and vnode operations will continue. + </p> + + </body> +</project> + +<project> + <title>GEOM - generalized block storage manipulation</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <links> + <!-- A hypertext link with a description... --> + <url href="http://www.FreeBSD.org/~phk/Geom/">Old concept paper here.</url> + + </links> + + <body> + <p> + The GEOM code has gotten so far that it beats our current code + in some areas while still lacking in others. The goal is for + GEOM to be the default in 5.0-RELEASE. + </p> + <p> + Currently work on a cryptographic module which should be able + to protect a diskpartition from practically any sort of attack + is progressing. + </p> + + </body> +</project> + +<project> + <title>OpenOffice.org for FreeBSD</title> + + <contact> + <person> + <name> + <given>Martin</given> + <common>Blapp</common> + </name> + + <email>mbr@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://projects.imp.ch/openoffice">OpenOffice.org FreeBSD port Homepage</url> + </links> + + <body> + <p>The port of openoffice 1.0 has been finished. Most showstopper issues + with rtld, libc and our toolchain have been fixed. There is one remaining + deadlock in the web-browser code of OO.org. If anybody like to help + us with fixing this bug (may be another libc_r bug as it looks like) + just mail me! Unfortunately gcc2 support got broken again with the import + of gcc2.95.4 in STABLE. Exceptions support seems to be broken again; we get + internal compiler errors with c++ exceptions code. You'll have to use gcc31 + again.</p> + + <p>Since our package cluster is outdated and can not build OO.org packages + anytime soon, I did my own little package cluster and can now offer + packages for 4.6R for 16 different languages. They can be found on the + project homepage.</p> + + <p>Porting of OpenOffice1.0.1 is on it's way. A beta port and a package have + been made available on the project homepage.</p> + + </body> +</project> + +<project> + <title>Lightweight Interrupt Scheduling</title> + + <contact> + <person> + <name> + <given>Bosko</given> + <common>Milekic</common> + </name> + <email>bmilekic@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://people.FreeBSD.org/~peter/p4db/chb.cgi?FSPC=//depot/projects/interrupt/sys/..."> + The interrupt p4 branch</url> + </links> + + <body> + <p>The lightweight interrupt scheduling code makes scheduling an + interrupt on i386 without having to grab the sched_lock possible, + and also avoids a full-blown context switch.</p> + + <p>Currently, the code in the p4 branch works, although needs a + little bit of cleanup and, most importantly, requires a merge to + post-KSE III. Now that stuff seems to have stabilized a bit, I'm + waiting to get a little time (and nerve) to do the merge. Also, + looking forward for some KSE interface that will allow for "KSE + borrowing," which would make this cleaner with regards to KSE and + lightweight interrupts. This is a 5.0 feature.</p> + </body> +</project> + +<project> + <title>TIRPC port for BSD sockets</title> + + <contact> + <person> + <name> + <given>Martin</given> + <common>Blapp</common> + </name> + + <email>mbr@FreeBSD.org</email> + </person> + </contact> + + <links> + <!-- A hypertext link with a description... --> + <url href="http://www.attic.ch/tirpc">TIRPC for FreeBSD Homepage</url> + + <!-- And/or one without. --> + <url href="http://www.attic.ch/tirpc" /> + </links> + + <body> + <p> + A lot of remaining PR's and Bugs have been closed. All relevant rpc + concerning patches have been committed. Thanks go to Alfred and Ian Dowese. + </p> + <p>Jean-Luc Richier <Jean-Luc.Richier@imag.fr> has made a patch + available which adds IPv6 support to all remaining rpc servers. + See ftp://ftp.imag.fr/pub/ipv6/NFS/NFS_IPV6_FreeBSD5.0.gz and + ftp://ftp.imag.fr/pub/ipv6/NFS/0README_NFS_IPV6_FreeBSD5.0 + We will check his code and add it to CURRENT ASAP.</p> + + <p>A first commit part from TIRPC99 has been done. I'm working now + on porting the remaining parts so when FreeBSD 5.0 gets released, + it will be TIRPC99 based. This will happen together with the NetBSD + project, as they use the same codebase as we do. + </p> + + </body> +</project> + +<project> + <title>mb_alloc updates</title> + + <contact> + <person> + <name> + <given>Bosko</given> + <common>Milekic</common> + </name> + <email>bmilekic@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~bmilekic/code/mb_alloc/">Some + [Old] mb_alloc stuff</url> + </links> + + <body> + <p>mb_alloc is getting some updates and a couple of optimizations. + A new allocator interface routine should already be committed by + the time this report is "published:" m_getcl() allocates an mbuf + and a cluster in one shot. This is the result of months + (literally) of requests from Alfred and, recently, Luigi - who, + coincidentally, is the author of the same [upcoming] routine in -STABLE.</p> + + <p>Other than that, mb_alloc is being shown how to perform + multi-mbuf or cluster allocations without dropping the cache lock in + between (m_getcl() and m_getm() will use this). Finally, work is + being done to optimize ext_buf ref. count allocations and to provide + support for jumbo (> 9K) clusters.</p> + </body> +</project> + +<project> + <title>Improving FreeBSD Startup Scripts</title> + + <contact> + <person> + <name> + <given>Doug</given> + <common>Barton</common> + </name> + <email>DougB@FreeBSD.org</email> + </person> + </contact> + <contact> + <person> + <name> + <given>Mike</given> + <common>Makonnen</common> + </name> + <email>makonnen@pacbell.net</email> + </person> + </contact> + <contact> + <person> + <name> + <given>Gordon</given> + <common>Tetlow</common> + </name> + <email>gordont@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://groups.yahoo.com/group/FreeBSD-rc/links/"> + The Yahoo! group site for discussion of this project + </url> + </links> + + <body> + <p>We are making excellent progress. There is a fully functioning + implementation imported to -current now. We need as many people as + possible to rc_ng equal to YES in /etc/rc.conf.</p> + <p>The next step is to set the default to YES, which we plan to do + before DP 2.</p> + </body> +</project> + +<project> + <title>ipfw2</title> + + <contact> + <person> + <name> + <given>Luigi</given> + + <common>Rizzo</common> + </name> + + <email>luigi@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.iet.unipi.it/~luigi/" /> + </links> + + <body> + <p>In summer 2002 the native FreeBSD firewall has been completely + rewritten in a form that uses BPF-like instructions + to perform packet matching in a more effective way. The external + user interface is completely backward compatible, though you can + make use of some newer + match patterns (e.g. to handle sparse sets of IP addresses) which + can dramatically simplify the writing of ruleset (and speed up + their processing). + The new firewall, called ipfw2, is much faster and easier to + extend than the old one. It has been already included in + FreeBSD-CURRENT, and patches for FreeBSD-STABLE are available + from the author. + </p> + + </body> +</project> + +<project> + <title>jp.FreeBSD.org daily SNAPSHOTs project</title> + <contact> + <person> + <name> + <given>Makoto</given> + <common>Matsushita</common> + </name> + <email>matusita@jp.FreeBSD.org</email> + </person> + </contact> + <links> + <url href="http://snapshots.jp.FreeBSD.org/">Project Webpage</url> + <url href="http://www.jp.FreeBSD.org/snapshots/">Project Webpage (in Japanese +)</url> + <url href="http://snapshots.jp.FreeBSd.org:8021">SNAPSHOTs anonftp area on the web</url> + <url href="ftp://daemon.jp.FreeBSD.org/pub/FreeBSD/releases/i386/">Release branch snapshots for FreeBSD/i386</url> + </links> + <body> + <p> + I spent busy days in last two months, many new topics are emerged + from the project. We now support FreeBSD/alpha 5-current + distribution by cross-compiling on the x86 PC. Anonymous ftp area + is now exported to the yet another web server. Our release branch + snapshots are relocated to daemon.jp.FreeBSD.org because of our + CPU/network bandwidth problem. + </p> + <p> + I'm seriously considering to solve the lack of CPU and network + resources for the project's future evolution. Maybe the bandwidth + problem can be resolved (several bandwidth offers have been received!), + but there is no answer about CPU problems (I have a plan to upgrade + our PCs from P3-500MHz to P4 or better). + If you have interested in donating PCs to the project, please email me + for more detail. + </p> + </body> +</project> + +<project> + <title>Userland Regression Tests</title> + + <contact> + <person> + <name> + <given>Juli</given> + + <common>Mallett</common> + </name> + + <email>jmallett@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Regression tests for many bugs fixed in text manipulation utilities + have been added, as well as tests for various non-standard versions + of functionality that FreeBSD users should expect. A library of + m4 macros for creating the tests themselves has been added.</p> + </body> +</project> + +<project> + <title>Single UNIX Specification conformant SCCS suite</title> + + <contact> + <person> + <name> + <given>Juli</given> + + <common>Mallett</common> + </name> + + <email>jmallett@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The final version of SCCS distributed by CSRG has been integrated + into the projects CVS repository, and worked on extensively to the + point where essential functionality works on FreeBSD (and other + operating systems). Some standards-related functionality has been + implemented</p> + </body> +</project> + +<project> + <title>Zero Copy Sockets status report</title> + + <contact> + <person> + <name> + <given>Ken</given> + + <common>Merry</common> + </name> + + <email>ken@FreeBSD.org</email> + </person> + </contact> + + <links> + <!-- A hypertext link with a description... --> + <url href="http://people.FreeBSD.org/~ken/zero_copy/">Zero copy patches + and information. </url> + </links> + + <body> + <p> The zero copy sockets code was committed to FreeBSD-current on June + 25th, 2002. I'm not planning on doing any more patches, although + I will leave the web page up as it contains useful information. </p> + <p> + Many thanks to the folks who have tested and reviewed the code over + the years. </p> + </body> +</project> + +<project> + <title>locking up pcb's in the networking stack</title> + + <contact> + <person> + <name> + <given>Jeffrey</given> + + <common>Hsu</common> + </name> + + <email>hsu@FreeBSD.org</email> + </person> + </contact> + + <links> + <!-- And/or one without. --> + <url href="http://www.FreeBSD.org/smp" /> + </links> + + <body> + <p>Jennifer Yang's patch was committed June 10 for the BSD Summit. + After a few bugs which were reported initially and + fixed that same week, networking in -current + has been stable, including the parts that were not locked up, + like IPv6. Work is on-going to lock up the rest of the stack.</p> + </body> +</project> + +<project> + <title>Bluetooth stack for FreeBSD (Netgraph implementation)</title> + + <contact> + <person> + <name> + <given>Maksim</given> + <common>Yevmenkin</common> + </name> + + <email>m_evmenkin@yahoo.com</email> + </person> + </contact> + + <links> + </links> + + <body> + + <p> +Not much to report. Another engineering snapshot is available +for download at +http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020709.tar.gz. +If anyone has Bluetooth hardware and spare time please join in and help +me +with testing. + </p> + + <p> +This snapshot includes basic support for USB devices and manual pages. +The HCI layer now has support for multiple control hooks. All HCI +transport +drivers (H4, BT3C and UBT) has been changed to provide consistent +interface +to the rest of the world. Some userspace utilities have been changed as +well. + </p> + + <p> +Still no support for RFCOMM (Serial port emulation over Bluetooth link) +and +SDP (Service Discovery Protocol). Several design flaws have been +discovered +and it might take some time to resolve these issues. + </p> + </body> +</project> + + <project> + <title>TrustedBSD MAC</title> + + <contact> + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + <person> + <name> + <given>TrustedBSD Discussion Mailing List</given> + </name> + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/">TrustedBSD main web page</url> + </links> + + <body> + <p>The TrustedBSD Project has been busy in May and June, + developing new features, presenting on the technology at + the FreeBSD Developer Summit, and improving the readiness + of the MAC branch for integration into the main FreeBSD + tree. The migration to dynamic labeling in the TrustedBSD + MAC framework is complete, with all policies now making + use of dynamic labels in the kernel. This permits policies + to associate arbitrary additional security data with a + variety of kernel objects at run-time. Implement mac_test, + a sanity checking module. Pass labels as well as objects + to each policy entry point to reduce knowledge of label + storage in the policies. Implement mac_partition, a simple + jail-like policy. Adapt the MAC framework for process locking. + </p> + + <p> + Improve support for sockets: provide a peerlabel maintained for + stream sockets (unix domain, tcp), entry points for accept, + bind, connect, listen. Improve support for IPv4 and IPv6 by + labeling IP fragment reassembly queues, and providing entry + points to instrument fragment matching, update, reassembly, etc. + Locally disable KAME if_loop mbuf contiguity hack because it + drops labels on mbufs: we need to make sure the label is + propagated. Label pipes and provide access control for them. + Improve vnode labeling: now handle labeling for devfs, pseudofs, + procfs. Fix interactions between MAC and ACLs relating to the + new VAPPEND flag.</p> + + <p> SELinux policy tools now ported to SEBSD. SEBSD now labels + subjects and file system objects. + Provide ugidfw, a tool for managing rules for the mac_bsdextended + policy.</p> + + <p> Massive diff reduction. KSEIII merged. Main tree integration + will begin shortly.</p> + + <p>Updated prototype code may be retrieved from the TrustedBSD + CVS trees on cvsup10.FreeBSD.org.</p> + </body> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2002-07-2002-08.xml b/en_US.ISO8859-1/htdocs/news/status/report-2002-07-2002-08.xml new file mode 100644 index 0000000000..3221aab857 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2002-07-2002-08.xml @@ -0,0 +1,1061 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2002-07-2002-08.xml,v 1.6 2006/08/19 21:20:40 hrs Exp $ --> + +<report> + <date> + <month>July - August</month> + <year>2002</year> + </date> + + <section> + <title>Introduction</title> + + <p>Throughout July and August, the FreeBSD Project has been working on + pulling together the last few major pieces of new functionality for + FreeBSD 5.0-RELEASE. At this point, the release appears to be on track + for late November or early December. Work on fine-grained locking + continues, especially in the VFS, as with improved support for threading + through the KSE work; features such as GEOM, UFS2, and TrustedBSD MAC are + maturing, and the new ia64 and sparc64 hardware ports are approaching + production quality. In the next two months, we have a lot to look forward + to: additional 5.0 developer preview snapshots, additional locking and + threading improvements, and many cleanups on the new supported + architectures. Firewire support has been imported into the main tree, and + substantial cleanup of the ACPI/legacy PCI code is also in the works. + Also, expect the import of new IPsec hardware acceleration support in the + near future.</p> + <p>When new developer previews are posted, please give them a try! While we + know that 5.0-RELEASE will be for "early adopters", the more testing we + get out of the way now, the less we have to tidy up later. The new + features are extremely exciting, and understanding when and how to deploy + them properly will be important. In the next two months, among other + things, the release engineering team will post updated release schedules, + as well as guidance for FreeBSD consumers as to how to decide what + releases of FreeBSD will be right for them. Keep an eye out for this, and + provide us with feedback.</p> + <p>Also, for those of you in Europe -- we look forward to seeing you at + BSDCon Europe in a couple of months!</p> + <p>Scott Long, Robert Watson</p> + + </section> + +<project> + <title>BSDCon 2003</title> + + <contact> + <person> + <name> + <given>Gregory</given> + <common>Shapiro</common> + </name> + <email>gshapiro@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.usenix.org/events/bsdcon03/cfp/">BSDCon 2003 Call For Papers</url> + </links> + + <body> + + <p>The BSDCon 2003 Program Committee invites you to contribute + original and innovative papers on topics related to BSD-derived + systems and the Open Source world. Topics of interest include + but are not limited to:</p> + + <ul> + <li>Embedded BSD application development and deployment</li> + <li>Real world experiences using BSD systems</li> + <li>Using BSD in a mixed OS environment</li> + <li>Comparison with non-BSD operating systems; technical, + practical, licensing (GPL vs. BSD)</li> + <li>Tracking open source development on non-BSD systems</li> + <li>BSD on the desktop</li> + <li>I/O subsystem and device driver development</li> + <li>SMP and kernel threads</li> + <li>Kernel enhancements</li> + <li>Internet and networking services</li> + <li>Security</li> + <li>Performance analysis and tuning</li> + <li>System administration</li> + <li>Future of BSD</li> + </ul> + + <p>Submissions in the form of extended abstracts are due by + April 1, 2003. Be sure to review the extended abstract + expectations before submitting. Selection will be based on the + quality of the written submission and whether the work is of + interest to the community.</p> + + <p>We look forward to receiving your submissions!</p> + + </body> +</project> + +<project> + <title>Network interface cloning and modularity</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Cloning support for ppp(4) and disc(4) interfaces has been + committed. A man page for disc has been created and the disc + devices now appear as disc# instead of ds#. Some work is still + needed on pppd to make it understand cloning though it should work + as long as the devices are created beforehand.</p> + <p>On the API front, management of mandatory interfaces (i.e. lo0) + is handled by the generic cloning code so if_clone_destroy has the + same API as NetBSD again and <if>_modevent doesn't need to create + the necessary devices manually.</p> + <p>At this point, all pseudo interfaces have been converted to the + cloning API or already did their own cloning (sl(4) for example + uses it's own mechanism). Some devices such as tun(4) and + tap/vmware should probably be converted to use the cloning API + instead of their current ad-hoc, devfs based cloning system. This + would be a good junior kernel hacker task. Also, the handbook and + FAQ could use some general cloning documentation prior to 5.0 + release.</p> + </body> +</project> + +<project> + <title>jpman project</title> + + <contact> + <person> + <name> + <given>Kazuo</given> + <common>Horikawa</common> + </name> + + <email>horikawa@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.jp.FreeBSD.org/man-jp/">jpman project</url> + </links> + + <body> + <p>We have been updating RELENG_4 targeting for 4.7-RELEASE. + When port ja-man-1.1j_5 was broken around the end of July, + Kumano-san and Mori-san tried to update the port to be based + on a newer FreeBSD base system's man commands. + But, we decided only to fix the port ja-man-1.1j_5 to be buildable, + as the new one was not complete at that time.</p> + </body> +</project> + +<project> + <title>GEOM - generalized block storage manipulation</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~phk/Geom/">Old concept paper here.</url> + + </links> + + <body> + <p>The GEOM code has gotten so far that it beats our current code + in some areas while still lacking in others. The goal is for + GEOM to be the default in 5.0-RELEASE.</p> + <p>Currently work on a cryptographic module which should be able + to protect a diskpartition from practically any sort of attack + is progressing.</p> + + </body> +</project> + +<project> + <title>UFS2 - 64bit UFS with native extended attributes</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + <person> + <name> + <given>Kirk</given> + + <common>McKusick</common> + </name> + + <email>mckusick@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The UFS2 filesystem approaches feature completion: Extended + attribute functionality have been added, including a new + compound modification API and basic testing has been passed.</p> + + </body> +</project> + +<project> + <title>French FreeBSD Documentation Project</title> + <contact> + <person> + <name> + <given>Sebastien </given> + <common>Gioria</common> + </name> + + <email>gioria@FreeBSD.org</email> + </person> + <person> + <name> + <given>Marc </given> + <common>Fonvieille</common> + </name> + <email>blackend@FreeBSD.org</email> + </person> + <person> + <name> + <given>Stephane</given> + <common>Legrand</common> + </name> + <email>stephane@FreeBSD-fr.ORG</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd-fr.org">The French FreeBSD Documentation Project.</url> + <url href="http://www.freebsd-fr.org/index-trad.html">The FreeBSD Web Server translate in French.</url> + <url href="http://people.FreeBSD.org/~blackend/doc/fr_FR.ISO8859-1/books/handbook/"> Translation of the Hanbook.</url> + </links> + + <body> + <p>We've got currently almost 50% of the new handbook translated (all the + installation part is translated). Most of the articles are translated + too.</p> + <p>The web site in on the way, see the Web Server. We need now to + integrate it on the US CVS tree.</p> + <p>One of the big job now, is to translate the latest FAQ and the very + big project will be the manual pages</p> + </body> +</project> +<project> + <title> Bluetooth stack for FreeBSD (Netgraph implementation)</title> + + <contact> + <person> + <name> + <given> + Maksim + </given> + + <common> + Yevmenkin + </common> + </name> + + <email> + m_evmenkin@yahoo.com + </email> + </person> + </contact> + + <links> + <url href="http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020909.tar.gz">Latest snapshot</url> + + <url href="http://bluez.sf.net">Linux BlueZ stack</url> + </links> + + <body> + <p>I'm very pleased to announce that another engineering + release is available for download at + http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020909.tar.gz</p> + <p>This release features several major changes and includes + support for H4 UART and H2 USB transport layers, Host + Controller Interface (HCI), Link Layer Control and + Adaptation Protocol (L2CAP) and Bluetooth sockets layer. + It also comes with several user space utilities that + can be used to configure and test Bluetooth devices. + Also there are several man pages.</p> + <p>Service Discovery Protocol (SDP) is now supported. This + release includes SDP daemon, configuration tool and user + space library (ported from BlueZ-sdp-0.7).</p> + <p>RFCOMM is now supported. This release includes rfcommd + daemon that provides RFCOMM service via pseudo ttys. + Not very useful for legacy application, but it is possible + to run PPP over Bluetooth now. This was ported from old + BlueZ-rfcommd-1.1 (no longer supported by BlueZ) and + still has some bugs in it.</p> + <p>Next step is to fix current RFCOMM support and work on + new in-kernel RFCOMM and BNEP (Bluetooth Network + Encapsulation Protocol) implementation. Also user space + need more work (better tools, libraries, documentation + etc.).</p> + </body> +</project> +<project> + <title>Netgraph ATM</title> + + <contact> + <person> + <name> + <given>Harti</given> + + <common>Brandt</common> + </name> + + <email>brandt@fokus.fhg.de</email> + </person> + </contact> + + <links> + <url href="http://www.fokus.fhg.de/research/cc/cats/employees/hartmut.brandt/ngatm/index.html">Introduction to NgAtm</url> + </links> + + <body> + <p>Version 1.2 has been released recently. It should compile and work + an any recent FreeBSD-current. Support to manipulate SUNI registers + has been added to the ATM drivers (to switch between SONET and SDH + modes, for example). The ngatmsig package now includes a small and + simple call control module that may be used to build a simple ATM + switch. The netgraph stuff has been patched to use the official + netgraph locking.</p> + </body> +</project> + +<project> + <title>FreeBSD C99 & POSIX Conformance Project</title> + + <contact> + <person> + <name> + <given>Mike</given> + + <common>Barcroft</common> + </name> + + <email>mike@FreeBSD.org</email> + </person> + <person> + <name> + <common>FreeBSD-Standards Mailing List</common> + </name> + + <email>standards@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/c99/" /> + </links> + + <body> + <p>On the API front, fmtmsg(3) was implemented, glob(3) was given support + for new flags, ulimit(3) was implemented, and wide character/string + support was significantly improved with the addition of 30 new functions + (see the project status board for details). Work is progressing on + adding the C99 restrict type-qualifier to functions throughout the + system. This allows the compiler to make additional optimizations based + on the knowledge that a restrict-qualified argument is the only reference + to a given object (ie. it doesn't overlap with another argument).</p> + <p>Several headers have been brought up to conformance with POSIX.1-2001, + they include: <fmtmsg.h>, <poll.h>, <sys/mman.h>, and + <ulimit.h>. The header <cpio.h> was implemented. The + headers <machine/ansi.h> and <machine/types.h> were merged + into a single header to help simplify the way variable types are + created.</p> + <p>The sh(1) built-in, command(1), was reimplemented to conform with + POSIX. Additionally, several utilities which were previously brought + up to conformance were merged into the 4-STABLE branch.</p> + </body> +</project> + +<project> + <title>FreeBSD GNOME Project</title> + + <contact> + <person> + <name> + <given>Joe</given> + + <common>Marcus</common> + </name> + + <email>marcus@FreeBSD.org</email> + </person> + <person> + <name> + <given>Maxim</given> + + <common>Sobolev</common> + </name> + + <email>sobomax@FreeBSD.org</email> + </person> + + </contact> + + <links> + <url href="http://www.FreeBSD.org/gnome/">FreeBSD GNOME Project + Homepage.</url> + + </links> + + <body> + <p>The GNOME 2 desktop port has reach version 2.0.2rc1 with an expected + 2.0.2 release before 4.7-RELEASE. Mozilla 1.1 has been ported, + and is resident in the tree with Mozilla 1.0.1. The GNOMENG porting + effort is going well. A good deal of ports have been moved to the + new infrastructure with the help of + Edwin Groothuis. We are now working on + smoothing out some of the rough edges, then, once all the work is done, + make GNOMENG the default.</p> + <p>A long-standing annoyance in Nautilus has also been recently + corrected. The desktop is no longer cluttered with volume icons, and + removable media (such as CDs) should now be handled correctly.</p> + + </body> +</project> +<project> + <title>ATAPI/CAM Status Report</title> + + <contact> + <person> + <name> + <given>Thomas</given> + + <common>Quinot</common> + </name> + + <email>thomas@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.cuivre.fr.eu.org/~thomas/atapicam/"/> + </links> + + <body> + <p>The ATAPI/CAM module allows ATAPI devices (CD-ROM, CD-RW, DVD + drives, floppy drives such as Iomega Zip, tape drives) to + be accessed through the SCSI subsystem (CAM). ATAPI/CAM has been + integrated in -CURRENT. The code should be fairly functional (it + has been used by many testers as patches against -STABLE and + -CURRENT over the past eight months), but there are pending issues + on SMP machines. Testers most welcome.</p> + <p>A MFC of this feature will probably happen after the end + of the 4.7 code freeze.</p> + </body> +</project> +<project> + <title>Hardware Crypto Support Status</title> + <contact> + <person> + <name> + <given>Sam</given> + <common>Leffler</common> + </name> + <email>sam@FreeBSD.org</email> + </person> + </contact> + <body> + <p>The goal of this project is to import the OpenBSD kernel-level crypto + subsystem. This facility provides kernel- and user-level access to + hardware crypto devices for the calculation of cryptographic hashes, + ciphers, and public key operations. The main clients of this facility + are the kernel RNG (/dev/random), network protocols (e.g. IPSEC), and + OpenSSL (through the /dev/crypto device).</p> + <p>OpenSSL 0.9.7 beta 3 was imported and patched with fixes from OpenBSD's + source tree. This permits any user-level application that use -lcrypto to + automatically get hardware crypto acceleration. Otherwise the core crypto + support is stable and has been in production use on -stable machines for + several months.</p> + <p>Import of this work into the -current tree has started. A publicly + available patch against 4.7 will be released once 4.7 ships. Integration + of this work into the -stable source tree is planned for 4.8.</p> + </body> +</project> + +<project> + <title>Fast IPsec Status</title> + <contact> + <person> + <name> + <given>Sam</given> + <common>Leffler</common> + </name> + <email>sam@FreeBSD.org</email> + </person> + </contact> + <body> + <p>The main goal of this project is to modify the IPsec protocols to use + the kernel-level crypto subsystem imported from OpenBSD (see elsewhere). A + secondary goal is to do general performance tuning of the IPsec + protocols.</p> + <p>Recent work focused on increasing performance. Support is still limited + to IPv4 protocols, with IPv6 support coded but not yet tested. </p> + <p>Import of this work into the -current tree has started. A publicly + available patch against 4.7 will be released once 4.7 ships.</p> + </body> +</project> + +<project> + <title>VM issues in -stable</title> + + <contact> + <person> + <name> + <given>Matthew</given> + + <common>Dillon</common> + </name> + + <email>dillon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://apollo.backplane.com/FreeBSD/wiring_patch_03.diff"> + VM corruption patch for -stable.</url> + </links> + + <body> + <p>Work is in progress to MFC a number of bug fixes related + to vm_map corruption into -stable. This work is probably + too involved to make it into the 4.7 release but is expected to + be committed just after the freeze is lifted. The corruption + in question typically occurs in large-memory systems under heavy + loads and typically panics or KPFs (kernel-page-fault's) the machine + in a vm_map related function.</p> + </body> +</project> + +<project> + <title>New SCSI Target Emulator</title> + + <contact> + <person> + <name> + <given>Nate</given> + + <common>Lawson</common> + </name> + + <email>nate@root.org</email> + </person> + </contact> + + <links> + <url href="http://www.root.org/~nate/freebsd/" /> + </links> + + <body> + + <p>The existing SCSI target code has been rewritten. The kernel driver is + much simpler, deferring all functionality to usermode and simply passing + CCBs to and from the SIM. The supplied usermode emulates a disk (RBC) + with IO going to a backing file. It replaces /sys/cam/scsi/scsi_target* + and /usr/share/examples/scsi_target.</p> + <p>The code is definitely alpha quality and has known problems on + -current although it appears to work ok on -stable. See the included + README for how to install and test. Feedback is welcome!</p> + + </body> +</project> + +<project> + <title>Lottery Scheduler for FreeBSD -STABLE</title> + + <contact> + <person> + <name> + <given>Mário Sérgio Fujikawa</given> + + <common>Ferreira</common> + </name> + + <email>lioux@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Yet another implementation of Lottery Scheduling devised by + Carl Waldspurger et. al. is being developed against FreeBSD + -STABLE branch. It is being developed as part of a graduation + project in Computer Science at Universidade de Brasília + in Brazil. Therefore, other implementations have not yet + been verified to avoid plagiarization but will be checked in + a later stage of this project searching for better implementation + ideas. Currently, part of the necessary scheduling kernel + structure has been mapped and work has progressed despite the + general lack of kernel documentation. Further outcomes of + this project will be a simple documentation of the kernel + scheduler structure of -STABLE branch, a port of the Lottery + Scheduler to -CURRENT branch and additional implementations + of other scheduling disciplines from Carl Waldspurger et. al. + Members of the FreeBSD community have been and will continue + to be instrumental in both testing and providing feedback for + ideas implemented here.</p> + </body> +</project> + +<project> + <title>The FreeBSD Brazilian Portuguese Documentation Project</title> + + <contact> + <person> + <name> + <given>Edson</given> + + <common>Brandi</common> + </name> + + <email>ebrandi.home@uol.com.br</email> + </person> + + <person> + <name> + <given>Mário Sérgio Fujikawa</given> + + <common>Ferreira</common> + </name> + + <email>lioux@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ricardo Nascimento</given> + + <common>Ferreira</common> + </name> + + <email>nightwish@techemail.com</email> + </person> + + <person> + <name> + <given>Diego</given> + + <common>Linke</common> + </name> + + <email>gamk@gamk.com.br</email> + </person> + + <person> + <name> + <given>Jean Milanez</given> + + <common>Melo</common> + </name> + + <email>jmelo@freebsdbrasil.com.br</email> + </person> + + <person> + <name> + <given>Patrick</given> + + <common>Tracanelli</common> + </name> + + <email>eksffa@freebsdbrasil.com.br</email> + </person> + + <person> + <name> + <given>Alexandre</given> + + <common>Vasconcelos</common> + </name> + + <email>alexandre@sspj.go.gov.br</email> + </person> + </contact> + + <links> + <url href="http://www.fugspbr.org/">FUG-BR Grupo de Usuários + FreeBSD - Brasil</url> + </links> + + <body> + <p>The FreeBSD Brazilian Portuguese Documentation Project is + merging with a translation group formed by members of the + FUG-BR FreeBSD Brazilian user group. The Brazilian Project + decided to become an official group under FUG-BR after receiving + continued excellent contributions from them. They have managed + to complete the translation of the FreeBSD FAQ which is + currently undergoing both proofing and SGML"fication" stages. + Work is progressing fast: the Handbook has been half translated + and articles are under way. The previous Brazilian Project + is proud to become part of such a dedicate group. The contacts + above represent the current official contacts for the new + translation group. We hope to have at least part of this + work ready for the FreeBSD 4.7 Release.</p> + </body> +</project> + +<project> + <title>KSE</title> + + <contact> + <person> + <name> + <given>Julian</given> + <common>Elischer</common> + </name> + <email>julian@FreeBSD.org</email> + </person> + <person> + <name> + <given>Jonathon</given> + <common>Mini</common> + </name> + <email>mini@FreeBSD.org</email> + </person> + <person> + <name> + <given>Dan</given> + <common>Eischen</common> + </name> + <email>deischen@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~julian">poor description</url> + </links> + + <body> + <p> David Xu and I have been working on cleaning up some of the work done + in KSE-III and Jonathon and Dan have been working on the userland + interface. The userland library will be committed soon in a + prototypical state and a working test program using that interface will + hopefully accompany it. I have just committed a rework of the run + states for kernel threads that simplifies or solves some problems that + were being seen recently.</p> + <p>Hopefully in the next few weeks we will be able to run threads on + separate processors. The basics of Signal support are presently + evolving. Archie Cobbs will also be assisting with some of this work. + I have a mail alias for all the developers at kse@elischer.org. It is + managed by hand at the moment.</p> + </body> + </project> + +<project> + <title>Release Engineering</title> + + <contact> + <person> + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/" /> + </links> + + <body> + <p>The Release Engineering (RE) Team completed and released FreeBSD + 4.6.2. This ``point release'' fixes several important bugs in + the ATA subsystem, as well as addressing a number of security + issues in the base system that surfaced shortly after FreeBSD + 4.6 was released. The release documentation distributed with + FreeBSD 4.6.2 contains more details. (Note: Some earlier + documents and reports referred to this release as version + 4.6.1.) The next release in the 4.X series will be FreeBSD 4.7, + which has a scheduled release date of 1 October 2002.</p> + <p>Concurrently, work is continuing on the 5.0-DP2 developer + preview snapshot, an important milestone along the release path + of FreeBSD 5.0, which is scheduled for release on 20 November. + As 5.0 draws closer, we are focusing more on getting the system + stabilized, as opposed to adding new functionality. To help us + with this effort, developers should discuss with us any new + features planned for -CURRENT, beginning 1 October.</p> + </body> +</project> + +<project> + <title>jp.FreeBSD.org daily SNAPSHOTs project</title> + <contact> + <person> + <name> + <given>Makoto</given> + <common>Matsushita</common> + </name> + <email>matusita@jp.FreeBSD.org</email> + </person> + </contact> + <links> + <url href="http://snapshots.jp.FreeBSD.org/">Project Webpage</url> + <url href="http://www.jp.FreeBSD.org/snapshots/">Project Webpage (in Japanese +)</url> + </links> + <body> + <p>The project runs as it should be. New security-branch snapshots are + available for both 4.5 and 4.6(.2). I've update buildboxes OS to + the latest 5-current/4-stable without any errors. Also current + problem, less CPU power for the future, is not solved yet -- but + situation is not so bad, I hope I'll show a good news in the next + report.</p> + </body> +</project> + +<project> + <title>FreeBSD Donations Team</title> + + <contact> + <person> + <name> + <given>Michael</given> + + <common>Lucas</common> + </name> + + <email>donations@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/donations/index.html" /> + </links> + + <body> + <p>The Donations team started rolling in the last couple of + months. Offers of equipment are coming in, and we are + allocating them to FreeBSD committers as quickly as possible. + We now have a "Committer Want List" available in our section of + the Web site. Several small items, such as network cards, have + been routed to people who are willing to write the code to + support them. We have a few larger donations (i.e., actual + servers) ready to go to developers, once shipping information is + straightened out.</p> + </body> +</project> + +<project> + <title>RAIDFrame for FreeBSD</title> + + <contact> + <person> + <name> + <given>Scott</given> + + <common>Long</common> + </name> + + <email>scottl@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~scottl/rf">Project homepage</url> + </links> + + <body> + <p>Work on RAIDFrame stalled for quite a bit, then it picked up in + early summer, then it stalled, and now it's going again. A + significant amount of work has been done to make the locking + SMPng-friendly and to cut down on kernel stack abuse. I'm happy + to say that it's starting to work reliably when used with file- + backed 'md' disks. Even more exciting is that it's finally starting + to work on real disks, too. A lot of cleanup is still needed, and + a few gross hacks still exist, but it might actually be ready for + the FreeBSD 5.0 release. Patches for FreeBSD 5-current and 4-stable + are available from the website. The 4-stable patches are a year old + but still apply and perform well.</p> + </body> +</project> + +<project> + <title>Libh Status Report</title> + + <contact> + <person> + <name> + <given>Antoine</given> + + <common>Beaupré</common> + </name> + + <email>anarcat@anarcat.ath.cx</email> + </person> + + <person> + <name> + <given>Alexander</given> + + <common>Langer</common> + </name> + + <email>alex@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/libh.html">Project's home + page</url> + + </links> + + <body> + <p>The primary libh development box, where the CVS repo and + development webpage was living, is dead. The server has crashed + after a system upgrade and has never came back to life. We had + to pull the drives out of it to make proper backups. We will + setup another box in place of this one and hope for the best. So + right now, the port is broken because the CVS is unaccessible, + as the development web page. We're working on it, please bear + with us.</p> + <p>On a brighter note, Max started implementing the changes he + proposed to the build system and the TCL API; LibH is switching + to SWIG for its TCL bindings, which should simplify the system a + lot, and shorten build times. The Hui subsystem is therefore + being completely re-written. On my side, I made a few tests in + building and running LibH under rhtvision, and it didn't fulfill + the promises I thought it would, so I just put aside that + idea. Work on libh stalled during July because I completely lost + network access for the whole month. So right now, LibH is in a + bit of a mess, but we have high hopes of settling everything + down to a new release pretty soon, which will make full use of + the new SWIG bindings.</p> + </body> +</project> + + +<project> + <title>FreeBSD Security Officer Team</title> + + <contact> + <person> + <name> + <given>Jacques</given> + + <common>Vidrine</common> + </name> + + <email>nectar@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/security/"/> + </links> + + <body> + + <p>The Security Team continues to be very busy. The + security-officer mailing list traffic for the months of June, July, + and August consisted of 1,230 messages (over 13 messages a day). + This is well over 50% of the freebsd-hackers traffic volume in the + same period!</p> + <p>Since June (the time of our last report), 9 new Security + Advisories were published, and one Security Notice was published + covering 25 Ports Collection issues.</p> + <p>FreeBSD 4.6.2-RELEASE was released on August 15th. This marked + the first time a point release was created from the security branch. + The process went smoothly from the Security Team perspective, despite + a schedule slippage due to newly discovered bugs, and a snafu which + resulted in 4.6.1-RELEASE being skipped.</p> + <p>In September, the FreeBSD Security Officer published a new PGP + key (ID 0xCA6CDFB2, found on the FTP site and in the Handbook). + This aligned the set of those who possess the corresponding private + key with the membership of the security-officer alias published on + the FreeBSD Security web site. It also worked around an issue with + the deprecated PGP key being found corrupted on some public key + servers.</p> + </body> +</project> + +<project> + <title>TrustedBSD Mandatory Access Control (MAC)</title> + <contact> + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + <person> + <name> + <common>TrustedBSD Discussion Mailing List</common> + </name> + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + <body> + <p>It's been a busy few months, with a variety of development, + documentation, and public relations activities. The MAC Framework, + our pluggable kernel access control mechanism for FreeBSD, has + matured substantially, and large parts of it were merged to the + main FreeBSD tree over July and August.</p> + <p>A variety of entry point changes were made, including: component + names are now passed to VFS namespace VOPs; aggressive caching + of MAC labels in vnodes; mmap memory access downgrades on subject + relabel; check for access()/eaccess(); checks for vnode read, + write, ioctl, pool, permitting revocation post-open() by aware + policies; labeling and access control checks for pipe IPC objects, + clean up of socket/visibility checks; checks for socket bind, + connect, listen, ....; many locking improvements and assertions, + especially for vnodes, processes; framework now supports partial + label updates on subjects and objects; credential management in + 'struct file' improved so that active_cred and file_cred are + more carefully distinguished and passed to MAC framework + explicitly; accounting system uses cached credentials for + write operations now; socreate() can use cached credential to + label sockets fixing deferred nfs socket connections and + reconnections with TCP; kse interactions with proc1 fixed; + IO_NOMACCHECK flag to vn_rdwr() for internal use to avoid + redundant or incorrect MAC checks on aio vnode operations; + mac_syscall() policy function demux; su no longer changes MAC + labels by default; mac_get_pid() to support ps and getpmac -p pid; + mmap revocation defaults to "fail stop"; MAC_DEBUG wraps atomic + label counters; UFS2 extended attributes supported; initial + port of LOMAC to the MAC framework; update all policies for all + these changes; merge of KSE III; merge of nmount(); upgrade of + ugidfw to speak user and group names; libugidfw; many namespace + and naming consistency improvements; module dependencies on + MAC framework; large scale merging of MAC functionality to the + main FreeBSD tree. KDE interfaces to common management + activities.</p> + <p>Wrote and taught full-day MAC framework tutorial at STOS + BSD and Darwin Security Symposium; first draft of MAC framework + architecture and API guide. This is now in the Developer's + Handbook.</p> + <p>Next couple of months will bring continued maturity improvements, + labeling and protection of more objects; VFS performance + improvements; better support for UFS2 EAs and separate EA + entries for each policy; improved support for LOMAC; MLS + compartments; IPsec security association labeling; improved + SEBSD FLASK/TE port; and much more.</p> + </body> +</project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2002-09-2002-10.xml b/en_US.ISO8859-1/htdocs/news/status/report-2002-09-2002-10.xml new file mode 100644 index 0000000000..25a432bbdf --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2002-09-2002-10.xml @@ -0,0 +1,1025 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2002-09-2002-10.xml,v 1.9 2006/08/19 21:20:40 hrs Exp $ --> + +<report> + <date> + <month>September-October</month> + <year>2002</year> + </date> + + <section> + <title>Introduction:</title> + + <p>Another busy pair of months at the FreeBSD Project have brought + substantial maturity and feature completeness to the fledgeling + 5.0-CURRENT branch. And just in time too, because by the time + you read the next status report, we hope that you'll have + FreeBSD 5.0 running on your desktop! Over the past two months, + we've seen an upgrade of sparc64 to Tier 1 (Fully Supported) + status, integration of a high quality storage encryption module, + the commit of hardware-accelerated IPsec support, the addition of + a general-purpose "Device Daemon" to process hardware + attach/detach events to replace earlier single-purpose and + bus-specific daemons, the commit of RAIDFrame, and the improved + maturity of the TrustedBSD work. We've also seen another + successful release of the 4.x branch, 4.7-RELEASE, which will + continue to be the production supported platform as 5.X is brought + in for landing.</p> + + <p>Over the next two months, the FreeBSD Project will be focused + almost entirely on making 5.0 a success: improving system + stability and performance, as well as increasing the pool of + applications that build and run on 5.0. The Release Engineering + team will have announced the 5.0 code freeze, and released DP2 by + the time you read this. Following DP2 will be a series of Release + Candidates (RC's), and then the release itself. If you're + interested in getting involved in the testing process, please lend + a hand -- a spare box and a copy of the DP and RC ISOs burnt onto + CD will make a difference. The normal caveats associated with + pre-release versions of operating systems apply! You may also be + interested in reading the Early Adopter's guide produced by the + Release Engineering team to help determine when a transition from + the 4.x branch to the 5.x branch will be appropriate for you and + your organization.</p> + + <p>Thanks,</p> + + <p>Robert Watson, Scott Long</p> + </section> + +<project> + <title>Bluetooth stack for FreeBSD (Netgraph implementation)</title> + + <contact> + <person> + <name> + <given>Maksim</given> + <common>Yevmenkin</common> + </name> + <email>m_evmenkin@yahoo.com</email> + </person> + </contact> + + <links> + <url href="http://www.geocities.com/m_evmenkin/">Latest snapshot</url> + <url href="http://bluez.sf.net">Linux BlueZ stack</url> + <url href="http://sourceforge.net/projects/openobex">OpenOBEX</url> + </links> + + <body> + <p>I'm very pleased to announce that another engineering release is + available for download at + http://www.geocities.com/m_evmenkin/ngbt-fbsd-20021104.tar.gz</p> + + <p>This release features minor bug fixes and new OpenOBEX library + port. The snapshot includes support for H4 UART and H2 USB transport + layers, Host Controller Interface (HCI), Link Layer Control and + Adaptation Protocol (L2CAP) and Bluetooth sockets layer. It also + comes with several user space utilities that can be used to configure + and test Bluetooth devices. Also there are several man pages.</p> + + <p>Service Discovery Protocol (SDP) port has been updated to + version 0.8. (ported from BlueZ-sdp-0.8). Most of the RFCOMM + issues have been resolved and now rfcommd works with Windows + (3COM, Xircom and Widcomm) and Linux stacks.</p> + + <p>New supported USB device - EPoX BT-DG02 dongle. Also I have + received successful report about Mitsumi USB dongle and C413S + Bluetooth enabled cell phone (L2CAP and SDP works, waiting on + RFCOMM report).</p> + + <p>I'm currently working on OBEX server (Push and File Transfer + profiles) which will be based on OpenOBEX library (included + in the snapshot).</p> + </body> +</project> + +<project> + <title>BSDCon 2003</title> + + <contact> + <person> + <name> + <given>Gregory</given> + <common>Shapiro</common> + </name> + <email>gshapiro@FreeBSD.org</email> + </person> + </contact> + + <links> + <!-- A hypertext link with a description... --> + <url href="http://www.usenix.org/events/bsdcon03/cfp/">BSDCon 2003 Call For Papers</url> + </links> + + <body> + + <p>The BSDCon 2003 Program Committee invites you to contribute + original and innovative papers on topics related to BSD-derived + systems and the Open Source world. Topics of interest include + but are not limited to:</p> + + <ul> + <li>Embedded BSD application development and deployment</li> + <li>Real world experiences using BSD systems</li> + <li>Using BSD in a mixed OS environment</li> + <li>Comparison with non-BSD operating systems; technical, + practical, licensing (GPL vs. BSD)</li> + <li>Tracking open source development on non-BSD systems</li> + <li>BSD on the desktop</li> + <li>I/O subsystem and device driver development</li> + <li>SMP and kernel threads</li> + <li>Kernel enhancements</li> + <li>Internet and networking services</li> + <li>Security</li> + <li>Performance analysis and tuning</li> + <li>System administration</li> + <li>Future of BSD</li> + </ul> + + <p>Submissions in the form of extended abstracts are due by + April 1, 2003. Be sure to review the extended abstract + expectations before submitting. Selection will be based on the + quality of the written submission and whether the work is of + interest to the community.</p> + + <p>We look forward to receiving your submissions!</p> + + </body> +</project> + +<project> + <title>C99 & POSIX Conformance Project</title> + + <contact> + <person> + <name> + <given>Mike</given> + <common>Barcroft</common> + </name> + <email>mike@FreeBSD.org</email> + </person> + <person> + <name> + <common>FreeBSD-Standards Mailing List</common> + </name> + <email>standards@FreeBSD.org</email> + </person> + </contact> + + <links><url href="http://www.FreeBSD.org/projects/c99/" /></links> + + <body> + <p>October 10, 2002 marked the one year anniversary of our project. + During that time we have made significant advances in FreeBSD's + standards conformance. FreeBSD 5.0-RELEASE will be the showcase + for most of our hard work. We hope that our tireless effort has + had a positive effect on FreeBSD and software vendors that + maintain or are considering porting their software to FreeBSD.</p> + + <p>On the API front, _Exit(3) (an alias for _exit(2)) was added, + sysconf(3) was update for POSIX.1-2001, and some of the glob(3) + additions were MFC'd. The insque(), lsearch(), and remque() + family of functions were reimplemented and moved to libc from + libcompat. Several wide character functions were implemented, + including all printf() and scanf() variants. Finally, support + for wide character format types (%C, %S, %lc, %ls) were added to + printf(3).</p> + + <p>Work on utility conformance continued as getconf(1)'s compliance + was updated, c99(1) (a new version of c89(1)) was implemented, + and cd(1) and command(1) changes were MFC'd.</p> + + <p>Almost 20 headers were brought up to conformance with applicable + standards. Not much work remains to fix conformance issues in + the remaining standard headers. Work in this area, as well as + others, has slowed down in preparation for 5.0-RELEASE.</p> + </body> +</project> + +<project> + <title>DEVD Status Report</title> + + <contact> + <person> + <name> + <given>Warner</given> + <common>Losh</common> + </name> + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>DEVD has been integrated into FreeBSD current. It was + integrated in an incomplete state. However, it is useful in the + state that it is in for doing simple things like running + camcontrol rescan when a SCSI pcmcia card is inserted, or running + /etc/pccard_ether with an ethernet card is inserted. The more + sophisticated regular expression matching is not yet complete. + Devd only does actions on device arrival and departure, but does + not yet do anything with unknown devices. In addition to + listening for device events, there is some desire to have + /dev/devctl also allow for some direct control of the device + tree.</p> + </body> +</project> + +<project> + <title>Fast IPsec Status</title> + + <contact> + <person> + <name> + <given>Sam</given> + <common>Leffler</common> + </name> + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The main goal of this project is to modify the IPsec protocols to use + the kernel-level crypto subsystem imported from OpenBSD (see elsewhere). A + secondary goal is to do general performance tuning of the IPsec + protocols.</p> + + <p>This work was committed to -current. To configure it for use specify + options FAST_IPSEC in your system configuration file. At present support is + limited to IPv4.</p> + </body> +</project> + +<project> + <title>GBDE - Geom Based Disk Encryption</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + <common>Kamp</common> + </name> + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>GBDE has been committed to -current.</p> + + <p>The "Geom Based Disk Encryption" module provides a mechanism for + very strong encryption of a GEOM "disk". The algorithm has passed + informal review by a couple of seasoned crypto heavy-weights. + Any GEOM device can be protected with GBDE, entire physical disks, + MBR slices, BSD partitions etc etc. Booting from an encrypted + partition is not possible, however.</p> + + <p>The focus of GBDE is to protect a "cold" disk media. (FreeBSD is + not equipped well for protecting key material on a running system + from being compromised.) + For a cold media, the only feasible attack on a GBDE protected + media is guessing the pass-phrase.</p> + + <p>Summary of the GBDE multilevel protection scheme: Up to four + separate pass-phrases can unlock their own separate copies of + the 2048 bit masterkey. The master-keys are protected using + AES/256/CBC keyed with a SHA-2 hash derived from the pass-phrase. + A salted MD5 hash over the sectoroffset "cherry-picks" which masterkey + bytes participate in the MD5 hash which generates the "kkey" + for each particular sector. The kkey AES/128/CBC encrypts the PRNG + produced single-use key which AES/128/CBC encrypts the actual + sector data.</p> + + <p>GBDE has features for master-key destruction and pass-phrase + invalidation.</p> + + <p>See gbde(4) and gbde(8) for more details.</p> + + <p>This software was developed for the FreeBSD Project by + Poul-Henning Kamp and NAI Labs, the Security Research + Division of Network Associates, Inc. under DARPA/SPAWAR + contract N66001-01-C-8035 ("CBOSS"), as part of the DARPA + CHATS research program.</p> + </body> +</project> + +<project> + <title>GEOM - generalized block storage manipulation</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + <common>Kamp</common> + </name> + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~phk/Geom/">Old concept paper here.</url> + </links> + + <body> + <p>The GEOM code is now the default on most (if not all ?) architectures + and the few remaining issues in libdisk/sysinstall is being hashed + out.</p> + + <p>Although we are far from finished developing GEOM, its current feature + set is a significant step forward for FreeBSD, providing not only + immediate relief for new architectures (sparc64, ia64 etc) but also + because it is designed as SMPng code from the start.</p> + + <p>This software was developed for the FreeBSD Project by + Poul-Henning Kamp and NAI Labs, the Security Research + Division of Network Associates, Inc. under DARPA/SPAWAR + contract N66001-01-C-8035 ("CBOSS"), as part of the DARPA + CHATS research program.</p> + </body> +</project> + +<project> + <title>FreeBSD GNOME Project</title> + + <contact> + <person> + <name> + <given>Joe</given> + <common>Marcus</common> + </name> + <email>marcus@FreeBSD.org</email> + </person> + <person> + <name> + <given>Maxim</given> + <common>Sobolev</common> + </name> + <email>sobomax@FreeBSD.org</email> + </person> + <person> + <name> + <given>Adam</given> + <common>Weinberger</common> + </name> + <email>adamw@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/gnome/">FreeBSD GNOME Project Homepage.</url> + </links> + + <body> + <p>These last two months have seen quite a lot of GNOME activity. + GNOME has started releasing development snapshots of the upcoming + GNOME 2.2 desktop. FreeBSD porting has begun outside of the + main ports tree in the + <a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi">MarcusCom + CVS repository</a>. If you are interested in testing the new + desktop, follow the instructions on the aforementioned cvsweb + URL, and checkout the "ports" module.</p> + + <p>Evolution 1.2 is also close at hand. Ximian has posted its + first release candidate, 1.1.90, which has been ported to FreeBSD, + and is available from the MarcusCom CVS repo listed above. As + soon as Ximian officially releases Evolution 1.2, it will be placed in + the FreeBSD ports tree.</p> + + <p>The Mozilla ports have received numerous updates. We are now + tracking all three released Mozilla versions. The mozilla-vendor + port is tracking the 1.0.x branch, mozilla is tracking 1.1.x, and + mozilla-devel is tracking 1.2.x. The mozilla-devel port now + has support for anti-aliased fonts as well as a GTK+-2 interface</p> + + <p>Finally, the GNOME team would like to welcome its newest + team member, Adam Weinberger. Adam has been submitting patches for + both GNOME ports as well as documentation. Currently, he has been + active in the GNOME 2.2 porting effort. We are happy to have him.</p> + </body> +</project> + +<project> + <title>Hardware Crypto Support Status</title> + + <contact> + <person> + <name> + <given>Sam</given> + <common>Leffler</common> + </name> + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The goal of this project is to import the OpenBSD kernel-level crypto + subsystem. This facility provides kernel- and user-level access to hardware + crypto devices for the calculation of cryptographic hashes, ciphers, and + public key operations. The main clients of this facility are the kernel RNG + (/dev/random), network protocols (e.g. IPsec), and OpenSSL (through the + /dev/crypto device).</p> + + <p>This work was committed to the -current tree. To configure it for use + specify device crypto in your system configuration file or you can load the + crypto module. The /dev/crypto device support is brought in with device + cryptodev or by loading the cryptodev module. Two crypto device drivers + exist: ubsec for Broadcom-based PCI hardware and hifn for Hifn-based PCI + hardware.</p> + + <p>Integration of this work into the -stable source tree should be + completed by the time this report is published.</p> + </body> +</project> + +<project> + <title>FreeBSD Java Project</title> + + <contact> + <person> + <name> + <given>Greg</given> + <common>Lewis</common> + </name> + <email>glewis@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/java/">FreeBSD Java Project</url> + </links> + + <body> + <p>Since the last status report the BSD Java Porting Team has continued + to make steady progress. The most exciting news we have is courtesy + of our newest team member, Alexey Zelkin of FreeBSD committer fame. + + <ul> + <li>Thanks to a lot of hard work, primarily by Alexey, the project + is very close to being able to release our first patch set for + the 1.4 JDK. Things are reportedly working quite well under + -CURRENT, with -STABLE support being only marginally behind (thanks + in part to the libc_r MFC by Max Khon).</li> + <li>The project has released another patchset for the 1.2.2 JDK, mainly + to add support for OpenBSD and for JPDA. Most of the projects + energy at the moment is focused on 1.3 and 1.4, however we still + hope to back port relevant fixes if appropriate to 1.2.2.</li> + <li>Nate Williams has been hard at work behind the scenes migrating + us to a new CVS server which has kindly been donated by the + FreeBSD Foundation. The Project appreciates the continued + support of the Foundation. Please support them so they can + continue to support us and other important FreeBSD efforts!</li> + </ul> + </p> + </body> +</project> + +<project> + <title>jpman project</title> + + <contact> + <person> + <name> + <given>Kazuo</given> + <common>Horikawa</common> + </name> + <email>horikawa@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.jp.FreeBSD.org/man-jp/">jpman project</url> + <url href="ftp://daemon.jp.FreeBSD.org/pub/FreeBSD-jp/man-jp/packages-4.7.0/ja-man-doc-4.7.tgz">package ja-man-doc-4.7.tgz</url> + </links> + + <body> + <p>For 4.7-RELEASE, we privately published package ja-man-doc-4.7.tgz + which consists of man[1256789] entries 10 days after the 4.7-RELEASE + release date. Man3 update god no progress, as updating other sections + busied us. We decided to suspend man3 update officially, as we need to + spend most of our time to catch up with the forthcoming 5.0-RELEASE.</p> + </body> +</project> + +<project> + <title>KDE FreeBSD Project</title> + + <contact> + <person> + <name> + <given>Will</given> + <common>Andrews</common> + </name> + <email>will@FreeBSD.org</email> + </person> + + <person> + <name> + <given>KDE-FreeBSD</given> + <common>Mailinglist</common> + </name> + <email>kde@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://freebsd.kde.org">KDE/FreeBSD Website</url> + <url href="http://rabarber.fruitsalad.org/">KDE/FreeBSD Build Server</url> + </links> + + <body> + <p>The KDE/FreeBSD team has been working on two major goals during the last + two months, Maintenance of the KDE 3.0.x ports and Preparing the + upcoming KDE 3.1 Release.</p> + + <p>Maintenance KDE 3.0 conducted by Alan Eldrige: September started with + the Removal of the KDE 2.x Ports from the FreeBSD-Repository. Later + Packages of KDE 3.0.4 were released and the FreeBSD Ports were updated.</p> + + <p>Preparing for KDE 3.1 conducted by Will Andrews: A lot of effort was + spent on Improving the Fruitsalad-Build-System. We are now able to + create packages directly from the KDE CVS.</p> + </body> +</project> + +<project> + <title>KSE Project Status</title> + + <contact> + <person> + <name> + <given>Julian</given> + <common>Elischer</common> + </name> + <email>julian@FreeBSD.org</email> + </person> + <person> + <name> + <given>David</given> + <common>Xu</common> + </name> + <email>davidxu@FreeBSD.org</email> + </person> + <person> + <name> + <given>Jonathon</given> + <common>Mini</common> + </name> + <email>mini@FreeBSD.org</email> + </person> + <person> + <name> + <given>Daniel</given> + <common>Eischen</common> + </name> + <email>deischen@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/kse/">KSE Project web page</url> + <url href="http://www.FreeBSD.org/~julian">some links</url> + </links> + + <body> + <p>The KSE code has now all the basic kernel functionality + to start being used by the userland. There are still things + to be done for testing and familiarization.</p> + + <p>General system utilities have not yet been changed. + e.g. ps and top etc. need to know about threads.</p> + + <p>There is quite a lot of code in the kernel that still + assumes that there is one thread in a process. Signals are + not yet handled in the final manner (though they are + delivered to a random thread in the process :-/ ).</p> + + <p>The system calls and datastructures are now however in + place. The test program successfully starts several threads + that can be scheduled on different processors, and closes + them down again. The userland is probably going to be able + to do simple scheduling of pthread threads using KSE by the + time that this report is published.</p> + + <p>I still need someone to take over the "official" web page + since jason left. LaTeX sure isn't my thing. </p> + </body> +</project> + +<project> + <title>LibH</title> + + <contact> + <person> + <name> + <given>Antoine</given> + <common>Beaupré</common> + </name> + <email>anarcat@anarcat.ath.cx</email> + </person> + + <person> + <name> + <given>Alexander</given> + <common>Langer</common> + </name> + <email>alex@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/libh.html" /> + <url href="http://rtp1.slowblink.com/~libh/">LibH development page</url> + </links> + + <body> + <p>Not much since the last status report, except that we now have + the repo and development web page back online, thanks to the + services of John De Boskey who freely provided the necessary + hardware and bandwidth to host the project. We have also ported + LibH to GCC 3.x, so that it can compile on -CURRENT + correctly. This, however, broke tvision, which doesn't compile + under GCC 3.x, so we moved to rhtvision but this caused linking + problems so we're stuck with no console front end, for now.</p> + + <p>Work on a Hui rewrite and SWIG bindings stalled. Alex was able + to come up with a simple patch to make the ports system use + LibH's pkg_create script to build libh packages, so we're + getting closer to a real pkg_create(1) drop-in replacement. I + rewrote the milestone list to show a bit more relevant and + encouraging tasks that will be dealt with in order to really + push LibH forward.</p> + </body> +</project> + +<project> + <title>FreeBSD/MIPS</title> + + <contact> + <person> + <name> + <given>Juli</given> + <common>Mallett</common> + </name> + <email>jmallett@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>A mailing list was created, freebsd-mips, and a Perforce branch + was created in //depot/projects/mips. Changes which will be + necessary to allow multiple MIPS (and PowerPC) metaports to exist + under one architecture port were made, and are being pushed back + into the main FreeBSD tree. Some preliminary header work has been + done, and porting the ARCBIOS interfaces to the kernel has begun. + The toolchain in tree was updated and modified in places to support + a FreeBSD/MIPS (Big Endian) target, in the Perforce branch. Some + early boot code has proven the GDB MIPS simulator to work, for at + least R3000 code, though whether R3000 will be supported has been + under discussion. Some initial architectural decisions were also + made, to steer current work.</p> + </body> +</project> + +<project> + <title>NEWCARD Status Report</title> + + <contact> + <person> + <name> + <given>Warner</given> + <common>Losh</common> + </name> + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work on newcard continues. A number of bugs have been fixed in + the last few months. You are now able to load and unload drivers + (including the bridge) to test changes to pccard and/or cardbus + bus code. It is now possible to load a driver that has a pccard + attachment and have a previously inserted card probe and attach. + This is also true for CardBus. A number of issues remain to be + solved before 5.0. However, with the integration of devd into the + tree nearly all of old functionality of OLDCARD is now present in + NEWCARD (the biggest remaining parts are power control for the + sockets, as well as pccardc dumpcis).</p> + </body> +</project> + +<project> + <title>PowerPC Port</title> + + <contact> + <person> + <name> + <given>Peter</given> + <common>Grehan</common> + </name> + <email>grehan@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The PowerPC port has been running diskless on NewWorld G3/G4 + machines for a while now. A GEOM module to support Apple Partition + Maps is being written. There should be an installable ISO image + available in the near future.</p> + </body> +</project> + +<project> + <title>RAIDFrame for FreeBSD</title> + + <contact> + <person> + <name> + <given>Scott</given> + <common>Long</common> + </name> + <email>scottl@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~scottl/rf">Project homepage</url> + </links> + + <body> + <p>RAIDFrame was imported into FreeBSD-current in late October, a + major milestone after 18 months. It is still very experimental and + not suitable for production environments. The website contains a + lengthy TODO list which I hope to start attending to soon. Still, + I encourage everyone to try it out and report bugs back to me.</p> + </body> +</project> + +<project> + <title>Release Engineering</title> + + <contact> + <person> + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/" /> + <url href="http://www.FreeBSD.org/relnotes.html" /> + </links> + + <body> + <p>The Release Engineering (RE) team completed and released + FreeBSD 4.7 on 10 October 2002. This release features updates + for a number of contributed software programs in the base + system, as well as all of the security and bug fixes from + FreeBSD 4.6.2. The next release in the 4.X series will be + FreeBSD 4.8, which has a scheduled release date of 1 February + 2003.</p> + + <p>Before that time, however, will be the release of FreeBSD 5.0. + Thus far, we have not been able to release the 5.0-DP2 developer + snapshot due to various stability issues. Thanks to much effort + from many of our fellow developers, we believe that most of + these have been resolved. The RE team wishes to emphasize that + FreeBSD 5.0 will involve new code and features that have not + seen widespread testing, and that more conservative users may + wish to continue to track the 4.X series for the near-term + future. To provide more information on these issues, we have + added an Early Adopter's Guide to the release documentation for + 5.0.</p> + + <p>Brian Somers has resigned from the RE team due to increased + time pressures. We thank him for all of his help with FreeBSD + 4.5, 4.6, 4.6.2, and 4.7, and we hope to continue working with + him as a fellow developer.</p> + + <p>Scott Long has graciously offered to help improve the + communication between the RE team and the rest of the developer + community. We greatly appreciate his assistance.</p> + </body> +</project> + +<project> + <title>jp.FreeBSD.org daily SNAPSHOTs project</title> + + <contact> + <person> + <name> + <given>Makoto</given> + <common>Matsushita</common> + </name> + <email>matusita@jp.FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://snapshots.jp.FreeBSD.org/">Project Webpage</url> + <url href="http://www.jp.FreeBSD.org/snapshots/">Project Webpage (in Japanese)</url> + </links> + + <body> + <p>Recent 5-current release procedure troubles prevent the + project from releasing a new snapshots. But 5-current FreeBSD/i386 + release is back again in late Oct/2002! I have a plan to build + daily FreeBSD/sparc64 snapshots for 5-current. Stay tuned...</p> + </body> +</project> + +<project> + <title>FreeBSD/sparc64 Status Report</title> + + <contact> + <person> + <name> + <given>Jake</given> + <common>Burkholder</common> + </name> + <email>jake@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Thomas</given> + <common>Moestl</common> + </name> + <email>tmm@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>A lot has happened recently for the sparc64 port. Sysinstall and + make release work and can be used to build installable snapshots. + The gdb5.3 port now works, and, thanks to Thomas Moestl, kernel crash + dumps are supported which can be analyzed by gdb. These 2 items are + the last things considered necessary by the Core team for FreeBSD/sparc64 + to be a Tier 1 architecture, which means that 5.0-RELEASE for sparc64 + will be officially supported by the release engineering team and by the + security officer team.</p> + + <p>Recently Jake Burkholder has been working on alternate installation + methods other than bootable iso, including a mini-root filesystem which + can be written to the swap partition of an existing machine. Thomas + Moestl has been putting some finishing touches on the release process, + ensuring that the release documentation can be built properly, and that + the port readme files can be generated by the release process.</p> + + <p>An experimental iso built with make release is now available on the + freebsd ftp site and mirrors in + /pub/FreeBSD/development/sparc64/5.0-20021031-SNAP. It is expected that + by the middle of November new 5.0-SNAP releases will be available every + few days for download and for ftp install, cpu power and bandwidth + permitting.</p> + </body> +</project> + +<project> + <title>TrustedBSD Project</title> + + <contact> + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + <person> + <name> + <common>TrustedBSD Discussion Mailing List</common> + </name> + <email>trustedbsd-discuss@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/">TrustedBSD web site</url> + </links> + + <body> + <p>Most progress on TrustedBSD over the last two months related + to improving the maturity of the ACL and MAC implementations, + and merging new aspects of those features into the primary + FreeBSD CVS Repository for inclusion in FreeBSD 5.0. This + included fixes to run better on sparc64, improved tuning + of what system objects are mediated, locking fixes and + optimizations especially relating to the vnode and pipe + implementations, improved support for MAC labeling on symlinks, + support for asynchronous process label changes as required + in some locking situations, remove use of "temporary labels" + and prefer use of object type specific labels reducing + redundant and/or confusing label management code in policies, + improve avoidance of memory allocation in M_NOWAIT scenarios + for socket allocation in the syncache, mediation of link + operations, race condition fixes for devfs involving label + creation, improve handling of VM events such as mmaping, + improve mediation of socket send/receive events (as + distinguished from socket transmit/deliver events), support + for manipulating EAs on symlinks using new system calls, + support for MNT_ACLS and MNT_MULTILABEL flags at mount time, + as well as FS_ACLS and FS_MULTILABEL superblock flags to + key useful defaults using tunefs, correction of a memory leak + in the UFS ACL code, enable UFS ACL support by default in + GENERIC, mediation points for file creation, deletion, and + rename, support for a mac_execve() execution interface in + the style of SELinux's execve_secure() permitting a label + transition request as part of the exec operation for policies + that support it, more consistent handling of NFS lookups, + support for labeling of multicast encapsulated packets, ATM + packet labeling, FDDI packet labeling, STF packet labeling, + revised label interface that avoids userland parsing of + per-policy elements, reducing us to a single instance of + parsing and printing for each policy (and further abstracting + policy implementation details from the library code).</p> + + <p>Also, change to single-level sockets for Biba and MLS + policies, support for partial label updates for Biba and MLS, + addition of mac.9 man page, revised user API system calls, + implementation of mac_get_pid(), and various other related + bits, creation of mac.conf(5) to specify label defaults, + checks for various system operations including swapon(), + settime(), and sysctl(), reboot(), acct(), introduction of + command line utilities for maintaining file and process labels, + support for user labels tied to login class, su support for + label changes, ifconfig support for interface labels, ps + support for process labels, ls support for file labels, ftpd + support for login labels, development of the Biba and MLS + notions of privilege, and a move to C99 sparse structure + initialization, restoring full type checking for policy entry + points.</p> + </body> +</project> + +<project> + <title>OSF DCE 1.1 RPC UUIDs</title> + + <contact> + <person> + <name> + <given>Marcel</given> + <common>Moolenaar</common> + </name> + <email>marcel@FreeBSD.org</email> + <person> + <name> + <given>Hiten</given> + <common>Pandya</common> + </name> + <email>hiten@uk.FreeBSD.org</email> + </person> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/cgi/cvsweb.cgi/src/lib/libc/uuid" /> + </links> + + <body> + <p>Universally Unique Identifiers (UUIDs) are 128 bit values that may + be generated independently on separate nodes (hosts), which result in + globally unique strings. UUIDs are also known as Globally Unique + Identifiers (GUIDs). The UUID support for FreeBSD (libc) conforms to the + DCE 1.1 RPC specification.</p> + + <p>UUID support has been added to FreeBSD -CURRENT, and will be available + in version 5.0. It is being extensively used in GPT partition handling + for IA-64 platform. For now, a simple manual page has been provided, + which outlines information about the provided uuid routines. Many + documentation additions and enhancements to uuidgen(1) are in the + pipeline.</p> + </body> +</project> + +<project> + <title>Wireless Networking Status</title> + + <contact> + <person> + <name> + <given>Sam</given> + <common>Leffler</common> + </name> + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The goal of this project is to improve the wireless networking support + in the system. The initial work will incorporate the 802.11 link layer + done by Atsushi Onoe for NetBSD. This core support code implements the + basic 802.11 protocols required for Station and AP operation in BSS, IBSS, + and Ad Hoc modes of operation. Wireless device drivers will then be revised + to use this common code instead of their private implementations.</p> + + <p>Following this initial stage the wireless networking support will be + extended to support functionality needed for workgroup, enterprise, and + metropolitan (e.g. mesh) networking environments. This will include full + power management support, the 802.1D spanning tree protocol for running + multiple AP's in a bridged configuration, QoS support, and enhanced + security protocols (LEAP, AES, EAP). Support for new hardware devices is + also planned.</p> + </body> +</project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2002-11-2002-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2002-11-2002-12.xml new file mode 100644 index 0000000000..52db54df8e --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2002-11-2002-12.xml @@ -0,0 +1,881 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2002-11-2002-12.xml,v 1.7 2007/04/11 04:11:09 brd Exp $ --> + +<report> + <date> + <month>November-December</month> + <year>2002</year> + </date> + + <section> + <title>Introduction:</title> + + <p>At long last, FreeBSD 5.0 is here. Along with putting the final + polish on the tree, FreeBSD developers somehow found the time to + work on other things too. IA64 took some major steps towards + working on the Itanium2 platform, an effort was started to + convert all drivers to use busdma and ban vtophys(), hardware + crypto support and DEVD hit the tree, NewReno was fixed and + effort began on locking down the network layer of the kernel. + Also high performance, modular scheduler started taking shape + and will be a welcome addition to the kernel soon.</p> + + <p>Looking forward, the focus will be on stabilizing and + improving the performance of 5.0. The RELENG_5 (aka 5-STABLE) + branch will be created once we've reached our goals in this + area, so hopefully we will get there quickly. Meanwhile, + preparations for the next release from the 4.x series, 4.8, + will begin soon. Of course, the best way to get 5.x to + stabilize os to install and run it!</p> + + <p>Thanks,</p> + + <p>Scott Long, Robert Watson</p> + </section> + +<project> + <title> + Bluetooth stack for FreeBSD (Netgraph implementation) + </title> + + <contact> + <person> + <name> + <given>Maksim</given> + <common>Yevmenkin</common> + </name> + + <email>m_evmenkin@yahoo.com</email> + </person> + </contact> + + <links> + <url href="http://www.geocities.com/m_evmenkin/">Latest snapshot</url> + + <url href="http://bluez.sf.net">Linux BlueZ stack</url> + + <url href="http://sourceforge.net/projects/openobex">OpenOBEX</url> + </links> + + <body> + <p>I'm very pleased to announce that all kernel modules and few userland + tools made it to the FreeBSD source tree. Many thanks to Julian + Elischer.</p> + + <p>Unfortunately no big changes since the last report. Some minor problems + have been discovered and patches are available on request. I will prepare + all the patches and submit them to Julian for review.</p> + + <p> OBEX server and client (based on OpenOBEX library) is almost complete. + I'm currently doing interoperability testing. If anyone has hardware and + time please contact me. The HCI security daemon has been implemented and + tested with Sony Ericsson T68i cell phone and Windows stack. It is now + possible to setup secure Bluetooth connections.</p> + + <p>A few people have complained about RFCOMM daemon. These individuals want + to use GPRS and Bluetooth enabled cell phone to access Internet. If you + have this problem please contact me for possible workaround. My next goal + is to get robust RFCOMM implementation to address all these issues.</p> + </body> +</project> + +<project> + <title>TrustedBSD Project: Access Control Lists</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + <person> + <name> + <common>TrustedBSD Discussion List</common> + </name> + + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/">TrustedBSD Project</url> + </links> + + <body> + <p>Largely bug-fixing and userland application tweaks; new + interfaces were added to manipulate ACLs on extended attributes; + bugs were fixed in ls relating to ACL flagging. Patches to + teach cp, mv, gzip, bzip, and other apps about ACL preservation + are in testing and review. tunefs flags were added to ease + configuration of ACLs, especially on UFS2 file systems.</p> + <p>Possible changes to make use of Linux/Solaris umask semantics + are under consideration: right now we implement verbatim + POSIX.1e/IRIX merging of the umask, ACL mask, and requested + creation mode during file, device, fifo, and directory creation. + Solaris and the most recent Linux patches ignore the umask in + the context of a default ACL; this requires some rearrangement + of umask handling in our VFS, although the results would be + quite useful. We're exploring how to do this in a low impact + way.</p> + </body> +</project> + +<project> + <title>TrustedBSD Project: MAC Framework</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + <person> + <name> + <common>TrustedBSD Discussion List</common> + </name> + + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/">TrustedBSD Project</url> + </links> + + <body> + <p>Framework changes:</p> + <p>Instrument KLD system calls (module and kld load, unload, stat) + Instrument NFSd system call. Instrument swapoff(2). + Instrument per-architecture privileged parts of sysarch(). + Make use of condition variables to allow callers to wait for the + framework to "unbusy" when loading/unloading policies, rather than + returning EBUSY. Store mount pointer in devfs_mount structure for + use by policies. Improve handling of labels in loopback interface + "re-align" packet copy case. Provide full paths on devfs object + creations to help policies label them properly (not merged). + Experimentation with moving MAC labels into m_tags (not merged). + NFS server now uses real ucreds, not hacked up ucreds, + meaning we can start laying the groundwork for enforcement on + NFS operations. (not merged)</p> + + <p>Policy changes</p> + <p>LOMAC: mac_lomac replaces lomac (LOMAC now uses the MAC Framework), + SEBSD: Improved support for devfs labeling based on SELinux genfs. + Handling of hard link checks. Support export of process transition + information for login and others using sysctl. Login now prompts + for roles. Allow policy reload. TTY labeling. Locking adaptation + from Linux. Many, many policy adaptations and fixes. We can + now boot in enforcing mode! mac_bsdextended: fix a bug in which + VAPPEND wasn't mapped to VWRITE, so opens with the O_APPEND bug + failed improperly.</p> + + <p>Userland changes</p> + <p>setfmac(8) now supports a setfsmac(8) execution mode, which accepts + initial labeling specification files. Supports an SELinux compatibility + mode so it can accept SELinux label specfiles using the SEBSD module. + sendmail(8) now sets user labels as part of the context switch for mail + delivery.</p> + + <p>Documentation changes</p> + <p>Man page updates for MAC command line tools, modules, admin hints, etc. + Updates to the FreeBSD Developer's Handbook chapter on MAC policies + and entry points. MAC section in FreeBSD Handbook.</p> + </body> +</project> + +<project> + <title>busdma driver conversion project</title> + + <contact> + <person> + <name> + <given>Maxime</given> + + <common>Henrion</common> + </name> + + <email>mux@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/busdma/" /> + </links> + + <body> + <p>This project has been coming along pretty well. The amd(4) and + xl(4) drivers have now been converted to use the busdma API, + sparc64 got the bus_dmamap_load_mbuf() and bus_dmamap_load_uio() + functions, and the gem(4) and hme(4) drivers have been updated + to use bus_dmamap_load_mbuf() instead of bus_dmamap_load().</p> + + <p>A lot more still needs to be done, as shown on the project's + page. A fair number of conversions are on their way though, + and we can expect a fair number of drivers to be converted + soon, thanks to all the developers who are working on this + project.</p> + </body> +</project> + +<project> + <title>FreeBSD C99 & POSIX Conformance Project</title> + + <contact> + <person> + <name> + <given>Mike</given> + <common>Barcroft</common> + </name> + + <email>mike@FreeBSD.org</email> + </person> + <person> + <name> + <common>FreeBSD-Standards Mailing List</common> + </name> + + <email>standards@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/c99/" /> + <url href="http://people.FreeBSD.org/~schweikh/posix-utilities.html" /> + </links> + + <body> + <p>The POSIX Utility Conformance in FreeBSD list (link above) has + been updated to reflect current reality. Not much work remains + to complete base utility conformance.</p> + + <p>On the API front, grantpt(), posix_openpt(), unlockpt(), + wordexp(), and wordfree() were implemented. The header + <wordexp.h> was added.</p> + + <p>There are currently about 40 unassigned tasks on our project's + status board ranging from documentation, utilities, to kernel + hacking. We would encourage any developers looking for something + to work on to check out the status board and see if anything + interests them.</p> + </body> +</project> + +<project> + <title>Hardware Crypto Support Status</title> + + <contact> + <person> + <name> + <given>Sam</given> + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The goal of this project is to import the OpenBSD kernel-level crypto + subsystem. This facility provides kernel- and user-level access to + hardware crypto devices for the calculation of cryptographic hashes, + ciphers, and public key operations. The main clients of this facility + are the kernel RNG (/dev/random), network protocols (e.g. IPsec), and + OpenSSL (through the /dev/crypto device).</p> + + <p>This work will be part of the 5.0 release and has been committed to + the -stable source tree for inclusion in the 4.8 release.</p> + + <p>Recent work has focused on improving performance. System statistics are + now maintained and an optional profiling facility was added for + analyzing performance. Using this facility the overhead for using the + crypto API has been significantly reduced.</p> + + <p>The ubsec (Broadcom) driver was changed to significantly improve + performance under load. In addition several memory leaks were fixed in + the driver and the public key support was enabled for use.</p> + + <p>Upcoming work will focus on load-balancing requests across multiple + crypto devices and integrating OpenSSL 0.9.7 which will automatically + enable application use of crypto hardware.</p> + </body> +</project> + +<project> + <title>DEVD</title> + + <contact> + <person> + <name> + <given>Warner</given> + <common>Losh</common> + </name> + + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Devd has been integrated into FreeBSD 5.0-RELEASE. The + integrated code supports a range of configuration options. The + config files are fully parsed now and their actions are + performed.</p> + + <p>Future work in this area is likely to be limited to improving + the devctl interface. /dev/devctl likely will be a cloneable + device in future versions. Individual device control via devctl + is also planned.</p> + </body> +</project> + +<project> + <title>Donations Team Status Report</title> + + <contact> + <person> + <name> + <given>Michael</given> + <common>Lucas</common> + </name> + + <email>donations@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/donations/">Donations main page</url> + <url href="http://www.FreeBSD.org/donations/wantlist.html">FreeBSD + developer wantlist</url> + <url href="http://www.FreeBSD.org/donations/donors.html"> + completed donations</url> + </links> + + <body> + <p>The Donations project expedited several dozen donations during + 2002, and was able to place most of what was offered. We still + are in dire need of SMP and Sparc systems. You can see + information on our needs and donations that have been handled by + the team on the donations web page.</p> + + <p>We are relying increasingly upon the developer wantlist to + place items offered to the Project, and using the commit + statistics to help place items. As such, active committers who + ask for what they want beforehand have a decent chance of + getting it. Less active committers, and committers who do not + ask for what they want, will be lower in our priorities but will + not be excluded.</p> + + <p>We are in the process of streamlining the tax deduction process + for donations, and hope to have news on that shortly. We are + also always working to accelerate and reduce our internal + processes, to get the most equipment in the hands of the most + people as quickly as possible.</p> + + <p>I especially want to thank David O'Brien and Tom Rhodes for + stepping up and making the team far more successful. Also, the + FreeBSD Foundation has been quite helpful in handling + tax-deductible contributions.</p> + </body> +</project> + + + +<project> + <title>Fast IPsec Status</title> + + <contact> + <person> + <name> + <given>Sam</given> + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The main goal of this project is to modify the IPsec protocols to use + the kernel-level crypto subsystem imported from OpenBSD (see elsewhere). + A secondary goal is to do general performance tuning of the IPsec + protocols.</p> + + <p>This work will be part of the 5.0 release. Performance has been improved + due to work on the crypto subsystem.</p> + </body> +</project> + +<project> + <title>FFS volume label support</title> + + <contact> + <person> + <name> + <given>Gordon</given> + <common>Tetlow</common> + </name> + + <email>gordon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~gordon/patches/volume.diff">Current patch set.</url> + </links> + + <body> + <p>The goal of the project is to use a small amount of space in the FFS + superblock to store a volume label of the user's choice. A GEOM module + will then expose the volume labels into a namespace in devfs. The idea + is to make it easier to manage filesystems across disk swaps and + movement from system to system.</p> + + <p>At this point, everything pretty much works. I've submitted parts of + the patch to respective subsystem maintainers for review. There are some + issues with namespace collision that I haven't addressed yet, but the + basic functionality is there</p> + </body> +</project> + +<project> + <title>French FreeBSD Documentation Project</title> + <contact> + <person> + <name> + <given>Sebastien </given> + <common>Gioria</common> + </name> + + <email>gioria@FreeBSD.org</email> + </person> + <person> + <name> + <given>Marc </given> + <common>Fonvieille</common> + </name> + <email>blackend@FreeBSD.org</email> + </person> + <person> + <name> + <given>Stéphane</given> + <common>Legrand</common> + </name> + <email>stephane@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd-fr.org">The French FreeBSD Documentation Project.</url> + <url href="http://www.freebsd-fr.org/index-trad.html">The FreeBSD Web Server translated in French.</url> + <url href="http://people.FreeBSD.org/~blackend/doc/fr_FR.ISO8859-1/books/handbook/"> Translation of the hanbook.</url> + <url href="http://www.FreeBSD-fr.info">French Daemon News like web site.</url> + </links> + + <body> + <p>Most of the articles are translated too. Marc is still translating the + handbook, 60% is currently translated. Stéphane has began the + integration of our French localization web site in the US CVS Tree. + Sébastien is still maintaining the Release Notes.</p> + + <p>We launched a new site, www.FreeBSD-fr.info, consisting in a French + Daemon News like site. Netasq have donated our new server; we will + install it in a new hosting provider in the few next weeks. One of the + big job now is the translation of the FAQ, and the big + project will be the manual pages.</p> + </body> +</project> + +<project> + <title>FreeBSD GNOME Project</title> + + <contact> + <person> + <name> + <given>Joe</given> + <common>Marcus</common> + </name> + + <email>marcus@FreeBSD.org</email> + </person> + <person> + <name> + <given>Maxim</given> + <common>Sobolev</common> + </name> + + <email>sobomax@FreeBSD.org</email> + </person> + <person> + <name> + <given>Adam</given> + <common>Weinberger</common> + </name> + + <email>adamw@FreeBSD.org</email> + </person> + + </contact> + + <links> + <url href="http://www.FreeBSD.org/gnome/">FreeBSD GNOME Project + Homepage.</url> + </links> + + <body> + <p>Since the ports tree has been frozen for most of this reporting period, + there have not been too many GNOME updates going into the official CVS + tree. However, development has not stopped. GNOME 2.2 is nearing + completion, and quite a few FreeBSD users have stepped up to test the + GNOME 2.1 port sources from the + <a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi">MarcusCom + CVS repository</a>. If anyone else is interested, follow the + instructions on the aforementioned cvsweb URL, and checkout the "ports" + module.</p> + + <p>The upcoming FreeBSD 5.0-RELEASE will be the first release to have the + GNOME 2.0 desktop as the default GNOME desktop choice. During the + previously mentioned ports freeze, all the GNOME 2 ports were fixed up + so that they build and package on both i386 and Alpha platforms. Alas, + the one port that will not make the cut for Alpha is Mozilla. There are + still problems with the xpcom code, but work is ongoing to get a working + Alpha port.</p> + + <p>Finally, the FreeBSD Mono (an OpenSource C# runtime) port has also + received some new life. Mono has been updated to 0.17 (the latest + released version), and Juli Mallett has ported gtk-sharp (GTK+ bindings + for C#).</p> + </body> +</project> + +<project> + <title>FreeBSD/ia64 Status</title> + + <contact> + <person> + <name> + <given>Peter</given> + <common>Wemm</common> + </name> + + <email>peter@FreeBSD.org</email> + </person> + <person> + <name> + <given>Marcel</given> + <common>Moolenaar</common> + </name> + + <email>marcel@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~peter/ia64.diff" /> + <url href="http://www.FreeBSD.org/platforms/ia64/" /> + </links> + + <body> + <p>The ia64 port is up and running on the new Itanium2 based hp + machines thanks to a lot of hard work by Marcel Moolenaar. So + far we are running on the hp rx2600 as these were the machines + graciously donated by Hewlett-Packard and Intel. We had a + prototype Intel Tiger4 system for a while, but we had to return + the machine and we do not know if it currently runs. Most of + the changes necessary to run these are sitting in the perforce + tree and are not in the -current or RELENG_5 cvs tree. As a + result, the cvs derived builds (-current and the 5.0-RC series + and presumably 5.0-RELEASE) are only usable on obsolete Itanium1 + systems.</p> + + <p>Lots of other stability and functionality fixes have been made + over the last few months, including initial libc_r support. The + OS appears to be stable enough for sustained workloads - it is + building packages now, for example. We still do not have gdb + support, even for reading core files.</p> + </body> +</project> + +<project> + <title>jpman project</title> + + <contact> + <person> + <name> + <given>Kazuo</given> + <common>Horikawa</common> + </name> + + <email>horikawa@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.jp.FreeBSD.org/man-jp/">jpman project</url> + </links> + + <body> + <p>We have been updating our Japanese translated manual pages to + RELENG_5 based. All existing entries have been updated, but 15 + exceptions are not, most of which require massive update. We + will also need to add translations which did not exist on RELENG_4.</p> + </body> +</project> + +<project> + <title>KGI/FreeBSD Status Report</title> + + <contact> + <person> + <name> + <given>Nicholas</given> + <common>Souchu</common> + </name> + + <email>nsouch@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~nsouch/ggiport.html" /> + <url href="http://www.kgi-project.org" /> + </links> + + <body> + <p>KGI (Kernel Graphic Interface) is a kernel infrastructure providing user + applications with means to access hardware graphic resources (dma, + irqs, mmio). KGI is already available under Linux as a separate + standalone project. The KGI/FreeBSD project aims at integrating KGI + in the FreeBSD kernel.</p> + + <p>KGI/FreeBSD has been recently donated 2 PCI graphic cards (Matrox + Millennium II and a coming Mach64) and other have been proposed. + Please see the FreeBSD web pages for details. Thanks to donation@ for + organizing and promoting donations. Thanks to the donators for their + contribution to KGI/FreeBSD.</p> + + <p>KGI/FreeBSD progressed fine the last months. Most of the VM issues for + mapping HW resources in user space have been addressed and a first + attempt of coding was made. This prototyping raised some API + compatibility problems with the current Linux implementation and was + discussed heavily on the kgi devel lists. Ask if you're + interested in such issues, I'll be pleased to share them.</p> + + <p>Most of coding is now done. Let's start debugging!</p> + </body> +</project> + +<project> + <title>SMP locking for network stack</title> + + <contact> + <person> + <name> + <given>Jeffrey</given> + <common>Hsu</common> + </name> + + <email>hsu@FreeBSD.org</email> + </person> + </contact> + + <body> + <p> Work is ongoing to continue to lock up the network stack. + Recently, the focus has been on the IP stack. The plan there + involves a series of inter-related pieces to lock up the + ifaddr ref count, the inet list, the ifaddr uses, the ARP code, + the routing tree, and the routing entries. We are over 3/5 of + the way done down this path.</p> + + <p>In addition to TCP and UDP, the other networking protocols + such as raw IP, IPv6, AppleTalk, and XNS need to be locked up. + Around 1/4 these remaining protocols have been locked and + will be committed after the IP stack is locked.</p> + + <p>The protocol independent socket layer needs to be locked and + operating correctly with the protocol dependent locks. This + part is mostly done save for much needed testing and code cleanup.</p> + + <p>Finally, a pass will be need to be made to lock up the devices drivers + and various statistics counters.</p> + </body> +</project> + +<project> + <title>TCP congestion control</title> + + <contact> + <person> + <name> + <given>Jeffrey</given> + <common>Hsu</common> + </name> + + <email>hsu@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>This effort fixes some outstanding problems in our TCP + stack with regard to congestion control. The first + item is to fix our NewReno implementation. Following that, + the next urgent correction is to fix a problem involving window updates + and dupack counts. When that stabilizes, we will then change + the recovery code to make use of SACK information. + Eventually, this project will update the BSD stack to add Limited Transmit + and other new internet standards and standards-track improvements.</p> + </body> +</project> + +<project> + <title>FreeBSD Package Cluster work</title> + + <contact> + <person> + <name> + <given>Kris</given> + <common>Kennaway</common> + </name> + + <email>kris@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://bento.FreeBSD.org/" /> + </links> + + <body> + <p>The 3 FreeBSD package clusters (i386, alpha, sparc64) have been + unified to run from the same master machine, instead of using 3 + separate masters. This has freed up some machine resources to + use as additional client machine, as well as simplifying + administrative overheads. Build logs for all 3 architectures + can now be found on the http://bento.FreeBSD.org webpage. The + sparc64 package cluster now has 3 build machines (an u5 and two + u10s), and an ia64 cluster is about to be created.</p> + + <p>Package builds now keep track of how many sequential times a + port has failed to build (html summaries are available on the + bento website). This allows tracking of ports which have + suddenly become broken (e.g. due to a bad upgrade, or due to + changes in the FreeBSD source tree), and in the future will be + used to send out notifications to port maintainers when their + port fails to build 5 times in a row. This feature is currently + experimental, and further code changes will be needed to + stabilize it.</p> + </body> +</project> + +<project> + <title>Wireless Networking Status</title> + + <contact> + <person> + <name> + <given>Sam</given> + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The goal of this project is to improve the wireless networking support in + the system. By the time of this report the 802.11 link layer code should + be committed. A version of the wi driver that uses this code should be + committed shortly. Conversion of other drivers is planned as are drivers + for new devices.</p> + + <p>Support for 802.1x/EAP is the next planned milestone (both as a + supplicant and authenticator).</p> + </body> +</project> + +<project> + <title>FreeBSD Release Engineering</title> + + <contact> + <person> + <name> + <given>Scott</given> + <common>Long</common> + </name> + + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/index.html">Release Engineering + Homepage</url> + </links> + + <body> + <p>November and December were especially busy for the release engineering + team. Scott Long joined the team to help with secretary and + communications tasks while Brian Somers bowed out to focus on other + projects.</p> + + <p>FreeBSD 5.0-DP2 was released in November after much delay and + anticipation, and marked the final milestone needed for 5.0 to + become a reality. Shortly after that, we imposed a code freeze on + the HEAD branch of CVS and released 5.0-RC1. Creation of the + RELENG_5_0 branch came next, followed by the release of 5.0-RC2 from + this branch. At this point, enough critical problems still existed + that we scheduled an RC3 release for the new year, and pushed the + final 5.0-RELEASE date to mid-January. By the time this is published, + FreeBSD 5.0-RELEASE should be a reality.</p> + + <p>For the time being, there will not be a RELENG_5 (aka 5-STABLE) + branch. FreeBSD 4.x releases will continue, with 4.8 being + scheduled for March 2003. Release in the 4.x series will be + lead by Murray Stokely, and releases in the 5.x series will be + lead by Scott Long. Once HEAD has reached acceptable performance + and stability goals, the RELENG_5 branch will be created and HEAD + will move towards 6.0 development. We hope to reach this with + the 5.1 release this spring.</p> + </body> +</project> + +<project> + <title>SMP aware scheduler</title> + + <contact> + <person> + <name> + <given>Jeff</given> + <common>Roberson</common> + </name> + + <email>jeff@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>A new scheduler will be available as an optional component along side + the current scheduler in the 5.1 release. It has been designed to + work well with KSE and SMP. Some ideas have been borrowed from solaris + and linux along with many novel approaches. It has O(1) performance + with regard to the number of processes in the system. It also has + cpu affinity which should provide a speed boost for many applications.</p> + + <p>The scheduler has a few loose ends and lots of tuning before it is + production quality although it is quite stable. Please see the post + to arch and subsequent discussion for more details.</p> + </body> +</project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2003-01-2003-02.xml b/en_US.ISO8859-1/htdocs/news/status/report-2003-01-2003-02.xml new file mode 100644 index 0000000000..7f6b4c87f0 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2003-01-2003-02.xml @@ -0,0 +1,704 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2003-01-2003-02.xml,v 1.6 2006/08/19 21:20:40 hrs Exp $ --> + +<report> + <date> + <month>January-February</month> + <year>2003</year> + </date> + + <section> + <title>Introduction:</title> + + <p>Another busy two months have passed in the FreeBSD project. With + 5.0 released, attention is focusing on making it faster via more + fine-grained locking, adding more high-end features like large + memory (PAE) support for i386, and further progress on many other + projects. FreeBSD 5.1 is expected to ship in late May or early + June, with 5.2 following at the end of summer. A roadmap for + the push to 5-STABLE is available at <a + href="http://www.FreeBSD.org/doc/en/articles/5-roadmap"> + http://www.FreeBSD.org/doc/en/articles/5-roadmap</a>. Although + the 5.x series isn't expected to fully stabilize until the 5.2 + release, 5.1 promises to be an exciting release and a significant + improvement over 5.0 in terms of speed and stability.</p> + + <p>Not to be forgotten, FreeBSD 4.8, the latest in the 4-STABLE + series, is nearing release. Lots of last minute work is going + into to it to deliver features like XFree86 4.3.0, Intel + HyperThreading(tm) support, and of course many more bug fixes. + Don't forget to support the FreeBSD vendors and developers by + buying a copy of the CD set when it comes out!.</p> + + <p>Thanks,</p> + + <p>Scott Long, Robert Watson</p> + </section> + +<project> + <title>FreeBSD/MIPS Status Report</title> + + <contact> + <person> + <name> + <given>Juli</given> + <common>Mallett</common> + </name> + <email>jmallett@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/mips/">FreeBSD/MIPS project + page.</url> + <url href="http://www.FreeBSD.org/platforms/mips.html">FreeBSD/MIPS + platform page.</url> + </links> + + <body> + <p>Large portions of headers have been filled in, all have been stubbed + out. Minimal functions and data elements have been stubbed out or + filled in. Machinery added to support some requisite tunables for + building real kernels. GCC fixed to generate correct local label + prefixes making it possible to link real kernels. Work begun on + providing enough to create and boot real kernels, on real hardware. + Decision to only support MIPS-III and above made.</p> + </body> +</project> + +<project> + <title>BSDCon 2003</title> + + <contact> + <person> + <name> + <given>Gregory</given> + <common>Shapiro</common> + </name> + <email>gshapiro@FreeBSD.org</email> + </person> + </contact> + + <links> + <!-- A hypertext link with a description... --> + <url href="http://www.usenix.org/events/bsdcon03/cfp/">BSDCon 2003 Call For Papers</url> + </links> + + <body> + + <p>The BSDCon 2003 Program Committee invites you to contribute + original and innovative papers on topics related to BSD-derived + systems and the Open Source world. Topics of interest include + but are not limited to:</p> + + <ul> + <li>Embedded BSD application development and deployment</li> + <li>Real world experiences using BSD systems</li> + <li>Using BSD in a mixed OS environment</li> + <li>Comparison with non-BSD operating systems; technical, practical, licensing (GPL vs. BSD)</li> + <li>Tracking open source development on non-BSD systems</li> + <li>BSD on the desktop</li> + <li>I/O subsystem and device driver development</li> + <li>SMP and kernel threads</li> + <li>Kernel enhancements</li> + <li>Internet and networking services</li> + <li>Security</li> + <li>Performance analysis and tuning</li> + <li>System administration</li> + <li>Future of BSD</li> + </ul> + + <p>Submissions in the form of extended abstracts are due by + April 1, 2003. Be sure to review the extended abstract + expectations before submitting. Selection will be based on the + quality of the written submission and whether the work is of + interest to the community.</p> + + <p>We look forward to receiving your submissions!</p> + + </body> +</project> + +<project> + <title> + Bluetooth stack for FreeBSD (Netgraph implementation) + </title> + + <contact> + <person> + <name> + <given>Maksim</given> + <common>Yevmenkin</common> + </name> + <email>m_evmenkin@yahoo.com</email> + </person> + </contact> + + <links> + <url href="http://www.geocities.com/m_evmenkin/">Latest snapshot</url> + <url href="http://bluez.sf.net">Linux BlueZ stack</url> + <url href="http://sourceforge.net/projects/openobex/">OpenOBEX</url> + </links> + + <body> + <p>I'm very pleased to announce that another release is available for + download at <a + href="http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030305.tar.gz"> + http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030305.tar.gz</a></p> + + <p>This release features new in-kernel RFCOMM implementation that + provides SOCK_STREAM sockets interface. This makes old user-space + RFCOMM daemon obsolete. People should not use old user-space + RFCOMM daemon any longer. The release features new RFCOMM PPP + daemon that supports DUN and LAN profiles. Note: PPP patch + (support for chat scripts in -direct mode) is required for DUN + support. Look for it in the mailing list archive or contact me + directly. People with Bluetooth enabled cell phones can now + use them to access Internet.</p> + + <p>The Bluetooth sockets layer has been cleaned up. People should not + see any WITNESS complaints with new code. Locking issues have been + revisited and code in much better shape now, although it probably + is not 100% SMP ready just yet. The code should work on SMP system + anyway because sockets layer is still under Giant.</p> + + <p>The simple OBEX server and client (based on OpenOBEX library) is + complete. OBEX File Push and OBEX File Transfer profiles work and + have been tested with Sony Ericsson T68i cell phone and Bluetooth + 3COM stack on Windows2K. It is now possible to send pictures, + address book and calendar entries from the cell phone via + Bluetooth. Minor bug in OpenOBEX library has been fixed and OPEX + Put-Empty command now works.</p> + + <p>Due to changes in API userland tools must be in sync with the + kernel. People should install new include files, recompile and + reinstall all userland tools as part of upgrade. I'm sorry about + that.</p> + </body> +</project> + +<project> + <title>FreeBSD 4.8 Release Engineering</title> + + <contact> + <person> + <name> + <given>Murray</given> + <common>Stokely</common> + </name> + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releases/4.8R/schedule.html">FreeBSD + 4.8 Release Schedule.</url> + </links> + + <body> + <p>The FreeBSD 4.8 Release Process is well underway. The RELENG_4 + branch has been under code freeze since February 15, and + the first release candidates were made available in early March. + A testing guide has been put together and is available from + http://www.FreeBSD.org/releases/4.8R/qa.html.</p> + + <p>Developers should coordinate with re@FreeBSD.org about any + changes they would like to include in this release, and users + are encouraged to try out the release candidates and help find + as many bugs as possible now, before the final release is + made.</p> + + <p>FreeBSD 4.8 represents the newest production release from the + stable '4.X' branch. It does not include all of the features + that were made available in the "new technology" 5.0 + release in January.</p> + </body> +</project> + +<project> + <title>New Doceng Body Formed</title> + + <contact> + <person> + <name> + <given>Murray</given> + <common>Stokely</common> + </name> + <email>doceng@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/internal/doceng.html" /> + </links> + + <body> + <p>The doceng@ team is a new body to handle some of the + meta-project issues associated with the FreeBSD Documentation + Project. The main responsibilities of this team are to grant + approval of new doc committers, to manage the doc release + process, to ensure the documentation toolchains are functional, + to maintain the doc project primer, and to maintain the sanctity + of the doc/ and www/ trees. The current members of this team + are Nik Clayton, Ruslan Ermilov, Jun Kuriyama, Bruce A. Mah, and + Murray Stokely.</p> + </body> +</project> + +<project> + <title>KGI/FreeBSD Status Report</title> + + <contact> + <person> + <name> + <given>Nicholas</given> + <common>Souchu</common> + </name> + <email>nsouch@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~nsouch/ggiport.html" /> + <url href="http://kgi-wip.sf.org" /> + </links> + + <body> + <p>The later months have been very busy on KGI. Most of the framework + has been debugged for typical usage (fb, no accel). I got + KII (the input interface) connected to syscons through atkbd. Opening + /dev/graphic works and framebuffer resource access is permitted. + Finally, the KGIM (KGI module) framework has a better building + tree for board / monitor drivers and board drivers are now loading + with resource allocation.</p> + + <p>Most important on the TODO list: + 5.0-RELEASE move (I currently work with a May-2002 5.0-current). + Most of debug is now done. Let's validate!</p> + + <p>Note that KGI project homepage has changed since the last report.</p> + </body> +</project> + +<project> + <title>jpman project</title> + + <contact> + <person> + <name> + <given>Kazuo</given> + <common>Horikawa</common> + </name> + <email>horikawa@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.jp.FreeBSD.org/man-jp/">jpman project</url> + <url href="ftp://daemon.jp.FreeBSD.org/pub/FreeBSD-jp/man-jp/packages-5.0.0/ja-man-doc-5.0.tbz">package ja-man-doc-5.0.tbz</url> + </links> + + <body> + <p>We have released Japanese translation of 5.0-RELEASE online manual + pages on February 2nd. Most of entries which did not exist on RELENG_4 + were not yet translated. I hope we can finish such entries soon.</p> + </body> +</project> + +<project> + <title>Disk I/O improvements</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + <common>Kamp</common> + </name> + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>We have the first disk device driver (aac) out from under Giant + now, and in certain scenarios it gives improvements up to 20%. + The device driver API was pruned to reflect that NO_GEOM + compatibility is unnecessary, this resulted in approx 1000 + lines less source code, the majority of which were removed + from the device drivers. The new API for cdevsw is a lot simpler + and hopefully less likely to confuse people. The ability to + automatically allocate a device major number has been introduced + and is already used by a handful of drivers. Checks introduced + with this facility has shown that the uniqueness of manually + allocated major numbers had already broken down.<p> + + </p>Work continues on the statistics collection API and on a unified + API for manual configuration of GEOM nodes.</p> + </body> +</project> + +<project> + <title>Support for PAE and >4G ram on x86</title> + + <contact> + <person> + <name> + <given>Jake</given> + <common>Burkholder</common> + </name> + <email>jake@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Support for PAE is mostly complete, and has been checked into the + jake_pae branch. The approach that is being taken to add support for + PAE is to allow the pmap module to view the page table directory as 4 + pages instead of 1, and to avoid using the 3rd level structure, the page + directory pointer table, as much as possible. Due to its small size, 32 + bytes, the PDPT cannot be uniformly recursively mapped, and as such does + not provide a regular multi level structure like the page tables used by + the alpha or x86-64 architectures. What remains to be done for PAE + support is to develop an API for manipulating page table entries which + will allow idempotent 64 bit loads and stores to be used where + necessary.</p> + + <p>Experimental support for >4G ram using PAE has been developed and + checked into the jake_pae_test branch in Perforce. This involved adding + a physical address type separate from virtual addresses, for use by the + vm system and bus code which needs to use physical addresses directly. + Initial testing has shown good results with device drivers that can dma + to 64 bit physical addresses.</p> + + <p>Funding for this project is being provided by DARPA and Network + Associate Laboratories, and hardware support by + <a href="http://www.freebsdsystems.com">FreeBSD Systems</a>.</p> + </body> +</project> + +<project> + <title>FreeBSD Security Officer Team</title> + + <contact> + <person> + <name> + <given>Jacques</given> + <common>Vidrine</common> + </name> + <email>nectar@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/security/"/> + </links> + + <body> + <p>In the period from September 2002 through February 2003, the + FreeBSD Security Team email aliases saw 1297 messages, a much + smaller volume than over the summer (remember the Apache and OpenSSL + worms? 4.6.1 oops I mean 4.6.2-RELEASE?).</p> + + <p>Also during this period: 95 items were added to the SO + issue-tracking database; 39 of these involved the FreeBSD base + system while the rest involved ports. 9 new Security Advisories + were published, 2 of which covered issues unique to FreeBSD.</p> + + <p>In January, the SO published a new PGP key (ID 0xCA6CDFB2, found + on the FTP site and in the Handbook). This aligned the set of those + who possess the corresponding private key with the membership of the + security-officer alias published on the FreeBSD Security web site. + It also worked around an issue with the deprecated PGP key being + found corrupted on some public key servers.</p> + + <p>In February, Mike Tancsa of Sentex donated two machines to + the Security Officer. These have been a great help already in + testing the security branches, preparing patches, and generating + updated binaries. Thank you very much, Mike!</p> + </body> +</project> + +<project> + <title>FreeBSD GNOME Project</title> + + <contact> + <person> + <name> + <given>Joe</given> + <common>Marcus</common> + </name> + <email>marcus@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Maxim</given> + <common>Sobolev</common> + </name> + <email>sobomax@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Adam</given> + <common>Weinberger</common> + </name> + <email>adamw@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/gnome/">FreeBSD GNOME Project + Homepage.</url> + </links> + + <body> + <p>FreeBSD 4.8-RELEASE will continue in the tradition of + 5.0-RELEASE, and include GNOME 2 as the default GNOME desktop. + This means that 4.8 will ship with GNOME 2.2.</p> + + <p>Following on the heels of the recent GNOME 2.2 release, GNOME 2.3 + snapshots are gearing up. The development schedule is + available from <a href="http://www.gnome.org/start/2.3/"> + http://www.gnome.org/start/2.3/</a>. Ports will be + made available the same way they were for the 2.1 development + releases. Stay tuned to freebsd-gnome@ for more details.</p> + + <p>We are currently in another ports freeze in preparation for + 4.8-RELEASE. Following the freeze, a new bsd.gnome.mk will + be committed that effectively removes the USE_GNOMENG macro. + This new version will add support for GNOME 2 as well as + setup backward compatibility for ports that have not yet + been converted to the new GNOME infrastructure. People + interested in testing this new Mk file, can check out + the ``ports'' module following the instructions at + <a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi"> + http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi</a>.</p> + </body> +</project> + +<project> + <title>PowerPC Port</title> + + <contact> + <person> + <name> + <given>Peter</given> + <common>Grehan</common> + </name> + <email>grehan@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work on PowerPC is progressing steadily. The system can now boot + multi-user from the net and disk. ATA-DMA is being integrated with + the ATAng code, and support for older G3 machines is being added.</p> + </body> +</project> + +<project> + <title>FreeBSD C99 & POSIX Conformance Project</title> + + <contact> + <person> + <name> + <given>Mike</given> + <common>Barcroft</common> + </name> + <email>mike@FreeBSD.org</email> + </person> + + <person> + <name> + <common>FreeBSD-Standards Mailing List</common> + </name> + <email>standards@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/c99/" /> + <url href="http://people.FreeBSD.org/~schweikh/posix-utilities.html" /> + </links> + + <body> + <p>January and February were quiet months that saw with them the + addition of some C99 math functions and macros, which include: + fpclassify(), isfinite(), isgreater(), isgreaterequal(), isinf(), + isless(), islessequal(), islessgreater(), isnan(), isnormal(), + and signbit(). Additional C99 math library support is in the + works.</p> + </body> +</project> + +<project> + <title>Buffer Cache lockdown</title> + + <contact> + <person> + <name> + <given>Jeff</given> + <common>Roberson</common> + </name> + <email>jeff@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Most of the file system buffer cache has been reviewed and protected. + The vnode interlock was extended to cover some buffer flag fields so + that a separate interlock was not required. The global buffer queue + data structures were locked and counters were converted to atomic ops. + The BUF_*LOCK functions grew an interlock argument so that buffers + could be safely removed from the vnode clean and dirty lists. The + lockmgr lock is now required for all access to buf fields. This was + not strictly followed before because splbio provided the needed + protection.</p> + + <p>There are a few areas of code that need to be protected and cleaned up + before giant can be pushed down. Most notably the background write + code is currently unsafe without giant. Also, many of the VM bits that + the buffer cache relies on are not safe. This work has been done with + the expectation that the VM and VFS subsystems will be giant free + soon.</p> + </body> +</project> + +<project> + <title>ULE Scheduler</title> + + <contact> + <person> + <name> + <given>Jeff</given> + <common>Roberson</common> + </name> + <email>jeff@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The ULE scheduler has been committed to the 5.0-CURRENT branch. Early + adopters and experimenters are welcome to try it and submit bug + reports. It has shown noticeable performance improvements over the old + scheduler under some workloads. There are currently problems with + nice fairness but otherwise the interactive performance is very good. + More work to improve the load balancing algorithm is required as well. + This should be ready for use by the general FreeBSD user base in the + next month or so.</p> + </body> +</project> + +<project> + <title>Read-ahead performance</title> + + <contact> + <person> + <name> + <given>Jeff</given> + <common>Roberson</common> + </name> + <email>jeff@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Some improvements have been made to the clustered read ahead code. They + allow for many more outstanding IO requests when an application does + sequential access. This has a larger impact on RAID systems than on + single disk systems. The maximum number of file system blocks that we + will read ahead is tunable via the 'vfs.read_max' sysctl. This + optimization has shown a 20% improvement in simple tests.</p> + </body> +</project> + +<project> + <title>Status Report for Newbus lockdown</title> + + <contact> + <person> + <name> + <given>Warner</given> + <common>Losh</common> + </name> + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Locking of the non-obj parts of newbus is nearing completion. + A single lock is used for the device tree. Minimal changes to + subr_bus have so far been necessary to make this work, however + some lock order issues remain. After this + work, it will no longer be necessary to hold Giant to call + device_* routines safely. kobj work is being done by others and + will likely require more extensive design work to make SMP + friendly.</p> + </body> +</project> + +<project> + <title>TCP congestion control</title> + + <contact> + <person> + <name> + <given>Jeffrey</given> + <common>Hsu</common> + </name> + <email>hsu@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The objective of this effort is to improve the performance, stability, + and correctness of the BSD networking stack by adding support for + new standards and standards track proposals while maintaining compliance + with existing specifications. The upcoming 4.8 and 5.1 releases will + be the first ones using the new NewReno logic. Recently, we + implemented the Limited Transmit algorithm (RFC 3042) which benefits + connections with small congestion windows, as happens, for example, + on many short web connections. We also recently added support for larger + sized starting congestion windows as described in RFC 3390. This helps + short TCP connections as well as those with large round-trip delays, + such as those over satellite links.</p> + </body> +</project> + +<project> + <title>SMP locking for network stack</title> + + <contact> + <person> + <name> + <given>Jeffrey</given> + <common>Hsu</common> + </name> + <email>hsu@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The list of subsystems locked up include IP, UDP, TCP, + ifaddr reference counting, syncache, the ifnet list, routing + radix trees, and ARP. These have already been committed into the tree. + In addition, SMP locking for raw IP, divert socket processing, + and Unix domain sockets have also recently been completed and tested. + Work is currently being done in some of the subsystems required + to make parallel networking processing SMP-safe.</p> + </body> +</project> + +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2003-03-2003-09.xml b/en_US.ISO8859-1/htdocs/news/status/report-2003-03-2003-09.xml new file mode 100644 index 0000000000..5f20f33720 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2003-03-2003-09.xml @@ -0,0 +1,974 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2003-03-2003-09.xml,v 1.5 2007/04/11 04:11:09 brd Exp $ --> + +<report> + <date> + <month>March-September</month> + <year>2003</year> + </date> + + <section> + <title>Introduction:</title> + + <p>The FreeBSD Bi-monthly status reports are back! In this edition, we + catch up on seven highly productive months and look forward to + the end of 2003.</p> + + <p>As always, the FreeBSD development crew has been hard at work. Support + for the AMD64 platform quickly sprang up and is nearly complete. KSE + has improved greatly since the 5.1 release and will soon become the + default threading package in FreeBSD. Many other projects are in the + works to improve performance, enhance the user experience, and expand + FreeBSD into new areas. Take a look below at the impressive summary of + work!</p> + + <p>Scott Long, Robert Watson</p> + </section> + +<project> + <title>VideoBSD</title> + + <contact> + <person> + <name> + <given>John-Mark</given> + <common>Gurney</common> + </name> + <email>jmg@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~jmg/videobsd.html">Documentation of + VideoBSD</url> + </links> + + <body> + <p>Still in the planning stage. Working on creating an extensible + interface that is usable for both userland and kernel implementations + for device drivers. Deciding on how to interface userland implemented + device drivers with applications.</p> + </body> +</project> + +<project> + <title>KSE</title> + + <contact> + <person> + <name> + <given>Dan</given> + <common>Eischen</common> + </name> + <email>deischen@FreeBSD.org</email> + </person> + + <person> + <name> + <given>David</given> + <common>Xu</common> + </name> + <email>davidxu@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/kse/index.html">KSE Project + Page</url> + </links> + + <body> + <p>KSE seems to be working well on x86, amd64, and ia64. The + alpha userland bits are done, but a couple of functions are + unimplemented in the kernel. For sparc64, the necessary + functions are implemented in the kernel, but the userland + context switching functions need more attention.</p> + + <p>Since 5.1, efficient scope system threads (no upcalls when they block) + have been implemented, and KSE based pthread library can have both POSIX + scope process threads and scope system threads. It is also possible + that KSE based pthread library can implement pthread both in 1:1 and M:N + mode, I know Dan has such Makefile file patch for libkse not yet + committed.</p> + + <p>KSE program now can work under ULE scheduler, its efficient should be + improved under the new scheduler in future. BSD scheduler is still the + best scheduler for current KSE implement.</p> + </body> +</project> + +<project> + <title>FreeBSD/ia64</title> + + <contact> + <person> + <name> + <given>Marcel</given> + <common>Moolenaar</common> + </name> + <email>marcel@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/platforms/ia64/index.html">Project home + page.</url> + </links> + + <body> + <p>Much has happened since the last bi-monthly report, which was more + than half a year ago. FreeBSD 5.0 and FreeBSD 5.1 have been released + for example. With FreeBSD 5.2 approaching quickly, we're not going + to look back too far when it comes to our achievements. There's too + much ahead of us...</p> + <p>Two milestones have been reached after FreeBSD 5.1. The first is the + ability to support both Intel and HP machines with sources in CVS. + This due to a whole new driver for serial ports, or UARTs. Unfortunately + this still implies that syscons is not configured. That's another task + for another time, but keep an eye on KGI/FreeBSD... + The second milestone is the completion of KSE support. Both M:N and + 1:1 threading is functional on ia64 and the old libc_r library has been + obsoleted. Testing has shown that KSE (i.e. M:N) may well become the + default threading model. It's looking good.</p> + <p>The ABI hasn't changed after 5.1 and the expectation is that it won't + change much. This means that we can think about becoming a tier 1 + platform. This also means we need gdb(1) support. Work on it has been + started but the road is bumpy and long. + Kernel stability also has improved significantly and we typically have + one kernel panic remaining: VM fault on no fault entry. This will be + addressed with the long awaited PMAP overhaul (see below).</p> + <p>Most work for FreeBSD 5.2 will be "sharpening the saw". Get those + loose ends tied. This is a slight change of plan made possible by a + slip in the release schedule. The 5.2 release is not going to be the + start of the -stable branch; it has been moved to 5.3. So, we use the + extra time to prepare the ground for 5.3.</p> + <p>The planned PMAP overhaul will probably be finished after 5.2. This + should address all known issues with SMP and fix those last panics. + As a side-effect, major performance improvements can be expected. More + news about this in the next status reports.</p> + </body> +</project> + +<project> + <title>Disk I/O</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + <common>Kamp</common> + </name> + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The following items are in progress in the Disk I/O area: + Turn scsi_cd.c into a GEOM driver. (Patch out for review). + Turn atapi-cd.c into a GEOM driver. + Turn fd.c into a GEOM driver. + Move softupdates and snapshot processing from SPECFS to UFS/FFS. + Move userland access to device drivers out of vnodes.</p> + <p>Once these preliminaries are dealt with, scatter/gather and + mapped/unmapped support will be added to struct bio/GEOM.</p> + </body> +</project> + +<project> + <title>Binary security updates for FreeBSD</title> + + <contact> + <person> + <name> + <given>Colin</given> + <common>Percival</common> + </name> + <email>cperciva@daemonology.net</email> + </person> + </contact> + + <links> + <url href="http://www.daemonology.net/freebsd-update/" /> + </links> + + <body> + <p>FreeBSD Update is a system for tracking the FreeBSD release + (security) branches. In addition to being faster and more + convenient than source updates, FreeBSD Update also requires + less bandwidth and is more secure than source updates via + CVSup. However, FreeBSD Update is limited; it can only + update files which were installed from an official RELEASE + image and not recompiled locally. Right now I'm publishing + binary updates for 4.7-RELEASE and 4.8-RELEASE; since my + only available box takes 3.5 hours to buildworld, I don't + have enough resources to do any more than that.</p> + + <p>In the near future, I'd like to: Find someone who is + willing to donate a faster buildbox; start building updates + for other releases (at a minimum, for all "supported" FreeBSD + releases); add warnings if a file would have been updated + but can't be updated because it was recompiled locally; add + code to compare the local system against a list of "valid" + MD5 hashes for intrusion detection purposes; and add support + for cross-signing, whereby several machines could build + updates independently to protect against buildbox + compromise.</p> + </body> +</project> + +<project> + <title>Porting OpenBSD's pf</title> + + <contact> + <person> + <name> + <given>Max</given> + <common>Laier</common> + </name> + <email>max@love2party.net</email> + </person> + <person> + <name> + <given>Pyun</given> + <common>YongHyeon</common> + </name> + <email>yongari@kt-is.co.kr</email> + </person> + </contact> + + <links> + <url href="http://pf4freebsd.love2party.net"> + http://pf4freebsd.love2party.net</url> + <url href="http://www.benzedrine.cx/pf.html">PF homepage</url> + <url href="http://openbsd.org/faq/pf/index.html">PF FAQ</url> + </links> + + <body> + <p>The project started this spring and released version 1.0 with a port + installation (security/pf) in may 2003. Version 2.0 is on the doorstep + as OpenBSD 3.4 will be released. Due to the porting efforts we were + able to reveal some bugs in the OpenBSD code and provided locking for + the PFIL_HOOKS, which we utilize. Tarball installation of a loadable + kernel module for testing can be found on the project homepage, a + patchset is in the making.</p> + + <p>PF was started at OpenBSD as a substitute for ipfilter and provides + the same function set. However, in the two years it exists now, it has + gained many superior features that no other packet filter has. For a + impression take a look at the pf FAQ.</p> + + <p>We hope to be eventually integrated into the base system. Before that + we have to resolve some issues with tcpdump and kame.</p> + </body> +</project> + +<project> + <title> + Bluetooth stack for FreeBSD (Netgraph implementation) + </title> + + <contact> + <person> + <name> + <given>Maksim</given> + <common>Yevmenkin</common> + </name> + <email>m_evmenkin@yahoo.com</email> + </person> + </contact> + + <links> + <url href="http://www.geocities.com/m_evmenkin/">Latest snapshot</url> + <url href="http://bluez.sf.net">Linux BlueZ stack</url> + <url href="http://sourceforge.net/projects/openobex/">OpenOBEX</url> + </links> + + <body> + <p>I'm very pleased to announce that another release is available for + download at + http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030908.tar.gz. + I have also prepared patch for the FreeBSD source tree. The patch + was submitted for review to the committers.</p> + + <p>Fixed few bugs in kernel modules. The ng_hci(4) and ng_l2cap(4) + modules were changed to fix issue with Netgraph timeouts. The + ng_ubt(4) module was changed to fix compilation issue on -current.</p> + + <p>Improved user-space utilities. Implemented new libsdp(3). Added + new sdpcontrol(8) utility. The rfcomm_sppd(1), rfcomm_pppd(8) and + obexapp(1) were changed and now can obtain RFCOMM channel via SDP + from the server. The hccontorol(8) utility now has four new + commands. The hcsecd(8) daemon now saves link keys on the disk.</p> + + <p>I've been recently contacted by few individuals who whould like to + port current FreeBSD Bluetooth code to other BSD systems (OpenBSD + and NetBSD). The work is slowly progressing towards + un-Netgraph'ing current code. In the mean time Netgraph version + will be the primary supported version of the code.</p> + </body> +</project> + + +<project> + <title>Rescue build infrastructure</title> + + <contact> + <person> + <name> + <given>Gordon</given> + <common>Tetlow</common> + </name> + <email>gordon@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Tim</given> + <common>Kientzle</common> + </name> + <email>kientzle@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The rescue build infrastructure has been committed. There is one + known issue with make using both the '-s' and '-j' flags that appears + to be a bug in make. Anyone interested in tracking down should contact + us.</p> + </body> +</project> + +<project> + <title>Dynamically Linked Root Support</title> + + <contact> + <person> + <name> + <given>Gordon</given> + <common>Tetlow</common> + </name> + <email>gordon@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Support for a dynamically linked /bin and /sbin has been committed, + although it is not turned on by default. Adventurous users can try it + out by building /bin and /sbin using the WITH_DYNAMICROOT make flag. + More testing is needed to determine if this is going to be default for + 5.2-RELEASE. If anyone would like to benchmark worldstones with and + without dynamically linked /bin and /sbin, please feel free to do so + and submit the results.</p> + </body> +</project> + +<project> + <title>ACPI Status Report</title> + + <contact> + <person> + <name> + <given>Nate</given> + <common>Lawson</common> + </name> + <email>njl@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.root.org/~nate/freebsd/" /> + </links> + + <body> + <p>Work is continuing on updating ACPI with new features as well + as bugfixing. A new embedded controller driver was written in + July with support for the ACPI 2.0 ECDT as well as more robust + polling support. Also, a buffer overflow in the ACPICA resource list + handling that caused panics for some users was fixed. Marcel + helped get acpidump(8) tested and basically working on ia64.</p> + + <p>Upcoming work includes integrating ACPI notifies with devd(8), + committing user-submitted drivers for ASUS and Toshiba hotkeys, + Cx processor sleep states (so my laptop doesn't burn my lap), and + power resource support for intelligently powering down unused or idle + devices.</p> + + <p>Users who have problems with ACPI are encouraged to submit a PR + and email its number to acpi-jp@jp.FreeBSD.org. Bug reports + of panics or crashes have first priority and non-working features + or missing devices (except suspend/resume problems) second. + Reports of failed suspend/resume should NOT be submitted as PRs + at this time due to most of them being a result of incomplete + device support that is being addressed. However, feel free + to mail them to the list as any information is helpful.</p> + </body> +</project> + +<project> + <title>uart(4)</title> + + <contact> + <person> + <name> + <given>Marcel</given> + <common>Moolenaar</common> + </name> + <email>marcel@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The uart(4) project was born out of the need to have a working + serial interface (i.e. an RS-232-C interface) in a legacy-free + configuration and after an unsuccessful attempt to convert sio(4). + The biggest problem with sio(4) is that it has been intertwined + in many ugly ways into the kernel's core. Conversion could not + happen without breaking something that invariably affects some + group of people negatively. With sio(4) as a good bad example + and a strong desire to solve multiple problems at once, the + idea of an UART (Universal Asynchronuous Receiver/Transmitter) + device that, given its generic name, could handle different + flavors of UART hardware started to settle firmly in the authors + mind.</p> + <p>The biggest challenge was of course solving the problem of the + low-level console access prior to the initialization of the bus + infrastructure and still have a driver that uses the bus access + exclusively. Along the way the problem of having an UART function + as the keyboard on sparc64 was solved with the introduction of + system devices, which also encapsulated the console as a system + device.</p> + <p>The uart(4) driver can be enhanced to support the various UART + hardware on pc98 and this is currently being worked on. Keyboard + support on sparc64 is underway as well. Plans exist for a rewrite + of the remote gdb support that uses a generic interface to allow + various drivers, including uart(4), to register itself as a + communications channel. And since uart(4) does not support multi- + port cards by itself, we likely need to either enhance puc(4) or + otherwise introduce other umbrella drivers</p> + </body> +</project> + +<project> + <title>Compile FreeBSD with Intels C compiler (icc)</title> + + <contact> + <person> + <name> + <given>Alexander</given> + <common>Leidinger</common> + </name> + <email>netchild@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.Leidinger.net/FreeBSD/">Some patches.</url> + </links> + + <body> + <p>Since I ported icc to FreeBSD I wanted to build FreeBSD with icc. Now + with icc 7.1 (and some patches) it is possible. There are still some bugs, + e.g. NFS doesn't work with an icc compiled kernel, IP seems to be fragile, + and some advanced optimizations trigger an ICE (Intel is working on it). + At the moment I'm waiting for our admins to install icc on the FreeBSD + cluster (we got a commercial license from Intel, so we are allowed to + distribute binaries which are compiled with icc), after that I will try + to convince some people with more knowledge of the IP and NFS parts of + the kernel to debug the remaining problems. When the icc compiled kernel + seems to work mostly bugfree the userland will get the porting focus. + Interested people may try to do a build of the ports tree with icc + independently from the status of the porting of the userland... if this + happens at the FreeBSD cluster, we would also be allowed to distribute + the binaries.</p> + <p>Benefits include: another set of compiler errors (debugging help), + more portable source, and code which is better optimized for a P4 (gcc + has some drawbacks in this area)</p> + </body> +</project> + +<project> + <title>KDE FreeBSD Project</title> + + <contact> + <person> + <name> + <given>KDE-FreeBSD</given> + <common>Mailinglist</common> + </name> + <email>kde@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://freebsd.kde.org/" /> + </links> + + <body> + <p>The FreeBSD ports were updated to KDE 3.1.4, another bug- and + security-fixes release. With this update, the QT port was updated + to version 3.2. Both will be included in FreeBSD 4.9. + Significant work was spent to fix KDE on FreeBSD-CURRENT after the + removal of the gcc -pthread Option. Automatic package builds from + KDE CVS continued to ensure and improve the quality of the upcoming + KDE 3.2 release.</p> + + <p>Future: Work is in progress to setup a new server for hosting the + KDE-FreeBSD Website, Repository and another KDE CVS mirror. With + help from Marcel Moolenaar the project will try to make KDE compile + and working on the Intel IA64. And last but not least efforts are + being made to fix the currently broken kdesu program.</p> + </body> +</project> + + +<project> + <title>WifiBSD Status Report</title> + + <contact> + <person> + <name> + <given>Jon</given> + <common>Disnard</common> + </name> + <email>masta@wifibsd.org</email> + </person> + </contact> + + <links> + <url href="http://www.wifibsd.org">www.wifibsd.org</url> + </links> + + <body> + <p>WifiBSD is a miniture version of FreeBSD for wireless applications. + Originally for the Soekris Net45xx line of main-boards, but is now + capable of being targeted to any hardware/architecture FreeBSD itself + supports. Although not feature complete, WifiBSD is expected to be + ready for 5.2-RELEASE. The design goal is to meet, or exceed, the + functionality of commercial/consumer 802.11 wireless gear. Features + that need attention (to name just a few) are: http interface, consol + menu interface, and installation. Volunters are welcome.</p> + </body> +</project> + +<project> + <title>PowerPC Port</title> + + <contact> + <person> + <name> + <given>Peter</given> + <common>Grehan</common> + </name> + <email>grehan@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work has restarted after a hiatus. Current focus is on getting + loadable modules working, NEWBUSing the NetBSD dbdma code, and + completing the BMAC ethernet driver.</p> + + <p>There is a huge amount of work to do. Volunteers more than welcome!</p> + </body> +</project> + +<project> + <title>AMD64 Porting</title> + + <contact> + <person> + <name> + <given>Peter</given> + <common>Wemm</common> + </name> + <email>peter@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The last known bug that prevented AMD64 machines completing a + full release has been fixed - one single character error that + caused ghostscript to crash during rendering diagrams. SMP work + is nearing completion and should be committed within the next few + days. The SMP code uses the ACPI MADT table based on John Baldwin's + work-in-progress there for i386. We need to spend some time on + low level optimization because there are several suboptimal places + that have been ignored for simplicity, context switching in + particular. MTRR support has been committed and XFree86 can use + it. cvsup now works but the ezm3 port has not been updated yet. + The default data segment size limit is 8GB instead of 512M, and + the (primitive) i386 binary emulation support knows how to lower + the rlimits for executing 32 bit binaries.</p> + + <p>Notable things missing still: Hardware debug register support + needs to be written; gdb is still being done as an external + set of patches relative to the not-yet-released FSF gdb tree; + DDB does not disassemble properly; DDB cannot do stack traces + without -fno-omit-frame-pointer - a stack unwinder is needed; + i386 and amd64 linux binary emulation is needed, and the i386 + FreeBSD binary emulation still needs work - removing the + stackgap code in particular.</p> + + <p>The platform in general is very reliable although a couple of + problems have been reported over the last week. One appears to + be a stuck interrupt, but all that code has been redone for SMP + support.</p> + + </body> +</project> + +<project> + <title>bsd.java.mk version 2.0</title> + <contact> + <person> + <name> + <given>Ernst</given> + <common>De Haan</common> + </name> + <email>znerd@FreeBSD.org</email> + </person> + <person> + <name> + <given>Herve</given> + <common>Quiroz</common> + </name> + <email>herve.quiroz@esil.univ-mrs.fr</email> + </person> + </contact> + <links> + <url href="http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html">Project homepage</url> + </links> + <body> + <p>The FreeBSD Java community has started an effort to improve the + current framework for Java-based ports. The main objective is the + automation of JDK/JRE build and run dependency checking.</p> + <p>The original version was aimed to ease the life of porters. Although + it has proved to be useful and reliable to a great extend, we are + currently working on a new version. We intend to reach a high degree + of flexibility to cope with the recent increase of available JDK/JRE + flavors. Furthermore, the new version will be easier to maintain, + which means improved reliability, and hopefully more frequent + updates.</p> + </body> +</project> + +<project> + <title>FreeBSD Java Project</title> + + <contact> + <person> + <name> + <given>Greg</given> + <common>Lewis</common> + </name> + <email>glewis@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/java/">FreeBSD Java Project</url> + </links> + + <body> + <p>The BSD Java Porting Team has recently reached an exciting milestone + with the release of the first "Diablo" JDK and JRE courtesy of the + FreeBSD Foundation. The release of Diablo Caffe and Diablo Latte + 1.3.1 was the first binary release of a native FreeBSD JDK since + 1.1.8 and marks an important step forward in FreeBSD Java support.</p> + + <p>The team is continuing development work, with a focus on achieving + a compliant JDK 1.4 release in the near future.</p> + </body> +</project> + +<project> + <title>ATAPI/CAM Status Report</title> + + <contact> + <person> + <name> + <given>Thomas</given> + <common>Quinot</common> + </name> + <email>thomas@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>With the introduction of ATAng, some users of ATAPI/CAM have + experienced various problems. These have been mostly tracked down + to issues in the new ATA code, as well as two long-standing problems + in portions of the CAM layer that are rarely exercised with + "real" SCSI SIMs. This has also been an occasion to cleanup + ATAPI/CAM to make it more robust, and to enable DMA for devices + accessed through it, resulting in improved performances.</p> + + </body> +</project> + +<project> + <title>jpman project</title> + + <contact> + <person> + <name> + <given>Kazuo</given> + <common>Horikawa</common> + </name> + + <email>horikawa@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.jp.FreeBSD.org/man-jp/">jpman project</url> + <url href="ftp://daemon.jp.FreeBSD.org/pub/FreeBSD-jp/man-jp/packages-5.1.0/ja-man-doc-5.1.tbz">package ja-man-doc-5.1.tbz</url> + </links> + + <body> + <p>We have released Japanese translation of 5.1-RELEASE online manual + pages on June 10.</p> + </body> +</project> + +<project> + <title>FreeBSD ports monitoring system</title> + + <contact> + <person> + <name> + <given>Mark</given> + <common>Linimon</common> + </name> + <email>linimon_at_lonesome_dot_com</email> + </person> + </contact> + + <links> + <url href="http://lonesome.dyndns.org:4802/bento/errorlogs/index.html"> + FreeBSD ports monitoring system</url> + </links> + + <body> + <p>Several months ago, I took it upon myself to to try present the + information contained on <a href="http://bento.FreeBSD.org">the bento + build cluster</a> to be presented in a more user-friendly fashion; that + is, to be browsed by error type, by maintainer, and so forth. An early + addition was code to attempt to classify ports PRs by either "existing + port" (after assiging the most likely category and portname); "new port"; + "framework" (e.g. bsd.port.mk changes); and "unknown". Various columns + about the ports PRs were added to the reports.</p> + + <p>The initial intent of this was to make life easier for ports + maintainers; however, the "general" reports are also useful to anyone who + just wants to, e.g., find out if a particular port is working on their + particular architecture and OS combination before downloading it. Those + with that general interest should start with the + <a href="http://lonesome.dyndns.org:4802/bento/errorlogs/portoverview.py"> + overview of one port</a>.</p> + </body> +</project> + +<project> + <title>kgi4BSD Status Report</title> + + <contact> + <person> + <name> + <given>Nicholas</given> + <common>Souchu</common> + </name> + <email>nsouch@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~nsouch/kgi4BSD"> Project URL</url> + </links> + + <body> + <p>A lot of work done since last report: site reworked completely (see new + URL), console design with console message in text or graphic modes + implemented, implementation of a compatibility layer to compile Linux + fbdev drivers with more or less changes in the original driver + (experimental).</p> + + <p>Except some memory allocation bugs, X (XGGI based on XFree 3.3.6) is + now working with the same driver as the console. A basic terminal has + now to be implemented.</p> + + <p> Volunteers are welcome to the project...</p> + + </body> +</project> + +<project> + <title>Device_t locking</title> + + <contact> + <person> + <name> + <given>Warner</given> + <common>Losh</common> + </name> + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>A number of races have been identified in locking device_t. + Most of the races have been identified in making device_t have to + do with how drivers are written. Efforts are underway to identify + all the races, and to contact the authors of subsystems that can + help the drivers. Of special concern is the need for the driver + to ensure that all threads are completely out of the driver code + before detach() finishes. Of additional concern is making sure + that all sleepers are woken up before certain routines are called + so that other subsystems can ensure the last condition and leave + no dangling references. Locking device_t is relatively straight + forward apart from these issues. Towards the end of proper + locking, sample strawmen drivers are being used to work out what, + exactly proper is. Once these issues are all known and documented + in the code, efforts will be made to update relevant documentation + in the tree. There are many problems with driver locking that has + been done to date, but until we nail down how to write a driver in + current, it will be premature to contact specific driver writers + with specific concerns.</p> + + </body> +</project> + +<project> + <title>Cryptographic Support</title> + + <contact> + <person> + <name> + <given>Sam</given> + <common>Leffler</common> + </name> + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Support for several new crypto devices was added. The SafeNet 1141 is a + medium performance part that is not yet available on retail products. The + Hifn 7955 and 7956 parts are starting to appear on retail products that + should be available by the end of the year. Both devices support AES + encryption. Support for public key operations for the SafeNet devices was + recently done for OpenBSD and will be backported. Public key support for + the Hifn parts is planned.</p> + + <p>A paper about the performance work done on the cryptographic subsystem + was presented at the Usenix BSDCon 2003 conference and received the best + paper award.</p> + + <p>NetBSD recently imported the cryptographic subsystem.</p> + </body> +</project> + +<project> + <title>Release Engineering Status</title> + + <contact> + <person> + <name> + <given>Scott</given> + <common>Long</common> + </name> + <email>re@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The release of 4.9 is just around the corner and offers Physical Address + Extensions (PAE) for x86 along with the same world-class stability and + performance that is expected from the 4-STABLE series. As always, don't + forget to purchase a copy of the CD set from your favorite FreeBSD + vendor.</p> + + <p>FreeBSD 5.1 was released in June and offered vastly improved + stability over 5.0 along with a working implementation of Kernel + Scheduled Entities, allowing for true multithreading of applications + across multiple CPUs. FreeBSD 5.2 will be released by the end of 2003 + and will focus on improved network and overall performance.</p> + + </body> +</project> + +<project> + <title>Wireless Networking Support</title> + + <contact> + <person> + <name> + <given>Sam</given> + <common>Leffler</common> + </name> + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Numerous bugs have been fixed since the last status report (and of + course a few new ones added). Progress on improved security has been + slowed by other work. But new features and fixes are coming in from + other groups that are now sharing the code. In particular NetBSD + recently imported the revised 802.11 layer and the Linux-based MADWIFI + project is using it too (albeit in an older form). The MADWIFI users + have already contributed features such as fragmentation reassembly of + 802.11 frames and improved signal monitoring. Power save polling and + an improved rate control algorothm are expected to come in from the + NetBSD folks. WPA support is still in the plans; the best estimate is + that work on that will start in January.</p> + + </body> +</project> + +<project> + <title>Network Subsystem Locking and Performance</title> + + <contact> + <person> + <name> + <given>Sam</given> + <common>Leffler</common> + </name> + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The purpose of this project is to improve performance of the network + subsystem. A major part of this work is to complete the locking of the + networking subsystem so that it no longer depends on the "Giant lock" + for proper operation. Removing the use of Giant will improve + performance and permit multiple instances of the network stack to + operate concurrently on multiprocessor systems.</p> + + <p>This project started in August. The emphasis has been on locking the + "lower half" of the networking code so that packet forwarding through the + IPv4 path can operate without the Giant lock as part of the 5.2 release. + To this end locking was added to several network interface drivers and + much of the "middleware" code in the network was locked (e.g. ipfw, + dummynet, then routing table, multicast routing support, etc). Work + towards this goal is still ongoing but should be ready for 5.2. A + variety of test systems have been running for several months without the + Giant lock in the network drivers and IP layer.</p> + + <p>Past the 5.2 release Giant will be removed from the "upper half" of the + network subsystem and the socket layer. Once this is done the plan is to + measure and improve performance (though some work of this sort is always + happening). The ultimate goal is a system that performs at least as well + as 4.x for normal use on uniprocessor systems. On multiprocessor systems + we expect to see significantly better performance than 4.x due to greater + concurrency and reduced latency.</p> + + </body> +</project> + +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2003-10-2003-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2003-10-2003-12.xml new file mode 100644 index 0000000000..1bfcc97cc2 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2003-10-2003-12.xml @@ -0,0 +1,1365 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2003-10-2003-12.xml,v 1.5 2006/08/19 21:20:40 hrs Exp $ --> + +<report> + <date> + <month>October-December</month> + <year>2003</year> + </date> + + <section> + <title>Introduction:</title> + + <p>The FreeBSD status reports are back again with the 2003 year-end + edition. Many new projects are starting up and gaining momentum, + including XFS, MIPS, PowerPC, and networking locking and + multithreading. The end of 2003 also saw the release of FreeBSD 4.9, + the first stable release to have greater than 4GB support for the + ia32 platform. Work on FreeBSD 5.2 also finished up and was released + early in January of 2004. Many thanks to all of the people who + worked so hard on these releases and made them happen.</p> + + <p>This is the largest status report ever, so read and enjoy!</p> + + <p>Scott Long, Robert Watson</p> + + </section> + + <project> + <title>libarchive, bsdtar</title> + + <contact> + <person> + <name> + <given>Tim</given> + <common>Kientzle</common> + </name> + <email>kientzle@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~kientzle/libarchive/" /> + </links> + + <body> + <p>The libarchive library, which reads and writes tar and cpio + archives, is about ready to commit to the tree. The bsdtar + program, built on libarchive, is also nearing completion and + should soon be a worthwhile successor to our aging GNU tar. I + plan a gradual transition during which "bsdtar" and "gtar" will + coexist in the tree.</p> + + <p>Oddly enough, libarchive and bsdtar are the first fruits of a + project to completely rewrite the pkg tools. I've started + architecting a libpkg library for handling routine package + management and have a prototype pkg_add that is three times faster + than the current version.</p> + </body> + </project> + + <project> + <title>Publications Page Update</title> + + <contact> + <person> + <name> + <given>Josef</given> + + <common>El-Rayes</common> + </name> + + <email>josef@daemon.li</email> + </person> + </contact> + + <links> + <url href="http://www.daemon.li/freebsd/">Updated Publications Page</url> + </links> + + <body> + <p>I did a xml/xslt conversion of the html files to make maintaining + of the page more comfortable. I removed the cdsets, which might be + kept in CVS or some kind of archive for historical reasons. The books + got an update, and were categorized in respect to the language they + are written in. As soon as I get my access on the cvs repository I + will commit the updates. People are encouraged to add local FreeBSD + books, I missed, especially in the asian area. Feel free to send me + links to books to add.</p> + </body> + </project> + + <project> + <title>DVB-ASI Support</title> + + <contact> + <person> + <name> + <given>Vincent</given> + + <common>Jardin</common> + </name> + + <email>Vincent.Jardin@6wind.com</email> + </person> + </contact> + + <links> + <url href="http://proxy.6wind.com/~jardin/dvb/">Home page and source code</url> + <url href="http://www.computermodules.com/broadcast/broadcast-dvb.shtml">Computer Modules</url> + <url href="http://www.dvb.org/"/> + </links> + + <body> + <p>DVB ASI stands for Digital Video Broadcast - Asynchronous Serial + Interface. It is the standard defined to send and receive DVB stream + from Satellite (DVB-S), Terrestrial link (DVB-T), and TV Cable + (DVB-C). This standard was developed in Europe to transport 188-byte + MPEG cells and 204-byte MPEG cells. However it can be used to carry IP + over DVB too.</p> + + <p>The FreeBSD driver uses the newbus amd the bus-dma API. It means that it + could be easily ported to all the BSD flavors (NetBSD, OpenBSD).</p> + + <p>It uses the same API than the Linux DVB ASI support from + ComputerModules that is based on the following devices: + <ul> + <li>/dev/asitxN for the transmit stream (only open, write, select, + close and ioctl are supported)</li> + <li>/dev/asirxN for the receive stream (only open, read, select, close + and ioctl are supported)</li> + </ul> + It means that software such as Videolan that support DVB-ASI + broadcasting could be supported by this driver.</p> + + <p>Special thanks to Tom Thorsteinson from Computer Modules who helped + 6WIND to port their driver. It is used by 6WIND in order to provide + IPv4, IPv6, Ethernet and our network services over DVB.</p> + + <p>Copyright 2003-2004, 6WIND</p> + </body> + </project> + + <project> + <title>FreeBSD ports monitoring system</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon_at_lonesome_dot_com</email> + </person> + </contact> + + <links> + <url href="http://lonesome.dyndns.org:4802/bento/errorlogs/index.html">FreeBSD + ports monitoring system</url> + </links> + + <body> + <p>Enhancements continue to be made to the system. Several, + including improvements to the PR classification algorithm, the + ability to more correctly guess when a PR has been updated, and + better handling of errors in both port Makefiles and the bento + builds, are invisible to end-users. However, the addition of + a "repocopy" classification is notable, as is the allowing the + wildcard search in "overview of one port" (thanks to edwin@ for + the shove in that direction.) Additionally, logic has been + added to identify the proposed category/portname of new ports, + with the goal being to quickly identify possible duplications + of effort. (Some SQL performance was sacrificed to this goal, + leading to some pages to load more slowly; this needs to be + fixed.)</p> + + <p>The other work has been on an email back-end to allow the + occasional sending of email to maintainers. Two functions are + currently available: "remind maintainers of their ports that + are marked BROKEN", and "remind maintainers of PRs that they + may not have seen." A recent run of the former got generally + good response, especially as changing some cases of BROKEN to + IGNORE (PR ports/61090) had removed almost all the annoying + false positives. However, work remains to try to find out why + a few allegedly broken ports only fail in certain environments + (including the bento cluster).</p> + + <p>The next plan is to use the proposed DEPRECATED Makevar (see + ports/59362) to create a new report to allow querying of "ports + currently slated to be removed". This report could also be + posted to ports@ periodically with minimal work. The author + believes that doing this would allow the port deprecation process + to be much more visible to the general FreeBSD user community.</p> + </body> + </project> + + <project> + <title>Compile FreeBSD with Intels C compiler (icc)</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.Leidinger.net/FreeBSD/">Some patches</url> + </links> + + <body> + <p>The FreeBSD kernel now builds and runs fine with icc v7 (only GENERIC + and a custom kernel tested so far). A review on arch@ revealed no + major concerns and some src committers are willing to commit the + patches. As icc v8 is out and defines __GNUC__ I want to rework the + patches before they get committed so an icc v8 compiled kernel DTRT + too.</p> + <p>A complete build of the ports collection (as of start of December) + finished and is under review to determine the reason of build + failures. Current <emph>icc</emph> stats: + <ul> + <li>1108 failed builds (excluding build failures because of failed + dependencies)</li> + <li>3535 successfully build packages (~ 1.7 GB)</li> + </ul> + A parallel build with <emph>gcc</emph> on the same snapshot of the + ports collection has: + <ul> + <li>520 failed builds (excluding build failures because of failed + dependencies)</li> + <li>7261 successfully build packages (~ 4.8 GB)</li> + </ul> + </p> + <p>The above mentioned build of the ports collection was run on a P4 + with a icc compiled kernel (optimized for a P4). No kernel panics or + other strange behavior was noticed. The ports collection was build + with a CPUTYPE of p4 and CFLAGS set to "-Os -pipe -mfpmath=sse -msse2" + in the gcc and "-O2" in the icc case. No package is tested for correct + run-time behavior so far.</p> + </body> + + </project> + + <project> + <title>Porting OpenBSD's pf</title> + + <contact> + <person> + <name> + <given>Max</given> + <common>Laier</common> + </name> + <email>max@love2party.net</email> + </person> + <person> + <name> + <given>Pyun</given> + <common>YongHyeon</common> + </name> + <email>yongari@kt-is.co.kr</email> + </person> + </contact> + + <links> + <url href="http://pf4freebsd.love2party.net" /> + <url href="http://www.benzedrine.cx/pf.html">PF homepage</url> + <url href="http://openbsd.org/faq/pf/index.html">PF FAQ</url> + </links> + + <body> + <p>Much work has been invested into getting release 2.00 stable. It + provides the complete OpenBSD 3.4 function set, as well as fine + grained locking to work with a giant free network stack.</p> + <p>pf provides: IPv6 filtering and normalization, "syn-proxy" + to protect (web)server against SYN-floods, passive OS detection, fast + and modular address tables, source/policy routing, stateful filter and + normalization engine, structured rulesets via anchors and many many + more. Especially in connection with ALTQ, pf can help to harden + against various flood attacks and improve user experience.</p> + <p>New features from OpenBSD-Current like: state synchronization over wire + and enhanced support for cloned interfaces require patches to the + kernel. We are trying to resolve this issue and start + OpenBSD-Current tracking again as soon as possible.</p> + </body> + </project> + + <project> + <title>Binary security updates for FreeBSD</title> + + <contact> + <person> + <name> + <given>Colin</given> + + <common>Percival</common> + </name> + + <email>cperciva@daemonology.net</email> + </person> + </contact> + + <links> + <url href="http://www.daemonology.net/freebsd-update/" /> + </links> + + <body> + <p>Thanks to recent donations, I am now building binary security + updates for FreeBSD {4.7, 4.8, 4.9, 5.0, 5.1, 5.2}-RELEASE. + (Note that FreeBSD 4.7 and 5.0 are no longer officially + supported; any advisories which are not reflected in the CVS + tree will likewise not result in binary updates.)</p> + + <p>The current version (1.5) of FreeBSD Update will warn about + locally modified files and will, by default, leave them + untouched; if a "distribution branch", (i.e. crypto, nocrypto, + krb4, or krb5) is specified, FreeBSD Update can be forced to + "update" files which have been compiled locally.</p> + + <p>The only major issue remaining with FreeBSD Update is the + single-point-of-failure of the update building process; I + would like to resolve this in the future by having several + machines cross-verify and cross-sign, but this will require + a significant investment of time, and will probably have to + wait until I've finished writing my DPhil thesis.</p> + </body> + </project> + + <project> + <title>SGI XFS port for FreeBSD</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Kabaev</common> + </name> + + <email>kan@FreeBSD.org</email> + </person> + <person> + <name> + <given>Russell</given> + + <common>Cattelan</common> + </name> + + <email>cattelan@thebarn.com</email> + </person> + </contact> + + <body> + <p>A project was started to revive a stalled effort to port SGI XFS + journaling filesystem to FreeBSD. The project is based on Linux + development sources from SGI and is currently being kept in a + private Perforce repository. The work is progressing slowly due + to lack of free time. At the moment we have XFS kernel module + which is capable of mounting XFS filesystems read-only, with a + panic or two happening infrequently, that need to be isolated and + fixed. Semi-working metadata updates with full transaction support + are there too, but will probably have to be rewritten to minimize + the amount of custom kernel changes required.</p> + + <p>We seek volunteers to help with userland part of the port. Namely, + existing xfsprogs port needs to be cleaned up, incompletely ported + utilities brought into a working shape. xfs_dump/xfs_restore and + as much from xfstests suite as possible need to be ported too. We do + not need testers for now, so please to not ask for module sources + just yet.</p> + + </body> + </project> + + <project> + <title> + Bluetooth stack for FreeBSD (Netgraph implementation) + </title> + + <contact> + <person> + <name> + <given> + Maksim + </given> + + <common> + Yevmenkin + </common> + </name> + + <email>m_evmenkin@yahoo.com</email> + </person> + </contact> + + <body> + <p>Not much to report. Bluetooth code was integrated into the FreeBSD + source tree. Bluetooth kernel modules appear to be stable. I have + received few success stories from the users.</p> + + <p>During last few months the efforts were to make Bluetooth code + more user friendly. Bluetooth Service Discovery Procotol daemon + sdpd was reimplemented under BSD-style license and committed. The + next step is to integrate existing Bluetooth utilities with SDP.</p> + + <p>Thanks to Matt Peterson <matt at peterson dot org> I now have + Bluetooth keyboard and mouse for development. I'm currently + working on Bluetooth HID profile implementation.</p> + + <p>Dave Sainty <dave at dtsp dot co dot nz> from NetBSD project + offered his help in porting Bluetooth stack to NetBSD.</p> + </body> + </project> + + <project> + <title>Network interface naming changes</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>At the end of October, the if_name and if_unit members of struct + ifnet were replaced with if_xname from NetBSD and if_dname and + if_dunit. These represent the name of the interface and the + driver name and instance of the interface respectively. Other then + breaking IPFilter for a few weeks due to the userland being on the + vendor branch, this change went quite well. A few ports needed + minor changes, but otherwise nothing changed from the user + perspective.</p> + + <p>The purpose of this change was the lay the groundwork for support + for network interface renaming and to allow the implementation of + more interesting pseudo interface cloning support. An example of + interesting cloning support would be using "ifconfig fxp0.20 + create" to create and configure a vlan interface on fxp0 that + handled frames marked with the tag 20. Interface + renaming is being worked on in Perforce at the moment with a + working version expected for review soon. Support for enhanced + device cloning is still in the planing stage.</p> + </body> + </project> + + <project> + <title>Kernel Tunables Documentation Project</title> + <contact> + <person> + <name> + <given>Tom</given> + <common>Rhodes</common> + </name> + <email>trhodes@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=docs/44034">The + problem report which kicked this project in action</url> + </links> + + <body> + <p>FreeBSD has well over a few hundred tunables without + documentation. This project aims at designing an + automated process to rip all available tunables and generate + a manual page based on the selected kernel options. + The ideal implementation, however; would gather tunables + from the LINT kernels as well. This would provide a + default manual page for all supported architectures. + A simple tool has been forged from the various off-list + and on-list discussions and is waiting review from the + -doc team. Anyone interesting in reviewing my current + work is requested to get in contact with me.</p> + </body> + </project> + + <project> + <title>jpman project</title> + + <contact> + <person> + <name> + <given>Kazuo</given> + <common>Horikawa</common> + </name> + + <email>horikawa@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.jp.FreeBSD.org/man-jp/">jpman project</url> + </links> + + <body> + <p>We have been updating existing Japanese translations + of manual pages to meet the 5.2-RELEASE schedule. + Also, 22 new translations were complete during this period.</p> + </body> + </project> + + <project> + <title>FreeBSD MIDI</title> + + <contact> + <person> + <name> + <given>Mathew</given> + + <common>Kanner</common> + </name> + + <email>matk@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>This project aims to update the current MIDI implementation. We + are currently looking at removing the current code sometime in + February and importing the new version soon after. I'm currently + working on a kernel/timidity bridge for those without external + hardware.</p> + + </body> + </project> + + <project> + <title>The FreeBSD Russian Documentation Project</title> + + <contact> + <person> + <name> + <given>Andrey</given> + + <common>Zakhvatov</common> + </name> + + <email>andy@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ru/index.html">The FreeBSD Project [Russian]</url> + </links> + + <body> + <p>The FreeBSD Russian Documentation Project aims to provide FreeBSD + Documentation translated to Russian. Already done: FAQ, Porters + Handbook, WWW (partially synched with English version), some + articles.</p> + + <p>We working at Handbook (and more docs) translation and synchronization + with English versions and need more translators (or financial aid to + continue our work. If you can help, please, contact us at + ru-cvs-committers@FreeBSD.org.ua (or andy@FreeBSD.org).</p> + </body> + </project> + + <project> + <title>KSE</title> + + <contact> + <person> + <name> + <given>Daniel</given> + + <common>Eischen</common> + </name> + + <email>deischen@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The libkse library will shortly be renamed to libpthread and + be made the default thread library. This includes making the + GCC -pthread option link to -lpthread instead of libc_r and + changing PTHREAD_LIBS to -lpthread. David Xu has been working + on GDB support and has it working with the GDB currently in our + tree. The next step is to make a libpthread_db and get it working + with GDB 6.0 which marcel has imported into the perforce tree.</p> + </body> + </project> + + <project> + <title>Donations Team</title> + + <contact> + <person> + <name> + <given>Michael</given> + + <common>Lucas</common> + </name> + + <email>donations@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/donations/">FreeBSD Donations Project</url> + </links> + + <body> + <p>2003 was quite successful for the Donations team. We + shepherded over 200 items from donors into the hands of + developers. Some high points include: a small cluster for the + security team, assorted laptop hardware for our cardbus work, + and documentation for our standards group. In the main FreeBSD.org + cluster we were able to replace 8 DEC Miata machines with 6 + Alpha DS10s (21264). Every committer doing SMP work now has + multi-processor testing hardware.</p> + + <p>We have smoothed out the tax deduction process with the FreeBSD + Foundation, and can ship donated items directly to the + recipients instead of tying up Foundation time handling + shipping.</p> + + <p>Current team membership is: Michael Lucas, David O'Brien, and + Tom Rhodes. Wilko Bulte has replaced Robert Watson as the Core + Team representative.</p> + </body> + </project> + + <project> + <title>ACPI</title> + + <contact> + <person> + <name> + <given>Nate</given> + + <common>Lawson</common> + </name> + + <email>njl@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.root.org/~nate/freebsd/">ACPI TODO</url> + <url href="http://home.jp.FreeBSD.org/mail-list/acpi-jp/">ACPI-JP + Mailing List</url> + + </links> + + <body> + <p>The updated acpi_cpu driver was committed in November. Work is + ongoing to finish support for _CST re-evaluation, which makes it + possible for laptops based on processors like the Centrino to use + varying CPU idle states when on or off AC power. 5.2-RELEASE also + went out with support for _CID packages, which fixed mouse probing + for Compaq users. Control of CPU idle states and throttling can + now be done through rc.conf(5) settings for the /etc/power_profile + script, which switches between performance/economy levels when + the AC status changes.</p> + + <p>One huge task underway is the cpufreq project, a framework for + detecting and controlling various frequency/voltage technologies + (SpeedStep, LongRun, ACPI Performance states, etc.) The ACPI + performance states driver is working and the framework is being + implemented. It requires newbus attachments for CPUs so some + ground work needs to go in before the driver can be committed.</p> + + <p>ACPI-CA was updated to 20031203 in early December and with a few + patches is reasonably stable. An ACPI debugging how-to has been + written and is being DocBooked by trhodes@. Ongoing work on fixing + interrupt storms due to various ways of setting up the SCI + is being done by jhb@.</p> + + <p>I'd like to welcome Philip Paeps (philip@) to the FreeBSD team. + Philip has written an ACPI ASUS driver that will be committed soon + and has been very helpful on the mailing lists. We've also had + a lot of help from jhb@, marcel@, imp@, and peter@. We're hoping + to see the return of takawata@ and iwasaki@, who have been very + helpful in the past. + If any developers are interested in assisting with ACPI, please + see the ACPI TODO and send us an email.</p> + </body> + </project> + + <project> + <title>kgi4BSD Status Report</title> + + <contact> + <person> + <name> + <given>Nicholas</given> + + <common>Souchu</common> + </name> + + <email>nsouch@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~nsouch/kgi4BSD" /> + <url href="http://www.kgi-project.org" /> + </links> + + <body> + <p>Most of the console blocks are in place with nice results + (see screenshots on the site). Boot console and virtual + terminals are working with 8bit rendering and perfect integration + of true graphic drivers in the kernel.</p> + + <p>Now it is time to bring it to end user and a precompiled R5.2 GENERIC + kernel is available for this (see the site news). In parallel, + after providing a last tarball/patch for R5.2, everything will + move to Perforce.</p> + + <p>As always, volunteers are welcome. The task is huge but very + exciting.</p> + </body> + </project> + + <project> + <title>FreeBSD/powerpc on PPCBug-based embedded boards</title> + + <contact> + <person> + <name> + <given>Rafal</given> + + <common>Jaworowski</common> + </name> + + <email>rafal.jaworowski@motorola.com</email> + </person> + </contact> + + <body> + <p>The direct objective is to make FreeBSD/powerpc work on Motorola + MCP750 and similar (single board computer that is compliant with + Compact PCI standard) Based on this work it would be easy to bring it + to other embedded systems.</p> + + <p>1. loader(8): it is based on the existing loader for FreeBSD/powerpc + port but binding to OpenFirmware was removed and replaced with PPCBug + firmware binding. It only supports netbooting for the moment, so disk + (compact flash) support needs to be done one day. The loader is the + only piece that relies onPPCBug system calls - once the kernel starts + it doesn't need firmware support any longer.</p> + + <p>2. kernel: it is now divorced from OpenFirmware dependencies; most of + the groundwork finished includes: nexus stuff is sorted out (resources + management is ok except interrupts assignment); host to PCI bridge low + level routines are finished so configuration of and access to PCI + devices works; the only important thing missing is the IRQ management + (Raven MPIC part is done, but the board has the second PIC, + 8259-compatible that needs to be set up, but here the existing code + from x86 arch will be adopted).</p> + + <p>Once the IRQ management is cleared out, most of the devices on board + would work straight away since they are pretty standard chips with + drivers already implemented in the tree (e.g. if_de).</p> + + <p>At the moment work is on hold (don't have physical access to the + device) but will resume when I'm back home (late Feb).</p> + + </body> + </project> + + <project> + <title>TrustedBSD Mandatory Access Control (MAC)</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <given>TrustedBSD Discussion Mailing List</given> + </name> + + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.trustedbsd.org/mac.html">TrustedBSD MAC + page</url> + </links> + + <body> + <p>The TrustedBSD Mandatory Access Control (MAC) Framework + permits the FreeBSD kernel and userspace access control + policies to be adapted at compile-time, boot-time, or + run-time. The MAC Framework provides common infrastructure + components, such as policy-agnostic labeling, making it + possible to easily development and distribute new access + control policy modules. Sample modules include Biba, MLS, + and Type Enforcement, as well as a variety of system + hardening policies.</p> + + <p>TrustedBSD MAC development branch in Perforce integrated + to 5.2-RELEASE.</p> + + <p>The TrustedBSD MAC Framework now enforces protections on System + V IPC objects and methods. Shared memory, semaphores, and + message queues are labeled, and most operations are controlled. + The Biba, MLS, Test, and Stub policies have been updated for + System V IPC. (Not yet merged)</p> + + <p>The TrustedBSD MAC Framework now enforces protections on POSIX + semaphore objects and methods. The Biba, MLS, Test, and Stub + policies have been updated. (Not yet merged)</p> + + <p>The TrustedBSD MAC Framework's central kernel implementation + previously existed in one large file, src/sys/kern/kern_mac.c. + It is now broken out into a series of by-service files in + src/sys/security/mac. src/sys/security/mac/mac_internal.h + specifies APIs, structures, and variables used internally + across the different parts of the framework. System calls + and registration still occur in kern_mac.c. This permits + more easy maintenance of locally added object types. (Merged)</p> + + <p>Break out mac_policy_list into two different lists, one to + hold "static" policy modules -- ones loaded prior to kernel + initialization, and that may not be loaded, and one for + "dynamic" policy modules -- that are either loaded later in + boot, or may be unloaded. Perform less synchronization when + using static modules only, reducing overhead for entering + the framework when not using dynamic modules. (Merged)</p> + + <p>Introduced a kernel option, MAC_STATIC, which permits only + statically registered policy modules to be loaded at boot + or compiled into the kernel. When running with MAC_STATIC, + no internal synchronization is required in the MAC Framework, + lowering the cost of MAC Framework entry points. (Not yet + merged)</p> + + <p>Make mac.h userland API definition C++-happy. (Merged)</p> + + <p>Created mac_support.4, a declaration of what kernel and + userspace features are (and aren't) supported with MAC. + (Not yet merged)</p> + + <p>Stale SEBSD module deleted from MAC branch; SEBSD module will + solely be developed in the SEBSD branch from now on. See + the TrustedBSD SEBSD report for more detail.</p> + + <p>Use only pointers to 'struct label' in various kernel objects + outside the MAC Framework, and use a zone allocator to allocate + label storage. This permits label structures to have their + size changed more easily without changing the normal kernel + ABI. This also lowers the non-MAC memory overhead for base + kernel structures. This also simplifies handling and storage + of labels in some of the edge cases where labels are exposed + outside of the Framework, such as in execve(). Include files + outside of the Framework are substantially simplified and now + frequently no longer require _label.h. (Merged)</p> + + <p>Giant pushed down into the MAC Framework in a number of MAC + related system calls, as it is not required for almost all + of the MAC Framework. The exceptions are areas where the + Framework interacts with pieces of the kernel still covered + by MAC and relies on Giant to protect label storage in those + structures. However, even in those cases, we can push Giant + in quite a bit past label internalization/externalization/ + storage allocation/deallocation. This substantially simplifies + file descriptor-based MAC label system calls. (Merged)</p> + + <p>Remove unneeded mpo_destroy methods for Biba, LOMAC, and MLS + since they cannot be unloaded. (Merged)</p> + + <p>Biba and MLS now use UMA zones for label allocation, which + improves storage efficiency and enhances performance. (Merged)</p> + + <p>Bug fix for mac_prepare_type() to better support arbitrary + object label definitions in /etc/mac.conf. (Merged)</p> + + <p>Labels added to 'struct inpcb', which represents TCP and UDP + connections at the network layer. These labels cache socket + labels at the application layer so that the labels may be + accessed without application layer socket locks. When a label + is changed on the socket, it is pushed down to the network + layer through additional entry points. Biba, MLS policies + updated to reflect this change. (Merged)</p> + + <p>SO_PEERLABEL socket option fixed so that peer socket labels + may be retrieved. (Merged)</p> + + <p>mac_get_fd() learns to retrieve local socket labels, providing + a simpler API than SO_LABEL with getsockopt(). mac_set_fd() + learns about local socket labels, providing a simpler API than + SO_LABEL with setsockopt(). This also improves the ABI by not + embedding a struct label in the socket option arguments, instead + using the copyin/copyout routine for labels used for other object + types. (Merged)</p> + + <p>Some function names simplified relating to socket options. + (Merged)</p> + + <p>Library call mac_get_peer() implemented in terms of getsockopt() + with SO_PEERLABEL to improve API/ABI for networked applications + that speak MAC. (Merged)</p> + + <p>mac_create_cred() renamed to mac_cred_copy(), similar to other + label copying methods, allowing policies to implement all the + label copying method with a single function, if desired. This + also provides a better semantic match for the crdup() behavior. + (Merged)</p> + + <p>Support "id -M", similar to Trusted IRIX. (Not yet merged)</p> + + <p>TCP now uses the inpcb label when responding in timed wait, + avoiding reaching up to the socket layer for label information + in otherwise network-centric code.</p> + + <p>Numerous bug fixes, including assertion fixes in the MAC + test policy relating to execution and relabeling. (Merged)</p> + </body> + </project> + + <project> + <title>TrustedBSD Access Control Lists (ACLs)</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <given>TrustedBSD Discussion Mailing List</given> + + </name> + + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.trustedbsd.org/components.html#acls">TrustedBSD + ACLs page</url> + </links> + + <body> + <p>TrustedBSD Access Control Lists (ACLs) provide extended + discretionary access control support for the UFS and UFS2 + file systems on FreeBSD. They implement POSIX.1e ACLs with + some extensions, and meet the Common Criteria CAPP + requirements. Most ACL-related work is complete, with + remaining tasks associated with userspace integration, third + party applications, and compatibility</p> + + <p>Prototyped Solaris/Linux semantics for combining ACLs and + the umask: if an default ACL mask is defined, substitute that + mask for the umask, permitting ACLs to override umasks. (Not + merged)</p> + </body> + </project> + + <project> + <title>TrustedBSD "Security-Enhanced BSD" -- FLASK/TE Port</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <given>TrustedBSD Discussion Mailing List</given> + </name> + + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/sebsd.html">TrustedBSD + SEBSD page</url> + </links> + + <body> + <p>TrustedBSD "Security-Enhanced BSD" (SEBSD) is a port of NSA's + SELinux FLASK security architecture, Type Enforcement (TE) + policy engine and language, and sample policy to FreeBSD using + the TrustedBSD MAC Framework. SEBSD is available as a loadable + policy module for the MAC Framework, along with a set of + userspace extensions support security-extended labeling calls. + In most cases, existing MAC Framework functions provide the + necessary abstractions for SEBSD to plug in without SEBSD-specific + changes, but some extensions to the MAC Framework have been + required; these changes are developed in the SEBSD development + branch, then merged to the MAC branch as they mature, and then + to the FreeBSD development tree.</p> + + <p>Unlike other MAC Framework policy modules, the SEBSD module + falls under the GPL, as it is derived from NSA's + implementation. However, the eventual goal is to support + plugging SEBSD into a base FreeBSD install without any + modifications to FreeBSD itself.</p> + + <p>TrustedBSD SEBSD development branch in Perforce integrated + to 5.2-RELEASE. Other changes in the MAC branch, including + restructuring of MAC Framework files also integrated, and a + move to zone allocation for labels. See the TrustedBSD MAC + Framework report for more detail on these and other MAC + changes that also affect the SEBSD work.</p> + + <p>FreeBSD PTY code modified so that the MAC Framework and SEBSD + module can create pty's with the label of the process trying + to access them. Improves compatibility with the SELinux + sample policy. (Not yet merged)</p> + + <p>SEBSD now loads its initial policy in the boot loader rather + than using a dummy policy until the root file system is + mounted, and then loading it using VFS operations. This + avoids initial labeling and access control conditions during + the boot.</p> + + <p>security_load_policy() now passes a memory buffer and length + to the kernel, permitting the policy reload mechanisms to + be shared between the early boot load and late reloads. The + kernel SEBSD code now no longer needs to perform direct file + I/O relating to reading the policy. checkpolicy now mmap's + the policy before making the system call.</p> + + <p>SEBSD now enforces protections on System V IPC objects and + methods. Shared memory, semaphores, and message queues are + labeled, and most operations are controlled. The sample + policy has been updated.</p> + + <p>The TrustedBSD MAC Framework now controls mount, umount, and + remount operations. A new MAC system call, mac_get_fs() can + be used to query the mountpoint label. lmount() system call + allows a mount label to be explicitly specified at mount + time. The SEBSD policy module has been updated to reflect + this functionality, and sample TE policy has been updated. + (Not yet merged)</p> + + <p>SEBSD now enforces protections on POSIX semaphores; the sample + policy has been updated to demonstrate how to label and control + sempahores. This includes sample rules for PostgreSQL.</p> + + <p>The SEBSD sample policy, policy syntax, and policy tools have + been updated to the SELinux code drop from August. Bmake these + pieces so we don't need gmake.</p> + + <p>Provide file ioctl() MAC Framework entry point and SEBSD + implementation.</p> + + <p>A large number of sample policy tweaks and fixes. The policy + has been updated to permit cron to operate properly. It has + been updated for FreeBSD 5.2 changes, including dynamically + linked root. Teach the sample policy about FreeBSD's sendmail + wrapper.</p> + + <p>Adapt sysinstall and install process for SEBSD pieces. Teach + sysinstall, newfs, et al, about multilabel file systems, install + SEBSD sample policy pieces, build policy. Automatically load + the SEBSD module on first boot after install.</p> + + <p>Allow "ls -Z" to print out labels without long format.</p> + </body> + </project> + + <project> + <title>TrustedBSD Audit</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <given>TrustedBSD Audit Discussion List</given> + </name> + + <email>trustedbsd-audit@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.trustedbsd.org/components.html#audit">TrustedBSD + Audit Page</url> + + </links> + + <body> + + <p>The TrustedBSD Project is producing an implementation of CAPP + compliant Audit support for use with FreeBSD. Little progress + was made on this implementation between October and December + other than an update to the existing development tree. However, + in January, work began on porting the Darwin Audit + implementation to FreeBSD. Details on this work will appear in + the next report; more information is available on the TrustedBSD + audit discussion list. Perforce messages may be seen on the + trustedbsd-cvs mailing list.</p> + + </body> + </project> + + <project> + <title>TrustedBSD Documentation</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <given>TrustedBSD Discussion Mailing List</given> + + </name> + + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/docs.html">TrustedBSD + Documentation Page</url> + </links> + + <body> + <p>The TrustedBSD Project is implementing many new features + for the FreeBSD Project. It also provides documentation for + users, administrators, and developers.</p> + + <p>mac_support.4 added -- documents TrustedBSD MAC Framework + feature compatibility. See also the MAC Framework report.</p> + + <p>FreeBSD security architecture updated and corrections/additions + made.</p> + + <p>A variety of documentation updates relating to API changes, + including the socket-related API changes in libc/mac(3).</p> + </body> + </project> + + <project> + <title>FreeBSD/MIPS Status Report</title> + + <contact> + <person> + <name> + <given>Juli</given> + + <common>Mallett</common> + </name> + + <email>jmallett@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/mips/" /> + </links> + + <body> + <p>TLB support code and PMAP have come along nicely. GCC and related + have been kept up to date with the main tree. An evaluation board + from Broadcom was donated and initial work on that platform has been + occurring. Much old and obsolete code brought from NetBSD for + bootstrapping the effort has been cleaned up. The system has been + seen to get to the point of trying to initialize filesystems, but + there are still bugs even before that milestone.</p> + </body> + </project> + + <project> + <title>AGP 3.0 Support</title> + + <contact> + <person> + <name> + <given>John</given> + + <common>Baldwin</common> + </name> + + <email>jhb@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Simple support AGP 3.0 including support for AGP 8x mode was + added. The support is simple in that it still assumes only one + master and one target. The main gain is the ability to use AGP + 8x with drm modules that support it.</p> + </body> + </project> + + <project> + <title>Network Subsystem Locking and Performance</title> + + <contact> + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The purpose of this project is to improve performance of the network + subsystem. A major part of this work is to complete the locking of + the networking subsystem so that it no longer depends on the "Giant + lock" for proper operation. Removing the use of Giant will improve + performance and permit multiple instances of the network stack to + operate concurrently on multiprocessor systems.</p> + + <p>Locking of the network subsystem is largely complete. Network + drivers, middleware layers (e.g. ipfw, dummynet, bridge, etc.), the + routing tables, IPv4, NFS, and sockets are locked and operating + without the use of Giant. Much of this work was included in the 5.2 + release, but not enabled by default. The remaining work (mostly + locking of the socket layer) will be committed to CVS as soon as we + can resolve how to handle "legacy protocols" (i.e. those protocols + that are not locked). The code can be obtained now from the Perforce + database. A variety of test and production systems have been running + this code for several months without any obvious issues.</p> + + <p>Performance analysis and tuning is ongoing. Initial results indicate + SMP performance is already better than 4.x systems but UP performance + is still lagging (though improved over -current). The removal of Giant + from the network subsystem has reduced contention on Giant and + highlighted performance bottlenecks in other parts of the system.</p> + + <p>This work was supported by the FreeBSD Foundation.</p> + </body> + </project> + + <project> + <title>Wireless Networking Support</title> + + <contact> + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work to merge the NetBSD and MADWIFI code bases is almost complete. + This brings in new features and improves sharing which will enable + future development. Support was added for 802.1x client + authentication (using the open1x xsupplicant program) and for shared + key authentication (both client and AP) which improves interopability + with systems like OS X. The awi driver was updated to use the common + 802.11 layer and the Atheros driver received extensive work to support + hardware multi-rate retry. Kismet now works with the + device-independent radiotap capture format. All of this work is still + in Perforce but should be committed to CVS soon. </p> + + <p>Work has begun on full 802.1x and WPA support.</p> + + </body> + </project> + + <project> + <title>SMPng Status Report</title> + + <contact> + <person> + <name> + <given>John</given> + + <common>Baldwin</common> + </name> + + <email>jhb@FreeBSD.org</email> + </person> + + <person> + <email>smp@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/smp/" /> + </links> + + <body> + <p>Work is progressing on SMPng on several different fronts. Sam + Leffler and several other folks have been working on locking the + network stack as mentioned elsewhere in this update. Several + infrastructure improvements have been made in the past few months + as well.</p> + + <p>The low-level interrupt code for the i386 architecture has been + redesigned to allow for a runtime selection between different types + of interrupt controllers. This work allows the Advanced Programmable + Interrupt Controllers (APICs) to be used instead of the AT 8259A PIC + without having to compile a separate kernel to do so. It also allows + the APIC to be used in a UP kernel as well as on a UP box. Together, + all these changes allow an SMP kernel to work on a UP box and thus + allowed SMP to be enabled in GENERIC as it already is on all of the + other supported architectures. This work also reworked the APIC + support to correctly route PCI interrupts when using an APIC to + service device interrupts. This work was also used to add SMP support + to the amd64 port.</p> + + <p>A turnstile implementation was committed that implemented a queue + of threads blocked on a resource along with priority inheritance of + blocked threads to the owner of the resource. Turnstiles were then + used to replace the thread queue built into each mutex object which + shrunk the size of each mutex as well as reduced the use of the + sched_lock spin mutex.</p> + </body> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2004-01-2004-02.xml b/en_US.ISO8859-1/htdocs/news/status/report-2004-01-2004-02.xml new file mode 100644 index 0000000000..2f068f62f4 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2004-01-2004-02.xml @@ -0,0 +1,869 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2004-01-2004-02.xml,v 1.6 2006/08/19 21:20:40 hrs Exp $ --> +<report> + <date> + <month>January-February</month> + <year>2004</year> + </date> + + <section> + <title>Introduction:</title> + + <p>2004 started with another exciting two months for the project. + FreeBSD 5.2 was released in early January and then quickly followed + in February with the 5.2.1 bug-fix release. Looking forward, we + are expecting a late-April release date for FreeBSD 4.10, and + mid-summer date for FreeBSD 5.3. And don't forget to support the + FreeBSD vendors and developers by buying a copy of the latest CD + or DVD sets.</p> + + <p>Thanks,</p> + + <p>Scott Long</p> + </section> + + <project> + <title>Disk and device I/O</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + <common>Kamp</common> + </name> + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>In the overall area of disk and device I/O, a significant + milestone was reached with the implementation of proper + reference counting on dev_t. We are now able to properly + allocate and free dev_t. Cloning device drivers also had + the job made easier for them with the addition of the unit + number management routines.</p> + <p>It is not quite decided which will be the next step in + the quest for a truly SMPng I/O subsystem, but a leading + candidate is to implement the device-access vnode bypass + to get more concurrency in the system: Instead of taking + the tour through the vnodes for each i/o operation on a + device we will go directly from the file descriptor layer to + DEVFS/SPECFS. In addition to Giant-less disk I/O, + this should enable us to pull the entire tty subsystem + and the PTY driver out from under Giant and we expect that + to improve the "snappiness" of the system measurably.</p> + </body> + </project> + <project> + <title>The FreeBSD Dutch Documentation Project.</title> + <contact> + <person> + <name> + <given>Remko</given> + <common>Lodder</common> + </name> + <email>remko@elvandar.org</email> + </person> + </contact> + <body> + <p>The Dutch Documentation Project is a ongoing project in + translating the handbook and other documentation to the dutch + language. Currently there is 1 active person (me) translating the + documentation. I am currently working on the handbook/basics + section. But i can use some more hands, please drop me an email if + you wish to help out so that the dutch translation will speed up + and be ready in some time. Contact remko@elvandar.org for + information.</p> + </body> + </project> + <project> + <title>Weekly cvs-src summaries</title> + + <contact> + <person> + <name> + <given>Mark</given> + <common>Johnston</common> + </name> + <email>mark@xl0.org</email> + </person> + </contact> + <links> + <url href="http://excel.xl0.org/FreeBSD/" /> + <url href="http://mocart.pinco.pl/FreeBSD/">Polish translations</url> + </links> + + <body> + <p>I have been producing weekly summaries of commits and the + surrounding discussions as reported on the cvs-src mailing list. + These summaries are posted to -current on Sunday evenings and + archived on the Web. The reception has been overwhelmingly good. + As of the end of February, Polish translations are being produced + by Lukasz Dudek and Szymon Roczniak; they are also + planning to translate the older summaries.</p> + </body> + </project> + <project> + <title>libarchive/bsdtar</title> + <contact> + <person> + <name> + <given>Tim</given> + <common>Kientzle</common> + </name> + <email>kientzle@FreeBSD.org</email> + </person> + </contact> + <links> + <url href="http://people.FreeBSD.org/~kientzle/"/> + </links> + <body> + <p>libarchive, with complete documentation, has been committed to + -CURRENT. bsdtar should follow soon. For a few months, gtar + and bsdtar will both be available in the base system. Once + bsdtar is in the tree, I hope to resume work on libpkg and my + pkg_add rewrite.</p> + + <p>Note that bsdtar is not an exact replacement for gtar: it does + some things better (reads/writes standard formats, archive ACLs + and file flags, detects format and compression automatically), + some things worse (does not handle multi-volume archives or + sparse files) and a few things just different (writes POSIX-format + archives by default, not GNU-format). The command lines are + sufficiently similar that most users should have no problems + with the transition. However, people who rely on peculiar + options or capabilities of gtar may have to look to ports.</p> + </body> + </project> + <project> + <title>Network interface naming changes</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The first actual feature related to the if_xname conversion was + committed in early February. Network interfaces can now be + renamed with "ifconfig <if> name <newname>".</p> + + <p>Work is slowly progressing on a new network interface cloning API + to enable interesting cloners like auto-configurating vlans. + This work is taking place in the perforce repository under: + //depot/user/brooks/xname/...</p> + </body> + </project> + <project> + <title>PowerPC Port</title> + + <contact> + <person> + <name> + <given>Peter</given> + <common>Grehan</common> + </name> + <email>grehan@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>After a slow time at the end of last year due to a disk crash, + the project is moving along rapidly. The loader is fully + functional with Forth support. Syscons has been integrated. + New Powerbook models are supported. Work is starting on a + G5 port.</p> + + <p>There's still lots to do, so as usual volunteers are most + welcome.</p> + </body> + </project> + <project> + <title>The FreeBSD Simplified Chinese Project</title> + <contact> + <person> + <name> + <given>Dong</given> + <common>LI</common> + </name> + <email>ld@FreeBSD.org.cn</email> + </person> + <person> + <name> + <given>Xin</given> + <common>LI</common> + </name> + <email>delphij@frontfree.net</email> + </person> + </contact> + <links> + <url href="http://www.FreeBSD.org.cn">The FreeBSD Simplified + Chinese Project (In Simplified Chinese)</url> + <url href="http://www.FreeBSD.org.cn/snap/zh_CN/">Translated + Website Snapshot</url> + <url href="http://www.FreeBSD.org.cn/snap/doc/zh_CN.GB2312/books/handbook/">Translated Handbook Snapshot</url> + </links> + <body> + <p>The project is a joint effort of volunteers, which focus in + the internationalization and localization of the FreeBSD + Operating System and applications running on FreeBSD. All of the + work resulted in this project will be contributed back to the + FreeBSD project.</p> + <p>Thanks to many volunteers' help, by this time of writing, we + have finished more than 60% of the translation of the FreeBSD + Handbook. We plan to submit a preliminary translation of the + FreeBSD website as well as the FreeBSD Handbook when most part of + them were finished, which is expected to happen in a couple of + months. The snapshot of the documentation translation effort + could be accessed through the URL listed above.</p> + <p>The project also supported individual efforts on porting + applications (especially software that supports Simplified + and/or Traditional Chinese) to FreeBSD. We are also doing some + research on making FreeBSD kernel and base system more + i18n-aware.</p> + </body> + </project> + <project> + <title>Verify source reachability option for ipfw2</title> + <contact> + <person> + <name> + <given>Andre</given> + <common>Oppermann</common> + </name> + <email>andre@FreeBSD.org</email> + </person> + </contact> + <links> + <url href="http://www.nrg4u.com/freebsd/ipfw_versrcreach.diff"/> + </links> + <body> + <p>The verify source reachability option for ipfw2 checks if the + source IP address of a packet entering the machine is reachable + at all. Thus if we can't send a packet back because we don't + have a route back we don't have to forward it because two way + communication isn't possible anyway. It is more than likely + that such a packet is spoofed. This option is almost the same as + what is known on Cisco IOS as "ip verify unicast source + reachable-via [any|ifn]". Using this option only makes sense + when you don't have a default route which naturally always + matches. So this is useful for machines acting as routers with + a default-free view of the entire Internet as common when running + a BGP daemon (Zebra/Quagga or OpenBSD bgpd).</p> + <p>One useful way of enabling it globally on a router looks like + this: ipfw add xxxx deny ip from any to any not versrcreach or for + an individual interface only: ipfw add xxxx deny ip from any to + any not versrcreach recv fxp0</p> + </body> + </project> + + <project> + <title>Move ARP out of routing table</title> + <contact> + <person> + <name> + <given>Andre</given> + <common>Oppermann</common> + </name> + <email>andre@FreeBSD.org</email> + </person> + </contact> + <body> + <p>The ARP IP address to MAC address mapping does not belong into + the routing table (FIB) as it is currently done. This will move + it to its own hash based structure which will be instantiated + per each 802.1 broadcast domain. With this change it is possible + to have more than one interface in the same IP subnet and layer 2 + broadcast domain. The ARP handling and the routing table will be + quite a bit simplified afterwards. As an additional benefit full + MAC address based accosting will be provided. Work on this + project is already in progress.</p> + </body> + </project> + <project> + <title>Automatic sizing of TCP send buffers</title> + <contact> + <person> + <name> + <given>Andre</given> + <common>Oppermann</common> + </name> + <email>andre@FreeBSD.org</email> + </person> + </contact> + <body> + <p>The current TCP send and receive buffers are static and set to a + conservative value to preserve kernel memory. This is sub-optimal + for connections with a high bandwidth*delay product because the + size of the TCP send buffer determines how big the send window + can get. For high bandwidth trans-continental links this seriously + limits the maximum transfer speed per TCP connection. For example + a 170ms RTT and a 32kB send buffer limit the speed to approximately + 1.5Mbit per second even thought you might have a 10Mbit pipe.</p> + <p>This project makes the TCP send buffer to automatically adapt to + the optimal buffer size for maximal link usage. In the case + above this would be a buffer of approximately 220kB. The main + challenge is to have a stable and reliable measurement of the link + parameters and manage the kernel memory properly and in a fair way. + We don't want to have a few connections to monopolize all available + socket buffer space and many edge cases have to be considered. The + first implementation will be tuned conservatively but even that + will provide significantly better performance than the static + buffers currently. Work on this project is already in + progress.</p> + </body> + </project> + + <project> + <title>Testbed for testing and qualification of TCP performance</title> + <contact> + <person> + <name> + <given>Andre</given> + <common>Oppermann</common> + </name> + <email>andre@FreeBSD.org</email> + </person> + </contact> + <body> + <p>The TCP performance test and qualification testbed is an automated + environment that simulates various common and uncommon end-to-end + network and link characteristics such as delay, bandwidth + limitations, congestion, packet drops, packet corruption and out + of order arrival. The testbed automatically steps through all + link types and tests various TCP optimizations and parameter + adjustments. In the end all data is graphically arranged and + compared against standard behaviour and each other to judge the + positive or negative effects of the modifications. Work on this + project has just started and is based on FreeBSDs dummynet.</p> + </body> + </project> + <project> + <title>FreeBSD ports monitoring system</title> + + <contact> + <person> + <name> + <given>Mark</given> + <common>Linimon</common> + </name> + <email>linimon_at_lonesome_dot_com</email> + </person> + </contact> + + <links> + <url href="http://portsmon.firepipe.net/index.html"> + FreeBSD ports monitoring system</url> + </links> + + <body> + <p>Thanks to the loan of a box by Will Andrews, the system has + been moved into production. The previous installation + at lonesome.com now refers you to the new system. As part of + the installation, a preliminary + <a href="http://portsmon.firepipe.net/faq.html">FAQ</a> was + added.</p> + <p>The database is updated once per hour.</p> + <p>New reports available include ones about ports marked DEPRECATED, + since that function has now been incorporated into bsd.port.mk. + (The author hopes that this will allow the port deprecation process + to be much more visible to the general FreeBSD user community.) In + addition, a report for ports marked FORBIDDEN was added (the code + was essentially the same).</p> + <p>The next topic of interest is to try to identify ports which are + slave ports because the status of these ports is not currently + being updated automatically. This problem also affects + FreshPorts. PR ports/63683 is an attempt to address this problem. + Also, preliminary work has been done on creating some graphs and + charts for various statistics, and in creating a tool to browse + port dependencies for the entire ports tree.</p> + <p>Some general observations about the trends in ports PRs can be + made: + <ul> + <li>In the past 6 months, the amount of time to get ports PRs + committed has dropped dramatically. (This is especially + true of PRs for new ports.)</li> + <li>The queue of PRs for existing ports that are unmaintained + has similarly been trimmed. Both of these two items are due + in large part to a few very active committers (how do they + ever get their "real" work done?) Thanks, guys, you know who + you are.</li> + <li>There is still a fairly high number of PRs (~400/~750) which + apply to existing ports, and have been assigned to a FreeBSD + committer. This represents around 370 individual ports. We + seem to have a much harder time getting these numbers to go + down; basically, we just hold our own most weeks. This is + somewhat disappointing.</li> + <li>The number of ports marked BROKEN has jumped dramatically, + currently standing at over 250 (for i386-current). This + represents less a sudden problem as it does Kris' effort to + bring existing brokenness to people's attention -- thus, a + much larger percentage of ports with build errors are now + labeled as BROKEN.</li> + <li>Approximately two-thirds of the port build errors are still + due to compilation problems, primarily from the gcc3.3 import. + Another 10% fail to install correctly. The reasons for the + others are more varied.</li> + </ul> + </p> + </body> + </project> + <project> + <title>FreeSBIE</title> + <contact> + <person> + <name> + <given>FreeSBIE</given> + <common>Staff</common> + </name> + <email>staff@FreeSBIE.org</email> + </person> + </contact> + <links> + <url href="http://www.freesbie.org">FreeSBIE Home</url> + <url href="mailto:freesbie@gufi.org">FreeSBIE Mailing + List</url> + <url href="http://www.freesbie.org/?section=mirror-en">FreeSBIE + Mirror List</url> + </links> + <body> + <p>The FreeSBIE Project aims to develop a set of scripts that allow + anyone to create their own FreeBSD Bootable Cdrom, with their own + set of installed packages. The Project releases an ISO builded + with FreeSBIE scripts, to show what they can do. On Sunday 29 + February 2004, FreeSBIE 1.0 was released and it had a great + success, as there were post on Slashdot.org, OSnews, DaemonNews + and BSDForums. Thanks to the huge amount of feedback they got, + FreeSBIE Developers are now developing new features such as + support for archs different from i386. Website redesign is on the + way too.</p> + </body> + </project> + <project> + <title>kgi4BSD</title> + <contact> + <person> + <name> + <given>Nicholas</given> + <common>Souchu</common> + </name> + <email>nsouch@FreeBSD.org</email> + </person> + </contact> + <links> + <url href="http://www.FreeBSD.org/~nsouch/kgi4BSD"> Project URL</url> + </links> + + <body> + <p>Move to Perforce is done. I spent some time on building a + common compilation tree with Linux: until now drivers were + build in a FreeBSD makefile tree, not compatible with Linux.</p> + + <p>The next priorities are ANSI support and keymaps in the + KGC Kernel Graphic Console system.</p> + </body> + </project> + + <project> + <title>FreeBSD/ia64</title> + + <contact> + <person> + <name> + <given>Marcel</given> + <common>Moolenaar</common> + </name> + <email>marcel@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/platforms/ia64/index.html"> + Home page.</url> + </links> + + <body> + <p>Work on the PMAP overhaul has been put into gear. A lot of issues + will be addressed, including support for sparse physical memory + and of course SMP. Performance will be addressed to the extend + possible, but functionality has priority. The redesign will lay + the foundation for NUMA support where possible. An example of this + is limiting TLB shootdowns to processors that actually have or had + TLBs belonging to the PMAP loaded. Of course, without NUMA + hardware the implementation of NUMA support is quite limited.</p> + </body> + </project> + <project> + <title>FreeBSD Package Grid</title> + + <contact> + <person> + <name> + <given>Kris</given> + <common>Kennaway</common> + </name> + <email>kris@FreeBSD.org</email> + </person> + </contact> + + <body> + + <p>Distributed package builds are currently done using a set of + home-grown shell scripts for managing, scheduling and + dispatching of package builds on the client machines. This has + been sufficient for our needs in the past, but has a number of + significant shortcomings that limit future growth. I am + rewriting the package build scripts to work on top of Sun + GridEngine (ports/sysutils/sge), as a client application of a + "FreeBSD package grid". Some of the design goals for the new + system are:</p> + + <ul> + <li>Better robustness against machine failure, and more efficient + scheduling of build jobs</li> + <li>Support for remote build machines, to make better use of machine + resources and clusters that are not on the same LAN as the + build master</li> + <li>Ability for other committers to submit port build jobs to the + system, for testing of changes, new ports, etc.</li> + </ul> + + </body> + </project> + <project> + <title>vinum + GEOM</title> + <contact> + <person> + <name> + <given>Lukas</given> + <common>Ertl</common> + </name> + <email>le@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://mailbox.univie.ac.at/~le/geom_vinum.tar.gz" /> + </links> + + <body> + <p>The "geomification" of vinum has made some progress. I now have + all basic setups working (concatenated plexes, striped plexes, + RAID5 plexes, and RAID1), but I still have to implement correct + error handling and status change handling.</p> + <p>Still missing is a userland tool, so currently you still have to + use "old-style" vinum to configure your setup.</p> + </body> + </project> + <project> + <title>NanoBSD</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + <common>Kamp</common> + </name> + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>NanoBSD, src/tools/tools/nanobsd, is a tool for stuffing FreeBSD + onto small disk media (like CompactFlash) for embedded + applications. The disk image is built with three partitions, two + for software images and one for configuration files. Having two + software partitions means that new software can be uploaded to the + non-active partition while running off the active partition.</p> + <p> The first really public version has been committed and many + suggestions and offers of patches have started pouring in.</p> + </body> + </project> + <project> + <title>Porting OpenBSD's pf</title> + <contact> + <person> + <name> + <given>Max</given> + <common>Laier</common> + </name> + <email>max@love2party.net</email> + </person> + <person> + <name> + <given>Pyun</given> + <common>YongHyeon</common> + </name> + <email>yongari@kt-is.co.kr</email> + </person> + </contact> + + <links> + <url href="http://pf4freebsd.love2party.net/" /> + <url href="http://www.benzedrine.cx/pf.html">PF homepage</url> + <url href="http://openbsd.org/faq/pf/index.html">PF FAQ</url> + <url href="http://www.rofug.ro/projects/freebsd-altq/">ALTQ</url> + </links> + + <body> + <p>The sources were imported from OpenBSD 3.4R and patched with + diffs obtained from the port. Since March the 8th it is linked + to the build and install. There is some more work to be done in + order make pf a home inside the tree, but the biggest hunk of + work was lifted during the past two month.</p> + <p>OpenBSD 3.5 is scheduled for early May, so we might see an update + before 5.3R. Work towards integration of the - often requested + - ALTQ framework is in progress also, though it is not yet clear + how well it goes along with the ongoing work towards a giant free + net stack.</p> + </body> + </project> + <project> + <title>FreeBSD/arm Status Report</title> + <contact> + <person> + <name> + <given>Olivier</given> + <common>Houchard</common> + </name> + <email>cognet@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Development goes reasonably fast, right now it boots single user. + It is still very simics-centric, and it deserves a huge cleanup + and a few bug fixes, but there's already a decent amount of code + to work with, mostly taken from NetBSD. I now plan to work on real + hardware support (as soon as I can get some), to get the missing + userland bits (mainly rtld and the pthread libs) so that I can + build a full world.</p> + </body> + </project> + <project> + <title>SGI XFS port for FreeBSD</title> + <contact> + <person> + <name> + <given>Alexander</given> + <common>Kabaev</common> + </name> + <email>kan@FreeBSD.org</email> + </person> + <person> + <name> + <given>Russell</given> + <common>Cattelan</common> + </name> + <email>cattelan@thebarn.com</email> + </person> + </contact> + + <body> + <p>Not much has changed since last report was submitted. The + read-only access XFS volumes is quite stable now. The work is + underway to rewrite xfs_buf layer to minimize local changes + intrusiveness. Initial attempt to make XFS code to compile and + run on amd64 is in progress too.</p> + <p>We really need a care-taker for our userland tools.</p> + </body> + </project> + <project> + <title>Compile FreeBSD with Intels C compiler (icc)</title> + + <contact> + <person> + <name> + <given>Alexander</given> + <common>Leidinger</common> + </name> + <email>netchild@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.Leidinger.net/FreeBSD/">Some patches.</url> + </links> + + <body> + <p>If nothing bad happened, the icc patches got committed around + the date of the deadline for submissions of this report. Please + search the archives of -current and/or cvs-all for more + information.</p> + + <p>The next steps in this project are to + <ul> + <li>fix the kernel to also run without problems when compiled + with icc v8</li> + <li>fix the kernel if some problems surface after more people + give it a try</li> + <li>get some ports to compile with icc</li> + </ul> + </p> + </body> + </project> + <project> + <title> + Bluetooth stack for FreeBSD (Netgraph implementation) + </title> + + <contact> + <person> + <name> + <given>Maksim</given> + <common>Yevmenkin</common> + </name> + <email>m_evmenkin@yahoo.com</email> + </person> + </contact> + + <body> + <p>Not much to report. Bluetooth Service Discovery Procotol daemon + sdpd was integrated with existing Bluetooth utilities. From now + on users should not use GNU sdpd (Linux BlueZ port).</p> + <p>Bluetooth HID profile implementation is almost complete. Thanks + to Matt Peterson < matt at peterson dot org > for giving me + Bluetooth keyboard and mouse for development.</p> + </body> + </project> + <project> + <title>FreeBSD GNOME Project Report</title> + + <contact> + <person> + <name> + <given>FreeBSD</given> + <common>GNOME Team</common> + </name> + <email>gnome@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/gnome/">FreeBSD GNOME Project + Site.</url> + </links> + + <body> + <p>It has been a year since our last status report, but we + haven't slowed down. Since the last report, Alexander + Nedotsukov (bland) and Pav Lucistnik (pav) have joined the + FreeBSD GNOME team. GNOME 2.4 was released back in September + 2003, followed by 2.4.1 and 2.4.2. We are actively working on + getting GNOME 2.6.0 out the door at the end of March. GNOME 2.6 + Beta releases can be obtained via the project URL above.</p> + + <p>To help make GNOME 2.6.0 our best release to date, we have + created a script to automate the upgrade from GNOME 2.4. We + also have a new GNOME + <a href="http://www.marcuscom.com/tinderbox/">package build + server</a> + that builds and serves i386 packages for all supported FreeBSD + releases. We plan on having the GNOME 2.6.0 packages available + the moment 2.6.0 hits the ports tree.</p> + + <p>Included in the release of GNOME 2.6 is GTK+ 2.4, the next + installment in the GTK+ 2 series. Because GTK+ 2 has become + very stable over the past few years, the FreeBSD GNOME Team is + pushing for GTK+ 2 support to be included by default in all + applications that support it. This has already been done with + Mozilla, Firefox, and Thunderbird. A complete GNOME Desktop and + application environment can already be built using only GTK+ 2. + The ultimate goal is to phase GTK+ 1 out of the ports tree.</p> + </body> + </project> + <project> + <title>Network Stack Locking</title> + + <contact> + <person> + <name> + <given>Sam</given> + <common>Leffler</common> + </name> + <email>sam@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>This project is aimed at converting the FreeBSD network stack from + running under the single Giant kernel lock to permitting it to + run in a fully parallel manner on multiple CPUs (i.e., a fully + threaded network stack). This will improve performance/latency + through reentrancy and preemption on single-processor machines, + and also on multi-processor machines by permitting real + parallelism in the processing of network traffic. As of FreeBSD + 5.2, it was possible to run low level network functions, as well + as the IP filtering and forwarding plane, without the Giant lock, + as well as "process to completion" in the interrupt handler.</p> + + <p>Work continues to improve the maturity and completeness of + the locking (and performance) of the network stack for 5.3. The + network stack locking development branch has been updated to the + latest CVS HEAD, tracking a variety of FreeBSD changes, including + tracking and driving changes in the interface and device cloning + APIs, push-down and fixes to locking in the Berkeley Packet + Filter, consistency improvements in allocation flags for network + objects, diagnosis of excessive acquisition of Giant in various + system callouts and timeouts, removal of Giant from several + system callouts, "const"-ification of a number of global + variables in the network stack (IPv4, IPv6, elsewhere) as part of + ananalysis of locking requirements, fine-grain locking of a + number of pseudo-interfaces (disc, loopback, faith, stf, gif, tap, + tun), IP encapsulation and tunneling, initial review and locking + of parts of PPP and SLIP, experimentation with PCB assertions on + IPv6, additional socket locking assertions, graphing of the FreeBSD + sockets layer to support locking analysis, merging of theMT_TAG to + m_tag conversion to improve the ability to queue packets, moving + of the debug.mpsafenet tunable to controlling Giant over the + forwarding plane to Giant over the entire stack("dual-mode" to + support non-MPSAFE protocols), adaption of existing network lock + assertions to also assert Giant when running non-MPSAFE, analysis + of high cost of select() locking, improved locking and + synchronization annotations, TCP callouts run MPSAFE, logtimeout() + runs MPSAFE, uma_timeout() runs MPSAFE, callout sampling + instrumentation, loadav() runs MPSAFE, AppleTalk locking begun: + AARP locked down and DDP analysis, rawcb list locked, locking + analysis of mrouter and IP ID code, IGMP locked, IPv6 analysis + begun, IPX/SPX analysis begun, PPP timeouts converted to callouts, + Netgraph analysis begun. Many of these changes have not yet been + merged to the main FreeBSDtree, but this is a work in progress.</p> + + <p>In related work on Pipe IPC (not quite network stack locking), + substantial time was invested in diagnosing an increase in the + cost of pipe allocation since FreeBSD 4.x, as well as coalescing + the several allocations needed to create a pipe, as well as moving + to slab allocation so as to amortize the cost of pipe + initialization. Future work here will include caching the VM + structures supporting pipe buffers.</p> + + <p>Recent contributors include Robert Watson, Sam Leffler, MaxLaier, + Maurycy Pawlowski-Wieronski, Brooks Davis, and many others who are + omitted here only by accident.</p> + </body> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2004-03-2004-04.xml b/en_US.ISO8859-1/htdocs/news/status/report-2004-03-2004-04.xml new file mode 100644 index 0000000000..52d809ffa4 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2004-03-2004-04.xml @@ -0,0 +1,1156 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2004-03-2004-04.xml,v 1.4 2006/08/19 21:20:40 hrs Exp $ --> + +<report> + <date> + <month>March-April</month> + <year>2004</year> + </date> + + <section> + <title>Introduction</title> + + <p>2004 continues on with wonderful progress. Work continues on locking + down the network stack, ACPI made more great strides, an ARM port + appeared in the tree, and the FreeBSD 4.10 release cycle wrapped up. + Once 4.10 is released, the next big focus will be FreeBSD 5.3. We + expect this is be the start of the 5-STABLE branch, meaning that not + only will it be stable for production use, it will also be largely + feature complete and stable from an internal API standpoint. We expect + to release 5.3 in mid-summer, and we encourage everyone to download the + latest snapshots from <url href="ftp://snapshots.jp.FreeBSD.org"/> + for a preview.</p> + <p>Thanks,</p> + <p>Scott Long</p> + </section> + + <project> + <title>OpenOffice.org porting status</title> + + <contact> + <person> + <name> + <given>NAKATA</given> + <common>Maho</common> + </name> + <email>maho@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>After almost three years efforts for porting OpenOffice.org 1.0.x and + 1.1.0 for FreeBSD by Martin Blapp (mbr@FreeBSD.org) and other + contributors, There are four version of OpenOffice.org (OOo) in ports + tree. 1.1.1: stable version, 1.1.2: next stable, 2.0: developer and + 1.0.3: legacy. + </p> + + <p>Stable version 1.1.1 in /usr/ports/editors/openoffice-1.1/ + builds/installs/works fine for 5.2.1-RELEASE. Packages for + 5.2.1-RELEASE, 26 localized versions and 4.10-PRELEASE only English + version, are available at + http://oootranslation.services.openoffice.org/pub/OpenOffice.org/ooomisc/ + (note: source of OOo 1.1.1.RC3 is identical OOo 1.1.1)</p> + + <p>Patches needed to build are currently 18 for 1.1.1, and 161 for 1.0.3 + the number of patches are greatly reduced.</p> + + <p>OOo 1.1.2, the next stable version in + /usr/ports/editors/openoffice-1.1-devel is also builds/installs/works + fine for 5.2.1-RELEASE. We are planning to upgrade this port as soon + as 1.1.2 will be released.</p> + + <p>Next major release, 2.0 (planned to be released at January 2005 + according to + http://development.openoffice.org/releases/OpenOffice_org_trunk.html), + /usr/ports/editors/openoffice-2.0-devel, now compiles for + 5.2.1-RELEASE but have big problem that prohibits to remove BROKEN.</p> + + <p>Legacy version, OOo 1.0.3: /usr/ports/editors/openoffice-1.0/ I'm not + interested in this port. We hope someone else will maintain this.</p> + + <p>For builds, my main environment is 5.2.1-RELEASE, and I have no access + to 4-series, so several build problems had been reported for 5-current + and 4-stable, however, they now seems to be fixed. Please make sure + your Java and/or kernel are up-to-date.</p> + + <p>For version 1.1.1, yet we have serious reproducible core dumps, this + means OOo cannot pass the Quality Assurance protocol of OpenOffice.org + (http://qa.openoffice.org), so we cannot release OOo as quality + assured package. It seems to be FreeBSD's userland bug, since some + reports show that there are no problem for 4-stable but we still + searchingthe reason.</p> + + <p>Note that developers should sign JCA (Joint Copyright Assignment) + before submitting patches via PR or e-mail, otherwise patches won't be + integrated to OOo's source tree. We seriously need more developers, + testers and builders.</p> + </body> + </project> + + <project> + <title>Network interface naming changes</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>An enhanced network interface cloning API has been created. It + allows interfaces to support more complex names than the current + name# style. This functionality has been used to enable + interesting cloners like auto-configuring vlan interfaces. Other + features include locking of cloner structures and the ability of + drivers to reject destroy requests. A patch has been posted to + the freebsd-net mailing list for review and will be committed in + early May. This work is taking place in the perforce repository + under: //depot/user/brooks/xname/...</p> + </body> + </project> + + <project> + <title>FreeBSD Dutch Documentation Project</title> + <contact> + <person> + <name> + <given>Remko</given> + <common>Lodder</common> + </name> + <email>remko@elvandar.org</email> + </person> + </contact> + + <links> + <url href="http://www.evilcoder.org/index.cgi?i=nav&t=freebsd">Status and download of the documentation (not yet complete)</url> + </links> + + <body> + <p>The FreeBSD Dutch Documentation Project is a ongoing project in + translating the handbook and other documentation to the Dutch + language. Currently we have a small team of individuals who + translate, check other's work, and publish them on the internet. + You can view the current status on the webpage (listed above). + Still we can use more people helping out, since we have a long + way to go. Every hand that wants to help, contact me, and i will + provide you details on how we work etc. Currently the project has + translated the handbook pages of: The X Windows System, and + Configuration and Tuning, they only need to be checked before + publishing.</p> + </body> + </project> + + <project> + <title>ACPI</title> + + <contact> + <person> + <name> + <given>Nate</given> + <common>Lawson</common> + </name> + <email>njl@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.root.org/~nate/freebsd/">ACPI TODO</url> + <url href="http://lists.freebsd.org/mailman/listinfo/freebsd-acpi"> + ACPI Mailing List</url> + </links> + + <body> + <p>Much of the ACPI project is waiting for architectural changes to be + completed. For instance, the cpufreq driver requires newbus + attachments for CPUs. Support code for this should be committed + at the time of publication. Other architectural changes needed + include rman support for memory/port resources and a generic hotkey + and extras driver. Important work in other areas of the kernel + including PCI powerstate support and APIC support have been + invaluable in improving ACPI on modern platforms. Thanks go to + Warner Losh and John Baldwin for this work.</p> + + <p>Code which is mostly completed and will go in once the groundwork + is finished includes the cpufreq framework, an ACPI floppy controller + driver, and full support for dynamic Cx states.</p> + + <p>ACPI-CA was updated to 20040402 in early April. This has some GPE + issues that persist in 20040427 that will hopefully be resolved by + the date of publication.</p> + + <p>I'd like to welcome Mark Santcroos (marks@) to the FreeBSD team. + He has helped in the past with debugging ACPI issues. + If any developers are interested in assisting with ACPI, please + see the ACPI TODO and send us an email.</p> + </body> + </project> + + <project> + <title>Verify source reachability option for ipfw2</title> + <contact> + <person> + <name> + <given>Andre</given> + <common>Oppermann</common> + </name> + <email>andre@FreeBSD.org</email> + </person> + </contact> + <links> + <url href="http://www.freebsd.org/news/status/report-jan-2004-feb-2004.html#Verify-source-reachability-option-for-ipfw2"/> + <url href="http://www.freebsd.org/cgi/man.cgi?query=ipfw&apropos=0&sektion=0&manpath=FreeBSD+5.2-current&format=html"/> + </links> + <body> + <p>The verify source reachability option for ipfw2 has been committed + on 23. April 2004 to FreeBSD-CURRENT. For more information see the + links above.</p> + </body> + </project> + + <project> + <title>Convert ipfw2 to use PFIL_HOOKS mechanism</title> + <contact> + <person> + <name> + <given>Andre</given> + <common>Oppermann</common> + </name> + <email>andre@FreeBSD.org</email> + </person> + </contact> + <links> + <url href="http://www.nrg4u.com/freebsd/ipfw-pfilhooks-and-more-20040510.diff"/> + </links> + <body> + <p>ipfw2 is built directly into ip_input() and ip_output() and it makes + these functions more complicated. For some time now we have the + generic packet filter mechanism PFIL_HOOKS which are used by IPFILTER + and the new OpenBSD PF firewall packages to hook themselves into the + IP input and output path.</p> + <p>This patch makes ipfw2 fully self contained and callable through the + PFIL_HOOKS. This is still work in progress and DUMMYNET and IPDIVERT + plus Layer2 firewall are not yet fully functional again but normal + firewalling with it works just fine.</p> + <p>The patch contains some more cleanups of ip_input() and ip_output() + that is work in progress too.</p> + </body> + </project> + + <project> + <title>Move ARP out of routing table</title> + <contact> + <person> + <name> + <given>Luigi</given> + <common>Rizzo</common> + </name> + <email>luigi@FreeBSD.org</email> + </person> + <person> + <name> + <given>Andre</given> + <common>Oppermann</common> + </name> + <email>andre@FreeBSD.org</email> + </person> + </contact> + <links> + <url href="http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026380.html"/> + </links> + <body> + <p>The ARP IP address to MAC address mapping does not belong into + the routing table (FIB) as it is currently done. This will move + it to its own hash based structure which will be instantiated per + each 802.1 broadcast domain. With this change it is possible to + have more than one interface in the same IP subnet and layer 2 + broadcast domain. The ARP handling and the routing table will be + quite a bit simplified afterwards. As an additional benefit full + MAC address based accounting will be provided.</p> + <p>Luigi has become the driver of this project and posted a first + implementation for comments on 25. April 2004 (see link).</p> + </body> + </project> + + <project> + <title>Automatic sizing of TCP send buffers</title> + <contact> + <person> + <name> + <given>Andre</given> + <common>Oppermann</common> + </name> + <email>andre@FreeBSD.org</email> + </person> + </contact> + <links> + <url href="http://www.freebsd.org/news/status/report-jan-2004-feb-2004.html#Automatic-sizing-of-TCP-send-buffers"/> + </links> + <body> + <p>The current TCP send and receive buffers are static and set to a + conservative value to preserve kernel memory. This is sub-optimal + for connections with a high bandwidth*delay product because the + size of the TCP send buffer determines how big the send window can + get. For high bandwidth trans-continental links this seriously + limits the maximum transfer speed per TCP connection. A moredetailed + description from the last status report can be found with the link + above.</p> + <p>Work on this project has been stalled due to some other network stack + projects with higher precedence (ipfw2 to pfil_hooks and + ip_input/ip_output cleanups).</p> + </body> + </project> + + <project> + <title>libarchive/bsdtar</title> + <contact> + <person> + <name> + <given>Tim</given> + <common>Kientzle</common> + </name> + <email>kientzle@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~kientzle/"/> + </links> + + <body> + <p>Both bsdtar and libarchive are now part of -CURRENT. + A few minor problems have been reported and addressed, + including performance issues with many hard-links, and + options required by certain packages. + For now, the "tar" command is still an alias for "gtar." + Those who would like to use bsdtar as the default system tar + can define WITH_BSDTAR to make "tar" be an alias for + "bsdtar."</p> + + <p>My current plan is to make bsdtar be the default in -CURRENT in + about another month, probably after the 5-STABLE split, and remove + gtar from -CURRENT sometime later. It's still open if and when + this switch will occur in 5-STABLE. On the one hand, I see + potential problems if 5-STABLE and 6-CURRENT have different tar + commands; on the other hand, switching could be disruptive for + some users.</p> + + </body> + </project> + + <project> + <title>GEOM Gate</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + + <common>Dawidek</common> + </name> + + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>GEOM Gate class is now committed as well as ggatec(8), ggated(8) + and ggatel(8) utilities. It makes distribution of disk devices + through the network possible, but on the disk level (don't confuse + it with NFS, which provides exporting data on the file system + level).</p> + </body> + </project> + + <project> + <title>Improved Multibyte/Wide Character Support</title> + <contact> + <person> + <name> + <given>Tim</given> + <common>Robbins</common> + </name> + <email>tjr@FreeBSD.org</email> + </person> + </contact> + <body> + <p>New locales: Unicode UTF-8 locales have been added to the base system. + All of the locales previously supported by FreeBSD now have a + corresponding UTF-8 version, along with one or two new ones -- + 53 in all.</p> + <p>Library changes: The restartable conversion functions (mbrtowc(), + wcrtomb(), etc.) in the C library have been updated to handle partial + characters in the way prescribed by the C99 standard. + The <wctype.h> functions have been optimized for handling + large, fragmented character sets like Unicode and GB18030. + Documentation has been improved.</p> + <p>Utilities: The ls utility has been modified to work with wide + characters internally when determining whether a character in a + filename is printable, and how many column positions it takes on + the screen. Character handling in the wc utility has been made + more robust. Other text-processing utilities (expand, fold, unexpand, + uniq) have been modified, but these changes have not been committed + until the performance impact can be evaluated. Work on a POSIX-style + localedef utility has started, with the aim to have it replace + the current mklocale and colldef utilities in FreeBSD 6. + (It is currently on the back-burner awaiting a response to a POSIX + defect report.)</p> + <p>Future directions: wide character handling functions need to be + optimized so that they are more competitive with the single-byte + functions when dealing with 8-bit character sets. Utilities need to + be modified to handle multibyte characters, but with a careful eye + on performance. Localedef needs to be finished.</p> + </body> + </project> + + <project> + <title>ATA project Status Report</title> + + <contact> + <person> + <name> + <given>Søren</given> + <common>Schmidt</common> + </name> + <email>sos@FreeBSD.org</email> + </person> + </contact> + + <body> + There is finally support (except for RAID5) for the Promise SX4/SX4000 + line of controllers. The support is rudimentary still, and doesn't + really make any good use of the cache/sequencer HW yet. The Silicon + Image 3114 support has been completed. Lots of bug fixes and cleanups. + Future work now concentrates on new controller chips (Marvell SATA + chips probably the most prominent) and getting the SATA support + finished so that hotswap etc works with SATA HW as well. Also ATA RAID + is about to get rewritten to take advantage of the features that the + ATA subsystem now offers, including support for the HW on + Promise/Marvell and the like controllers. A number of new RAID metadata + <p>formats (Intel, AMI) is also in the works.</p> + </body> + </project> + + <project> + <title>Porting OpenBSD's packet filter</title> + + <contact> + <person> + <name> + <given>Max</given> + <common>Laier</common> + </name> + <email>mlaier@FreeBSD.org</email> + </person> + <person> + <name> + <given>Daniel</given> + <common>Hartmeier</common> + </name> + <email>dhartmei@FreeBSD.org</email> + </person> + <person> + <name> + <given>Pyun</given> + <common>YongHyeon</common> + </name> + <email>yongari@kt-is.co.kr</email> + </person> + </contact> + + <links> + <url href="http://pf4freebsd.love2party.net/"/> + <url href="http://www.benzedrine.cx/pf.html"/> + <url href="http://openbsd.org/faq/pf/index.html"/> + <url href="http://www.rofug.ro/projects/freebsd-altq/"/> + </links> + + <body> + <p>The two months after the import was done were actually rather quiet. + We imported a couple of minor fixes from the OpenBSD stable branch. + The import of tcpdump 3.8.3 and libpcap 0.8.3 done by Bruce M.Simpson + in late March finally put us into the position to build a working + pflogd(8) and provide rc.d linkage for it. Tcpdump now understandsthe + pflog(4) pseudo-NIC packet format and can be used to read the + log-files.</p> + + <p>There has also been work behind the scenes to prepare an import of + the OpenBSD 3.5 sources. The patches are quite stable already andwill + be posted shortly. Altq is in the making as well and going alongquite + well based on the great work from rofug.ro, but as it needs + modifications to every network driver which have to be tested + thoroughly it needs more time.</p> + </body> + </project> + + <project> + <title>The FreeBSD Simplified Chinese Project</title> + + <contact> + <person> + <name> + <given>Xin</given> + <common>LI</common> + </name> + + <email>delphij@frontfree.net</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org.cn">The FreeBSD Simplified + Chinese Project (In Simplified Chinese)</url> + <url href="http://www.FreeBSD.org.cn/snap/doc/zh_CN.GB2312/books/handbook/"> + Translated Handbook Snapshot</url> + <url href="http://www.freebsd.org.cn/cndocs/translations.html"> + Translation status</url> + <url href="http://www.FreeBSD.org.cn/snap/zh_CN/">Translated + Website Snapshot</url> + </links> + + <body> + <p>We have finished about 75% of the Handbook translation work. + In the last two months we primarily worked on bringing the + handbook chapters more up to date. To make the translation + more high quality we are also doing some revision on it.</p> + <p>We are still looking for manpower on SGML'ifying the FAQ + translation which has been done last year by several volunteers.</p> + </body> + </project> + + + <project> + <title>Cronyx Tau-ISA driver</title> + + <contact> + <person> + <name> + <given>Roman</given> + <common>Kurakin</common> + </name> + <email>rik@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.cronyx.ru/hardware/wan.html">Cronyx WAN Adapters.</url> + </links> + + <body> + <p>ctau(4) driver for Cronyx Tau-ISA was added. Cronyx Tau-ISA is family + of synchronous WAN adapters with various set of interfaces such as + V.35, RS-232, RS-530(449), E1 (both framed and unframed). This is a + second family of Cronyx adapters that is supported by FreeBSD now. The + first one was Cronyx Sigma-ISA, cx(4).</p> + + <p>Cronyx Tau-PCI family will become a third one. The peculiarity of this + driver that it contains private code. This code is distributed as + obfuscated source code with usual open source license agreement.Since + code is protected by obfuscation it is satisfy needs of commerce. On + the other hand it still stays a source code and thus it becomes closer + to open source projects. I hope this form of private code distribution + will become a real alternative to object form.</p> + </body> + </project> + + + <project> + <title>Sync protocols (Netgraph and SPPP)</title> + + <contact> + <person> + <name> + <given>Roman</given> + <common>Kurakin</common> + </name> + <email>rik@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>As part of my work on synchronous protocol stack a ng_sppp driver was + added to the system. This driver allows to use sppp as a Netgraph + node. Now I plan to update sppp driver as much as possible to make it + in sync with Cronyxs one (PPP part). Also I work on FRF.12 support in + FreeBSD (now I have FRF.12 support for Netgraph and SPPP (and for + Cronyx linux fr driver) but only End-to-End). I plan to test it by my + self within a week and after that I plan to make full support of + FRF.12.</p> + <p>If you want to get current version and test it, please feel free to + contact me.</p> + </body> + </project> + + <project> + <title>FreeBSD threading support</title> + <contact> + <person> + <name> + <given>David</given> + <common>Xu</common> + </name> + <email>davidxu@FreeBSD.org</email> + </person> + <person> + <name> + <given>Doug</given> + <common>Rabson</common> + </name> + <email>dfr@FreeBSD.org</email> + </person> + <person> + <name> + <given>Julian</given> + <common>Elischer</common> + </name> + <email>julian@FreeBSD.org</email> + </person> + <person> + <name> + <given>Marcel</given> + <common>Moolinar</common> + </name> + <email>marcel@FreeBSD.org</email> + </person> + <person> + <name> + <given>Dan</given> + <common>Eischen</common> + </name> + <email>deischen@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~marcel/tls.html">basic data on + TLS</url> + <url href="http://www.freebsd.org/kse/index.html">basic threads + page</url> + </links> + + <body> + <p> + Threading developers have been active behind the scenes + though not much has been visible. Real Life(TM) has been + hard on us as a group however.</p> + <p> Marcel and Davidxu have both (individually) + been looking at the support + for debugging threaded programs. David has a set of + patches that allow gdb to correctly handle KSE programs and + patches are being considered for libthr based processes. + Marcel added a Thread ID to allow debugging code to unambiguously + specify a thread to debug. He has also been looking at corefile + support. Both sets of patches are preliminary.</p> + <p>Dan Eischen continues to support people migrating to + libpthreads and it seems to be going well.</p> + <p>Doug Rabson has done his usual miracle work and produced + a set of preliminary patches to implement TLS (Thread + Local Storage) for the i386 platform.</p> + <p>Julian Elischer is investigating some refactoring of the kernel + support code.</p> + <p>Platforms:</p> + <p>i386, amd64, ia64 libpthread works.</p> + <p>alpha, sparc64 not implemented.</p> + </body> + </project> + + <project> + <title>Binary security updates for FreeBSD</title> + <contact> + <person> + <name> + <given>Colin</given> + <common>Percival</common> + </name> + <email>cperciva@daemonology.net</email> + </person> + </contact> + + <links> + <url href="http://www.daemonology.net/freebsd-update/"/> + </links> + + <body> + <p>Having recently passed its first birthday, FreeBSD Update is + now being used on about 170 machines every day; on a typical + day, around 60 machines will download updates (the others being + already up to date). To date, over 157000 files have been + updated on over 4200 machines.</p> + </body> + </project> + + + <project> + <title>PCI Powerstates and Resource</title> + + <contact> + <person> + <name> + <given>Warner</given> + <common>Losh</common> + </name> + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Lazy allocation of pci resources has been merged into the main + tree. These changes allow FreeBSD to run on computers where PnP + OS is set to true. In addition, the saving and restoring of the + resources across suspend/resume has helped some devices come + back from suspend.</p> + + <p>Future work will focus on bus numbering.</p> + </body> + </project> + + <project> + <title>Book: The Design and Implementation of the FreeBSD Operating System</title> + <contact> + <person> + <name> + <given>Kirk</given> + <common>McKusick</common> + </name> + <email>mckusick@FreeBSD.org</email> + </person> + <person> + <name> + <given>George</given> + <common>Neville-Neil</common> + </name> + <email>gnn@neville-neil.com</email> + </person> + </contact> + <links> + <url href="http://www.mckusick.com/FreeBSDbook.html"/> + </links> + <body> + <p>The new Book "The Design and Implementation of the FreeBSD Operating + System" is the successor of the legendary "The Design and + Implementation of 4.4BSD" book which has become the de-facto standard + for teaching of Operating System internals in universities + world-wide.</p> + <p>This new and completely reworked edition is based on FreeBSD 5.2 and + the upcoming FreeBSD 5.3 releases and contains in-details looks into + all areas (from virtual memory management to interprocess + communication and network stack) of the operating system on 700 + pages.</p> + <p>It is now in final production by Addison-Wesley and will be available + in early August 2004. The ISBN is 0-201-70245-2.</p> + </body> + </project> + + <project> + <title>Status Report </title> + <contact> + <person> + <name> + <given>Roland</given> + <common>van Laar</common> + </name> + <email>the_mip_rvl@myrealbox.com</email> + </person> + </contact> + + <links> + <url href="http://wleiden.webweaving.org:8080/svn/node-config/other/enh-sec-patch/README"/> + <url href="http://bsd.slashdot.org/article.pl?amp;sid=03/12/27/2035245&mode=thread&tid=122&tid=126&tid=137&tid=172&tid=185&tid=190&tid=193"/> + </links> + + <body> + <p>This patch if for if_wi current. It enables you to disable the ssid + broadcasting and it also allows you to disable clients connecting + with a blank ssid.</p> + </body> + </project> + + <project> + <title>SMPng Status Report</title> + + <contact> + <person> + <name> + <given>John</given> + <common>Baldwin</common> + </name> + <email>jhb@FreeBSD.org</email> + </person> + + <person> + <email>smp@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/smp/"/> + </links> + + <body> + <p>Several folks continue to work on the locking the network stack + as noted elsewhere in this report. Outside of the network stack, + the following items were worked on during the March and April time + frame. Giant was pushed down in the fork, exit, and wait system + calls as far as possible. Alan Cox (alc@) continues to lock the + VM subsystem and push down Giant where appropriate. A few system + calls and callouts were marked MP safe as well.</p> + + <p>A few changes were made to the interrupt thread infrastructure. + Interrupt thread preemption was finally enabled on the Alpha + architecture with the help of the recently added support to the + scheduler for pinning threads to a specific CPU. An optimization + to reduce context switches during heavy interrupt load was added + as well as rudimentary interrupt storm protection.</p> + </body> + </project> + + <project> + <title>FreeBSD/arm</title> + + <contact> + <person> + <name> + <given>Olivier</given> + <common>Houchard</common> + </name> + <email>cognet@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>FreeBSD/arm is now in the FreeBSD CVS tree. Dynamic libraries now work, + and NO_CXX=true NO_RESCUE=true buildworld works too (with patches for + toolchain that will live outside the tree for now). Now the focus + should be on xscale support.</p> + </body> + </project> + + <project> + <title>CAM lockdown and threading</title> + + <contact> + <person> + <name> + <given>Scott</given> + <common>Long</common> + </name> + <email>scottl@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work has begun on locking down the CAM subsystem. The project is + divided into several steps: + </p> + <ul> + <li>Separation of the SCSI probe peripheral from cam_xpt.c to + scsi_probe.c</li> + <li>Threading of the device probe sequence.</li> + <li>Locking and reference counting the peripheral drivers.</li> + <li>Locking the XPT and device queues.</li> + <li>Locking one or more SIMs and devising a way for non-locked drivers + to function.</li> + </ul> + + <p>While the immediate goal of this work is to lock CAM, it also points + us in the direction of separating out the SCSI-specific knowledgefrom + the core. This will allow other transports to be written, such as + SAS, iSCSI, and ATA.</p> + + <p>Progress is being tracked in the FreeBSD Perforce server in the + camlock branch. I will make public patches available once it has + progressed far enough for reasonable testing. So far, the first two + items are being worked on.</p> + </body> + </project> + + <project> + <title>Network Stack Locking</title> + + <contact> + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/smp/">SMPng Web Page</url> + <url href="http://www.watson.org/~robert/freebsd/netperf/">Robert's + Network Stack Locking Page</url> + </links> + + <body> + <p>This project is aimed at converting the FreeBSD network stack from + running under the single Giant kernel lock to permitting it to run + in a fully parallel manner on multiple CPUs (i.e., a fully threaded + network stack). This will improve performance/latency through + reentrancy and preemption on single-processor machines, and also on + multi-processor machines by permitting real parallelism in the + processing of network traffic. As of FreeBSD 5.2, it was possible to + run low level network functions, as well as the IP filtering and + forwarding plane, without the Giant lock, as well as "process to + completion" in the interrupt handler.</p> + + <p>Work continues to improve the maturity and completeness of the + locking (and performance) of the network stack for 5.3. The network + stack development branch has been updated to the latest CVS HEAD, + as well as the following and more:</p> + + <ul> + <li>Review of socket flag and socket buffer flag locking; + so_state broken out into multiple fields covered by different + locks to avoid lock orders in frobbing the so_state field. + Work in progress.</li> + <li>WITNESS now includes hard ordering for many network locks to + improve lock order debugging process.</li> + <li>MAC Framework modified to use pcbs instead of sockets in a + great many situations to avoid socket locking in network layer, + especially when generating new mbufs.</li> + <li>New annotations relating to socket and interface locking.</li> + <li>Began NetGraph review and corrected NetGraph socket locking + problems.</li> + <li>sendfile() locking appears now to be fixed, albeit holding + Giant more than strictly necessary.</li> + <li>if_ppp global variable locking performed and merged.</li> + <li>A variety of race conditions and bugs in soreceive() locking + fixed, including existing race conditions triggered only rarely + in -HEAD and -STABLE that triggered easily with SMP and Giant-free + operation.</li> + <li>Locking of socket buffer and socket fields from fifofs. + Proposed patch to correct lock order problem between vnode + interlock and socket buffer lock order problems. fifofs + interactions with UNIX domain sockets cleaned up.</li> + <li>Research into KQueue issues. Feedback to KQueue locking + patch authors.</li> + <li>netatalk AARP locked down, MPSAFE, and merged to CVS.</li> + <li>Lock order issues between socket, socket buffer, and UNIX domain + socket locks corrected. Race conditions and potential deadlocks + removed.</li> + <li>if_gif recursion cleanups, if_gif is much more MPSAFE.</li> + <li>First pass MPSAFE locking of NFS server uses an NFS server + subsystem lock to allow so_upcall() from socket layer without + Giant. This closes race conditions in the NFS server when + operating Giant free. Second pass for data based locking is + also in testing.</li> + <li>if_sl.c (SLIP) fine-grained locking completed and merged to + CVS.</li> + <li>if_tun.c (tunnel) fine-grained locking completed and merged to + CVS.</li> + <li>Merge of conditional Giant locking on debug.mpsafenet to CVS; + semantics now changed so that Giant isn't just twiddled over + the forwarding path, but the entire stack. Must be used with + caution unless running with our patches. Callouts also + convered to conditional safety.</li> + <li>if_gif, if_gre global variables locked and merged to CVS.</li> + <li>netatalk DDP cleanup (break out PCB from protocol code), + largely locked down at the PCB level. Some work remains to + be done before patches can be distributed for testing, but close + to MPSAFE.</li> + <li>Began review of netipx, netinet6 code for locking requirements, + some bugs corrected.</li> + <li>Race conditions in handling of socket so_comp, so_incomp + debugged and hopefully closed through new locking of these + fields.</li> + <li>Many new locking annotations, field documentation, lock order + documentation.</li> + </ul> + <p>Netperf patches are proving to be quite stable in a broad variety + of environment, as long as non-MPSAFE chunks are avoided. Kqueue, + IPv6, and ifnet locking remain the most critical areas where + additional functionality is required. Focus is shifting from new + development to in depth testing, performance measurement, and + interactions with other subsystems.</p> + <p>This work would not be possible without contributions from the + following people (and no doubt many others): + John Baldwin, Bob Bishop, Brooks Davis, Pawel Jakub Dawidek, Matthew + Dodd, Julian Elischer, Ruslan Ermilov, John-Mark Gurney, Jeffrey Hsu, + Kris Kennaway, Roman Kurakin, Max Laier, Sam Leffler, Scott Long, Rick + Maklem, Bosko Milekic, George Neville-Neil, Andre Oppermann, Luigi + Rizzo, Jeff Roberson, Tim Robbins, Mike Silberback, Bruce Simpson, + Seigo Tanimura, Hajimu UMEMOTO, Jennifer Yang, Peter Wemm. We hope to + present these patches on arch@ within a few days, although some + elements required continued refinement (especially socket locking).</p> + </body> + </project> + + <project> + <title>TrustedBSD Mandatory Access Control (MAC)</title> + + <contact> + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <common>TrustedBSD Discussion List</common> + </name> + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/">TrustedBSD Project</url> + </links> + + <body> + <p>The TrustedBSD Mandatory Access Control (MAC) Framework + permits the FreeBSD kernel and userspace access control + policies to be adapted at compile-time, boot-time, or + run-time. The MAC Framework provides common infrastructure + components, such as policy-agnostic labeling, making it + possible to easily development and distribute new access + control policy modules. Sample modules include Biba, MLS, + and Type Enforcement, as well as a variety of system + hardening policies.</p> + + <p>The TrustedBSD MAC development branch in Perforce was + integrated to the most recent 5-CURRENT.</p> + + <p>mdmfs(8) -l to create multi-label mdmfs file systems (merged).</p> + + <p>Diskless boot updated to support MAC.</p> + + <p>Re-arrangement of MAC Framework code to break out mac_net.c + into mac_net.c, mac_inet.c, mac_socket.c (merged).</p> + + <p>libugidfw(3) grows bsde_add_rule(3) to automatically allocate + rule numbers (merged). ugidfw(8) grows 'add' to use this + (merged).</p> + + <p>pseudofs(4) no longer requires MAC localizations.</p> + + <p>BPF fine-grained locking now used to protect BPD descriptor + labels instead of Giant (merged).</p> + + <p>Prefer inpcb's as the source of labels over sockets when + creating new mbufs throughout the network stack, reducing + socket locking issues for labels.</p> + </body> + </project> + + <project> + <title>TrustedBSD Security-Enhanced BSD (SEBSD) port</title> + + <contact> + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <common>TrustedBSD Discussion List</common> + </name> + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/">TrustedBSD Project</url> + </links> + + <body> + + <p>TrustedBSD "Security-Enhanced BSD" (SEBSD) is a port of NSA's + SELinux FLASK security architecture, Type Enforcement (TE) + policy engine and language, and sample policy to FreeBSD using + the TrustedBSD MAC Framework. SEBSD is available as a loadable + policy module for the MAC Framework, along with a set of + userspace extensions support security-extended labeling calls. + In most cases, existing MAC Framework functions provide the + necessary abstractions for SEBSD to plug in without SEBSD-specific + changes, but some extensions to the MAC Framework have been + required; these changes are developed in the SEBSD development + branch, then merged to the MAC branch as they mature, and then + to the FreeBSD development tree.</p> + + <p>Unlike other MAC Framework policy modules, the SEBSD module + falls under the GPL, as it is derived from NSA's + implementation. However, the eventual goal is to support + plugging SEBSD into a base FreeBSD install without any + modifications to FreeBSD itself.</p> + + <p>Integrated to latest FreeBSD CVS and MAC branch.</p> + + <p>New FreeBSD code drop updated for capabilities in preference + to superuser checks.</p> + + <p>Installation instructions now available!</p> + + </body> + </project> + + <project> + <title>TrustedBSD Audit</title> + + <contact> + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <common>TrustedBSD Discussion List</common> + </name> + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/">TrustedBSD Project</url> + </links> + + <body> + <p>The TrustedBSD Project is producing an implementation of CAPP + compliant Audit support for use with FreeBSD based on the Apple + Darwin implementation.</p> + + <p>Experimentally integrated the XNU audit implementation from Apple's + Darwin 7.2 into Perforce.</p> + + <p>Adapted audit framework to compile into FreeBSD -- required + modifying memory allocation and synchronization to use FreeBSD + SMPng primitives instead of Mach primitives. + Pushed down the Giant lock out of most of the audit code, various + other FreeBSD adaptations such as suser() API changes, using BSD + threads, td->td_ucred, etc.</p> + + <p>Adapted per-thread audit data to map to FreeBSD threads</p> + + <p>Cleaned up userspace/kernel API interactions, including udev_t/ + dev_t inconsistencies between Darwin and FreeBSD.</p> + + <p>Use vn_fullpath() instead of vn_getpath(), which is a less + complete solution we'll need to address in the future.</p> + + <p>Basic kernel framework now operates on FreeBSD; praudit + tool written that can parse FreeBSD BSM and Solaris BSM.</p> + + </body> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2004-05-2004-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2004-05-2004-06.xml new file mode 100644 index 0000000000..44e1101db2 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2004-05-2004-06.xml @@ -0,0 +1,1107 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2004-05-2004-06.xml,v 1.6 2006/08/19 21:20:40 hrs Exp $ --> +<report> + <date> + <month>May-June</month> + <year>2004</year> + </date> + + <section> + <title>Introduction</title> + + <p>This installment of the Bi-Monthly Status Report is a few days late, + but I'm pleased to say that it is chocked full of over 30 articles. + May and June were yet again busy months; the Netperf project passed + major milestones and can now be run with the debug.mpsafenet tunable + turned on from sources in CVS. The ARM, MIPS, and PPC ports saw quite + a bit of progress, as did several other SMPng and Netgraph projects. + FreeBSD 5.3 is just around the corner, so don't hesitate to grab a + snapshot and test the progress!</p> + + <p>On a more serious note, it's very important to remember that code + freeze for FreeBSD 5.3 will happen on August 15, 2004. This is only + a few weeks away and there is still a lot to do. The TODO list for + the release can be found at + <a href="http://www.freebsd.org/releases/5.3R/todo.html"> + http://www.freebsd.org/releases/5.3R/todo.html</a>. If + you are looking for a way to contribute to the release, this TODO list + has several items that are in urgent and in need of attention. + Testing is also very important. The tree has had some stability + stability problems in the past few weeks, but there are work-arounds + that should allow everyone to continue testing and using FreeBSD. We + absolutely must have FreeBSD 5.3 be a rock-solid release, so every + little bit of contributed effort helps!</p> + <p>Thanks,</p> + <p>Scott Long</p> + </section> + + <project> + <title>Network Stack Locking</title> + + <contact> + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/smp/">FreeBSD SMPng Web Page</url> + <url href="http://www.watson.org/~robert/freebsd/netperf/">Netperf Web Page</url> + </links> + + <body> + <p>This project is aimed at converting the FreeBSD network stack from + running under the single Giant kernel lock to permitting it to + run in a fully parallel manner on multiple CPUs (i.e., a fully + threaded network stack). This will improve performance/latency + through reentrancy and preemption on single-processor machines, and + also on multi-processor machines by permitting real parallelism in + the processing of network traffic. As of FreeBSD 5.2, it was + possible to run low level network functions, as well as the IP + filtering and forwarding plane, without the Giant lock, as well as + "process to completion" in the interrupt handler. This permitted + both inbound and outbound traffic to run in parallel across + multiple interfaces and CPUs.</p> + + <p>Work continues to improve the maturity and completeness of the + locking (and performance) of the network stack for 5.3. The network + stack development branch has been updated to the latest CVS HEAD, + as well as the following and more. Many but not all of these + changes have been merged to the FreeBSD CVS tree as of the writing + of this report. Complete details and more minor changes are + documented in the README file on the netperf web page.</p> + + <ul> + <li>Addition of hard-coded WITNESS lock orders for socket-related + locks, route locks, interface locks, file descriptor locks, + SLIP, and PCB locks for various protocols (UDP, TCP, UNIX + domain sockets). (Merged)</li> + <li>Modified MAC Framework to use inpcbs as the source for mbuf + labels rather than reaching up to the socket layer, avoiding the + additional acquisition of socket locks. Locked access to + so_label and so_peerlabel using the socket lock throughout; + assert socket lock in the MAC Framework where depended on. MAC + Framework now makes a copy of the socket label before + externalizing to prevent a copyout while holding the label lock + (and potentially seeing an inconsistent label). (Merged)</li> + <li>Extensive annotation of locking state throughout the network + stack, especially relating to sockets.</li> + <li>Several locking fixes for ng_base.c, the basic Netgraph + infrastructure. (Merged)</li> + <li>Global accept filter list locking, especially during registration. + (Partially merged)</li> + <li>Revise locking in socket state transition helpers, such as + soisconnecting(), soisconnected(), etc, to simplify lock + handling. (Merged)</li> + <li>Fix bugs in netatalk DDP locking, merge all netatalk locking to + CVS. (Merged)</li> + <li>soref() socket locking assertions and associated fixes. + (Merged)</li> + <li>Fifofs now uses its own mutex instead of the vnode interlock to + synchronize fifo operations, avoiding lock order issues with + socket buffer locking. (Merged)</li> + <li>Cleanup of locking related to file descriptor close and Giant + requirements. Experimentation with reducing locking here.</li> + <li>Review and fix several instances of socket locking in the TCP + code. (Merged)</li> + <li>NFS server locking merged to FreeBSD CVS. (Merged)</li> + <li>Accept locking merged to rwatson_netperf, and to FreeBSD CVS. + A new global mutex, accept_mtx, now protects all socket related + accept queue and state fields (SS_COMP, SS_INCOMP), and flags + relating to accept are moved from the generic so_state field to + so_qstate. accept1() rearranged, as with sonewconn() as a result, + and a file descriptor leak fixed. Close a variety of races in + socket referencing during accept. soabort() and other partially + connected socket related functions updated to take locking into + account. (Merged)</li> + <li>Issue associated with non-atomic setting of SS_NBIO in fifofs + resolved by adding MSG_NBIO. (Merged)</li> + <li>Several flags from so_state moved to sb_state so they can be + locked properly using the socket buffer mutex. (Merged)</li> + <li>Socket locks are now not held over calls into the protocol + preventing many lock order issues between socket and protocol + locks, and avoiding a substantial amount of conditional locking. + (Merged)</li> + <li>mbuma, the UMA-based mbuf allocator, is merged to CVS. This + reduces the kernel to one widely used memory allocator, improves + performance, and allows memory from mbufs to be reclaimed and + reused for other types of storage when pressure lowers. + (Merged)</li> + <li>sb_flags now properly locked. (Merged)</li> + <li>Global MAC label ifnet lock introduced to protect labels on + network interfaces. (Merged)</li> + <li>Rewrites of parts of soreceive() and sosend() to improve + MP safety merged to CVS, including modifications to make sure + socket buffer cache state is consistent when locks are released. + sockbuf_pushsync() added to guarantee consistency of cached + pointers. (Merged)</li> + <li>UNIX domain socket locking revised to use a subsystem lock due + to inconsistencies in lock order and inconsistent coverage ofunpcb + fields. Cleanup of global variable locking in UNIX domain + sockets, Giant handling when entering VFS. All UNIX domain socket + locking merged to CVS. (Merged)</li> + <li>netisr dispatch introduced in the routing code such that routing + socket message delivery is performed asynchronously from routing + events to avoid lock order issues. (Merged)</li> + <li>IGMP and multicast locking merged to CVS. (Merged)</li> + <li>Cleanup of lasting recursive Giant acquisition left over from + forwarding/bridging plane only locking. (Merged)</li> + <li>ALTQ imported into the FreeBSD in a locked state. (Merged)</li> + <li>Conditional locking in sbdrop(), sbdroprecord(), sbrelease(), + sbflush(), spappend(), sbappendstream(), sbappendrecord(), + sbinsertoob(), sbappendaddr(), sbappendcontrol() eliminated. + (Merged)</li> + <li>Some cleanup of IP stack management ioctls and lock order issues. + (Merged)</li> + <li>Cleanup and annotation of sorflush() use of a temporary stack held + socket buffer during flush. (Merged)</li> + <li>Substantial cleanup of socket wakeup mechanisms to drop locks in + advance of wakeup, avoid holding locks over upcalls, and + assertions of proper lock state. (Merged)</li> + <li>With the integration of revised ifnet cloning, cloning data + structures are now better locked. (Merged)</li> + <li>Socket locking for portalfs. (Merged)</li> + <li>Global so_global_mtx introduced to protect generation numbers and + socket counts. (Merged)</li> + <li>KAME IPSEC and FAST_IPSEC now use rawcb_mtx to protect raw socket + list integration. More work required here. (Merged)</li> + <li>Socket locking around SO_SNDLOWAT and SO_RCVLOWAT. (Merged)</li> + <li>soreserve() and sbreserve() reformulation to improve locking and + consistency. Similar cleanup in the use of reservation + functions in tcp_mss(). (Merged)</li> + <li>Locking cost reduction in sbappend*(). (Merged)</li> + <li>Global locking for a number of Netgraph modules, including + ng_iface, ng_ppp, ng_socket, ng_pppoe, ng_frame_relay, ng_tty, + ng_eiface. (Merged)</li> + <li>IPv6 inpcb locking. Resulting cleanup of inpcb locking + assertions, and enabling of inpcb locking assertions by default + even with IPv6 compiled in.</li> + <li>if_xl now MPSAFE. (Merged)</li> + <li>soreceive() non-inline OOB support placed in its own function. + (Merged)</li> + <li>NFS client socket locking. (Merged)</li> + <li>SLIP now uses a asynchronous task queue to prevent Giant-free + entrance of the TTY code.</li> + <li>E-mail sent to current@ providing Giant-free operation guidelines + and details.</li> + </ul> + </body> + </project> + + <project> + <title>FreeBSD/MIPS Status Report</title> + + <contact> + <person> + <name> + <given>Juli</given> + <common>Mallett</common> + </name> + <email>jmallett@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/mips/" /> + <url href="http://www.mdstud.chalmers.se/~md1gavan/mips64emul/">mips64emul</url> + </links> + + <body> + <p>In the past two months, opportunities to perform a good chunk of + work on FreeBSD/MIPS have arisen and significant issues with + context switching, clocks, interrupts, and kernel virtual memory + have been resolved. A number of issues with caches were fixed, + however those are far from complete and at last check, there + were issues when running cached which would prevent booting + sometimes. + Due to toolchain issues in progress, current kernels are no + longer bootable on real hardware.</p> + <p>A 64-bit MIPS emulator has arisen giving the ability to test and + debug in an emulator, and much testing has taken place in it. + It has been added to the FreeBSD ports tree, and the port will be + actively tracking the main codebase as possible. In general, + FreeBSD/MIPS kernels should run fine in it.</p> + <p>Before toolchain and cache issues, the first kernel threads would + run, busses and some devices would attach, and the system would + boot to a mountroot prompt.</p> + </body> + </project> + + <project> + <title>PowerPC Port</title> + + <contact> + <person> + <name> + <given>Peter</given> + <common>Grehan</common> + </name> + + <email>grehan@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The port has been moving along steadily. There have been + reports of buildworld running natively. Works is almost complete + on make release so there will be bootable CD images in the near + future.</p> + </body> + </project> + + <project> + <title>IPFilter Upgraded to 3.4.35</title> + <contact> + <person> + <name> + <given>Darren</given> <common>Reed</common> + </name> + <email>darrenr@FreeBSD.org</email> + </person> + </contact> + <links> + <url href="http://coombs.anu.edu.au/~avalon/ip-filter.html">IPFilter home page</url> + </links> + <body> + <p>IPFilter has been upgraded in both FreeBSD-current and 4-STABLE + (post 4.10) from version 3.4.31 to 3.4.35.</p> + </body> + </project> + + <project> + <title>Low-overhead performance monitoring for FreeBSD</title> + + <contact> + <person> + <name> + <given>Joseph</given> + <common>Koshy</common> + </name> + <email>jkoshy@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~jkoshy/projects/perf-measurement/">A + best-in-class performance monitoring system for FreeBSD built + over the hardware performance monitoring facilities of modern + CPUs.</url> + </links> + + <body> + <p>The current design attempts to support both per-process and + system-wide statistical profiling and per-process "virtual" + performance counters. The userland API libpmc(3) is somewhat + stable now, but the kernel module's design is being redone to + handle MP better. Initial development is targeting the AMD + Athlon CPUs, but the intent is to support all the CPUs that + FreeBSD runs on.</p> + + <p>An early prototype is available under Perforce [under + //depot/user/jkoshy/projects/pmc/].</p> + </body> + </project> + + <project> + <title>FreeBSD profile.sh</title> + + <contact> + <person> + <name> + <given>Tobias</given> + + <common>Roth</common> + </name> + + <email>ports@fsck.ch</email> + </person> + </contact> + + <links> + <url href="https://projects.fsck.ch/profile/" /> + </links> + + <body> + <p>FreeBSD profile.sh is an enhancement to the FreeBSD 5 rcng boot + system, targeted at laptops. One can configure multiple network + environments (eg, home, work, university). After this initial + configuration, the laptop detects automatically in what environment + it is started and configures itself accordingly. Not only network + settings, but almost everything from under /etc can be configured + per environment. It is also possible to suspend the machine in one + environment and wake it up in a different one, and reconfiguration + will happen automatically.</p> + </body> + </project> + + <project> + <title>Sync protocols (Netgraph and SPPP)</title> + + <contact> + <person> + <name> + <given>Roman</given> + <common>Kurakin</common> + </name> + <email>rik@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/~rik">Current code, ideas, problems.</url> + </links> + + <body> + <p>Currently I work on two directions: if_spppfr.c and sppp locking + (on behalf of netperf). At the moment of writing this sppp locking + is not ready yet. But it would be ready in couple of days. Also you + may find as a part of this work some user space fixes for rwatson + netperf code (Only that I was able to catch while world compilation. + If you know some others let me know and I'll try to fix them + too).</p> + + <p>Since sppp code is quite big and state machine is very complicated, + it would be difficult to test all code paths. I will glad to get + any help in testing all this stuff. More tester more probability to + test all possible cases.</p> + + <p>Work on FRF.12 (ng_frf12) is frozen since of low interest and + lack of time. Current state of stable code: support of FRF.12 + End-to-End fragmentation. Support of FRF.12 Interface (UNI and NNI) + fragmentation is not tested.</p> + </body> + </project> + + <project> + <title>Cronyx Adapters Drivers</title> + + <contact> + <person> + <name> + <given>Roman</given> + <common>Kurakin</common> + </name> + <email>rik@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.cronyx.ru/hardware/wan.html">Cronyx WAN Adapters.</url> + </links> + + <body> + <p>cp(4) driver for Cronyx Tau-PCI was added. Cronyx Tau-PCI is family + of synchronous WAN adapters with various set of interfaces such as + V.35, RS-232, RS-530(449), X.21, E1, E3, T3, STS-1. This is a third + family of Cronyx adapters that is supported by FreeBSD now. Now all + three drivers cx(4), ctau(4) and cp(4) are on both major branches + (HEAD and RELENG_4).</p> + <p>Busdma conversion was recently finished. Current work is + concentrated on locking both for adapters drivers and for sppp (see + my other report for additional information).</p> + </body> + </project> + + <project> + <title>Network interface naming changes</title> + + <contact> + <person> + <name> + <given>Brooks</given> + <common>Davis</common> + </name> + <email>brooks@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>An enhanced network interface cloning API has been committed. It + allows interfaces to support more complex names then the current + <code>name#</code> style. This functionality has been used to + enable interesting cloners like auto-configuring vlan interfaces. + Other features include locking of cloner structures and the ability + of drivers to reject destroy requests.</p> + <p>Work on userland support for this functionality is ongoing.</p> + </body> + </project> + + <project> + <title>SMPng Status Report</title> + + <contact> + <person> + <name> + <given>John</given> + <common>Baldwin</common> + </name> + <email>jhb@FreeBSD.org</email> + </person> + <person> + <email>smp@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/smp/" /> + </links> + + <body> + <p>Not a lot happened on the SMPng front outside of the work on + locking the network stack (which is a large amount of work). + The priorities of the various software interrupt threads were + corrected and locking for taskqueues was improved. The return + value of the sema_timedwait() function was adjusted to be more + consistent with cv_timedwait(). A small fix was made to the + sleepqueue code to shorten the amount of time that a + sleepqueue chain lock is held when waking up threads. Some + simple debug code for profiling the hash tables used in the + sleep queue and turnstile code was added. This will allow + developers to measure the impact of any tweaks to the hash + table sizes or the hash algorithm.</p> + </body> + </project> + + <project> + <title>i386 Interrupt Code & PCI Interrupt Routing</title> + + <contact> + <person> + <name> + <given>John</given> + <common>Baldwin</common> + </name> + <email>jhb@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Support for programming the polarity and trigger mode of + interrupt sources at runtime was added. This includes a + mini-driver for the ELCR register used to control the + configuration for ISA and EISA interrupts. The atpic driver + reprograms the ELCR as necessary, while the apic driver + reprograms the interrupt pin associated with an interrupt + source as necessary. The information about which + configuration to use mostly comes from ACPI. However, + non-ACPI systems also force any ISA interrupts used to route + PCI interrupts to use active-low polarity and level + trigger.</p> + + <p>Support for suspend and resume on i386 was also slightly + improved. Suspend and resume support was added to the ELCR, + $PIR, and apic drivers.</p> + + <p>The ACPI PCI-PCI bridge driver was fixed to fall back to the + PCI-PCI bridge swizzle method for routing interrupts when a + routing table was not provided by the BIOS.</p> + + <p>Mixed mode can now be disabled or enabled at boot time via a + loader tunable.</p> + </body> + </project> + + <project> + <title>KDE on FreeBSD</title> + + <contact> + <person> + <name> + <given>Michael</given> + <common>Nottebrock</common> + </name> + <email>lofi@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://freebsd.kde.org" /> + </links> + + <body> + <p>The work on converting the build switches/OPTIONS + currently present in the ports of the main KDE modules into + separate ports in order to make packages available for the + software/features they provide is progressing. Porting of + KOffice 1.3.2 are nearly completed. The Swedish FreeBSD + snapshot server <a href="http://snapshots.se.freebsd.org"> + http://snapshots.se.freebsd.org</a>, + operated and maintained by members of the KDE/FreeBSD team, + is back up and running at full steam. Additional amd64 + hardware has been added and amd64 snapshots will be available + soon.</p> + </body> + </project> + + <project> + <title>Various GEOM classes and geom(8) utility</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + <common>Dawidek</common> + </name> + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>I'm working on various GEOM classes. Some of them are already + committed and ready for use (GATE, CONCAT, STRIPE, LABEL, NOP). The + MIRROR class is finished in 90% and will be committed in very near + future. Next I want to work on RAID3 and RAID5 implementations. + Userland utility to control GEOM classes (geom(8)) is already in + the tree.</p> + </body> + </project> + + <project> + <title>FreeBSD Handbook, 3rd Edition, Volume II: Administrator Guide</title> + + <contact> + <person> + <name> + <given>Murray</given> + <common>Stokely</common> + </name> + <email>murray@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/docproj/handbook3.html">FreeBSD Handbook 3rd Edition Task List.</url> + </links> + + <body> + <p>The Third Edition of the FreeBSD Handbook has been split + into two volumes. The first volume, the User Guide, has been + published. Work is progressing on the second volume. The + following chapters are included in the second volume : + advanced-networking, network-servers, config, boot, cutting-edge, + disks, l10n, mac, mail, ppp-and-slip, security, serialcomms, + users, vinum, eresources, bibliography, mirrors. Please see the + Task List for information about what work remains to be done. In + addition to technical and grammatical review, a number of HTML + output assumptions in the document need to be corrected.</p> + </body> + </project> + + <project> + <title>VuXML and portaudit</title> + + <contact> + <person> + <name> + <given>Tom</given> + <common>Rhodes</common> + </name> + <email>trhodes@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.vuxml.org">VuXML DTD and more information</url> + <url href="http://vuxml.FreeBSD.org">Rendered contents of FreeBSD VuXML</url> + <url href="http://www.freebsd.org/ports/portaudit/">Rendered version of portaudit.txt</url> + </links> + + <body> + <p>The portaudit utility is currently an add-on to FreeBSD + designed to give administrators and users a heads up + with regards to security vulnerabilities in third + party software. The VuXML database keeps a record + of these security vulnerabilities along with internal + security holes. When installed, the portaudit utility + periodically downloads a database with known issues and + checks all installed ports or packages against it; should + it find vulnerable software installed the administrator + or user is notified during the daily run output of the + periodic scripts.</p> + + <p>These utilities are considered to be of production + quality and discussion is taking place over whether or not + they should be included as part of the base system. All + ports committers are urged to add entries when when a + vulnerability is discovered; any questions may be sent to + eik@ or myself.</p> + </body> + </project> + + <project> + <title> + Bluetooth stack for FreeBSD (Netgraph implementation) + </title> + + <contact> + <person> + <name> + <given>Maksim</given> + <common>Yevmenkin</common> + </name> + <email>m_evmenkin@yahoo.com</email> + </person> + </contact> + + <body> + <p>Bluetooth code was marked as non-i386 specific. It is now possible + to build it on all supported platforms. Please help with testing. + Other then this there was not much progress during last few months. + I've been very busy with Real Life.</p> + </body> + </project> + + <project> + <title>FreeBSD Dutch Documentation Project</title> + <contact> + <person> + <name> + <given>Remko</given> + <common>Lodder</common> + </name> + <email>remko@elvandar.org</email> + </person> + </contact> + <links> + <url href="http://www.evilcoder.org/freebsd_html">Preview html documentation</url> + <url href="http://www.evilcoder.org/freebsd/handbook.tbz">Preview documentation tree</url> + <url href="http://www.evilcoder.org/freebsd/html.tbz">Preview html in in tbz</url> + </links> + <body> + <p>The FreeBSD Dutch Documentation project is a ongoing project + translating the FreeBSD handbook {and others} to the dutch + language. We are still on the look for translators and people + that are willing to check the current html documentation. + If you are interested, contact me at the email address shown + above. We currently are reading for some checkups and then + insert the first documents into the documentation tree.</p> + </body> + </project> + + <project> + <title>FreeBSD Brazilian Documentation Project</title> + + <contact> + <person> + <name> + <given>DOC-BR</given> + <common>Discussion List</common> + </name> + <email>doc@fugspbr.org</email> + </person> + </contact> + + <links> + <url href="http://doc.fugspbr.org" /> + <url href="http://lists.fugspbr.org/listinfo.cgi/doc-fugspbr.org" /> + <url href="http://developer.berlios.de/projects/doc-br/" /> + </links> + + <body> + <p>The FreeBSD Brazilian Documentation Project is an effort of + the Brazilian FreeBSD Users Group (FUG-BR) to translate the + available documentation to pt_BR. We are proud to announce + that we've finished the Handbook and FDP Primer translation and + they are being revised. Both should be integrated to the FreeBSD + CVS repository shortly.</p> + <p>There are many other articles being translated and their status + can be checked at our website. If you want to help please + create an account at BerliOS, since our CVS repository is being + hosted there, and contact us through our mailing list. Any help is + welcome!</p> + </body> + </project> + + <project> + <title>Packet Filter - pf</title> + + <contact> + <person> + <name> + <given>Max</given> + <common>Laier</common> + </name> + <email>mlaier@FreeBSD.org</email> + </person> + <person> + <name> + <given>Daniel</given> + <common>Hartmeier</common> + </name> + <email>dhartmei@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.benzedrine.cx/pf.html">The pf homepage.</url> + </links> + + <body> + <p>We imported pf as of OpenBSD 3.5 stable on June, 17th which will be + the base for 5-STABLE pf (according to the current schedule). The + most important improvement in this release is the new interface + handling which makes it possible to write pf rule sets for + hot-pluggable devices and pseudo cloning devices, before they exist. + The import of the ALTQ framework enabled us to finally provide the + related pf functions as well.</p> + + <p>Before 5-STABLE we will import some bug fixes from OpenBSD-current, + which have not been merged to their stable branch, as well as some + FreeBSD specific features. The planned ALTQ API make-over will also + affect pf.</p> + + <p>We are (desperately) looking for non-manpage documentation for + FreeBSD pf and somebody to write it. Few things have changed + so a port of the excellent "PF FAQ" on the OpenBSD homepage should + be fitting. There are, however, a couple of points that need + conversion. A simple tutorial how to setup a NAT gateway with pf + would also help. The in-kernel NAT engine is very easy to use, we + should tell people about this alternative. This is even more true + since the pf module now plugs into GENERIC without modifications.</p> + </body> + </project> + + <project> + <title>ALTQ import</title> + + <contact> + <person> + <name> + <given>Max</given> + <common>Laier</common> + </name> + <email>mlaier@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.csl.sony.co.jp/person/kjc/kjc/software.html#ALTQ"> ALTQ homepage.</url> + <url href="http://www.rofug.ro/projects/freebsd-altq/">ALTQ integration in FreeBSD project.</url> + <url href="http://kerneltrap.org/node.php?id=505">ALTQ merged into pf.</url> + <url href="http://people.freebsd.org/~mlaier/ALTQ_driver/" /> + + </links> + <body> + <p>The ALTQ framework is part of KAME for more than 4 years and has + been adopted by Net- and OpenBSD since more than 3 years. It + provides means of managing outgoing packets to do QoS and bandwidth + limitations. OpenBSD developed a different way to interact with + ALTQ using pf, which was adopted by KAME as the "default for + everyday use".</p> + + <p>The Romanian FreeBSD Users Group has had a project to work towards + integration of ALTQ into FreeBSD, which provided a very good + starting point for the final import. The import only provides the + "pf mode" configuration and classification API as the older ALTQ3 + API does not suit to our SMP approach.</p> + + <p>A reworked configuration API (decoupled from pf) is in the making + as are additional driver modifications. Both should be done before + 5-STABLE is branched, although additional drivers can be imported + during the lifetime of 5-STABLE as well.</p> + </body> + </project> + + <project> + <title>HP Network Scanjet 5</title> + + <contact> + <person> + <name> + <given>Julian</given> + <common>Stacey</common> + </name> + <email>jhs@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://berklix.com/scanjet/">HP Network Scanjet 5 Running FreeBSD Inside</url> + </links> + + <body> + <p>HP Network Scanjet 5 can unobtrusively run FreeBSD <i>inside</i> the + scanner. Those who miss their Unix at work can have a FreeBSD box, + un-noticed & un-challenged by blinkered managers who block any + non Microsoft PC in the building. http://berklix.com/scanjet/</p> + </body> + </project> + + <project> + <title>EuroBSDCon 2004 registration now open</title> + + <contact> + <person> + <name> + <given>Patrick M.</given> + <common>Hausen</common> + </name> + <email>hausen@punkt.de</email> + </person> + </contact> + + <links> + <url href="http://www.eurobsdcon2004.de/">EuroBSDCon 2004 official website</url> + </links> + + <body> + <p>Registration for EuroBSDCon 2004 taking place in Karlsruhe, Germany, + from Oct. 29th to 31st has just opened. An early bird discount will + be offered to all registering until Aug. 15th. Please see the + conference website for details.</p> + </body> + </project> + + <project> + <title>Buf Junta project</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + <common>Kamp</common> + </name> + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The buf-junta project is underway, I am trying to bisect the code + such that we get a struct bufobj which is the handle and method + carrier for a buffer-cache object. All vnodes contain a bufobj, but + as filesystems get migrated to GEOM backing, bufobj's will exist + which do not have an associated vnode. The work is ongoing.</p> + </body> + </project> + + <project> + <title>TTY subsystem realignment</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + <common>Kamp</common> + </name> + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>An effort to get the tty subsystem out from under Giant has + morphed into an more general effort to eliminate a lot of + code which have been improperly copy & pasted into device + drivers. In an ideal world, tty drivers would never get + near a cdevsw, but since some drivers are more than just + tty drivers (for instance sync) a more sensible compromise + must be reached. The work is ongoing.</p> + </body> + </project> + + <project> + <title>kgi4BSD</title> + + <contact> + <person> + <name> + <given>Nicholas</given> + <common>Souchu</common> + </name> + <email>nsouch@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~nsouch/kgi4BSD"> Project URL</url> + </links> + + <body> + <p>KGI is going slowly but surely. The port of the KGI/Linux accel to + FreeBSD is in progress. It's no more than a double buffering API for + graphic command passing to the HW engine.</p> + + <p>Most of the work in the past months was about console management + and more especially dual head console. Otherwise a new driver + building tree is now ready to compile Linux and FreeBSD drivers in + the same tree.</p> + + <p>Documentation about KGI design is in progress.</p> + </body> + </project> + + <project> + <title>FreeBSD ports monitoring system</title> + + <contact> + <person> + <name> + <given>Mark</given> + <common>Linimon</common> + </name> + + <email>linimon_at_lonesome_dot_com</email> + </person> + </contact> + + <links> + <url href="http://portsmon.firepipe.net/index.html">FreeBSD ports monitoring system</url> + </links> + + <body> + <p>The system continues to function well. The accuracy of the + automatic classification algorithm has been improved by + assigning a higher priority to port names found in pieces of + Makefiles.</p> + <p>Several bugs had to be fixed due to the transition from bento to + pointyhat. For about two weeks the URLs to the build errors + were wrong. This has now been corrected (but note that some of the + pointyhat summary pages themselves still show the broken + links.)</p> + <p>A report was added to show only PRs in the 'feedback' state, so + that committers can focus on maintainer and/or responsible timeouts. + (As a reminder, the policy is 2 weeks). Another report on 'ports + that are in ports/MOVED, but still exist' has also been added to the + Anomalies page. Sometimes these are actual errors but not always.</p> + <p>Here are my latest observations about the trends in ports PRs:</p> + <ul> + <li>We were (very briefly) down to 650 ports PRs. From looking + at the graphs, this appears to be the lowest number since 2001. + This is despite the fact that between the two time periods the + number of ports had increased 70%.</li> + <li>We have made a little bit of progress on the number of PRs + which apply to existing ports and have been assigned to a FreeBSD + committer, from 400 to around 350. This is partly due to some + committers going through the database, putting old PRs into the + 'feedback' state, and then later invoking the 'maintainer timeout' + rule mentioned above. (In some cases the PRs are now too old to + still apply, and those are just closed.)</li> + <li>A few maintainers are currently responsible for one-third of + those 350. Please, if you feel that you are over committed, + consider asking for new volunteers to maintain these ports.</li> + <li>In terms of build errors, there is some new breakage from + the preliminary testing with gcc3.4, which is even stricter with + respect to the code it will accept than was gcc3.3. Many of these + errors are shown as 'unknown' by the classification script. I + have submitted a patch to fix this.</li> + <li>The majority of the build errors are still due to compilation + problems, primarily from the gcc upgrades. Since FreeBSD tends to + be at the forefront of gcc adaptation, this is to be expected, but + IMHO we should really try to fix as many of these as possible + before 5.3 is released.</li> + <li>The next highest number of build errors are caused by code + that does not build on our 64-bit architectures due to the + assumption that "all the world's a PC". + <a href="http://portsmon.firepipe.net/ploticus/uniqueerrorcounts.html"> + Here is the entire list</a>; the individual bars are + clickable.</li> + </ul> + </body> + </project> + + <project> + <title>Improved Multibyte/Wide Character Support</title> + <contact> + <person> + <name> + <given>Tim</given> + <common>Robbins</common> + </name> + <email>tjr@FreeBSD.org</email> + </person> + </contact> + <body> + <p>Many more text-processing utilities in the FreeBSD base system have + been updated to work with multibyte characters, including comm, cut, + expand, fold, join, paste, unexpand, and uniq. New versions of GNU + grep and GNU sort (from coreutils) have been imported, together with + multibyte support patches from developers at IBM and Red Hat.</p> + <p>Future work will focus on modifying the regular expression + functions to work with multibyte characters, improving performance + of the C library routines, and updating the remaining utilities (sed + and tr are two important ones still remaining).</p> + </body> + </project> + + <project> + <title>FreeBSD/arm</title> + + <contact> + <person> + <name> + <given>Olivier</given> + <common>Houchard</common> + </name> + <email>cognet@FreeBSD.org</email> + </person> + </contact> + + <body> + Not much to report, Xscale support is in progress, and should + boot at least single user really soon on an Intel IQ31244 + <p>Evaluation board.</p> + </body> + </project> + + <project> + <title>CAM Lockdown</title> + + <contact> + <person> + <name> + <given>Scott</given> + <common>Long</common> + </name> + <email>scottl@freebsd.org</email> + </person> + </contact> + + <body> + <p>Not much coding has taken place on this lately, with the recent + focus being on refining the design. We are currently investigating + per-CPU completion queues and threads in order to reduce locks and + increase concurrency. Also reviewing the BSD/OS CAM lockdown to see + what ideas can be shared. Work should hopefully puck back up in late + July. Development is taking place in the FreeBSD Perforce repository + under the <tt>//depot/projects/scottl-camlock/...</tt> branch for now.</p> + </body> + </project> + + <project> + <title>Project Mini-Evil</title> + + <contact> + <person> + <name> + <given>Scott</given> + <common>Long</common> + </name> + <email>scottl@freebsd.org</email> + </person> + </contact> + + <body> + <p>Project Mini-Evil is an attempt to extend Bill Paul's 'Project Evil' + Windows NDIS wrapper layer to the SCSI MiniPort and StorePort layers. + While drivers exist for most storage controllers that are on the + market today, many companies are integrating software RAID into their + products but not providing any source code or design specs. Instead + of constantly reverse-engineering these raid layers and attempting to + shoehorn them into the ata-raid driver, Project Mini-Evil will run + the Windows drivers directly. It will hopefully also run most any + SCSI/ATA/RAID drivers that conform to the SCSI Miniport or Storeport + specification.</p> + <p>Work on this project is split between making the NDIS wrapper code + more general and implementing the new APIs. Development is taking + place in the FreeBSD Perforce repository under the + //depot/projects/sonofevil/... branch.</p> + </body> + </project> + +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2004-07-2004-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2004-07-2004-12.xml new file mode 100644 index 0000000000..d91fc0fbc7 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2004-07-2004-12.xml @@ -0,0 +1,2341 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<report> + <date> + <month>July-December</month> + + <year>2004</year> + </date> + + <section> + <title>Introduction</title> + + <p>The FreeBSD status report is back again after another small break. The + second half of 2004 was incredibly busy; FreeBSD 5.3 was released, the + 6-CURRENT development branch started, and EuroBSDCon 2004 was a huge + success, just to name a few events. This report is packed with an + impressive 44 submissions, the most of any report ever!</p> + + <p>It's also my pleasure to welcome Max Laier and Tom Rhodes to the status + report team. They kindly volunteered to help keep the reports on time + and help improve their quality. Max in particular is responsible for + the reports being divided up into topics for easier browsing. Many + thanks to both for their help!</p> + </section> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>doc</name> + + <description>Documentation</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <category> + <name>vendor</name> + + <description>Vendor / 3rd Party Software</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='proj'> + <title>Project Frenzy (FreeBSD-based Live-CD)</title> + + <contact> + <person> + <name> + <given>Sergei</given> + + <common>Mozhaisky</common> + </name> + + <email>technix@ukrpost.com.ua</email> + </person> + </contact> + + <links> + <url href="http://frenzy.osdn.org.ua/">Official web site</url> + + <url href="http://frenzy.osdn.org.ua/eng/">English version</url> + </links> + + <body> + <p>Frenzy is a "portable system administrator toolkit," Live-CD + based on FreeBSD. It generally contains software for hardware + tests, file system check, security check and network setup and + analysis. Current version 0.3, based on FreeBSD 5.2.1-RELEASE, + contains almost 400 applications in 200MB ISO-image.</p> + + <p>Tasks for next release: script for installation to HDD; unified + system configuration tool; updating of software collection.</p> + </body> + </project> + + <project cat='vendor'> + <title>ALTQ</title> + + <contact> + <person> + <name> + <given>Max</given> + + <common>Laier</common> + </name> + + <email>mlaier@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~mlaier/ALTQ_driver/" /> + + <url + href="http://www.freebsd.org/cgi/man.cgi?query=altq&manpath=FreeBSD+6.0-current&format=html"> + ALTQ(4) man-page.</url> + </links> + + <body> + <p>ALTQ is part of FreeBSD 5.3 release and can be used to do + traffic shaping and classification with PF. In CURRENT IPFW gained + the ability to do ALTQ classification as well. A steadily + increasing number of NIC drivers has been converted to support + ALTQ. For details see the ALTQ(4) man-page.</p> + </body> + + <help> + <task>Convert/test more NIC drivers.</task> + + <task>Write documentation.</task> + </help> + </project> + + <project cat='kern'> + <title>TCP Reassembly Rewrite and Optimization</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://www.nrg4u.com/freebsd/tcp_reass-20041213.patch" /> + + <url + href="http://lists.freebsd.org/pipermail/freebsd-net/2004-December/005918.html" /> + </links> + + <body> + <p>Currently TCP segment reassembly is implemented as a linked list + of segments. With today's high bandwidth links and large + bandwidth*delay products this doesn't scale and perform well.</p> + + <p>The rewrite optimizes a large number of operational aspects of + the segments reassembly process. For example it is very likely that + the just arrived segment attaches to the end of the reassembly + queue, so we check that first. Second we check if it is the missing + segment or alternatively attaches to the start of the reassembly + queue. Third consecutive segments are merged together (logically) + and are skipped over in one jump for linear searches instead of + each segment at a time.</p> + + <p>Further optimizations prototyped merge consecutive segments on + the mbuf level instead of only logically. This is expected to give + another significant performance gain. The new reassembly queue is + tracking all holes in the queue and it may be beneficial to + integrate this with the scratch pad of SACK in the future.</p> + + <p>Andrew Gallatin was able to get 3.7Gb/sec TCP performance on + dual-2Gbit Myrinet cards with severe packet reordering (due to a + firmware bug) with the new TCP reassembly code. See second + link.</p> + </body> + </project> + + <project cat='kern'> + <title>TTCPv2: Transactional TCP version 2</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://lists.freebsd.org/pipermail/cvs-all/2004-November/089939.html" /> + </links> + + <body> + <p>The old TTCP according to RFC1644 was insecure, intrusive, + complicated and has been removed from FreeBSD >= 5.3. Although + the idea and semantics behind it are still sound and valid.</p> + + <p>The rewrite uses a much easier and more secure system with 24bit + long client and server cookies which are transported in the TCP + options. Client cookies protect against various kinds of blind + injection attacks and can be used as well to generally secure TCP + sessions (for BGP for example). Server cookies are only exchanged + during the SYN-SYN/ACK phase and allow a server to ensure that it + has communicated with this particular client before. The first + connection is always performing a 3WHS and assigning a server + cookie to a client. Subsequent connections can send the cookie back + to the server and short-cut the 3WHS to SYN->OPEN on the + server.</p> + + <p>TTCPv2 is fully configurable per-socket via the setsockopt() + system call. Clients and server not capable of TTCPv2 remain fully + compatible and just continue using the normal 3WHS without any + delay or other complications.</p> + + <p>Work on implementing TTCPv2 is done to 90% and expected to be + available by early February 2005. Writing the implementation + specification (RFC Draft) has just started.</p> + </body> + </project> + + <project cat='kern'> + <title>CPU Cache Prefetching</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://www.nrg4u.com/freebsd/tcp_reass+prefetch-20041216.patch" /> + </links> + + <body> + <p>Modern CPU's can only perform to their maximum if their working + code is in fast L1-3 cache memory instead of the bulk main memory. + All of today's CPU's support certain L1-3 cache prefetching + instructions which cause data to be retrieved from main memory to + the cache ahead of the time that it is already in place when it is + eventually accessed by the CPU.</p> + + <p>CPU Cache Prefetching however is not a golden bullet and has to + be used with extreme care and only in very specific places to be + beneficial. Incorrect usage can lead to massive cache pollution and + a drop in effective performance. Correct and very carefully usage + on the other can lead to drastic performance increases in common + operations.</p> + + <p>In the linked patch CPU cache prefetching has been used to + prefetch the packet header (OSI layer 2 to 4) into the CPU caches + right after entering into the network stack. This avoids a complete + CPU stall on the first access to the packet header because packets + get DMA'd into main memory and thus never are already pre-cache in + the CPU caches. A second use in the patch is in the TCP input code + to prefetch the entire struct tcpcb which is very large and used + with a very high probability. Use in both of these places show a + very significant performance gain but not yet fully quantified.</p> + + <p>The final patch will include documentation and a guide to + evaluate and assess the use of CPU cache prefetch instructions in + the kernel.</p> + </body> + </project> + + <project cat='kern'> + <title>TCP Cleanup and Optimizations</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~andre/tcpcleanup.html" /> + </links> + + <body> + <p>The TCP code in FreeBSD has evolved significantly since the fork + from 4.4BSD-Lite2 in 1994 primarily due to new features and + refinements of the TCP specifications.</p> + + <p>The TCP code now needs a general overhaul, streamlining a + cleanup to make it easily comprehensible, maintainable and + extensible again. In addition there are many little optimizations + that can be done during such an operation propelling FreeBSD back + at the top of the best performing TCP/IP stacks again, a position + it has held for the longest time in the 90's.</p> + + <p>This overhaul is a very involved and delicate matter and needs + extensive formal and actual testing to ensure no regressions + compared to the current code. The effort needed for this work is + about two man-month of fully focused and dedicated time. To get it + done I need funding to take time off my day job and to dedicate me + to FreeBSD work much the way PHK did with his buffer cache and + vnode rework projects.</p> + + <p>In February 2005 I will officially announce the funding request + with a detailed description of the work and how the funding works. + In general I can write invoices for companies wishing to sponsor + this work on expenses. Tax exempt donations can probably be + arranged through the FreeBSD foundation. Solicitations of money are + already welcome, please contact me on the email address above.</p> + </body> + + <help> + <task>Funding for two man-month equivalents of my time.</task> + + <task>If you want or intend to sponsor US$1k or more please contact + me in advance already now.</task> + </help> + </project> + + <project cat='kern'> + <title>Move ARP out of routing table</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Qing</given> + + <common>Li</common> + </name> + + <email>qingli@speackeasy.net</email> + </person> + </contact> + + <links> + <url + href="http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026380.html" /> + </links> + + <body> + <p>The ARP IP address to MAC address mapping does not belong into + the routing table (FIB) as it is currently done. This will move it + to its own hash based structure which will be instantiated per each + 802.1 broadcast domain. With this change it is possible to have + more than one interface in the same IP subnet and layer 2 broadcast + domain. The ARP handling and the routing table will be quite a bit + simplified afterwards. As an additional benefit full MAC address + based accounting will be provided.</p> + + <p>Qing Li has become the driver and implementor of this project + and is expected to post a first patch for comments shortly in + February 2005.</p> + </body> + </project> + + <project cat='kern'> + <title>Layer 2 PFIL_HOOKS</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://lists.freebsd.org/pipermail/cvs-all/2004-August/079811.html" /> + </links> + + <body> + <p>IPFW2 has been converted to use PFIL_HOOKS for the IP[46] + in/output path. (See link.) Not converted yet is the Layer 2 + Etherfilter functionality of IPFW2. It is still directly called + from the ether_input/output and bridging code.</p> + + <p>Layer 2 PFIL_HOOKS provide a general abstraction for packet + filters to hook into the Layer 2 packet path and filter or + manipulate such packets. This makes it possible to use not only + IPFW2 but also PF and others for Layer 2 filtering.</p> + </body> + </project> + + <project cat='proj'> + <title>Common Address Redundancy Protocol - CARP</title> + + <contact> + <person> + <name> + <given>Max</given> + + <common>Laier</common> + </name> + + <email>mlaier@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~mlaier/CARP/" /> + </links> + + <body> + <p>CARP is an alternative to VRRP. In contrast to VRRP it has full + support for IPv6 and uses crypto to protect the advertisements. It + was developed by OpenBSD due to concerns that the HSRP patent might + cover VRRP and CISCO might defend its patent. CARP has, since then, + improved a lot over VRRP.</p> + + <p>CARP is implemented as an in-kernel multicast protocol and + displays itself as a pseudo interface to the user. This makes + configuration and administration very simple. CARP also + incorporates MAC based load-balancing.</p> + + <p>Patches for RELENG_5 and recent HEAD are available from the URL + above. I plan to import these patches in the course of the next two + to four month. RELENG_5 has all necessary ABI to support CARP and I + might MFC it for release 5.4 or 5.5 - depending how well the HEAD + import goes.</p> + </body> + + <help> + <task>Please test and send feedback!</task> + + <task>Write documentation.</task> + + <task>Import newest OpenBSD changes.</task> + </help> + </project> + + <project cat='misc'> + <title>FreeBSD Source Repository Mirror for svn/svk</title> + + <contact> + <person> + <name> + <given>Kao</given> + + <common>Chia-liang</common> + </name> + + <email>clkao@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://svn.clkao.org/svnweb/freebsd/">Repository + browser.</url> + + <url + href="http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/branches/RELENG_5/"> + RSS for RELENG_5 commits.</url> + + <url href="http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/trunk/"> + RSS for CURRENT commits.</url> + + <url href="http://svk.elixus.org/">svk homepage.</url> + </links> + + <body> + <p>A public Subversion mirror of the FreeBSD repository is provided + at svn://svn.clkao.org/freebsd/. This is intended for people who + would like to try the svk distributed version control system.</p> + + <p>svk allows you to mirror the whole repository and commit when + offline. It also provides history-sensitive branching, merging, and + patches. Non-committers can easily maintain their own branch and + track upstream changes while their patches are being reviewed.</p> + </body> + </project> + + <project cat='proj'> + <title>Secure Updating</title> + + <contact> + <person> + <name> + <given>Colin</given> + + <common>Percival</common> + </name> + + <email>cperciva@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.daemonology.net/portsnap/">Portsnap</url> + + <url href="http://www.daemonology.net/freebsd-update/">FreeBSD + Update</url> + </links> + + <body> + <p>In my continuing quest to secure the mechanisms by which FreeBSD + users keep their systems up to date, I've added a new tool: + Portsnap. Available as sysutils/portsnap in the ports tree, this + utility securely downloads and updates a compressed snapshot of the + ports tree; this can then be used to extract or update an + uncompressed ports tree. In addition to operating in an end-to-end + secure manner thanks to RSA signatures, portsnap operates entirely + over HTTP and can use under one tenth of the bandwidth of cvsup for + users who update their ports tree more than once a week.</p> + + <p>FreeBSD Update -- my utility for secure and efficient binary + tracking of the Security/Errata branches -- continues to be widely + used, with over 100 machines downloading security or errata updates + daily.</p> + + <p>At some point in the future I intend to bring both of these + utilities into the FreeBSD base system, probably starting with + portsnap.</p> + </body> + </project> + + <project cat='vendor'> + <title>Cronyx Adapters Drivers</title> + + <contact> + <person> + <name> + <given>Roman</given> + + <common>Kurakin</common> + </name> + + <email>rik@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.cronyx.ru/software">Cronyx Software download + page.</url> + </links> + + <body> + <p>Currently FreeBSD supports three family of Cronyx sync adapters: + Tau-PCI - cp(4), Tau-ISA - ctau(4) and Sigma - cx(4). All these + drivers were updated (in 6.current) and now they are Giant free. + However, this is true only for sppp(4). If you are using Netgraph + or async mode (for Sigma) you may need to turn mpsafenet off for + that driver with appropriate kernel variable.</p> + </body> + + <help> + <task>Now all these drivers and sppp(4) are using recursive lock. + So the first task is to make these locks non recursive.</task> + + <task>Second task is to check/make drivers workable in + netgraph/async mode.</task> + + <task>I think about ability to switch between sppp/netgraph mode at + runtime. For now you should recompile module/kernel to change + mode.</task> + </help> + </project> + + <project cat='misc'> + <title>EuroBSDCon 2005 - Basel / Switzerland</title> + + <contact> + <person> + <name> + <given>Max</given> + + <common>Laier</common> + </name> + + <email>mlaier@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.eurobsdcon.org/">EuroBSDCon Homepage</url> + </links> + + <body> + <p>This year's EuroBSDCon will be held at the University of Basel, + Switzerland from 25th through 27th November. The call for papers + should happen shortly. Please consider attending or even + presenting. Check the conference homepage for more information.</p> + </body> + </project> + + <project cat='proj'> + <title>FreeSBIE Status Report</title> + + <contact> + <person> + <name> + <given>FreeSBIE</given> + + <common>Staff</common> + </name> + + <email>staff@FreeSBIE.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeSBIE.org">FreeSBIE Website</url> + + <url href="http://liste.gufi.org/mailman/listinfo/freesbie"> + FreeSBIE Mailing List</url> + </links> + + <body> + <p>FreeSBIE is a Live-CD based on the FreeBSD Operating system, or + even easier, a FreeBSD-based operating system that works directly + from a CD, without touching your hard drive.</p> + + <p>On December, 6th, 2004, FreeSBIE Staff released FreeSBIE 1.1, + based on FreeBSD 5.3-RELEASE. Some of the innovations are: a + renewed series of scripts to support power users in the use of + FreeSBIE 1.1, an installer to let users install FreeSBIE 1.1 on + their hard drives, thus having a powerful operating system such as + FreeBSD, but with all the personalizations FreeSBIE 1.1 carries, + the presence of the best open source software, chosen and + personalized, such as X.Org 6.7, XFCE 4.2RC1, Firefox 1.0 and + Thunderbird 0.9.2.</p> + + <p>For a complete list of the included software, please consult: + <a + href="http://www.freesbie.org/doc/1.1/FreeSBIE-1.1-i386.pkg_info.txt"> + http://www.freesbie.org/doc/1.1/FreeSBIE-1.1-i386.pkg_info.txt</a> + </p> + + <p>At EuroBSDCon 2004 in Karlsruhe, Germany, people from the + FreeSBIE staff gave a talk, deeping into FreeSBIE scripts + implementation and use.</p> + </body> + + <help> + <task>Translating website and documentation</task> + </help> + </project> + + <project cat='arch'> + <title>PowerPC Port</title> + + <contact> + <person> + <name> + <given>Peter</given> + + <common>Grehan</common> + </name> + + <email>grehan@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/~grehan/miniinst.iso">Miniinst + ISO.</url> + + <url href="http://www.freebsd.org/~grehan/miniinst.txt">Miniinst + relnotes.</url> + </links> + + <body> + <p>A natively built 6.0-CURRENT miniinst ISO is available at the + above link. It runs best on G4 Powermacs, but may run on other + Newworld machines. See the release notes for full details.</p> + + <p>As usual, lots of help is needed. This is a great project for + those who want to delve deeply into FreeBSD kernel internals.</p> + </body> + </project> + + <project cat='proj'> + <title>Dingo Monthly Report</title> + + <contact> + <person> + <name> + <given>George</given> + + <common>Neville-Neil</common> + </name> + + <email>gnn@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/projects/dingo/index.html"> + Network Stack Cleanup Project.</url> + </links> + + <body> + <p>In the last month we set up the project page noted above and + also created a p4 branch for those of us who use p4 to do work + outside of CVS.</p> + </body> + </project> + + <project cat="ports"> + <title>FreeBSD GNOME Project Status Report</title> + + <contact> + <person> + <name> + <given>Joe</given> + + <common>Marcus</common> + </name> + + <email>marcus@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/gnome/">FreeBSD GNOME + Project</url> + </links> + + <body> + <p>We haven't produced a status report in a while, but that's just + because we've been busy. Since our last report in March 2004, we + have added three new team members: Koop Mast (kwm), Jeremy + Messenger (mezz), and Michael Johnson (ahze). Jeremy has been quite + helpful in GNOME development porting while Michael and Koop have + been focusing on improving GNOME multimedia, especially GStreamer. + The stable release of GNOME is now up to 2.8.2, and we are actively + working on the GNOME 2.9 development branch with is slated to + become 2.10 on March 9 of this year.</p> + + <p>The + <a href="http://www.FreeBSD.org/gnome/docs/faq2.html#q21">GNOME + Tinderbox</a> + + is still cranking away, and producing packages for both the stable + and development releases of GNOME for all supported i386 versions + of FreeBSD.</p> + + <p>Thanks to Michael Johnson, the FreeBSD GNOME team has recently + been given + <a + href="http://people.FreeBSD.org/~ahze/firefox_thunderbird-approved.txt"> + permission to use the Firefox and Thunderbird names</a> + + , official icons, and to produce officially branded builds. Mozilla + has also been very interested in merging our local patches back + into the official source tree. This should greatly improve the + quality of Firefox and Thunderbird on FreeBSD moving forward.</p> + + <p>Finally, Adam Weinberger (adamw) has been pestering the team + for photos so that we can finally show the community who we are. It + is still unclear as to whether or not this will attract more + FreeBSD GNOME users, or land us on the Homeland Security no-fly + list.</p> + </body> + + <help> + <task>Need help porting + <a href="http://www.freedesktop.org/wiki/Software_2fhal">HAL</a> + + to FreeBSD (contact + <a href="mailto:marcus@FreeBSD.org">marcus@FreeBSD.org</a> + + )</task> + + <task>Need help porting + <a href="http://www.freedesktop.org/wiki/Software_2fburn"> + libburn</a> + + to FreeBSD (contact + <a href="mailto:bland@FreeBSD.org">bland@FreeBSD.org</a> + + )</task> + + <task>Anyone interested in reviving + <a href="http://www.gnomemeeting.org/">Gnome Meeting</a> + + should contact + <a href="mailto:kwm@FreeBSD.org">kwm@FreeBSD.org</a> + </task> + </help> + </project> + + <project cat='kern'> + <title>SMPng Status Report</title> + + <contact> + <person> + <name> + <given>John</given> + + <common>Baldwin</common> + </name> + + <email>jhb@FreeBSD.org</email> + </person> + + <person> + <email>smp@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/smp/" /> + </links> + + <body> + <p>Lots of changes happened inside the network stack that will + hopefully be covered by a separate report. Outside of the network + stack, several changes were made however including changes to proc + locking, making the kernel thread scheduler preemptive, fixing + several priority inversion bugs in the scheduler, and a few + performance tweaks in the mutex implementation.</p> + + <p>Locking work on struct proc and its various substructures + continued with locking added where needed for struct uprof, struct + rusage, and struct pstats. This also included reworking how the + kernel stores process time statistics to store the raw struct + bintime and tick counts internally and only compute the more user + friendly values when requested via getrusage() or wait4().</p> + + <p>Support for kernel thread preemption was added to the scheduler. + Basically, when a thread makes another thread runnable, it may + yield the current CPU to the new thread if the new thread has a + more important priority. Previously, only interrupt threads + preempted other threads and the implementation would occasionally + trigger spurious context switches. This change exposed bugs in + other parts of the kernel and was turned off by default in + RELENG_5. Currently, only the i386, amd64, and alpha platforms + support native preemption.</p> + + <p>Several priority inversion bugs present in the scheduler due to + various changes to the kernel from SMPng were also fixed. Most of + the credit for these fixes belongs Stephan Uphoff who has recently + been added as a new committer. Fixes include: closing a race in the + turnstile wakeup code, changing the sleep queue code to store + threads in FIFO order so that the sleep queue wakeup code properly + handles having a thread's priority changes, and abstracting the + concept of priority lending so that the thread scheduler is now + able to properly track priority inheritance and handle priority + changes for threads blocked on a turnstile.</p> + + <p>Works in progress include separating critical sections from spin + mutexes some so that bare critical sections become very cheap as + well as continuing to change the various ABI compatibility layers + to use in-kernel versions of system calls to reduce stackgap usage + and make the system call wrappers MPSAFE.</p> + </body> + </project> + + <project cat='kern'> + <title>i386 Interrupt Code & PCI Interrupt Routing</title> + + <contact> + <person> + <name> + <given>John</given> + + <common>Baldwin</common> + </name> + + <email>jhb@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The ACPI PCI link support code was reworked to work around some + limitations in the previous implementation. The new version more + closely matches the current non-ACPI $PIR link support. + Enhancements include disabling unused link devices during boot and + using a simpler and more reliable algorithm for choosing ISA IRQs + for unrouted link devices.</p> + + <p>Support for using the local APIC timer to drive the kernel + clocks instead of the ISA timer and i8254 clock is currently being + worked on in the jhb_clock perforce branch. It is mostly complete + and will probably hit the tree in the near future. By letting each + CPU use its own private timer to drive the kernel clocks, the + kernel no longer has to IPI all the other CPUs in the system every + time a clock interrupt occurs.</p> + </body> + </project> + + <project cat='kern'> + <title>Low-overhead performance monitoring for FreeBSD</title> + + <contact> + <person> + <name> + <given>Joseph</given> + + <common>Koshy</common> + </name> + + <email>jkoshy@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~jkoshy/projects/perf-measurement/"> + A best-in-class performance monitoring system for FreeBSD built + over the hardware performance monitoring facilities of modern + CPUs.</url> + </links> + + <body> + <p>System-wide and process-virtual counting-mode performance + monitoring counters are now supported for the AMD Athlon and Intel + P4 CPUs. SMP works, but is prone to freezes. Immediate next steps + include: (1) implementing the system-wide and process-virtual + sampling modes, (2) debugging, (3) writing a test suite and (4) + improving the project's documentation.</p> + </body> + </project> + + <project cat='misc'> + <title>Wiki with new software</title> + + <contact> + <person> + <name> + <given>Josef</given> + + <common>El-Rayes</common> + </name> + + <email>josef@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/">Wiki</url> + </links> + + <body> + <p>After experiencing spam attacks on the old wiki-engine caused by + non-existent authentification mechanism, I had to replace it with a + more advanced software. Instead of usemod, we now run moinmoin. As + a consequence it's no longer just a 'browse & edit', but you + have to sign up and let someone who is already in the ACL group + 'developers' add you to the group. So it is a 'developers-only' + resource now. The old wiki is found at + <a href="http://wiki2.daemon.li">http://wiki2.daemon.li</a> + </p> + </body> + + <help> + <task>Move content from old wiki to new one.</task> + </help> + </project> + + <project cat='kern'> + <title>kgi4BSD</title> + + <contact> + <person> + <name> + <given>Nicholas</given> + + <common>Souchu</common> + </name> + + <email>nsouch@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/~nsouch/kgi4BSD">Homepage</url> + + <url href="http://wiki.daemon.li/moin.cgi/KGI" /> + </links> + + <body> + <p>The project was very quiet (but still alive!) and mostly + dedicated to testing by volunteers. New documentation at + <a href="http://wiki.daemon.li/moin.cgi/KGI"> + http://wiki.daemon.li/moin.cgi/KGI</a> + + .</p> + </body> + + <help> + <task>Help improving the documentation</task> + </help> + </project> + + <project cat='ports'> + <title>OpenOffice.org port status</title> + + <contact> + <person> + <name> + <given>Maho</given> + + <common>Nakata</common> + </name> + + <email>maho@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://porting.openoffice.org/freebsd/">FreeBSD + OpenOffice.org porting status page</url> + + <url + href="http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/FreeBSD/"> + Stable OOo Packages for FreeBSD</url> + + <url href="http://sourceforge.jp/projects/waooo/files/">Some + volatile WIP status of packages</url> + </links> + + <body> + <p>OpenOffice.org 2.0 status + <ul> + <li>OpenOffice.org 2.0 is planned to be released in March 2005. + Currently developer snapshot versions are available. Now one of + the developer version has been ported, and committed to ports + tree (/usr/ports/editors/openoffice-2.0-devel).</li> + + <li>Packages for 5.3-RELEASE are available at + <a + href="http://sourceforge.jp/projects/waooo/files/asOOo_1.9m71_FreeBSD53Intel_install_en-US.tbz"> + http://sourceforge.jp/projects/waooo/files/asOOo_1.9m71_FreeBSD53Intel_install_en-US.tbz</a> + + etc., and soon it will also available at : + <a + href="http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/FreeBSD/"> + http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/FreeBSD/</a> + + with the language pack.</li> + + <li>Almost all of the patches required to build will be + integrated to master. + <a href="http://www.openoffice.org/issues/show_bug.cgi?id=40187"> + http://www.openoffice.org/issues/show_bug.cgi?id=40187</a> + </li> + + <li>Now we have three external ports : lang/gcc-ooo, + devel/bison-devel and devel/epm. To avoid regressions and bugs of + gcc, we use the exactly same gcc as Hamburg team (former + StarDivision) uses. We need bison later than 1.785a. Note this + port CONFLICTS with devel/bison. Epm is a package manager which + now OpenOffice.org uses.</li> + </ul> + + OpenOffice.org 1.1 status + <ul> + <li>1.1.4 has been ported and committed to ports tree.</li> + + <li>Packages are available at + <a + href="http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/FreeBSD/"> + http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/FreeBSD/</a> + + .</li> + + <li>Now recognizes Linux version of Java JDKs.</li> + </ul> + + General + <ul> + <li>Invoking OpenOffice.org from command line has been changed. + Now `.org' is mandatory. e.g. openoffice-1.1.4 -> + openoffice.org-1.1.4. Since the name of the software is + OpenOffice.org, not OpenOffice. We are also considering the name + of the ports (/usr/ports/editors/openoffice-2.0-devel -> + openoffice.org2-devel etc)</li> + + <li>Now marked as BROKEN OOo ports for prior than 5.3-RELEASE and + 4.11-RELEASE. These ports have been suffering from a minor + implementation difference of rtld.c between FreeBSD and Linux, + Solaris, NetBSD. We have been applying a patch adding _end in + mapfile. We need this since rtld depend on existence of _end + symbol in obj_from_addr_end, unfortunately this seem to induce + hard-to-solve errors. A great progress has been made kan, rtld + now do not depend on _end. A fix was committed 2004/02/25 + 17:06:16, + <a + href="http://www.freebsd.org/cgi/cvsweb.cgi/src/libexec/rtld-elf/rtld.c.diff?r1=1.91&r2=1.92&f=h"> + http://www.freebsd.org/cgi/cvsweb.cgi/src/libexec/rtld-elf/rtld.c.diff?r1=1.91&r2=1.92&f=h</a> + + .</li> + + <li>Benchmark test! Building OOo requires huge resources. We just + would like to know the build timings, so that how your machine is + well tuned for demanding jobs. + <a href="http://porting.openoffice.org/freebsd/benchmark.html"> + http://porting.openoffice.org/freebsd/benchmark.html</a> + + . Currently, GOTO daichi (daichi)'s Pentium 4 3.0GHz machine + build fastest. Just 1h25m22.42s for second build of OOo 1.1.4, + using ccache.</li> + + <li>SDK tutorial is available at + <a href="http://porting.openoffice.org/freebsd/sdk.html"> + http://porting.openoffice.org/freebsd/sdk.html</a> + </li> + + <li>Still implementation test and quality assurance have not yet + been done. Even systematic documentations are not yet available + for FreeBSD. + <a href="http://porting.openoffice.org/freebsd/testing.html"> + http://porting.openoffice.org/freebsd/testing.html</a> + + and + <a href="http://porting.openoffice.org/freebsd/QA.html"> + http://porting.openoffice.org/freebsd/QA.html</a> + + for details.</li> + </ul> + + Acknowledgments Two persons contributed in many aspects. Pavel + Janik (reviewing and giving me much advice) and Kris Kennaway + (extremely patient builder). and (then, alphabetical order by first + name). daichi, Eric Bachard, kan, lofi, Martin Hollmichel, nork, + obrien, Sander Vesik, sem, Stefan Taxhet, and volunteers of + OpenOffice.org developers (esp. SUN Microsystems, Inc.) for + cooperation and warm encouragements.</p> + </body> + </project> + + <project cat='vendor'> + <title>OpenBSD packet filter - pf</title> + + <contact> + <person> + <name> + <given>Max</given> + + <common>Laier</common> + </name> + + <email>mlaier@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Daniel</given> + + <common>Hartmeier</common> + </name> + + <email>dhartmei@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://pf4freebsd.love2party.net/">PF4FreeBSD + Homepage</url> + </links> + + <body> + <p>FreeBSD 5.3 is the first release to include PF. It went out + okay, but some bugs were discovered too late to make it on the CD. + It is recommend to update `src/sys/contrib/pf' to RELENG_5. The + specific issues addressed are:</p> + + <ul> + <li>Possible NULL-deref with user/group rules.</li> + + <li>Crash with binat on dynamic interfaces.</li> + + <li>Silent dropping of IPv6 packets with option headers.</li> + + <li>Endless loops with `static-port' rules.</li> + </ul> + + <p>Most of these issues were discovered by FreeBSD users and got + fed back to OpenBSD. This is a prime example of open source at + work.</p> + + <p>The Handbook's Firewall section was modified to mention PF as an + alternative to IPFW and IPF.</p> + </body> + + <help> + <task>Write more documentation/articles.</task> + + <task>Write an IPFilter to PF migration guide/tool.</task> + </help> + </project> + + <project cat='kern'> + <title>New Modular Input Device Layer</title> + + <contact> + <person> + <name> + <given>Philip</given> + + <common>Paeps</common> + </name> + + <email>philip@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://lists.freebsd.org/pipermail/cvs-src/2004-November/035462.html" /> + </links> + + <body> + <p>Following a number of mailing lists discussions on the topic, + work has been progressing on the development of a new modular input + device layer for FreeBSD. The purpose of this is twofold:</p> + + <ul> + <li>Easier development of new input device drivers.</li> + + <li>Support for concurrent use of multiple input devices, + particularly the hot-pluggable kind.</li> + </ul> + + <p>Currently, implementing support for new input devices is a + painful process and there is great potential for code-duplication. + The new input device layer will provide a simple API for developers + to send events from their hardware on to the higher regions of the + kernel in a consistent way, much like the 'input-core' driver in + the Linux kernel.</p> + + <p>Using multiple input devices at the moment is painful at best. + With the new input device layer, events from different devices will + be properly serialized before they are sent to other parts of the + kernel. This will allow one to easily use, for instance, multiple + USB keyboards in a virtual terminal.</p> + + <p>The work on this is still in very rudimentary state. It is + expected that the first visible changes will be committed to + -CURRENT around late February or early March.</p> + </body> + </project> + + <project cat='proj'> + <title>Funded FreeBSD kernel development</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://lists.freebsd.org/pipermail/freebsd-announce/2004-December/000971.html"> + Long winded status report.</url> + </links> + + <body> + <p>A longish status report for the 6 months of funded development + was posted on announce, rather than repeat it here, you can find it + at the link provided.</p> + </body> + </project> + + <project cat='doc'> + <title>The FreeBSD Dutch Documentation Team</title> + + <contact> + <person> + <name> + <given>Remko</given> + + <common>Lodder</common> + </name> + + <email>Remko@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.evilcoder.org/content/section/6/39/">The + project's webpage.</url> + + <url href="http://www.FreeBSD.org/doc/nl/books/handbook/">The + officially released documentation.</url> + + <url href="http://www.evilcoder.org/freebsd_html/">Preview of the + documentation.</url> + </links> + + <body> + <p>The FreeBSD Dutch Documentation Project is a ongoing project to + translate the documentation into the Dutch language. Currently we + are mainly focused on the Handbook, which is progressing pretty + well. However, lots need to be translated and checked before we + have a 'complete' translation ready. So if you are willing to help + out, please checkout our website and/or contact me.</p> + </body> + + <help> + <task>Translating the Handbook</task> + + <task>Checking the grammar of the Dutch Handbook</task> + + <task>Translate the rest of the documentation</task> + </help> + </project> + + <project cat='ports'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon_at_FreeBSD_dot_org</email> + </person> + + <person> + <name> + <given>Erwin</given> + + <common>Lansing</common> + </name> + + <email>erwin@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ports/">The FreeBSD ports + collection</url> + + <url href="http://portsmon.firepipe.net/index.html">FreeBSD ports + monitoring system</url> + </links> + + <body> + <p>Since the last report on the Ports Collection, much has changed. + Organizationally, the portmgr team saw the departure of some of the + long-term members, and the addition of some newer members, Oliver + Eikemeier, Kirill Ponomarew and Mark Linimon. Later on, portmgr + also had to say goodbye to Will Andrews. In addition, we have + gained quite a few new ports committers during this time period, + and their contributions are quite welcome!</p> + + <p>Most effort was devoted to two releases. The 5.3 release saw an + especially long freeze period, but due to the good shape of the + ports tree, the freeze for the 4.11 could be kept to a minimum. + Several iterations of new infrastructure changes were tested on the + cluster and committed. Also, the cluster now builds packages for + 6-CURRENT, increasing the total number of different build + environment to 10.</p> + + <p>Additionally, several sweeps through the ports tree were made to + bring more uniformity in variables used in the different ports and + their values, e.g. + <tt>BROKEN</tt> + + , + <tt>IGNORE</tt> + + , + <tt>DEPRECATED</tt> + + , + <tt>USE_GCC</tt> + + , and others.</p> + + <p>In technical terms, the largest change was moving to the X.org + codebase as our default X11 implementation. At the same time, code + was committed to be able to select either the X.org code or the + XFree86 code, which also saw an update during that time. Due to + some hard work by Eric Anholt, new committer Dejan Lesjak, and Joe + Marcus Clarke, all of this happened more smoothly than could have + reasonably been expected.</p> + + <p>As well, GNOME and KDE saw updates during this time, as did Perl + and the Java framework. Further, there were some updates to the + Porter's Handbook, but more sections are still in need of updates + to include recent changes in practices. Also, during this time, + Bill Fenner was able to fix a bug in his + <a href="http://people.FreeBSD.org/~fenner/portsurvey">distfile + survey</a> + + .</p> + + <p>Shortly before the release for 4.11 our existing linux_base was + marked forbidden due to security issues. A lot of effort was spent + to upgrade the default version to 8 from 7 to ship 4.11 with a + working linuxolator.</p> + + <p>Due to stability problems in the April-May timeframe, the + package builds for the Alpha were dropped. After Ken Smith and + others put some work into the Alphas in the build cluster, package + builds for 4.X were reenabled late in 2004.</p> + + <p>Ports QA reminders -- portmgr team members are now sending out + periodic email about problems in the Ports Collection. The current + set includes: + <ul> + <li>a public list of all ports to be removed due to security + problems, build failures, or general obsolescence, unless they + are fixed first</li> + + <li>private email to all maintainers of the affected ports + (including ports dependent on the above)</li> + + <li>private email to all maintainers of ports that are marked + <tt>BROKEN</tt> + + and/or + <tt>FORBIDDEN</tt> + </li> + + <li>private email to maintainers who aren't committers, who have + PRs filed against their ports (to flag PRs that might never have + been Cc:ed to them)</li> + + <li>public email about port commits that break building of + <tt>INDEX</tt> + </li> + + <li>public email about port commits that send the revision + metadata backwards (and thus confuse tools like portupgrade)</li> + </ul> + + The idea behind each of these reminders is to try to increase the + visibility of problems in the Ports Collection so that problems can + be fixed faster.</p> + + <p>Finally, it should be noted that we passed yet another milestone + and the Ports Collection now contains over 12,000 ports.</p> + </body> + + <help> + <task>The majority of our build errors are still due to compilation + problems, primarily from the gcc upgrades. Thanks to the efforts of + many volunteers, these are decreasing, but there is still much more + work to be done.</task> + + <task>The next highest number of build errors are caused by code + that does not build on our 64-bit architectures due to the + assumption that "all the world's a PC." + <a + href="http://portsmon.firepipe.net/ploticus/uniqueerrorcounts.html"> + Here is the entire list</a> + + ; the individual bars are clickable. This will become more and more + important now that the amd64 port has been promoted to tier-1 + status.</task> + + <task>A lot of progress has been meed to crack down on ports that + install files outside the approved directories and/or do not + de-install cleanly (see "Extra files not listed in PLIST" on + <a href="http://pointyhat.FreeBSD.org/errorlogs/">pointyhat</a> + + ) and this will remain a focus area.</task> + </help> + </project> + + <project cat="doc"> + <title>Hardware Notes</title> + + <contact> + <person> + <name> + <given>Simon L.</given> + + <common>Nielsen</common> + </name> + + <email>simon@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Christian</given> + + <common>Brueffer</common> + </name> + + <email>brueffer@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://www.FreeBSD.org/releases/5.3R/hardware-i386.html"> + FreeBSD/i386 5.3-RELEASE Hardware Notes</url> + + <url + href="http://www.freebsd.org/relnotes/CURRENT/hardware/i386/article.html"> + FreeBSD/i386 6.0-CURRENT Hardware Notes</url> + </links> + + <body> + <p>The FreeBSD Hardware Notes have been (mostly) converted to being + directly generated from the driver manual pages. This makes it much + simpler to maintain the Hardware Notes, so they should be more + accurate. The Hardware Notes for FreeBSD 5.3 use this new + system.</p> + </body> + </project> + + <project cat='ports'> + <title>Update of the Linux userland infrastructure</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The default linux_base port port was changed from the RedHat 7 + based emulators/linux_base to the RedHat 8 based + emulators/linux_base-8 just in time for FreeBSD 4.11-Release + because of a security problem in emulators/linux_base. In the + conversion process several problems where fixed in some Linux + ports.</p> + + <p>Both RedHat 7 and 8 are at their end of life, so expect an + update to a more recent Linux distribution in the future. For QA + reasons this update wasn't scheduled before FreeBSD + 4.11-Release.</p> + </body> + </project> + + <project cat='misc'> + <title>FreeBSD Security Officer and Security Team</title> + + <contact> + <person> + <name> + <given>Jacques</given> + + <common>Vidrine</common> + </name> + + <email>nectar@FreeBSD.org</email> + </person> + + <person> + <name> + <common>Security Officer</common> + </name> + + <email>security-officer@FreeBSD.org</email> + </person> + + <person> + <name> + <common>Security Team</common> + </name> + + <email>security-team@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/security/">FreeBSD Security + Information</url> + + <url href="http://www.freebsd.org/security/charter.html">FreeBSD + Security Officer Charter</url> + + <url + href="http://www.freebsd.org/administration.html#t-secteam"> + FreeBSD Security Team members</url> + + <url href="http://vuxml.freebsd.org/">FreeBSD VuXML web site</url> + + <url href="http://cvsweb.freebsd.org/ports/security/portaudit/"> + portaudit</url> + </links> + + <body> + <p>During 2004, there were several notable changes and events + related to the FreeBSD Security Officer role and Security Team.</p> + + <p>The charter for the Security Officer (SO) as approved by Core in + 2002 was finally published on the web site. This document describes + the mission, responsibilities, and authorities of the SO. (The + current SO is Jacques Vidrine.)</p> + + <p>The SO is supported by a Deputy SO and the Security Team. In + April, Chris Faulhaber resigned as Deputy SO and Dag-Erling + Smorgrav was appointed in his place. Also during the year, the + following team members resigned: Julian Elischer, Bill Fumerola, + Daniel Harris, Trevor Johnson, Kris Kennaway, Mark Murray, Wes + Peters, Bruce Simpson, and Bill Swingle; while the following became + new members: Josef El-Rayes, Simon L. Nielsen, Colin Percival, and + Tom Rhodes. A huge thanks is due to all past and current members! + The current Security Team membership is published on the web + site.</p> + + <p>With the release of FreeBSD 4.8, the SO began extended support + for some FreeBSD releases and their corresponding security + branches. "Early adopter" branches, such as FreeBSD 5.0 + (RELENG_5_0), are supported for at least six months. "Normal" + branches are supported for at least one year. "Extended" branches, + such as FreeBSD 5.3 (RELENG_5_3), are supported for at least two + years. The currently supported branches and their estimated "end of + life" (EoL) dates are published on the FreeBSD Security Information + web page. In 2004, four releases "expired": 4.7, 4.9, 5.1, and + 5.2.</p> + + <p>With the releases of FreeBSD 4.10 and 5.3, the SO and the + Release Engineering team extended the scope of security branches to + incorporate critical bug fixes unrelated to security issues. + Currently, separate Errata Notices are published for such fixes. In + the future, Security Advisories and Errata Notices will be merged + and handled uniformly.</p> + + <p>17 Security Advisories were published in 2004, covering 8 issues + specific to FreeBSD and 9 general issues.</p> + + <p>2004 also saw the introduction of the Vulnerabilities and + Exposures Markup Language (VuXML). VuXML is a markup language + designed for the documentation of security issues within a single + package collection. Over 325 security issues in the Ports + Collection have been documented already in the FreeBSD Project's + VuXML document by the Security Team and other committers. This + document is currently maintained in the ports repository, path + ports/security/vuxml/vuln.xml. The contents of the document are + made available in a human-readable form at the FreeBSD VuXML web + site. The "portaudit" tool can be used to audit your local system + against the listed issues. Starting in November, the popular + FreshPorts.org web site also tracks issues documented in VuXML.</p> + </body> + </project> + + <project cat='kern'> + <title>Sync Protocols (SPPP and NETGRAPH)</title> + + <contact> + <person> + <name> + <given>Roman</given> + + <common>Kurakin</common> + </name> + + <email>rik@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/~rik">My FreeBSD home page. You + could find here some results of my work. Unfortunately I do not + update this page often.</url> + </links> + + <body> + <p>sppp(4) was updated (in 6.current) to be able to work in mpsafe + mode. For compatibility if an interface is unable to work in mpsafe + mode, sppp will not use mpsafe locks.</p> + + <p>Support of FrameRelay AnnexD was added as a historical commit. + Many of Cronyx users were expecting this commit for a long long + time, and most of them still prefer sppp vs netgraph because of + simplicity of its configuration (especially for ppp (vs mpd) and fr + (vs a couple of netgraph modules). After MFCing this I'll finally + close a PR 21771, from 2000/10/05</p> + </body> + </project> + + <project cat="proj"> + <title>Improved Multibyte/Wide Character Support</title> + + <contact> + <person> + <name> + <given>Tim</given> + + <common>Robbins</common> + </name> + + <email>tjr@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Support for multibyte characters has been added to many more + base system utilities, including basename, col, colcrt, colrm, + column, fmt, look, nl, od, rev, sed, tr, and ul. As a result of + changes to the C library (see below), most utilities that perform + regular expression matching or pathname globbing now support + multibyte characters in these aspects.</p> + + <p>The regular expression matching and pathname globbing routines + in the C library have been improved and now recognize multibyte + characters. Various performance improvements have been made to the + wide character I/O functions. The obsolete 4.4BSD "rune" interface + and UTF2 encoding have been removed from the 6-CURRENT branch.</p> + + <p>Work is progressing on implementations of the POSIX iconv and + localedef interfaces for potential inclusion into the FreeBSD 6.0 + release.</p> + </body> + </project> + + <project cat='arch'> + <title>FreeBSD/arm status report</title> + + <contact> + <person> + <name> + <given>Olivier</given> + + <common>Houchard</common> + </name> + + <email>cognet@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/platforms/arm">FreeBSD/arm + project page.</url> + </links> + + <body> + <p>FreeBSD/arm made some huge progress. It can boot multiuser, and + run things like "make world" and perl on the IQ31244 board. It also + now has support for various things, including DDB, KTR, ptrace and + kernel modules. A patch is available for early gdb support, and the + libpthread almost works.</p> + </body> + </project> + + <project cat='kern'> + <title>ATA Driver Status Report</title> + + <contact> + <person> + <name> + <given>Søren</given> + + <common>Schmidt</common> + </name> + + <email>sos@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The ATA driver is undergoing quite a few important changes, + mainly it is being converted into modules so it can be + loaded/unloaded at will, and just the pieces for wanted + functionality need be present.</p> + + <p>This calls for ata-raid to finally be rewritten. This is almost + done for reading metadata so arrays defined in the BIOS can be + used, and its grown quite a few new metadata formats. This also + paves the way for ataraid to finally be able to take advantage of + some of the newer controllers "RAID" abilities. However this needs + more work to materialize but now its finally possible</p> + + <p>There is also support coming for a few new chipsets as + usual.</p> + + <p>The work is just about finished enough that it can be released + as patches to sort out eventual problems before hitting current. + The changes are pretty massive as this touches all over the driver + infrastructure, so lots of old bugs and has also been spotted and + fixed during this journey</p> + </body> + </project> + + <project> + <title>Atheros Wireless Support</title> + + <contact> + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The ath driver was updated to support all the new features added + to the net80211 layer. As part of this work a new version of the + Hardware Access Layer (HAL) module was brought in; this version + supports all available Atheros parts found in PCI and Cardbus + products. Otherwise, adhoc mode should now be usable, antenna + management has been significantly improved, and soft LED support + now identifies traffic patterns.</p> + + <p>The transmit rate control algorithm was split out of the driver + into an independent module. Two different algorithms are available + with other algorithms (hopefully) to be added.</p> + + <p>Work is actively going on to add Atheros' SuperG + capabilities.</p> + </body> + </project> + + <project> + <title>New DHCP Client</title> + + <contact> + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The OpenBSD dhcp client program has been ported and enhanced to + listen for 802.11-related events from the kernel. This enables + immediate IP address acquisition when roaming (as opposed to the + polling done by the old code). The main change from the previous + client is that there is one dhclient process per interface as + opposed to one for the entire system. This necessitates changes to + the system startup scripts.</p> + + <p>Incorporation into the base system is waiting on a volunteer who + will shepherd the changes into the tree and deal with bugs.</p> + </body> + </project> + + <project cat='misc'> + <title>EuroBSDCon 2004 submitted papers are online</title> + + <contact> + <person> + <name> + <given>Patrick M.</given> + + <common>Hausen</common> + </name> + + <email>hausen@punkt.de</email> + </person> + </contact> + + <links> + <url href="http://www.eurobsdcon2004.de/papers.html"> + Papers/Presentations Download Page</url> + </links> + + <body> + <p>Finally all of the papers and presentations are online for + download from our conference website. Thanks again to all who + helped make EuroBSDCon 2004 a success.</p> + </body> + </project> + + <project> + <title>ifconfig Overhaul</title> + + <contact> + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The ifconfig program used to configure network interfaces was + overhauled. Over the years ifconfig has grown into a complex and + often contorted piece of software that is hard to understand and + difficult to maintain. The primary motivation for this work was to + enable minimal configurations (for embedded use) without changing + the code and to support future additions in a modular way. + Functionality is now broken out into separate files and operations + are registered with the central ifconfig code base. Features are + configured simply by specifying which code is to be included when + building the program.</p> + + <p>In the future the plan is for ifconfig to auto-load + functionality through dynamic libraries. This mechanism will allow, + for example, third party software packages to provide kernel + services and ifconfig add-on code without changing the base + system.</p> + </body> + </project> + + <project cat='kern'> + <title>Network Stack Locking</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/projects/netperf/">FreeBSD + Project Netperf project web page.</url> + + <url href="http://www.watson.org/~robert/freebsd/netperf/">Robert + Watson's personal Netperf web page.</url> + </links> + + <body> + <p>The netperf project is working to enhance the performance of the + FreeBSD network stack. This work grew out of the SMPng Project, + which moved the FreeBSD kernel from a "Giant Lock" to more + fine-grained locking and multi-threading. SMPng offered both + performance improvement and degradation for the network stack, + improving parallelism and preemption, but substantially increasing + per-packet processing costs. The netperf project is primarily + focused on further improving parallelism in network processing + while reducing the SMP synchronization overhead. This in turn will + lead to higher processing throughput and lower processing latency. + Tasks include completing the locking work, optimizing locking + strategies, amortizing locking costs, introducing new + synchronization primitives, adopting non-locking synchronization + strategies, and improving opportunities for parallelism through + additional threading.</p> + + <p>Between July, 2004, and December, 2004, the Netperf project did + a great deal of work, for which there is room only to include + limited information. Much more information is available by visiting + the URLS above, including information on a variety of on-going + activities. Accomplishments include:</p> + + <p>July, 2004: A variety of improvements to PCB locking in the IPv6 + implementation; locking for the if_xl driver; socket locking for + the NFS client; cleanup of the soreceive() code path including + structural improvements, assertions, and locking fixes; cleanup of + the IPX/SPX code in preparation for locking; additional locking and + locking assertions for the TCP implementation; bug fixes for + locking and memory allocation in raw IP; + <em>netatalk cleanup and locking merged to FreeBSD CVS</em> + + ; + <em>locking for many netgraph nodes merged to FreeBSD CVS</em> + + ; SLIP structural improvements; experimental locking for netatalk + ifaddrs; BPF locking optimizations (merged); Giant assertions for + VFS to check VFS/network stack boundaries; UNIX domain socket + locking optimizations; expansion of lock order documentation in + WITNESS, additional NFS server code running MPSAFE; pipe locking + optimizations to improve pipe allocation performance; Giant no + longer required for fstat on sockets and pipes (merged); Giant no + longer required for socket and pipe file descriptor closes + (merged); + <em>IFF_NEEDSGIANT interface flag added to support compatibility + operation for unlocked device drivers (merged)</em> + + ; merged accept filter locking to FreeBSD CVS; documented uidinfo + locking strategy (merged); Giant use reduced in fcntl().</p> + + <p>August, 2004: UMA KTR tracing (merged); UDP broadcast receive + locking optimizations (merged); TCP locking cleanup and + documentation; IPv6 inpcb locking, cleanup, and structural + improvements; + <em>IPv6 inpcb locking merged to FreeBSD CVS</em> + + ; KTR for systems calls added to i386; + <em>substantial optimizations of entropy harvesting synchronization + (merged)</em> + + ; callout(9) sampling converted to KTR (merged); inpcb socket + option locking (merged); GIANT_REQUIRED removed from netatalk in + FreeBSD CVS; + <em>merged ADAPTIVE_GIANT to FreeBSD CVS, resulting in substantial + performance improvements in many kernel IPC-intensive + benchmarks</em> + + ; prepend room for link layer headers to the UDP header mbuf to + avoid one allocation per UDP send (merged); a variety of UDP bug + fixes (merged); additional network interfaces marked MPSAFE; UNIX + domain socket locking reformulated to protect so_pcb pointers; + <em>MP_WATCHDOG, a facility to dedicate additional HTT logical CPUs + as watchdog CPUs developed (merged)</em> + + ; annotation of UNIX domain socket locking merged to FreeBSD CVS; + <em>kqueue locking developed and merged by John-Mark Gurney</em> + + ; task list for netinet6 locking created; conditional locking + relating to kqueues and socket buffers eliminated (merged); NFS + server locking bugfixes (merged); in6_prefix code removed from + netinet6 by George Neville-Neil, lowering the work load for + netinet6 (merged); unused random tick code in netinet6 removed + (merged); + <em>ng_tty, IPX, KAME IPSEC now declare dependence on Giant using + compile-time declaration NET_NEEDS_GIANT("component") permitting + the kernel to detect unsafe components and automatically acquire + the Giant lock over network stack operation if needed (merged)</em> + + ; additional locking optimizations for entropy code (merged); Giant + disabled by default in the netperf development branch (merged).</p> + + <p>September, 2004: bugs fixed relating to Netgraph's use of the + kernel linker while not holding Giant (merged); + <em>merged removal of Giant over the network stack by default to + FreeBSD CVS</em> + + ; races relating to netinet6 and if_afdata corrected (merged); + annotation of possible races in the BPF code; BPF code converted to + queue(3) (merged); race in sopoll() corrected (merged).</p> + + <p>October, 2004: IPv6 netisr marked as MPSAFE; TCP timers locked, + annotated, and asserted (merged); IP socket option locking and + cleanup (merged); Netgraph ISR marked MPSAFE; netatalk ISR marked + MPSAFE (merged); some interface list locking cleanup (merged); use + after free bug relating to entropy harvesting and ethernet fixed + (merged); soclose()/sofree() race fixed (merged); IFF_LOCKGIANT() + and IFF_UNLOCKGIANT() added to acquire Giant as needed when + entering the ioctls of non-MPSAFE network interfaces.</p> + + <p>November, 2004: cleanup of UDPv6 static global variables + (merged); + <em>FreeBSD 5.3 released! First release of FreeBSD with an MPSAFE + and Giant-free network stack as the default configuration!</em> + + ; additional TCP locking documentation and cleanup (merged); + <em>optimization to use file descriptor reference counts instead of + socket reference counts for frequent operations results in + substantial performance optimizations for high-volume send/receive + (merged)</em> + + ; an accept bug is fixed (merged) experimental network polling + locking introduced; + <em>substantial measurement and optimization of mutex and locking + primitives (merged)</em> + + ; + <em>experimental modifications to UMA to use critical sections to + protect per-CPU caches instead of mutexes yield substantial + micro-benchmark benefits when combined with experimental critical + section optimizations</em> + + ; FreeBSD Project Netperf page launched; performance + micro-benchmarks benchmarks reveal IP forwarding latency in 5.x is + measurably better than 4.x on UP when combined with optional + network stack direct dispatch; several NFS server locking bugfixes + (merged); + <em>development of new mbufqueue primitives and substantial + experimentation with them permits development of amortized cost + locking APIs for handoff between the network stack and network + device drivers (work in collaboration with Sandvine, Inc)</em> + + ; Linux TCP_INFO API added to allow user-space monitoring of TCP + state (merged); SMPng task list updated; UDP static/global fixes + merged to RELENG_5.</p> + + <p>December, 2004: UDP static/global fixes developed for + multi-threaded in-bound UDP processing (merged); socket buffer + locking fixes for urgent TCP input processing (merged); lockless + read optimizations for IF_DEQUEUE() and IF_DRAIN(); Giant-free + close for sockets/pipes/... merged to FreeBSD CVS; optimize + mass-dequeues of mbuf chains in netisr processing; netrate tool + merged to RELENG_5; TCP locking fixes merged to RELENG_5; "show + alllocks" added to DDB (merged); IPX locking bugfixes (merged); + IPX/SPX __packed fixes (merged); IPX/SPX moved to queue(9) + (merged); TCP locking fixes and annotations merged to FreeBSD CVS; + IPX/SPX globals and pcb locking (merged); + <em>IPX/SPX marked MPSAFE (merged)</em> + + ; IP socket options locking merged to FreeBSD; SPPP locked by Roman + Kurakin (merged); UNIX domain socket locking fixes by Alan Cox + (merged).</p> + + <p>On-going work continues with regard to locking down network + stack components, including additional netinet6 locking, mbuf queue + facilities and operations; benchmarking; moving to critical + sections or per-CPU mutexes for UMA per-CPU caches; moving to + critical sections or per-CPU mutexes for malloc(9) statistics; + elimination of separate mbuf allocator statistics; additional + interface locking; a broad variety of cleanups and documentation of + locking; a broad range of optimizations.</p> + </body> + </project> + + <project cat='proj'> + <title>FreeBSD profile.sh</title> + + <contact> + <person> + <name> + <given>Tobias</given> + + <common>Roth</common> + </name> + + <email>ports@fsck.ch</email> + </person> + </contact> + + <links> + <url href="https://projects.fsck.ch/profile">FreeBSD profile.sh + site</url> + </links> + + <body> + <p>FreeBSD profile.sh is targeted at laptops. It allows to define + multiple network environments (eg, home, work), and will then + detect in which environment the laptop is started and configure it + accordingly. Almost everything from under /etc can be configured + per environment, and only the overrides to the default /etc have to + be defined. Suspending in one environment and resuming in a + different one is also supported.</p> + + <p>Proper integration into the acpi/apm and several small + improvements are underway. More testing with different system + configurations is needed.</p> + </body> + </project> + + <project cat='proj'> + <title>FreeBSD Release Engineering</title> + + <contact> + <person> + <name> + <given>Scott</given> + + <common>Long</common> + </name> + + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng" /> + </links> + + <body> + <p>At long last, FreeBSD 5.3 was released in November of 2004. This + marked the start of the RELENG_5/5-STABLE branch and the beginning + of the 6-CURRENT development branch. Many thanks to the tireless + efforts of the FreeBSD developer and user community for making this + release a success.</p> + + <p>FreeBSD 4.11 release engineering is also now in progress. This + will be the final release from the 4.x series and is mainly + incremental bug fixes and a handful of feature additions. Of note + is that the IBM ServeRAID 'IPS' driver is now supported on 4.x and + will be included in this release, and the Linux emulation layer has + been updated to support a RedHat 8.0 userland. The release is + expected to be available on January 24.</p> + + <p>Looking forward, there will be several FreeBSD 5.x releases in + the coming year. FreeBSD 5.4 release engineering will start in + March, and FreeBSD 5.5 release engineering will likely start in + June. These releases are expected to be more conservative than + previous 5.x releases and will follow the same philosophy as + previous -STABLE branches of fixing bugs and adding incremental + improvements while maintaining API stability.</p> + + <p>For the 6-CURRENT development branch as well as all future + development and stable branches, we are planning to move to a + schedule with fixed timelines that move away from the uncertainty + and wild schedule fluctuations of the previous 5.x releases. This + means that major branches will happen at 18 month intervals, and + releases from those branches will happen at 4 month intervals. + There will also be a dedicated period of testing and bug fixing at + the beginning of each branch before the first release is cut from + that branch. With the shorter and more defined release schedules, + we hope to lessen the problem of needed features not reaching users + in a reasonable time, as happened too often with 5.x. This is a + significant change in our strategy, and we look forward to + realizing the benefits of it. This will kick off with the RELENG_6 + branch happing in June of 2005, followed by the 6.0 release in + August of 2005.</p> + + <p>Also on the roadmap is a plan to combine the live-iso disk2 and + the install distributions of disk1 into a single disk which can be + used for both installation and for recovery. 3rd party packages + that currently reside on disc1 will be moved to a disk2 that will + be dedicated to these packages. This move will allow us to deal + with the ever growing size of packages and also provide more + flexibility to vendors that wish to add their own packages to the + releases. It also opens the door to more advanced installers being + put in place of sysinstall. Anyone interested in helping with this + is encouraged to contact us.</p> + </body> + </project> + + <project> + <title>Wireless Networking Support</title> + + <contact> + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The wireless networking layer was updated to support the 802.1x, + WPA, and 802.11i security protocols, and the WME/WMM multi-media + protocol. As part of this work extensible frameworks were added for + cryptographic methods, authentication, and access control. + Extensions are implemented as loadable kernel modules that hook + into the net80211 layer. This mechanism is used, for example, to + implement WEP, TKIP, and CCMP crypto protocols. The Atheros driver + (ath) is currently the only driver that uses the full set of + features. Adding support to other drivers is simple but waiting on + volunteers. Ports of the wpa_supplicant and hostapd programs enable + use of the new security protocols.</p> + + <p>The support for tracking stations in a bss (managed or adhoc) + and stations found when scanning was overhauled. Multiple tables + are now used, each with different management policies, reference + counting is now done consistently, and inactivity processing is + done more intelligently (e.g. associated stations are probed before + removal). This is the first step towards proper roaming support and + other advanced features.</p> + + <p>AP power save support was added. Associated stations may now + operate in power save mode; frames sent to them will be buffered + while they are sleeping and multicast traffic will be deferred + until after the next beacon (per the 802.11 protocol). Power save + support is required in a standards-compliant access point. Only the + ath driver currently implements power save support.</p> + + <p>Work is actively going on to add Atheros' SuperG capabilities, + WDS, and for multi-bss support (ssid and/or bssid) on a single + device.</p> + </body> + + <help> + <task>Drivers other than ath need updates to support the new + security protocols</task> + + <task>hostapd needs work to support the IAPP and 802.11i + preauthentication protocols (these are simple conversion of + existing Linux code)</task> + </help> + </project> + + <project cat='arch'> + <title>FreeBSD on Xen</title> + + <contact> + <person> + <name> + <given>Kip</given> + + <common>Macy</common> + </name> + + <email>kmacy@fsmware.com</email> + </person> + </contact> + + <links> + <url href="http://www.fsmware.com/xenofreebsd/">binaries + source + + slightly out of date HOWTO</url> + + <url href="http://www.cl.cam.ac.uk/Research/SRG/netos/xen/">Xen + project page</url> + </links> + + <body> + <p>FreeBSD 5.2.1 is stable on the stable branch of Xen as a guest. + FreeBSD 5.3 runs on the stable branch of Xen as a guest, but a + couple of bugs need to be tracked down.</p> + </body> + + <help> + <task>FreeBSD support for running in Domain 0 (host)</task> + + <task>FreeBSD support for VM checkpoint and migration</task> + </help> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2005-01-2005-03.xml b/en_US.ISO8859-1/htdocs/news/status/report-2005-01-2005-03.xml new file mode 100644 index 0000000000..86e3a63a41 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2005-01-2005-03.xml @@ -0,0 +1,2147 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<report> + <date> + <month>January-April</month> + + <year>2005</year> + </date> + + <section> + <title>Introduction</title> + + <p>The first quarter of 2005 has been extremely active in both + FreeBSD-CURRENT and -STABLE. With FreeBSD 5.4 in the final RC stage + and an anticipated branch of FreeBSD-6 this summer we have seen a lot + of performance improvements in 5 and a couple of exciting new + features in 6.</p> + + <p>The report turnout was extremely good and it seems that the + webform provided by Julian Elischer has made it more enjoyable to + write reports. Many thanks to Julian for providing this. We also + like to get your attention to the open tasks section provided in some + reports.</p> + + <p>On special note, please take a look at the report about the + upcoming BSDCan in Ottawa. There will be lots of interesting FreeBSD + related talks and activities. If you enjoy reading these reports, you + will love the conference. See you there!</p> + + <p>Thanks to all the reporters, we hope you enjoy reading.</p> + </section> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>doc</name> + + <description>Documentation</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>net</name> + + <description>Network infrastructure</description> + </category> + + <category> + <name>bin</name> + + <description>Userland programs</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <category> + <name>vendor</name> + + <description>Vendor / 3rd Party Software</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='proj'> + <title>Secure Updating</title> + + <contact> + <person> + <name> + <given>Colin</given> + + <common>Percival</common> + </name> + + <email>cperciva@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.daemonology.net/portsnap/" /> + + <url href="http://www.daemonology.net/freebsd-update/" /> + </links> + + <body> + <p>Shortly before the ports freeze for FreeBSD 5.4, I released a + new version of Portsnap. In addition to being secure and more + efficient than CVSup, this latest version distributes INDEX, + INDEX-5, and INDEX-6 files, thereby eliminating the need to run + "make fetchindex" and ensuring that the ports INDEX will match the + existing ports tree. In addition, portsnap builds have now moved + onto hardware managed by the FreeBSD project, thereby sharply + increasing portsnap's chances of survival if I get hit by a + bus.</p> + + <p>In early February hardware problems caused both FreeBSD Update + and Portsnap to stop functioning for a few days, but those were + resolved thanks to a server donated by layeredtech.com.</p> + + <p>I intend bring Portsnap into the FreeBSD base system before the + end of the month, followed by FreeBSD Update a few months + later.</p> + </body> + </project> + + <project cat='project'> + <title>if_bridge from NetBSD</title> + + <contact> + <person> + <name> + <given>Andrew</given> + + <common>Thompson</common> + </name> + + <email>andy@fud.org.nz</email> + </person> + </contact> + + <links> + <url href="http://www.fud.org.nz/~andy/if_bridge.diff" /> + </links> + + <body> + <p>This project aims to import the bridging code and interface from + NetBSD and OpenBSD. The bridge is a cloned interface which can be + modified by ifconfig and brconfig. It supports assigning an IP + address directly to the bridge (e.g. bridge0) instead of one of the + member interfaces, and can be used with tcpdump to inspect the + bridged packets. The code also supports spanning tree (802.1D) for + loop detection and link redundancy. Any pfil(9) packet filter can + be used to filter the bridged packets.</p> + </body> + + <help> + <task>Testing performance and functionality against the existing + bridge code. Testers welcome!</task> + </help> + </project> + + <project cat='arch'> + <title>ARM Support for TS-7200</title> + + <contact> + <person> + <name> + <given>John-Mark</given> + + <common>Gurney</common> + </name> + + <email>jmg@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.embeddedarm.com/epc/ts7200-spec-h.html"> + TS-7200 Board</url> + + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/jmg/arm&HIDEDEL=NO"> + Perforce Code Location</url> + + <url href="http://people.freebsd.org/~jmg/dmesg.ts7200">FreeBSD/arm + TS-7200 dmesg output</url> + </links> + + <body> + <p>I have been working on getting FreeBSD/arm running on the + TS-7200. So far the board boots, and has somewhat working ethernet + (some unexplained packet loss). I can netboot from a FreeBSD/i386 + machine, and I can also mount msdosfs's on CF.</p> + </body> + + <help> + <task>Figuring out why some small packets transmit with + error</task> + + <task>EP93xx identification information to properly attach various + onboard devices</task> + </help> + </project> + + <project cat='ports'> + <title>Update of the Linux userland infrastructure</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Emulation</given> + + <common>Mailinglist</common> + </name> + + <email>freebsd-emulation@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The update to RedHat 8 as discussed in the last status report + went smoothly (just some minor glitches which got resolved + fast).</p> + + <p>As a next step a cleanup/streamlining and the possibility of + overriding the default Linux base is in progress. This depends on + changes which need at least one testrun on the ports build cluster, + so the final date for those changes depends upon the availability + of the cluster resources.</p> + </body> + + <help> + <task>Refactoring the common RPM code into bsd.rpm.mk.</task> + + <task>Determining which up-to-date Linux distribution to use as the + next default Linux base. Important criteria: + <ul> + <li>RPM based (to be able to use the existing + infrastructure)</li> + + <li>good track record regarding availability of security + fixes</li> + + <li>packages available from several mirror sites</li> + + <li>available for several hardware architectures (e.g. i386, + amd64, sparc64; Note: not all architectures have a working + linuxolator for their native bit with, but as long as there are + no userland bits available, no motivation regarding writing the + kernel bits will arise)</li> + </ul> + </task> + + <task>Moving the linuxolator userland to an up-to-date version (see + above).</task> + </help> + </project> + + <project cat='bin'> + <title>Pipe namespace added to portalfs</title> + + <contact> + <person> + <name> + <given>Diomidis</given> + + <common>Spinellis</common> + </name> + + <email>dds@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.spinellis.gr/blog/20050413/index.html" /> + </links> + + <body> + <p>A new sub-namespace, called pipe, has been added to portalfs. + The pipe namespace executes the named command, starting back at the + root directory. The command's arguments can be provided after the + command's name, by separating them with spaces or tabs. Files + opened for reading in the pipe namespace will receive their input + from the command's standard output; files opened for writing will + send the data of write operations to the command's standard input. + The pipe namespace allows us to perform scatter gather operations + without using temporary files, create non-linear pipelines, and + implement file views using symbolic links.</p> + </body> + </project> + + <project cat='kern'> + <title>Low-overhead performance monitoring for FreeBSD</title> + + <contact> + <person> + <name> + <given>Joseph</given> + + <common>Koshy</common> + </name> + + <email>jkoshy@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~jkoshy/projects/perf-measurement"> + Project home page</url> + </links> + + <body> + <p>Many modern CPUs have on-chip performance monitoring counters + (PMCs) that can be used to count low-level hardware events like + instruction retirals, branch mispredictions, cache and TLB misses + and the like. PMC architectures and capabilities vary between CPU + vendors and between CPU generations from the same vendor, making + the creation of portable applications difficult. This project + attempts to provide a uniform API for applications to use, and the + necessary infrastructure to "virtualize" and manage the available + PMC hardware resources. The creation of performance analysis tools + that use this infrastructure is also part of the project's + goals.</p> + + <p>Work since the last status report:</p> + + <ul> + <li>Support for Intel + Pentium-Pro/Pentium-II/Pentium-III/Pentium-M/Celeron style PMCs + has been added.</li> + + <li>The Pentium-4/HTT machine dependent layer has been + overhauled.</li> + + <li>A Python language interface to the C library interface pmc(3) + has been written.</li> + + <li>Many bugs have been fixed and documentation has been + updated.</li> + </ul> + </body> + + <help> + <task>The code needs to be tested on Intel Pentium-M, Celeron, + Pentium II and Pentium Pro CPUs.</task> + </help> + </project> + + <project cat='proj'> + <title>GELI - GEOM class for providers encryption</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + + <common>Dawidek</common> + </name> + + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/geom%5fclasses/sys/geom/eli&HIDEDEL=NO"> + Kernel module.</url> + + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/geom%5fclasses/sbin/geom/class/eli&HIDEDEL=NO"> + Userland configuration utility.</url> + </links> + + <body> + <p>GELI is a GEOM class used for GEOM providers encryption. I + decided to work on this, as I needed some feature, which cannot be + found in similar projects. Here is the list of features, I found + interesting:</p> + + <ul> + <li>makes use of crypto(9)</li> + + <li>if there is a crypto hardware available, GELI will run + cryptography on it automatically; if not, it starts dedicated + kernel thread and do crypto software work in there</li> + + <li>supports many cryptographic algorithms (AES, Blowfish, + 3DES)</li> + + <li>is able to take key components from many sources at once + (user entered passphrase, random bits from a file, etc.)</li> + + <li>allows to encrypt root partition</li> + + <li>user will be asked for the passphrase before root file system + is mounted</li> + + <li>uses "PKCS #5: Password-Based Cryptography Specification + Version 2.0" for user passphrase protection (optional)</li> + + <li>allows to use two independent keys (e.g. "user key" and + "company key")</li> + + <li>is fast</li> + + <li>GELI does simple sector-to-sector encryption</li> + + <li>allows to backup/restore Master Keys, so when user have to + quickly destroy keys, it is able to get the data back by + restoring keys from the backup</li> + + <li>provider can be configured at attach time to automatically + detach on last close (so user don't have to remember to detach + after unmounting file system)</li> + + <li>allows to attach provider with a random, one-time keys</li> + + <li>useful for swap partitions and temporary file systems</li> + </ul> + </body> + + <help> + <task>Code audit/review is more than welcome!</task> + </help> + </project> + + <project cat='doc'> + <title>FreeBSD Dutch Documentation Project</title> + + <contact> + <person> + <name> + <given>Remko</given> + + <common>Lodder</common> + </name> + + <email>remko@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/doc/nl/books/handbook">FreeBSD + Dutch Handbook</url> + + <url href="http://www.evilcoder.org/freebsd_html/">FreeBSD Dutch + Handbook preview</url> + + <url href="http://www.evilcoder.org/content/section/6/39/">The + Project Page</url> + </links> + + <body> + <p>The FreeBSD Dutch Documentation Project is a ongoing project in + translating the English documentation to the Dutch language. + Currently we have translated almost the entire handbook, and more + to come. If you want to help out by review the Dutch documents, or + you want to help translating the remainders of the handbook or + other documents, feel free to contact me at + <a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a> + </p> + </body> + + <help> + <task>Translate the English handbook, then review the Dutch + handbook</task> + + <task>Translate the English FAQ, then review the Dutch FAQ</task> + + <task>Translate the English Articles, then review the Dutch + Articles</task> + </help> + </project> + + <project cat='proj'> + <title>FreeBSD Java Project</title> + + <contact> + <person> + <name> + <given>Greg</given> + + <common>Lewis</common> + </name> + + <email>glewis@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Alexey</given> + + <common>Zelkin</common> + </name> + + <email>phantom@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/java/" /> + </links> + + <body> + <p>The FreeBSD Java Project released its initial support for JDK + 1.5.0 with patch set 1 "Sabretooth" in January. The initial release + featured support for both FreeBSD 5.3/i386 and 5.3/amd64. Since + then preliminary support for FreeBSD 4.11/i386 has been added and + several bug fixes have been made. Updates in the coming months will + add support for the browser plug in and Java Web Start, which were + not in the initial release.</p> + </body> + + <help> + <task>Volunteers to look into some serious problems with JDK 1.5.0 + on FreeBSD 4.x</task> + </help> + </project> + + <project cat='proj'> + <title>Common Address Redundancy Protocol - CARP</title> + + <contact> + <person> + <name> + <given>Max</given> + + <common>Laier</common> + </name> + + <email>mlaier@FreeBSD.org</email> + </person> + </contact> + + <contact> + <person> + <name> + <given>Gleb</given> + + <common>Smirnoff</common> + </name> + + <email>glebius@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://www.freebsd.org/cgi/man.cgi?query=carp&manpath=FreeBSD+6.0-current" /> + + <url href="http://people.freebsd.org/~mlaier/CARP/" /> + </links> + + <body> + <p>CARP is an alternative to VRRP. In contrast to VRRP it has full + support for IPv6 and uses crypto to protect the advertisements. It + was developed by OpenBSD due to concerns that the HSRP patent might + cover VRRP and CISCO might defend its patent. CARP has, since then, + improved a lot over VRRP.</p> + + <p>CARP has been committed to HEAD and MFCed to RELENG_5. It will + be available in upcoming 5.4-RELEASE.</p> + + <p>Big thanks to all users who provided testing and reported bugs + to Max and Gleb. Daniel Seuffert has donated hardware to Max for + this project. Gleb's work was sponsored by + <a href="http://www.rambler.ru">Rambler</a> + + .</p> + </body> + + <help> + <task>Improve vlan(4) support. Test ng_eiface(4).</task> + + <task>Improve locking, consider removing interface layer.</task> + </help> + </project> + + <project cat='net'> + <title>netgraph(4) status report</title> + + <contact> + <person> + <name> + <given>Gleb</given> + + <common>Smirnoff</common> + </name> + + <email>glebius@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://www.freebsd.org/cgi/man.cgi?query=ng_netflow&manpath=FreeBSD+6.0-current"> + ng_netflow(4)</url> + + <url + href="http://www.freebsd.org/cgi/man.cgi?query=ng_ipfw&manpath=FreeBSD+6.0-current"> + ng_ipfw(4)</url> + + <url href="http://people.freebsd.org/~glebius/totest/ng_nat/"> + ng_nat work in progress</url> + </links> + + <body> + <p>This report covers period since August 2004 until April + 2005.</p> + + <p>New nodes. Two new nodes have been added to base FreeBSD + distribution. ng_netflow(4) node, which implements NetFlow version + 5 accounting of IPv4 packets. ng_ipfw(4) node, which diverts + packets from ipfw(4) to netgraph(4) and back. A well known + ng_ipacct node has been added to ports tree.</p> + + <p>SMP. Nodes, which need to allocate unique names have been + protected with mutex in RELENG_5, and subr_unit allocator in HEAD. + Nodes, which need to run periodical jobs were reworked to use + mpsafe ng_callout() API. ng_tty(4) node has been overhauled to be + compatible with debug.mpsafenet=1. NetGraph ISR and callout are now + declared MPSAFE in HEAD.</p> + + <p>NetGraph flow control. Two nodes ng_ether(4) and ng_cisco(4) + have been improved to emit flow control messages to upstream node, + when state of link changes. New link failure detection method have + been introduced in ng_one2many(4) node - listening to these flow + control messages from downstream.</p> + </body> + + <help> + <task>more SMP testing of many nodes</task> + + <task>review locking of graph restructuring</task> + + <task>ng_nat node - an in-kernel natd(8)</task> + + <task>make ng_bridge(4) multithreaded</task> + </help> + </project> + + <project cat='kern'> + <title>drm</title> + + <contact> + <person> + <name> + <given>Eric</given> + + <common>Anholt</common> + </name> + + <email>anholt@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://r300.sourceforge.net/">ATI R300 DRI project</url> + </links> + + <body> + <p>A DRM update was finally committed to -current on 2005-04-15, + after jhb@ did the necessary fix to vm_mmap. New development + drivers were added for mach64 and r300 (see URL for info). The + nearly-finished code for savage and i915 were also added, but left + disconnected from the build. However, the most visible change is + likely the support for texture tiling, color tiling, and HyperZ on + Radeons, which (with updated userland) likely provide a 50-75% + framerate increase in many applications.</p> + </body> + + <help> + <task>Find someone with newbus knowledge to figure out why the i915 + won't attach to drmsub0.</task> + + <task>Finish porting the savage driver.</task> + + <task>Integrate busdma code from Tonnerre (NetBSD).</task> + </help> + </project> + + <project cat='kern'> + <title>Storage driver SMPng locking</title> + + <contact> + <person> + <name> + <given>Scott</given> + + <common>Long</common> + </name> + + <email>scottl@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Several storage drivers have been taken out from under the Giant + mutex in the past few months. Thanks to sponsorship from + <a href="http://www.freebsdsystems.com">FreeBSD Systems, Inc</a> + + and + <a href="http://www.imp.ch">ImproWare, AG, Switzerland</a> + + , the LSI MegaRAID (AMR) and IBM/Adaptec ServeRAID (IPS) drivers + have been locked. SMPng locking is a key step in improving the + performance of system drivers in FreeBSD 5.x and beyond, and both + of these drivers are showing the benefits of this. FreeBSD 5.4 will + contains these improvements when it is released.</p> + + <p>Similar work is ongoing with the 3WARE Escalade (TWE) driver, + and preliminary patches have been made available to testers. I hope + to have this driver complete in time for the next FreeBSD + release.</p> + + <p>Unfortunately, most benefits can only be gained from pure block + storage drivers such as the ones mentioned here due to the SCSI + subsystem in FreeBSD (CAM) not be locked itself at this time. It is + possible, however, to lock a CAM sub-driver and bring the driver's + interrupt handler out from under Giant for a partial gain. The Sun + FAS366 SCSI driver (ESP) operates like this. Volunteers to lock + other drivers or to tackle locking CAM are gladly accepted, so + please contact me if you are interested.</p> + </body> + </project> + + <project cat='kern'> + <title>Filesystem journalling for UFS</title> + + <contact> + <person> + <name> + <given>Scott</given> + + <common>Long</common> + </name> + + <email>scottl@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://repoman.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/scottl/ufsj" /> + </links> + + <body> + <p>It's time to bite the bullet and admit that fsck is no longer + scalable for modern storage capacities. While a healthy debate can + still be had on the merits and data integrity guarantees of + journalling vs. SoftUpdates, the fact that SoftUpdates still + requires a fsck to ensure consistency of the filesystem metadata + after an unclean shutdown means uptime is lost. While background + fsck is available, it saps system performance and stretched the + fsck time out to hours.</p> + + <p>Journalling provides a way to record transactions that might not + have fully been written to disk before the system crashed, and then + quickly recover the system back to a consistent state by replaying + these transactions. It doesn't guarantee that no data will be lost, + but it does guarantee that the filesystem will be back to a + consistent state after the replay is performed. This contrasts to + SoftUpdates that re-arranges metadata updates so that + inconsistencies are minimized and easy to recover from, though + recovery still requires the traditional full filesystem scan.</p> + + <p>Journalling is a key feature of many modern filesystems like + NTFS, XFS, JFS, ReiserFS, and Ext3, so the ground is well covered + and the risks for UFS/FFS are low. I'm aware that groups from CMU + and RPI have attempted similar work in the past, but unfortunately + the work is either very outdates, or I haven't had any luck in + contacting the groups. Is this absence, I've decided to work on + this project myself in hopes of having a functional prototype in + time for FreeBSD 6.0.</p> + + <p>The approach is simple and journals full metadata blocks instead + of just deltas or high-level operations. This greatly simplifies + the replay code at the cost of requiring more disk space for the + journal and more work within the filesystem to identify discreet + update points. An important design consideration is whether to make + the journal data and code compatible with the UFS2 filesystem, or + to start a new UFS3 derivative. Since the latter presents a very + high barrier to adoption for most people, I'm going to try to make + it a compatible option for UFS2. This means that the journal blocks + will likely appear as an unlinked file to legacy filesystem and + fsck code, and will be treated as such. This will allow seamless + fallback to using fsck, though once the unlinked journal data + blocks are reclaimed by fsck, the user will have to take action to + re-create the journal file again.</p> + + <p>One key piece of journalling is ensuring that each journal + transaction is fully written to disk before the associated metadata + blocks are written to the filesystem. I plan to adopt the buffer + 'pinning' mechanism from Alexander Kabaev's XFS work to assist with + this. This will allow the journalling subsystem fine-grained + control over which blocks get flushed to disk by the buffer daemon + without having to further complicate the UFS/FFS code. One + consideration is how Softupdates falls into this and whether it is + mutually exclusive of journalling or if it can help provide + transaction ordering functionality to the journal. Research here is + on-going.</p> + + <p>Some preliminary work can be found in Perforce in the + //depot/user/scottl/ufsj/... tree or at the URL provided. Hopefully + this will quickly accelerate.</p> + </body> + </project> + + <project cat='kern'> + <title>Status Report for FreeBSD ATA driver project</title> + + <contact> + <person> + <name> + <given>Søren</given> + + <common>Schmidt</common> + </name> + + <email>sos@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>ATA mkIII has been committed to -current after a couple of month + testing as patches post on -current and 5-stable. I will continue + to provide patches for 5-stable for those that need up-to-date ATA + support there.</p> + + <p>Here a short rehash of what mkIII brings:</p> + + <p>ATA is now fully modular so each part can be loaded/unloaded at + will to provided the wanted functionality.</p> + + <p>Much improved SATA support that support hotplug events on + controllers that support it (Promise, SiS, nVidia so far) ie the + system will automagically detect when SATA devices come and go and + add/delete device entries etc.</p> + + <p>Much improved ATA RAID support. The ata-raid driver has been + largely rewritten to take advantage of the features the improved + infrastructure provides, including composite ATA operations etc. + The rebuild functionality has been changed to rebuild on userland + reads, so a simple dd of the entire array will get it rebuild (what + atacontrol now does). This means that the resources used for this + can be better tailored to the actually usage pattern if needed. ATA + RAID now supports 10+ different RAID metadata formats, so most BIOS + defined ATA RAID arrays can be picked up and used. The number of + metadata formats that can be created from within FreeBSD is still + limited though and is not a high priority feature right now.</p> + + <p>The lowlevel infrastructure of the ATA driver has been refined + even further to support "strange" chipsets much more easily and in + most case transparent to the higher levels. This to easy ports to + new platforms where ATA controllers doesn't necessarily have the + x86 legacy layout.</p> + + <p>Lots of bug fixes and corrections all over the driver proper. + The rework of the infrastructure has revealed bugs and deficiencies + that has been fixed in the process of modulerising ATA and making + the infrastructure more generic, and hopefully easier to + understand.</p> + + <p>The work continues to keep ATA on top of new chipsets and other + advancements in the ATA camp. SATA ATAPI support is in the works + and so are support for NCA/TCQ (tags). Donations of unsupported + hardware is the way to get it supported as I'm way out of my budget + for new hardware for the next decade or so according to my wife + :)</p> + </body> + + <help> + <task>Lots of testing wanted, especially SATA and RAID + support</task> + </help> + </project> + + <project cat='proj'> + <title>GSHSEC - GEOM class for handling shared secret</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + + <common>Dawidek</common> + </name> + + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://www.freebsd.org/cgi/man.cgi?query=gshsec&apropos=0&sektion=0&manpath=FreeBSD+6.0-current&format=html"> + Manual page.</url> + </links> + + <body> + <p>GSHSEC is a GEOM class used for handling shared secret data + between multiple GEOM providers. For every write request, SHSEC + class splits the data using XOR operation with random data, so N-1 + providers gets just random data and one provider gets the data + XORed with the random data from the other providers. All of the + configured providers must be present in order to reveal the secret. + The class is already committed to HEAD and RELENG_5 branches.</p> + </body> + </project> + + <project cat='kern'> + <title>ATAPI/CAM</title> + + <contact> + <person> + <name> + <given>Thomas</given> + + <common>Quinot</common> + </name> + + <email>thomas@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>ATAPI/CAM integration with the new ATA (mkIII) framework is now + completed. ATAPI/CAM is now available as a loadable module + (atapicam.ko). It is also independent from the native ATAPI drivers + again, as was the case before mkIII.</p> + + <p>Thanks to Scott Long and Søren Schmidt for their + participation in the integration work.</p> + </body> + </project> + + <project cat='vendor'> + <title>twa driver</title> + + <contact> + <person> + <name> + <given>Vinod</given> + + <common>Kashyap</common> + </name> + + <email>vkashyap at amcc.com</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/twa/"> + source code</url> + + <url + href="http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/modules/twa/"> + source code</url> + </links> + + <body> + <p>A newly re-architected twa(4) driver was committed to 6 -CURRENT + on 04/12/2005. Highlights of this release are:</p> + + <ol> + <li>The driver has been re-architected to use a "Common Layer" + (all tw_cl* files), which is a consolidation of all + OS-independent parts of the driver. The FreeBSD OS specific + portions of the driver go into an "OS Layer" (all tw_osl* files). + This re-architecture is to achieve better maintainability, + consistency of behavior across OS's, and better portability to + new OS's (drivers for new OS's can be written by just adding an + OS Layer that's specific to the OS, by complying to a "Common + Layer Programming Interface (CLPI)" API. If there's interest in + porting the 3ware driver to any other OS, you may contact ctchu + at amcc.com to get a copy of the CLPI specifications.</li> + + <li>The driver takes advantage of multiple processors. It does + not need to be Giant protected anymore.</li> + + <li>The driver has a new firmware image bundled, the new features + of which include Online Capacity Expansion and multi-lun support, + among others. More details about 3ware's 9.2 release can be found + here: + <a + href="http://www.3ware.com/download/Escalade9000Series/9.2/9.2_Release_Notes_Web.pdf"> + http://www.3ware.com/download/Escalade9000Series/9.2/9.2_Release_Notes_Web.pdf</a> + </li> + </ol> + </body> + </project> + + <project cat='net'> + <title>IPv6 Support for IPFW</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://lists.freebsd.org/pipermail/cvs-all/2005-April/116671.html" /> + </links> + + <body> + <p>In April 18th, I committed support for IPv6 to IPFW. This + support was written by two student of Luigi's, Mariano Tortoriello + and Raffaele De Lorenzo. I updated it to use PFIL_HOOKS and fixed a + few minor issues. As of this commit, IP6FW should be considered + deprecated in favor of IPFW. It should be possible to MFC this + change to 5.x, but that is not currently planned.</p> + </body> + + <help> + <task>Testing.</task> + + <task>IP6FW to IPFW migration guide.</task> + + <task>Patches relative to 5-STABLE.</task> + </help> + </project> + + <project cat='net'> + <title>Removable interface improvements.</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~brooks/pubs/eurobsdcon2004/" /> + + <url href="http://www.freebsd.org/projects/dingo/" /> + </links> + + <body> + <p>This project is an attempt to clean up handling of network + interfaces in order to allow interfaces to be removed reliably. + Current problems include panics if Dummynet is delaying packets to + an interface when it is removed.</p> + + <p>I am currently working to remove struct ifnet's from device + driver structures to allow them to be managed properly upon device + removal. I believe I have removed all known instances of casting a + struct ifnet pointer to something else (except that that are just + magic values and not real struct ifnets.) I will begin committing + these changes to the tree shortly and will then add a new function + if_alloc() that will allocate struct ifnets. if_detach() will be + modified to destroy them.</p> + </body> + </project> + + <project cat='kern'> + <title>cpufreq</title> + + <contact> + <person> + <name> + <given>Nate</given> + + <common>Lawson</common> + </name> + + <email>njl</email> + </person> + </contact> + + <links> + <url + href="http://www.freebsd.org/cgi/man.cgi?query=cpufreq&manpath=FreeBSD+6.0-current&format=html"> + cpufreq man page</url> + </links> + + <body> + <p>The cpufreq project was committed to 6-CURRENT in early February + and has undergone bugfixes and updates. It will soon be MFCd to + 5-STABLE.</p> + + <p>The cpufreq driver provides a unified kernel and user interface + to CPU frequency control drivers. It combines multiple drivers + offering different settings into a single interface of all possible + levels. Users can access this interface directly via sysctl(8), by + indicating to power_profile that it should switch settings when the + AC line state changes, or by using powerd(8).</p> + + <p>For example, an absolute driver offering frequencies of 1000 Mhz + and 750 Mhz combined with a relative driver offering settings of + 100% and 50% would result in cpufreq providing levels of 1000, 750, + 500, and 375 Mhz.</p> + + <p>Colin Percival helped with powerd(8), which provides automatic + control of CPU frequencies. The adaptive mode is especially + interesting since it attempts to respond to changes in system load + while reducing power consumption.</p> + + <p>Current hardware drivers include acpi_perf (ACPI CPU performance + states), est (Intel Enhanced SpeedStep for Pentium-M), ichss + (Intel's original SpeedStep for ICH), and powernow (AMD Powernow! + K7 and K8 support). Other drivers for relative hardware include + acpi_throttle (ACPI CPU throttling) and p4tcc (Pentium 4 Thermal + Control Circuitry)</p> + + <p>Thanks to Bruno Ducrot for the powernow driver, Colin Percival + for the est driver, and the many testers who have sent in + feedback.</p> + </body> + + <help> + <task>We'd appreciate someone with a Transmeta CPU converting the + existing longrun driver to the cpufreq framework. It would also be + good if someone wrote a VIA Longhaul driver. See the Linux + arch/i386/kernel/cpu/cpufreq directory for examples.</task> + + <task>Various other architectures, including ARM, have CPU power + control that could be implemented as a cpufreq driver.</task> + + <task>The powerd(8) algorithm is rather simple and we'd appreciate + more help in testing it and alternative algorithms with various + workloads. The -v flag causes powerd to report frequency + transitions and print a summary of total energy used upon + termination. This should help testers profile their + algorithms.</task> + </help> + </project> + + <project cat='net'> + <title>Move ARP out of routing table</title> + + <contact> + <person> + <name> + <given>Qing</given> + + <common>Li</common> + </name> + + <email>qingli@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~qingli/">containing the + patch</url> + </links> + + <body> + <p>I have finished the basic functionality for both IPv4 and IPv6. + The userland utilities ("arp" and "ndp") have been updated. I have + tested the changes with "make buildworld". I have been testing the + new code in a production environment and things appear to be + stable. Gleb Smirnoff (glebius@FreeBSD.org) has provided review + comments and I have incorporated these feedback into the patch. I + have discussed the IPv6 changes with two of the core KAME + developers during the last IETF meeting in March 2005. They + indicated that these changes may result in divergence from the KAME + project but that is not necessarily a bad thing.</p> + </body> + + <help> + <task>I am waiting for review feedback from my mentor Andre. I need + locking experts to help me fix my giant-lock shortcut. I am hoping + to send out the code for wider review soon.</task> + </help> + </project> + + <project cat='net'> + <title>Support for telephone hardware (aka Zaptel)</title> + + <contact> + <person> + <name> + <given>Maxim</given> + + <common>Sobolev</common> + </name> + + <email>sobomax@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Oleksandr</given> + + <common>Tymoshenko</common> + </name> + + <email>gonzo@pbxpress.com</email> + </person> + + <person> + <name> + <given>Max</given> + + <common>Khon</common> + </name> + + <email>fjoe@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://www.digium.com/index.php?menu=hardware_products" /> + </links> + + <body> + <p>During the last 2 months lot of progress has been made. Existing + support for TDM400 (FXO/FXS) has been significantly improved. + Drivers for PRI and BRI cards have been added and now should be + considered beta-quality.</p> + </body> + + <help> + <task>More testing of PRI/BRI drivers.</task> + + <task>Add support for channelized DS3 card(s).</task> + </help> + </project> + + <project cat='ports'> + <title>FreshPorts</title> + + <contact> + <person> + <name> + <given>Dan</given> + + <common>Langille</common> + </name> + + <email>dan@langille.org</email> + </person> + </contact> + + <links> + <url href="http://www.freshports.org/">FreshPorts</url> + </links> + + <body> + <p>This is the first status report for FreshPorts. FreshPorts + started in early 2000 and now contains over 170,000 commits. + FreshPorts is primarily concerned with port commits, but actually + processes and records all commits to the FreeBSD source tree. Its + sister site, + <a href="http://www.freshsource.org/">FreshSource</a> + + uses the same database as FreshPorts but has a wider reporting + scope. In recent months, FreshPorts has been enhanced to process + and include + <a href="http://www.vuxml.org/freebsd/">VuXML</a> + + information. In addition, RESTRICTED and NO_CDROM have been added + to list of things that FreshPorts keeps track of. For unmaintained + ports, we recently added this message: + <p> + <em>There is no maintainer for this port. + <br /> + + Any concerns regarding this port should be directed to the + FreeBSD Ports mailing list via ports@FreeBSD.org</em> + </p> + + FreshPorts, with direct and indirect support from the FreeBSD + community, continues to evolve and to provide a great tool for + users and developers alike.</p> + </body> + + <help> + <task>Provide a copy/paste method for updating watch lists</task> + + <task>improvement of query times for "People watching this port, + also watch"</task> + + <task>pagination of commits within a port</task> + + <task>pagination of watch lists</task> + + <task>create an RSS feed for individual watch lists</task> + </help> + </project> + + <project cat='misc'> + <title>BSDCan</title> + + <contact> + <person> + <name> + <given>Dan</given> + + <common>Langille</common> + </name> + + <email>dan@langille.org</email> + </person> + </contact> + + <links> + <url href="http://www.bsdcan.org/" /> + </links> + + <body> + <p>BSDCan made a strong debut in + <a href="http://www.bsdcan.org/2004/">2004</a> + + . The favorable reception gave us a strong incentive for + <a href="http://www.bsdcan.org/2005/">2005</a> + + . We have been rewarded with a very interesting + <a href="http://www.bsdcan.org/2005/schedule.php">program</a> + + and a higher rate of registrations. Percentage-wise, we have more + Europeans than last year as they have decided that the trip across + the Atlantic is worth taking. We know they won't be disappointed. + See you at BSDCan 2005!</p> + </body> + + <help> + <task>volunteers needed for the conference</task> + </help> + </project> + + <project cat='ports'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/ports/">The FreeBSD ports + collection</url> + + <url href="http://portsmon.firepipe.net/index.html">FreeBSD ports + monitoring system</url> + + <url href="http://www.freebsd.org/portmgr/index.html">The FreeBSD + Ports Management Team</url> + </links> + + <body> + <p>As this report was being written, the 5.4 release was + ongoing.</p> + + <p>A new charter for the Ports Management (portmgr) team was + approved by core and has been posted at the URL above. In addition, + two other new pages describe the policies of the team, and the + range of QA activities both during and between releases.</p> + + <p>Due to being absent from email discussions for some time, Oliver + Eikemeier (eik) was moved to non-voting status on portmgr.</p> + + <p>We have added several new and very active committers recently; + this is helping us to keep the PR count low even with the large + numbers of new ports that have been added.</p> + + <p>Several more iterations of infrastructure changes have been + tested on the cluster and committed; see /usr/ports/CHANGES for + details.</p> + + <p>Updates have occurred to x.org, GNOME, KDE, and perl.</p> + + <p>There have been some updates to the Porter's Handbook, but more + sections are still in need of updates to include recent changes in + practices.</p> + + <p>The ports collection now contains almost 12,750 ports.</p> + </body> + + <help> + <task>Further progress has been made in cracking down on ports that + install files outside the approved directories and/or do not + deinstall cleanly (see "Extra files not listed in PLIST" on + <a href="http://pointyhat.freebsd.org/errorlogs/">pointyhat</a> + + ) and this will remain a focus area. We appreciate everyone who has + sent in PRs or committed fixes.</task> + + <task>Demand for new features and revisions for bsd.port.mk is + still very high and the portmgr team is trying to work through them + all.</task> + + <task>We still have a large number of PRs that have been assigned + to committers for some time (in fact, they constitute the + majority). One goal of portmgr in the coming months is to try to + reduce this number, and we would like to ask our committers to help + us out as much as possible.</task> + </help> + </project> + + <project cat='arch'> + <title>PowerPC Port</title> + + <contact> + <person> + <name> + <given>Peter</given> + + <common>Grehan</common> + </name> + + <email>grehan@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Progress continues. X.Org 6.8.1 server has been up and running + on a number of different Macs, and the work is being merged into + 6.8.2. There have been successful installs on Mac Minis</p> + </body> + </project> + + <project cat='vendor'> + <title>OpenBSD packet filter - pf</title> + + <contact> + <person> + <name> + <given>Max</given> + + <common>Laier</common> + </name> + + <email>mlaier@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://pf4freebsd.love2party.net/">pf4FreeBSD + Homepage</url> + + <url href="http://people.freebsd.org/~mlaier/pf37/">pf 3.7 patches</url> + </links> + + <body> + <p>OpenBSD is about to release + <a href="http://www.openbsd.org/37.html">version 3.7</a> + + . There are + <a href="http://people.freebsd.org/~mlaier/pf37/">patches</a> + + available to catch up with the development done in OpenBSD 3.6 and + 3.7. These patches are in an early stage, but ready for testing, + please help.</p> + + <p>Otherwise there was not much activity on pf, as it already is + quite stable. Other work, such as CARP and if_bridge are having + impact on pf in FreeBSD however, please see the respective + reports.</p> + </body> + + <help> + <task>Alpha/Betatesting of the 3.7 import</task> + + <task>Testing with if_bridge</task> + </help> + </project> + + <project cat='bin'> + <title>libthread</title> + + <contact> + <person> + <name> + <given>David</given> + + <common>Xu</common> + </name> + + <email>davidxu@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>libthread is a pure 1:1 threading library, it had stayed in my + perforce branch for a long time, recent it was imported into source + tree and replaced libthr. The purpose of the work is to improve 1:1 + threading on FreeBSD, the library is designed in mind that simplest + is best, currently it can run almost all of the applications + libpthread can run, but gives you better SMP performance. The + library size is smaller than libpthread.</p> + + <p>Currently it supports i386, AMD64, sparc64 and ia64 and may + support alpha, powerpc and arm. I didn't do many tests on sparc64 + and ia64, I only tested it on FreeBSD cluster machines. For i386, I + always used LDT, but know that Peter committed GDT code, and now + there is no 8191 threads limitation anymore.</p> + + <p>libthread_db was updated to support debugging the new libthr. It + is an assistant library used by gdb to debug threaded process, that + understands internal detail of thread libraries. I have improved it + a bit to support event reports for libthr, currently it can report + thread creation and death events. That means a thread that was + created and died will be reported to the user regardless if you are + tracking it or not.</p> + </body> + + <help> + <task>I am working on thread creation performance, currently it + needs considerable number of libc functions and syscalls to create + a thread, I would like to introduce a syscall to create a thread in + atomically. That means one syscall will setup thread entry, tls, and + signal mask and PTHREAD_SCOPE_PROCESS/SYSTEM; in future maybe even + CPU affinity masks, when userland entry code is executed, the + thread is already fully setup.</task> + + <task>Process shareable synchronization objects. In Current FreeBSD + does not support this specification. The idea about the shareable + mutex and others is like other systems did, one can use mmap() to + create a shared memory page, and put a pthread synchronization + object in the page, multiple processes use the shared object to + control resource access. I am not working on it, if someone is + interested, please let me know.</task> + </help> + </project> + + <project cat='kern'> + <title>Coverity Code Analysis</title> + + <contact> + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.coverity.com/" /> + </links> + + <body> + <p>There has been an ongoing effort to review the kernel source + code using Coverity's source code analysis tools + (http://www.coverity.com). These tools check for a variety of + problems such as null pointer dereference, use-after-free of + allocated variables, invalid array references, etc. This work is a + joint project between FreeBSD and Coverity.</p> + + <p>Two passes have been completed over the 6-current kernel source + code base and all significant problems have been corrected. These + runs were done in February and March of this year. A few reports of + minor problems await response from outside groups and will be + resolved in time for the first 6.x release. Another analysis run + over the kernel will happen soon. We are looking for a way to use + these tools on a regular basis as they have been helpful in + improving the code base.</p> + + <p>Thanks to Coverity for their help and especially Ted Unangst. + Several developers have been especially helpful in resolving + reports: Poul-Henning Kamp, David Schultz, Pawel Jakub Dawidek, + George V. Neville-Neil, and Matthew Dodd.</p> + </body> + </project> + + <project cat='net'> + <title>Wireless Networking Support</title> + + <contact> + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Several new drivers by by Damien Bergamini were brought into the + tree: iwi, ipw, ral, and ural.</p> + + <p>WPA-PSK support for the ndis driver was contributed by Arvind + Srinivasa.</p> + + <p>A new tx rate control algorithm for the ath driver was + contributed by John Bicket. It will become the default algorithm + shortly.</p> + + <p>Work on multi-bss support is going on outside the cvs tree. A + presentation on this work will be given at BSDCan 2005 and the + slides for the talk will be made available after.</p> + </body> + + <help> + <task>Drivers other than ath and ndis need updates to support the + new security protocols.</task> + + <task>hostapd needs work to support the IAPP and 802.11i + preauthentication protocols (these are simple conversions of + existing Linux code).</task> + + <task>The OpenBSD dhclient program has been ported but needs a + developer that will maintain it once it is brought into cvs.</task> + </help> + </project> + + <project cat='kern'> + <title>Many subdirs for UFS</title> + + <contact> + <person> + <name> + <given>David</given> + + <common>Malone</common> + </name> + + <email>dwmalone@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://groups-beta.google.com/group/muc.lists.freebsd.fs/browse_frm/thread/a36d1143d695287e/40cad00cf2c0823b?hl=en#40cad00cf2c0823b"> + Thread on freebsd-fs</url> + </links> + + <body> + <p>I'm currently looking at the limit on the number of + subdirectories a directory can have in UFS. There is currently a + limit of 32K subdirectories because of the 16 bit link count field + in both struct stat and the on-disk inode format. The thread above + shows that dirhash provides acceptable performance for directories + with 100k subdirectories using a prototype patch. Two options for + allowing many subdirectories seem to exist: changing the link + counting scheme for directories and expanding the link count field. + The prototype patch implements the first scheme and there are plans + to investigate the second scheme (which may require an ABI + change).</p> + </body> + </project> + + <project cat='misc'> + <title>IMUNES - a FreeBSD based kernel-level network topology + emulator</title> + + <contact> + <person> + <name> + <given>Miljenko</given> + + <common>Mikuc</common> + </name> + + <email>miljenko@tel.fer.hr</email> + </person> + + <person> + <name> + <given>Marko</given> + + <common>Zec</common> + </name> + + <email>zec@tel.fer.hr</email> + </person> + </contact> + + <links> + <url href="http://www.imunes.net/" /> + </links> + + <body> + <p>IMUNES is a scalable kernel-level network topology emulator + based on FreeBSD. In IMUNES each virtual node operates on its + private instance of network stack state variables, such as routing + tables, interface addresses, sockets, ipfw rules etc. Most if not + all existing FreeBSD application binaries, including routing + protocol daemons such as quagga or XORP, can run unmodified within + the context of virtual nodes with no noticeable performance + penalty. Complex network topologies can be constructed by + connecting the virtual nodes through netgraph-based link-layer + paths. A GUI tool allows for simple and intuitive network topology + specification, deployment and management. The current version of + IMUNES is based on FreeBSD 4.11-RELEASE and supports IPv4.</p> + </body> + </project> + + <project cat='arch'> + <title>XenFreeBSD - FreeBSD on Xen</title> + + <contact> + <person> + <name> + <given>Kip</given> + + <common>Macy</common> + </name> + + <email>kmacy@fsmware.com</email> + </person> + </contact> + + <links> + <url href="http://www.cl.cam.ac.uk/Research/SRG/netos/xen/">Xen + project page</url> + + <url href="http://xen.bkbits.net/">Xen changeset logs</url> + </links> + + <body> + <p>FreeBSD 5.3 runs on the stable and the development branches of + xen and is now checked into both trees. Over the next couple of + weeks I will be adding improvements for better batching of page + table updates and SMP support.</p> + </body> + + <help> + <task>FreeBSD support for running as Domain 0, i.e. running as the + hosting operating system.</task> + + <task>FreeBSD support for VM checkpoint and migration.</task> + </help> + </project> + + <project cat='net'> + <title>Dingo</title> + + <contact> + <person> + <name> + <given>George</given> + + <common>Neville-Neil</common> + </name> + + <email>gnn@neville-neil.com</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~gnn/Dingo/notebook/60.html"> + Project page (out of date)</url> + + <url href="http://zoo.unixdaemons.com/index.php?blog=7">Blog + covering test framework</url> + </links> + + <body> + <p>On the protocol conformance tool I have finally made some + progress getting a scriptable packet library using libnet, and + SWIG. This will hopefully become a port that can then be used to do + conformance testing on protocol stack changes. Qing Li has + separately taken up the ARP rewrite and that will be taken out of + the Dingo project pages.</p> + </body> + + <help> + <task>Many :-)</task> + </help> + </project> + + <project cat='kern'> + <title>Interrupt Latency</title> + + <contact> + <person> + <name> + <given>Warner</given> + + <common>Losh</common> + </name> + + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>I've setup a test system to measure interrupt latency on FreeBSD + 5.3 and current. So far I've measured the baseline latency for a + 300MHz embedded cyrix based single board computer. I've tried a + number of different strategies to optimize the interrupt path. Most + of these strategies resulted in some improvement of the time it + takes to get from the start of the interrupt servicing to the + driver's ISR. These improvements turned out to be about 1-2% of the + processing times on this single board computer, but a wash on + faster machines. However, the time between when the interrupt + should happen, and when FreeBSD starts to service the interrupt is + the dominant factor in these measurements. Despite the fact that + these are fast interrupt handlers (so the scheduler is out of the + loop), I routinely see average latencies of 18us, with large + variations (on the order of 5us standard deviation).</p> + </body> + + <help> + <task>I need to measure the latencies with 4.x and current to + characterize the differences more precisely. I'm especially + interested in the effects on interrupt latency that the elimination + of mixed mode will cause.</task> + + <task>I need to characterize different parts of our ISR routines to + see if some of the variation I've seen so far can be reduced by + improved coding techniques.</task> + + <task>I need to re-run my tests with 5.4 and summarize my results + in a paper.</task> + </help> + </project> + + <project cat='kern'> + <title>Infrastructure Cleanup</title> + + <contact> + <person> + <name> + <given>Warner</given> + + <common>Losh</common> + </name> + + <email>imp@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Takahashi</given> + + <common>Yoshihiro</common> + </name> + + <email>nyan@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Unglamorous cleanup of the code base continues. The focus of + recent efforts have been to reduce the number of machine #ifdefs + that are in the machine independent code. In addition, we're also + trying to increase code sharing between pc98 and i386 ports and + reduce the number of #ifdef PC98 instances in the tree.</p> + + <p>In addition, a number of cleanup tasks are underway for + different parts of the kernel that are more complicated than + necessary. Recently, the pccard code's allocation routines were + simplified to reassign ownership of resources more directly than + before. The search is on for other areas that can benefit from + cleanup.</p> + </body> + + <help> + <task>On pc98, there's no such thing as an ISA bus. It is desirable + to move to having cbus appear in the probe messages. This would + also allow for additional segregation of pc98 specific code in the + drivers and eliminate many ifdefs. Ideally, isa and cbus would + share a common newbus ancestor class so their similarities can be + exploited (they both have PNPBIOS enumeration methods, for + example).</task> + + <task>cbus devices can have complicated resources. There's support + for vectors of resources. Yet there's no support for populating a + vector of resources from the plug and play information. Doing so + would help the complex world of pc98 a lot, and the odd edge cases + in i386 (floppy, ata) a little.</task> + + <task>The hints mechanism provides a way to associate hardware with + drivers and resource that would otherwise be completely unknown to + the system. A refinement in the hints mechanism to allow matching + of driver instances to resources is desirable. This would allow one + to hardwire sio0 to 0x2f8, even when the serial device in the plug + and play resource list (or acpi resource list) is listed second. A + further refinement could also be wiring sio0 to "port B" as defined + by acpi or some other enumeration method. Chances are good that + these seemingly related concepts may need separate implementations + due to the decision points for unit assignment.</task> + + <task>Pccard, cardbus and usb probe their devices after interrupts + are enabled. It would be desirable to hook into new kernel APIs to + allow the mounting of root to be put off until those systems know + that they are done with their initial probe of the devices present + at boot.</task> + </help> + </project> + + <project cat='misc'> + <title>FreeBSD Security Officer and Security Team</title> + + <contact> + <person> + <name> + <given>Security</given> + + <common>Officer</common> + </name> + + <email>security-officer@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Security</given> + + <common>Team</common> + </name> + + <email>security-team@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/security/" /> + + <url + href="http://www.freebsd.org/administration.html#t-secteam" /> + + <url href="http://vuxml.freebsd.org/" /> + </links> + + <body> + <p>In January 2005, Warner Losh (Security Officer Emeritus) stepped + down from the FreeBSD Security Team in order to better devote his + time to other projects. In March, Colin Percival was named as a + second Deputy Security Officer, joining Dag-Erling Smørgrav in + that position. The current Security Team membership is published on + the web site.</p> + + <p>So far in 2005, four security advisories have been issued + concerning problems in the base system of FreeBSD, three of which + were specific to FreeBSD. The Vulnerabilities and Exposures Markup + Language (VuXML) document has continued to be updated by the + Security Team and the Ports Committers documenting new + vulnerabilities in the FreeBSD Ports Collection. As of April 17, + 127 entries have been added in 2005 bringing the FreeBSD VuXML file + up to a total of 422 entries.</p> + + <p>In the past months both the + <a href="http://vuxml.FreeBSD.org/">VuXML web site</a> + + and the + <a href="http://www.FreshPorts.org/">FreshPorts</a> + + VuXML integration have been improved. The VuXML web site has had a + face lift and, among other things, each package now has a separate + web page which lists all documented vulnerabilities for the + particular package. + <a href="http://cve.mitre.org/">CVE</a> + + information is now also included directly on the VuXML web + site.</p> + + <p>Finally, the first few months of 2005 also saw FreeBSD 4.8 -- + the first release to be offered "extended support" -- reach its + designated End of Life. The currently supported releases are + FreeBSD 4.10, 4.11, and 5.3.</p> + </body> + </project> + + <project cat='proj'> + <title>FreeBSD Release Engineering</title> + + <contact> + <person> + <name> + <given>RE</given> + <common>Team</common> + </name> + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/releng" /> + </links> + + <body> + <p>FreeBSD 4.11, the final formal release of the 4.x series, was + released on 25 Jan 2005. Many thanks to the all of the developers + and users over the past 5 years who made it successful. While no + more releases are planned, the security team will continue to + support it through security update patches until 2007. Developers + are also free to commit bug fixes and low-risk features to the + RELENG_4 branch for the foreseeable future.</p> + <p>FreeBSD 5.4 is going through its final release candidate stages + and is expected to be released in late April. Its focus is mostly + bug fixes and minor feature and performance improvements, so it is + an excellent target for those looking to upgrade from previous + versions or to give FreeBSD a try for the first time. FreeBSD 5.5 + will be release in about 4-6 months after 5.4.</p> + <p>FreeBSD 6.0 is rapidly approaching also. In contrast to FreeBSD + 5.0, the goal is to take a more incremental approach to major + changes, and not wait for years to get as many features in as + possible. FreeBSD 6.0 will largely be an evolutionary change from + the 5.x series, with the largest changes centered around + multi-threading and streamlining the filesystem and device layers. + Feature freeze and code freeze for 6.0 are coming up in May and + June, and we hope to have 6.0 stable and ready for release in July + or August.</p> + <p>The release engineering team has also started doing monthly + informal snapshots of the 6-CURRENT and 5-STABLE trees. These are + intended to increase the exposure of new features and get more + users involved in testing and providing feedback. Snapshots can + be found at <a href="http://www.freebsd.org/snapshots"> + http://www.freebsd.org/snapshots</a>.</p> + </body> + </project> + + <project cat='net'> + <title>New Wireless Drivers</title> + + <contact> + <person> + <name> + <given>Damien</given> + + <common>Bergamini</common> + </name> + + <email>damien@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://ipw2100.sourceforge.net/firmware.php?fid=4" /> + + <url href="http://ralink.rapla.net/" /> + </links> + + <body> + <p>Four new wireless drivers were imported:</p> + + <p> + <em>ipw</em> + + : driver for Intel PRO/Wireless 2100 adapters (MiniPCI). + <br /> + + <em>iwi</em> + + : driver for Intel PRO/Wireless 2200BG/2225BG/2915ABG adapters (PCI + or MiniPCI). + <br /> + + <em>ral</em> + + : driver for Ralink RT2500 wireless adapters (PCI or CardBus). + <br /> + + <em>ural</em> + + : driver for Ralink RT2500USB wireless USB 2.0 adapters.</p> + + <p>The ipw and iwi drivers require firmwares to operate. + <br /> + + These firmwares can't be redistributed with the base system due to + license restrictions. + <br /> + + See firmware licensing terms here: + <a href="http://ipw2100.sourceforge.net/firmware.php?fid=4"> + http://ipw2100.sourceforge.net/firmware.php?fid=4</a> + + . + <br /> + </p> + + <p>Ports which include the firmware images as well as the firmware + loader are being worked on. + <br /> + + A list of adapters supported by ral and ural can be found here: + <a href="http://ralink.rapla.net/">http://ralink.rapla.net/</a> + + .</p> + </body> + + <help> + <task>Create ports for ipw and iwi firmwares.</task> + + <task>Add IBSS support to iwi.</task> + + <task>Add WPA (802.11i) support to ipw and iwi.</task> + + <task>Add hardware encryption (WEP, TKIP and CCMP) support in ral + and ural.</task> + + <task>Add automatic rate adaptation support to ural.</task> + </help> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2005-03-2005-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2005-03-2005-06.xml new file mode 100644 index 0000000000..2c8d5cb64b --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2005-03-2005-06.xml @@ -0,0 +1,2173 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<report> + <date> + <month>March-June</month> + + <year>2005</year> + </date> + + <section> + <title>Introduction</title> + + <p>The second quarter of 2005 has again been very exciting. The + BSDCan and MeetBSD conferences were both very interesting and the + sources of very good times. I highly recommend attending them again + next year.</p> + + <p>The Google Summer of Code project has also generated quite a bit + of excitement. FreeBSD has been granted 19 funded mentorship spots, + the fourth most of all of participating organizations. Projects being + worked on range from UFS Journaling to porting the new BSD Installer + to redesigning the venerable www.FreeBSD.org website. We are quite + pleased to be working with so many talented students, and eagerly + await the results of their work. More information and status can be + found at the Wiki site at + <a href="http://wiki.freebsd.org/moin.cgi/SummerOfCode2005"> + http://wiki.freebsd.org/moin.cgi/SummerOfCode2005</a> + + .</p> + + <p>The FreeBSD 6.0 release cycle is also starting up. The purpose of + quickly jumping from 5.x to 6.0 is to reduce the amount of transition + pain that most users and developers felt when switching from 4-STABLE + to 5.x. 6.0 will feature improved performance and stability over 5.x, + experimental PowerPC support, and many new WiFi/802.11 features. The + 5.x series will continue for at least one more release this fall, and + will then be supported by the security team for at least 2 years + after that. We encourage everyone to give the 6.0-BETA snapshots a + try and help us make it ready for production. We hope to release + FreeBSD 6.0 by the end of August.</p> + + <p>Thanks again to everyone who submitted reports, and thanks to Max + Laier for running the show and putting the reports together. Enjoy + reading!</p> + </section> + + <category> + <name>soc</name> + + <description>Google summer of code</description> + </category> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>doc</name> + + <description>Documentation</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>net</name> + + <description>Network infrastructure</description> + </category> + + <category> + <name>bin</name> + + <description>Userland programs</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <category> + <name>vendor</name> + + <description>Vendor / 3rd Party Software</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='misc'> + <title>BSDCan</title> + + <contact> + <person> + <name> + <given>Dan</given> + + <common>Langille</common> + </name> + + <email>dan@langille.org</email> + </person> + </contact> + + <links> + <url href="http://www.bsdcan.org/2005/" /> + </links> + + <body> + <p>The second annual + <a href="http://www.bsdcan.org">BSDCan</a> + + conference was well presented, well attended, and everyone went + away with good stories to tell. If you know anything that attended, + get them to tell you what they did, who they met with, and talks + they listened to.</p> + + <p>We had 197 people from 15 different countries. That's a strong + turnout by any definition.</p> + + <p>We'll be adding more people to the program committee for BSDCan + 2006. This job involves prodding and poking people from your + respective projects. You get them to submit papers. There are a lot + of very interesting projects out there and not all of them submit a + paper.</p> + + <p>If you know someone doing interesting work, please let me know + and urge them to start thinking about BSDCan 2006.</p> + </body> + </project> + + <project cat='soc'> + <title>Integrate the BSD Installer into FreeBSD</title> + + <contact> + <person> + <name> + <given>Andrew</given> + + <common>Turner</common> + </name> + + <email>soc-andrew@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.bsdinstaller.org">The BSD Installer</url> + + <url href="http://wiki.freebsd.org/moin.cgi/BSDInstaller">BSD + Installer Wiki page</url> + + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2005/bsdinstaller"> + BSD Installer Perforce tree</url> + </links> + + <body> + <p>Progress towards integrating the BSD Installer for Google's + Summer of Code is coming along nicely. The installation CD will + boot to multi-user mode and run both the front and back ends. It + can then partition a hard drive, install the base distribution and + make the disk bootable.</p> + </body> + + <help> + <task>Test in non-i386</task> + + <task>Investigate installing from other media</task> + + <task>Many more tasks</task> + </help> + </project> + + <project cat='ports'> + <title>FreshPorts</title> + + <contact> + <person> + <name> + <given>Dan</given> + + <common>Langille</common> + </name> + + <email>dan@langille.org</email> + </person> + </contact> + + <links> + <url href="http://www.freshports.org/" /> + </links> + + <body> + <p>The following new features have been added to FreshPorts:</p> + + <ul> + <li> + <a href="http://www.freshports.org/ports- deprecated.php"> + Deprecated Ports</a> + </li> + + <li> + <a href="http://www.freshports.org/ports- expired.php">Expired + Ports</a> + </li> + + <li> + <a href="http://www.freshports.org/ports-expiration- date.php"> + Ports Set To Expire</a> + </li> + + <li> + <a + href="http://www.freshports.org/phorum/read.php?f=1&i=1021&t=1021#repl y_1021"> + Display relevant entries from ports/UPDATING on your watch + list</a> + </li> + </ul> + </body> + + <help> + <task>I've noticed that FreshPorts is incorrectly reporting + vulnerabilities under a + <a + href="http://www.freshports.org/phorum/read.php?f=1&i=1025&t=1025"> + very specific situation</a> + + . The fix is sitting in BETA, waiting to be moved to + production.</task> + + <task>I've been working on added Last-Modified to the headers. At + present, there are none. Most of the pages on the BETA website have + been completed. I need to move this to production soon.</task> + + <task>Customized news feeds are in the works. You'll be able to + create a news feed for each of your watch lists. This work is + contingent upon finishing the Last-Modified headers.</task> + </help> + </project> + + <project cat='proj'> + <title>Fundraising - TCP & IP Routing Optimization</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~andre/tcpoptimization.html" /> + </links> + + <body> + <p>The TCP code in FreeBSD has evolved significantly since the fork + from 4.4BSD-Lite2 in 1994 primarily due to new features and + refinements of the TCP specifications.</p> + + <p>The TCP code now needs a general overhaul, streamlining and + cleanup to make it easily comprehensible, maintainable and + extensible again. In addition there are many little optimizations + that can be done during such an operation, propelling FreeBSD back + at the top of the best performing TCP/IP stacks again, a position + it has held for the longest time in the 90's.</p> + + <p>This overhaul is a very involved and delicate matter and needs + extensive formal and actual testing to ensure no regressions + compared to the current code. The effort needed for this work is + about three man-month of fully focused and dedicated time. To get + it done I need funding to take time off my day job and to dedicate + me to FreeBSD work much the way PHK did with his buffer cache and + vnode rework projects.</p> + + <p>I've got the opportunity to work up to three man-month + exclusively full-time on FreeBSD during the second half of 2005. + That means up to 720 hours of full-steam coding (at 60 hours/week)! + I will work as much time as the fundraise provides.</p> + + <p>I need to raise enough money for each month from donations from + the FreeBSD community to cover my fixed cost of living, office and + associated overhead. These fixed cost amount to US$6,300/month + (EUR5,200 or CHF8,000). Yes, Switzerland is not the cheapest place + to live. :)</p> + + <p>A detailed description of the tasks involved and the code I will + write is on my FreeBSD website; Follow the link above.</p> + </body> + + <help> + <task>Raise enough money to get all the almost finished TCP and IP + code into the tree.</task> + </help> + </project> + + <project cat='kern'> + <title>CPU Cache Prefetching</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~andre/tcpoptimization.html" /> + + <url + href="http://www.nrg4u.com/freebsd/tcp_reass+prefetch-20041216.patch" /> + </links> + + <body> + <p>Modern CPU's can only perform to their maximum if their working + code is in fast L1-3 cache memory instead of the bulk main memory. + All of today's CPU's support certain L1-3 cache prefetching + instructions which cause data to be retrieved from main memory to + the cache ahead of the time that it is already in place when it is + eventually accessed by the CPU.</p> + + <p>CPU Cache Prefetching however is not a silver bullet and has to + be used with extreme care and only in very specific places to be + beneficial. Incorrect usage can lead to massive cache pollution and + a drop in effective performance. Correct and very carefully usage + on the other can lead to drastic performance increases in common + operations.</p> + + <p>In the linked patch CPU cache prefetching has been used to + prefetch the packet header (OSI layer 2 to 4) into the CPU caches + right after entering into the network stack. This avoids a complete + CPU stall on the first access to the packet header because packets + get DMA'd into main memory and thus never are already pre-cache in + the CPU caches. A second use in the patch is in the TCP input code + to prefetch the entire struct tcpcb which is very large and used + with a very high probability. Use in both of these places show a + very significant performance gain but not yet fully quantified.</p> + + <p>The final patch will include documentation and a guide to + evaluate and assess the use of CPU cache prefetch instructions in + the kernel.</p> + </body> + + <help> + <task>Need funding, see "Fundraising - TCP & IP Routing + Optimization".</task> + </help> + </project> + + <project cat='net'> + <title>TCP Reassembly Rewrite and Optimization</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~andre/tcpoptimization.html" /> + + <url + href="http://www.nrg4u.com/freebsd/tcp_reass-20041213.patch" /> + + <url + href="http://lists.freebsd.org/pipermail/freebsd-net/2004-December/005918.html" /> + </links> + + <body> + <p>Currently TCP segment reassembly is implemented as a linked list + of segments. With today's high bandwidth links and large + bandwidth*delay products this doesn't scale and perform well.</p> + + <p>The rewrite optimizes a large number of operational aspects of + the segments reassembly process. For example it is very likely that + the just arrived segment attaches to the end of the reassembly + queue, so we check that first. Second we check if it is the missing + segment or alternatively attaches to the start of the reassembly + queue. Third consecutive segments are merged together (logically) + and are skipped over in one jump for linear searches instead of + each segment at a time.</p> + + <p>Further optimizations prototyped merge consecutive segments on + the mbuf level instead of only logically. This is expected to give + another significant performance gain. The new reassembly queue is + tracking all holes in the queue and it may be beneficial to + integrate this with the scratch pad of SACK in the future.</p> + + <p>Andrew Gallatin was able to get 3.7Gb/sec TCP performance on + dual-2Gbit Myrinet cards with severe packet reordering (due to a + firmware bug) with the new TCP reassembly code. See second + link.</p> + </body> + + <help> + <task>Need funding, see "Fundraising - TCP & IP Routing + Optimization".</task> + </help> + </project> + + <project cat='net'> + <title>TTCPv2: Transactional TCP version 2</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~andre/tcpoptimization.html" /> + + <url + href="http://lists.freebsd.org/pipermail/cvs-all/2004-November/089939.html" /> + </links> + + <body> + <p>The old TTCP according to RFC1644 was insecure, intrusive, + complicated and has been removed from FreeBSD >= 5.3. Although + the idea and semantics behind it are still sound and valid.</p> + + <p>The rewrite uses a much easier and more secure system with 24bit + long client and server cookies which are transported in the TCP + options. Client cookies protect against various kinds of blind + injection attacks and can be used as well to generally secure TCP + sessions (for BGP for example). Server cookies are only exchanged + during the SYN-SYN/ACK phase and allow a server to ensure that it + has communicated with this particular client before. The first + connection is always performing a 3WHS and assigning a server + cookie to a client. Subsequent connections can send the cookie back + to the server and short-cut the 3WHS to SYN->OPEN on the + server.</p> + + <p>TTCPv2 is fully configurable per-socket via the setsockopt() + system call. Clients and server not capable of TTCPv2 remain fully + compatible and just continue using the normal 3WHS without any + delay or other complications.</p> + + <p>Work on implementing TTCPv2 is done to 90% and expected to be + available by early February 2005. Writing the implementation + specification (RFC Draft) has just started.</p> + </body> + + <help> + <task>Need funding, see "Fundraising - TCP & IP Routing + Optimization".</task> + </help> + </project> + + <project cat='soc'> + <title>Network Interface API Cleanup</title> + + <contact> + <person> + <name> + <given>Anders</given> + + <common>Persson</common> + </name> + + <email>soc-anders@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://wiki.freebsd.org/moin.cgi/CleanupOfNetworkIterfaceApis" /> + </links> + + <body> + <p>The goal of this project is to review the network interface API + and try to remove references to kernel-only data structures by + removing the use of libkvm and instead rely on other interfaces to + provide information. If there are no adequate interfaces, they + would be created.</p> + + <p>Currently netstat is being reviewed and parts of it have been + modified to use sysctl rather than libkvm to provide the + information.</p> + + <p>A big thank you to Brooks Davis for mentoring :-)</p> + </body> + </project> + + <project cat='misc'> + <title>FreeBSD Security Officer and Security Team</title> + + <contact> + <person> + <name> + <given>Security</given> + + <common>Officer</common> + </name> + + <email>security-officer@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Security</given> + + <common>Team</common> + </name> + + <email>security-team@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/security/" /> + + <url + href="http://www.freebsd.org/administration.html#t-secteam" /> + + <url href="http://vuxml.freebsd.org/" /> + </links> + + <body> + <p>In May 2005, Remko Lodder joined the FreeBSD Security Team, + followed by Christian S.J. Peron in July 2005. In the same time + period, Gregory Shapiro and Josef El-Rayes resigned from the team + in order to devote their time to other projects. The current + Security Team membership is published on the web site.</p> + + <p>In the time since the last FreeBSD status report, twelve + security advisories have been issued concerning problems in the + base system of FreeBSD; of these, six problems were in + "contributed" code, while five problems were in code maintained + within FreeBSD. The Vulnerabilities and Exposures Markup Language + (VuXML) document has continued to be updated by the Security Team + and the Ports Committers documenting new vulnerabilities in the + FreeBSD Ports Collection; since the last status report, 97 new + entries have been added, bringing the total up to 519.</p> + + <p>The following FreeBSD releases are supported by the FreeBSD + Security Team: FreeBSD 4.10, FreeBSD 4.11, FreeBSD 5.3, and FreeBSD + 5.4. Their respective End of Life dates are listed on the web + site.</p> + </body> + </project> + + <project cat='net'> + <title>Dingo</title> + + <contact> + <person> + <name> + <given>Several</given> + </name> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/projects/dingo/">somewhat out of + date</url> + </links> + + <body> + <p>Currently trying to restart bits of the project. Cleaning up the + p4 branch. Recently more people have volunteered to help as well. + Brooks Davis has completed removing the ifnet from the softc.</p> + </body> + + <help> + <task>See the web page.</task> + </help> + </project> + + <project cat='doc'> + <title>The FreeBSD Dutch Documentation Project</title> + + <contact> + <person> + <name> + <given>Remko</given> + + <common>Lodder</common> + </name> + + <email>remko@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Siebrand</given> + + <common>Mazeland</common> + </name> + + <email>siebrand.mazeland@xs4all.nl</email> + </person> + + <person> + <name> + <given>Rene</given> + + <common>Ladan</common> + </name> + + <email>r.c.ladan@student.tue.nl</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/doc/nl/books/handbook">The Dutch + Handbook</url> + + <url href="http://www.evilcoder.org/content/section/6/39/">The + Dutch Project Site</url> + + <url href="http://www.evilcoder.org/freebsd_html/">The Dutch + Preview Documentation</url> + + <url href="http://www.evilcoder.org/freebsd/flyer.pdf">The Dutch + FreeBSD Flyer</url> + </links> + + <body> + <p>The FreeBSD Dutch Documentation Project is a ongoing project in + translating the english documentation to the Dutch language. + Currently we are almost done with the FreeBSD Handbook. Finishing + the Handbook is our first priority, and we could use your help. + Please contact Siebrand or myself if you want to helpout. After the + handbook we will focus on other documents as well, so feel free to + help us there as well</p> + </body> + + <help> + <task>FreeBSD Handbook translation. Finish the translation from + English to Dutch</task> + + <task>FreeBSD Handbook review. Finish the review of the translated + documents</task> + + <task>FreeBSD Articles. Start translating the articles from English + to the Dutch Language</task> + + <task>FreeBSD www. Start translating the website from English to + the Dutch Language</task> + + <task>The rest of the FreeBSD Documents. Start translating them + from English to the Dutch Language.</task> + </help> + </project> + + <project cat='kern'> + <title>Transparent support for superpages in the FreeBSD + Kernel</title> + + <contact> + <person> + <name> + <given>Alan L.</given> + + <common>Cox</common> + </name> + + <email>alc@cs.rice.edu</email> + </person> + + <person> + <name> + <given>Olivier</given> + + <common>Crameri</common> + </name> + + <email>olivier.crameri@epfl.ch</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>We are currently working on an updated implementation of + <a href="http://www.cs.rice.edu/~jnavarro/papers/osdi02.ps">Juan + Navarro's transparent support for superpages in FreeBSD.</a> + </p> + + <p>The idea is to take advantage of the architectural support for + big memory pages (superpages) by using a reservation mechanism + allowing us to transparently promote groups of base pages into + superpages and demote superpages into several smaller superpages or + base pages.</p> + + <p>The advantage of using superpages vs. base pages is to + significantly improve the TLB coverage of the physical memory, thus + improving the peformance by reducing the number of TLB misses.</p> + + <p>The modification of the FreeBSD kernel that we are working on + involves the replacement of the current list based page allocation + mechanism with a system using a buddy allocator to reserve groups + of pages for a memory object. The promotion and demotion of the + pages occur directly within the pmap module.</p> + + <p>The former implementation was supporting the alpha and IA64 + architectures. We are adding the support for amd64. We currently + have an almost complete implementation. Once completed we will make + a performance study with a particular emphasis on TLB and cache + misses.</p> + </body> + </project> + + <project cat='net'> + <title>Wireless Networking Support</title> + + <contact> + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@freebsd.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>A lot of bugs were fixed in preparation for the 6.0 release. 6.0 + will be the first release to include full WPA support (both + supplicant and authenticator).</p> + + <p>A presentation on the forthcoming multi-bss support was given at + BSDCan 2005. The slides from the talk are available at + <a href="http://www.freebsd.org/~sam/BSDCan2005.pdf"> + http://www.freebsd.org/~sam/BSDCan2005.pdf</a>. + + The plan is to commit this work to HEAD after 6.0 is released + which means the first release that will have it is 7.0.</p> + </body> + + <help> + <task>hostapd needs work to support the IAPP and 802.11i + preauthentication protocols (these are simple conversions of + existing Linux code).</task> + </help> + </project> + + <project cat='soc'> + <title>FreeSBIE toolkit integration</title> + + <contact> + <person> + <name> + <given>Dario</given> + + <common>Freni</common> + </name> + + <email>saturnero@freesbie.org</email> + </person> + </contact> + + <links> + <url href="http://www.freesbie.org">FreeSBIE main site</url> + + <url href="http://wiki.freebsd.org/moin.cgi/DarioFreni">My page + on FreeBSD wiki</url> + </links> + + <body> + <p>My Summer of Code project is reengineering and rewrite of + FreeSBIE toolkit, in order to include it in the source tree. Let's + call it FreeSBIE 2</p> + + <p>Before being accepted, I worked hard on the FreeSBIE 1 toolkit + to make it more flexible. It now supports amd64 and PowerPC + architecture. The built filesystem can now boot from almost every + media, from DVD to compact flash or hard disk. Also on i386 it is now + possible to include the BSD Installer on the livefs. We've received + reports that our toolkit is successfully used for the install CD of + <a href="http://www.pfsense.com">pfSense</a> + + and + <a href="http://www.pcbsd.org">PC-BSD</a> + + projects.</p> + + <p>My future goals are to make the toolkit even more flexible, + capable to build embedded images (like nanoBSD) or big Live-DVD + systems, depending on user's choice, to support all the + architectures supported by FreeBSD and to write a set of tools for + making a netboot server with a FreeSBIE image.</p> + </body> + </project> + + <project cat='arch'> + <title>PowerPC Port</title> + + <contact> + <person> + <name> + <given>Peter</given> + + <common>Grehan</common> + </name> + + <email>grehan@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/platforms/ppc.html">FreeBSD/PPC + Platform page.</url> + </links> + + <body> + <p>Florent Thoumie has updated the massively out-of-date platform + page. Work continues to creating a 6.0 release of the PowerPC + port.</p> + </body> + </project> + + <project cat='proj'> + <title>GEOM Gate rewrite</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + + <common>Dawidek</common> + </name> + + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://cvsweb.freebsd.org/src/sys/geom/gate/" /> + + <url href="http://cvsweb.freebsd.org/src/sbin/ggate/" /> + </links> + + <body> + <p>GGATE is a mechanism for exporting storage devices over the + network. It was reimplemented to be much faster and to handle + network failures better. The ggatec uses two threads now: sendtd, + which takes I/O request from the kernel and sends it to ggated; + recvtd, which receives finished requests and forwards them to the + kernel. The ggated uses three threads: recvtd, which receives I/O + requests from ggatec; disktd, which executes I/O requests (reads or + writes data); sendtd, which sends finished requests to ggatec. The + new ggate has been committed to 6.x.</p> + + <p>The work was sponsored by + <a href="http://www.wheel.pl">Wheel Sp. z o.o.</a> + </p> + </body> + </project> + + <project cat='soc'> + <title>gjournal</title> + + <contact> + <person> + <name> + <given>Ivan</given> + + <common>Voras</common> + </name> + + <email>ivoras@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/moin.cgi/gjournal">gjournal + wiki</url> + </links> + + <body> + <p>The schedule (as stated on the wiki page) is honoured, which + means that the development has started, but there's not enough code + for testing. Many details have been thought-out and the development + is ongoing.</p> + </body> + </project> + + <project cat='soc'> + <title>FreeBSD Summer of Code</title> + + <contact> + <person> + <name> + <given>Summer of Code</given> + + <common>Mentors</common> + </name> + + <email>soc-mentors@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://wiki.freebsd.org/moin.cgi/SummerOfCode2005" /> + </links> + + <body> + <p>Google has generously funded 19 students to spend the summer + working on FreeBSD related projects. Each student is working with + one or more mentors to learn about how open source software + development is done with FreeBSD. This development work is + happening in the Perforce repository as //depot/projects/soc2005. + This tree will soon be exported via CVSup -- check the Wiki for + more information.</p> + </body> + </project> + + <project cat='soc'> + <title>gvinum 'move', 'rename'</title> + + <contact> + <person> + <name> + <given>Chris</given> + + <common>Jones</common> + </name> + + <email>soc-cjones@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/moin.cgi/GvinumMoveRename"> + gvinum 'move', 'rename' wiki entry</url> + </links> + + <body> + <p>With the releases of FreeBSD 5.3 and 5.4, FreeBSD has been + moving away from "old-style" vinum towards GEOM-enabled gvinum for + logical volume management. While gvinum is a mostly + feature-complete replacement for vinum, it does not implement the + 'move' or 'rename' verbs which are rather useful when reorganizing + one's volume layout, the alternative being a tedious process of + deleting and recreating subdisks, plexes, or volumes. Additionally, + gvinum is nearly completely undocumented, which contributes to the + perception of gvinum as an unfinished project.</p> + + <p>I'm working on implementing 'move' (being able to move a subdisk + from one drive to another) and 'rename' (being able to rename an + subdisk, plex, volume, or drive), as well as on documentation for + gvinum.</p> + + <p>So far, I've come up with a plan of attack with le@ and phk@, + and implemented the bulk of the userland code for gvinum 'move' and + 'rename'. Still to come are the kernel-side code and + documentation.</p> + </body> + + <help> + <task>'move' and 'rename' userland implementation</task> + + <task>'move' and 'rename' kernel-side implementation</task> + + <task>Outline new handbook section and man page</task> + + <task>Implement new handbook section and man page</task> + </help> + </project> + + <project cat='net'> + <title>if_bridge</title> + + <contact> + <person> + <name> + <given>Andrew</given> + + <common>Thompson</common> + </name> + + <email>thompsa@freebsd.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>This was committed to current on 5 Jun 2005 and will first + appear in the 6.0 release, thanks to everyone who tested. Recent + improvements include:</p> + + <ul> + <li>IPFW layer2 filtering</li> + + <li>DUMMYNET support</li> + + <li>IP header alignment checking</li> + </ul> + + <p>There is ongoing work to bring in some of the advanced features + from OpenBSD such as IPSec bridging. People are encouraged to use + if_bridge and report any problems to the mailing lists.</p> + </body> + </project> + + <project cat='net'> + <title>IPv6 Support for IPFW</title> + + <contact> + <person> + <name> + <given>Max</given> + + <common>Laier</common> + </name> + + <email>mlaier@freebsd.org</email> + </person> + + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@freebsd.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>At the developer summit before BSDCan it was decided to remove + IP6FW from the tree as it has a couple of problems. The most + pressing one is the lack of synchronization and thus the need for + debug.mpsafenet=0. As a replacement Brooks Davis has imported + patches to teach the existing and well-locked IPFW2 code about + IPv6.</p> + + <p>Since the initial import I have added some features required to + manage IPv4 and IPv6 in a single ruleset. I have also extended + existing opcodes to work with IPv6. There are, however, still some + opcodes that do not work with IPv6 and most of the more exotic ones + haven't been tested. As long as IPFW2+v6 does not provide enough + functionality and stability to work as a drop-in replacement for + IP6FW, we won't remove IP6FW.</p> + + <p>In order to get the new code to that point we + <b>really</b> + + need more testers with real world IPv6 deployment and interest in + IPFW+v6. The lack thereof (I haven't received a single answer on my + requests to various FreeBSD mailing lists) has made it hard to + progress.</p> + </body> + + <help> + <task>Properly implement O_REJECT for IPv6</task> + + <task>Maybe implement O_LOG</task> + + <task>Test new(er) IPFW2 opcodes with IPv6</task> + + <task>Test</task> + + <task>Test</task> + + <task>Test</task> + </help> + </project> + + <project cat='soc'> + <title>launchd(8) for FreeBSD</title> + + <contact> + <person> + <name> + <given>R. Tyler</given> + + <common>Ballance</common> + </name> + + <email>tyler@tamu.edu</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/moin.cgi/launchd">Wiki + Project Page</url> + + <url + href="http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/launchd.8.html"> + Apple's launchd(8) man page</url> + </links> + + <body> + <p>So far progress has been slow, the autoconf build system has + been removed from all of the launchd(8) code, and launchctl(1) is + building and semi-functional on FreeBSD-CURRENT (i.e. + CoreFoundation hooks have been removed).</p> + + <p>I'm currently working on porting "liblaunch" which is the core + backend to both launchd(8) (the actual daemon) and launchctl(1), + there are some mach/xnu specific hooks and calls that need to be + remove and either reimplemented or worked around.</p> + + <p>We're also waiting on a response from Apple on a possible + BSD-licensed version of the code (it's currently under the APSL) + Progress is slow, but steady.</p> + </body> + </project> + + <project cat='kern'> + <title>Removable interface improvements</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~brooks/pubs/eurobsdcon2004/" /> + + <url href="http://www.freebsd.org/projects/dingo/" /> + </links> + + <body> + <p>This project is an attempt to clean up handling of network + interfaces in order to allow interfaces to be removed reliably. + Current problems include panics if Dummynet is delaying packets to + an interface when it is removed.</p> + + <p>I have removed struct ifnet's and layer two common structures + from device driver structures. This will eventually allow them to + be managed properly upon device removal. This code has been + committed and will appear in 6.0. Popular drivers have generally + been fixed, but more testing is needed.</p> + </body> + </project> + + <project cat='bin'> + <title>OpenBSD dhclient import.</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The OpenBSD rewrite of dhclient has been imported, replacing the + ISC dhclient. The OpenBSD client provides better support for + roaming on wireless networks and a simpler model of operation. + Instead of a single dhclient process per system, there is one per + network interface. This instance automatically goes away in the + even of link loss and is restarted via devd when link is + reacquired. To support this change, many aspects of the network + interface configuration process were overhauled.</p> + + <p>The current code works well in most circumstances, but more + testing and polishing is needed.</p> + </body> + </project> + + <project cat='net'> + <title>Move ARP out of routing table</title> + + <contact> + <person> + <name> + <given>Qing</given> + + <common>Li</common> + </name> + + <email>qingli@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~qingli/" /> + </links> + + <body> + <p>I've sent the patch to jinmei@isl.rdc.toshiba.co.jp @KAME for + review. I'm still waiting for feedback from Andre. There hasn't + been any major change since the last report. I've kept the code in + sync with CURRENT. Gleb has created a separate P4 branch and has + been helping out on the locking side. Gleb is also helping out on + the testing front.</p> + </body> + + <help> + <task>I'm waiting for review feedback from my mentor Andre on the + overall design and code. I'm waiting for feedback from Andre on + Gleb's suggested modification.</task> + </help> + </project> + + <project cat='soc'> + <title>Nsswitch / Caching daemon</title> + + <contact> + <person> + <name> + <given>Michael</given> + + <common>Bushkov</common> + </name> + + <email>soc-bushman@rsu.ru</email> + </person> + </contact> + + <links> + <url + href="http://wiki.freebsd.org/moin.cgi/NsswitchAndCachingTechnicalDetails" /> + + <url href="http://wiki.freebsd.org/moin.cgi/MichaelBushkov" /> + </links> + + <body> + <p>The + <strong>nsswitch / caching daemon</strong> + + project is being developed within the Google's Summer Of Code + program. The first goal of this project is to implement a set of + patches to extend the use of nsswitch subsystem. The second goal is + the development of the caching library and daemon to add the + caching ability to the nsswitch.</p> + + <p>Currently services, protocols, rpc and openssh patches are + finished. Support for services, services_compat, rpc, protocols, + and ssh_host_keys databases is added with 'files', 'nis' and + 'compat' (for services) sources possible. The nsswitch-friendly + openssh port is almost completed.</p> + </body> + + <help> + <task>Implement set of patches to make nsswitch support + <strong>globus grid security files</strong> + + , + <strong>MAC and audit related configuration files</strong> + + databases.</task> + + <task>Implement the caching library and the caching daemon and + patch nsdispatch function to support caching.</task> + </help> + </project> + + <project cat='vendor'> + <title>OpenBSD packet filter - pf</title> + + <contact> + <person> + <name> + <given>Max</given> + + <common>Laier</common> + </name> + + <email>mlaier@freebsd.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>We will have pf as of OpenBSD 3.7 for RELENG_6. Import has been + completed in early May and FreeBSD release 6.0 will ship with + it.</p> + + <p>A few serious issues with pfsync on SMP have been discovered + since CARP is around and more and more people use it on big iron. + Everything that has been discovered is fixed in HEAD and (if + applicable) MFCed back to RELENG_5. Some functional changes are + undergoing testing right now and will be MFCed in the coming + days.</p> + + <p>With the import of if_bridge from Net/OpenBSD we finally have a + bridge implementation that allows for stateful filtering as well as + IPv6 filtering. Please see the respective report.</p> + </body> + + <help> + <task>Shared lock implementation?</task> + </help> + </project> + + <project cat='kern'> + <title>Low-overhead performance monitoring for FreeBSD</title> + + <contact> + <person> + <name> + <given>Joseph</given> + + <common>Koshy</common> + </name> + + <email>jkoshy@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~jkoshy/projects/perf-measurement"> + Project home page</url> + </links> + + <body> + <p>Modern CPUs have on-chip performance monitoring counters (PMCs) + that may be used to count low-level hardware events like + instruction retirals, branch mispredictions, and cache misses. PMC + architectures and capabilities vary between CPU vendors and between + CPU generations from the same vendor, making the creation of + portable applications difficult. This project implements a + cross-platform PMC management API for applications, and implements + the infrastructure to "virtualize" and manage these PMCs. The + creation of performance analysis tools that use this infrastructure + is also part of the project's goals.</p> + + <p>Work since the last status report:</p> + + <ul> + <li>Sampling mode support for P4 and AMD64 PMCs has been + implemented.</li> + + <li>A pmclog(3) API for parsing hwpmc(4) log files has been + added.</li> + + <li>A number of bugs in libpmc(3), hwpmc(4) and pmcstat(8) have + been fixed.</li> + </ul> + + <p>Future work:</p> + + <ul> + <li>Creating user documentation showing a few real-world uses of + the currently available tools.</li> + + <li>Testing, improving the stability of the code, and + characterizing its overheads.</li> + + <li>Implementing P5 PMC support.</li> + </ul> + </body> + </project> + + <project cat='soc'> + <title>Improve libalias</title> + + <contact> + <person> + <name> + <given>Paolo</given> + + <common>Pisati</common> + </name> + + <email>soc-pisati@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/moin.cgi/PaoloPisati">Wiki + page about libalias work.</url> + </links> + + <body> + <p>My SoC project is about improving libalias and integrating it + with ipfw2, adding nat support into the firewall. Till now I ported + libalias (as a kld) and ng_nat to 4.x and 5.x branches, and I've + already a first working patchset that adds 'nat' action into ipfw. + Next step will be to add a complete syntax to ipfw that will let us + manipulate libalias operations, much like we already do with queue + and pipes for dummynet. In the end the entire work will compile and + work out of the box for 4.x, 5.x and 6.x. More details about the + project and its status are available on wiki page.</p> + </body> + </project> + + <project cat='proj'> + <title>TODO list for volunteers</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Since Google's "Summer of Code" resulted in a lot of interest in + open projects, I'm in the process of compiling a list of nice + projects for volunteers. Unlike Google's SoC those projects aren't + backed with money (but this doesn't means nobody is allowed to + sponsor one of those projects), so we can only guarantee the social + aspects (some "Thank you!" and "That's great!" messages). So far + the list has several entries where the difficulty ranges from + "someone just has to sit down and spend some time on it" up to "we + need a guru for this".</p> + </body> + + <help> + <task>Merging untaken entries from the SoC list as soon as the + official participants/tasks in the SoC are announced.</task> + + <task>Sending the document to some doc people for review.</task> + + <task>Commit the list.</task> + </help> + </project> + + <project cat='bin'> + <title>Removing of old basesystem files and directories</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://www.Leidinger.net/FreeBSD/current-patches/obsolete_removal.diff"> + Patch</url> + </links> + + <body> + <p>FreeBSD lacks a way to remove old/outdated files and directories + in the basesystem. I have a patch which removes obsolete files in a + safe way (interactively, since only the administrator really knows + if there's a need to keep an old file or not; there's a switch for + batch-processing). This feature may or may not be available for + 6.0-RELEASE, depending on the decision from the Release + Engineering team.</p> + </body> + + <help> + <task>Respect the NO_* switches and remove those files too. This is + easy to do with the current implementation, but isn't needed to + commit the removal of obsolete files feature.</task> + </help> + </project> + + <project cat='ports'> + <title>Porting v9 of Intels C/C++ Compiler</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Intel released version 9 of its C/C++ compiler. Work to port the + x86 version to FreeBSD is in progress as time permits. Porting the + EM64T (amd64) version is on the TODO list too, but is subject to + enough free time and access to appropriate hardware.</p> + </body> + </project> + + <project cat='ports'> + <title>Update of the Linux userland infrastructure</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Emulation</given> + + <common>Mailinglist</common> + </name> + + <email>emulation@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The cleanup/streamlining and the possibility of overriding the + default Linux base as reported in the last report happened without + major problems. Work on the open tasks hasn't started yet, but is + scheduled to start "soon". If a volunteer wants to spend some hours + on one of the open tasks, he should tell it on the emulation + mailinglist.</p> + </body> + + <help> + <task>Refactoring the common RPM code in + x11-toolkits/linux-gtk/Makefile into bsd.rpm.mk.</task> + + <task>Determining which up-to-date Linux distribution to use as the + next default Linux base. Important criteria: + <ul> + <li>RPM based (to be able to use the existing + infrastructure)</li> + + <li>good track record regarding availability of security + fixes</li> + + <li>packages available from several mirror sites</li> + + <li>available for several hardware architectures (e.g. i386, + amd64, sparc64; Note: not all architectures have a working + linuxolator for their native bit with, but as long as there are + no userland bits available, no motivation regarding writing the + kernel bits will arise)</li> + </ul> + </task> + + <task>Moving the linuxolator userland to an up-to-date version (see + above).</task> + </help> + </project> + + <project cat='kern'> + <title>Autotuning of the page queue coloring algorithm</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://www.Leidinger.net/FreeBSD/current-patches/pq.diff"> + Patch</url> + </links> + + <body> + <p>The VM subsystem has code to reduce the amount of cache + collisions of VM pages. Currently this code needs to be tuned with + a kernel option. I have a patch which changes this to auto-tuning + at boot time. The auto-tuning is MI, the cache size detection is + MD. Cache size detection is currently available for x86/amd64 (on + other systems it uses default values).</p> + </body> + + <help> + <task>Add cache-detection code for other arches too (Marius told me + how to do this for sparc64).</task> + + <task>Analyze why the cache detection on Athlons doesn't work (no + problems on a P4, but it uses a different code-path).</task> + </help> + </project> + + <project cat='soc'> + <title>FreeBSD website improvements</title> + + <contact> + <person> + <name> + <given>Emily</given> + + <common>Boyd</common> + </name> + + <email>soc-emily@freebsd.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>As part of the Google Summer of Code, I'm working on + improvements to the FreeBSD website (including a proposed website + redesign). My mentor for this project is Murray Stokely.</p> + </body> + </project> + + <project cat='soc'> + <title>UFSJ -- Journaling for UFS</title> + + <contact> + <person> + <name> + <given>Brian</given> + + <common>Wilson</common> + </name> + + <email>polytopes@gmail.com</email> + </person> + + <person> + <name> + <given>Scott</given> + + <common>Long</common> + </name> + + <email>scottl@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>filesystem. Journaling helps ensure the filesystem's integrity + should the system crash. Journaling eliminates the need for + fsck'ing a filesystem, as the filesystem is never in an + inconsistent state (barring hardware failure). This implementation + is inspired by Darwin's HFS+ filesystem and the SGI XFS filesystem. + This is a Summer of Code project, with Scott Long as the mentor and + Brian Wilson as the developer/mentee. Currently this project is + still in the early stages, but will be in a usable state by + September 1 (the Google Summer of Code completion date).</p> + </body> + + <help> + <task>Finish making the file system log metadata updates.</task> + + <task>Add facilities to replay the log on dirty file + systems.</task> + + <task>Make snapshots work with journaling.</task> + </help> + </project> + + <project cat='soc'> + <title>SEBSD</title> + + <contact> + <person> + <name> + <given>Yanjun</given> + + <common>Wu</common> + </name> + + <email>yanjun03@ios.cn</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/moin.cgi/YanjunWu">Show + status in wiki, update more frequently.</url> + </links> + + <body> + <ol> + <li>Setup a local P4 workspace of SEBSD source and Setup lxr for + TrustedBSD source for studying source code.</li> + + <li>Test a simple policy configuration for vsftpd.</li> + + <li>Writing a HOWTO document + <em>Getting Started with SEBSD HOWTO</em> + + by deriving the existing + <em>Getting Started with SELinux HOWTO</em>.</li> + </ol> + + <p>Thanks Robert Watson and Scott Long for their kind help.</p> + </body> + + <help> + <task>When writing the document, try to figure out the sebsd + userland utils that need to be ported.</task> + + <task>Test and edit more policies for BSD environment.</task> + </help> + </project> + + <project cat='proj'> + <title>VFS SMP</title> + + <contact> + <person> + <name> + <given>Jeff</given> + + <common>Roberson</common> + </name> + + <email>jeff@freebsd.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>FreeBSD's VFS layer has been fine grain locked along with the + FFS filesystem for the FreeBSD 6.0 release. The locking has been + underway for several years, with the project really picking up over + the last 6 months thanks largely to sponsorship provided by Isilon + Systems, Inc. a leading vendor of clustered storage systems. The + project has entered a stabilization phase, with a few bugs being + reported in extreme circumstances while the majority of users have + seen no problems. Tests on a 8 and 16 way machines yield reasonable + parallelization, however, it will be beneficial to do lock + contention analysis once things are fully stable.</p> + + <p>For those interested in technical details, there have been a few + relatively significant changes with vnode life-cycle management. + Vnode reference counting and recycling is now no longer an ad-hoc + process involving a variety of flags, a use count and the hold + count. A single hold count is used to track all vnode references + and a destroyed vnode is freed in the context of the caller when + the last ref is lost. The old system would never reclaim memory + used by vnodes and also had pathlogical behavior with unreferenced + vnode caching under pressure. The new system is much simpler than + the old one, however, callers are now required to vhold a vnode + that they lock directly without going through vget to prevent it + from being recycled while they are waiting on a lock. Relying on + 'location stable storage', which is a more strict version of 'type + stable storage' is no longer a valid approach.</p> + + <p>Some other side effects include a much simpler and faster nullfs + implementation, an improved buf daemon flushing algorithm which + eliminated high latency that caused audio skipping, and a lots of + minor cleanups and debugging aids.</p> + </body> + </project> + + <project cat='misc'> + <title>EuroBSDCon 2005 - Basel</title> + + <contact> + <person> + <name> + <common>Information</common> + </name> + + <email>info@eurobsdcon.org</email> + </person> + </contact> + + <links> + <url href="http://www.eurobsdcon.org/">Homepage</url> + + <url href="http://www.eurobsdcon.org/cfp.php">Call for papers</url> + </links> + + <body> + <p>The fourth European BSD conference in Basel, Switzerland is a + great opportunity to present new ideas to the community and to meet + some of the developers behind the different BSDs.</p> + + <p>The two day conference program (Nov 26 and 27) will be + complemented by a tutorial day preceding the conference (Nov + 25).</p> + + <p>The program committee is looking for tutorial and paper + submissions. For details, please see: The + <a href="http://www.eurobsdcon.org/cfp.php">call for papers</a> + + online.</p> + </body> + </project> + + <project cat='kern'> + <title>SMP Network Stack</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/netperf/">Netperf home + page</url> + </links> + + <body> + <p>Significant work has occurred over the last few months relating + to the SMP network stack work. A few of the highlights are covered + here at a high level:</p> + + <ul> + <li>The UMA(9) per-CPU caches have been modified to use critical + sections instead of mutexes. Recent critical section + optimizations make this a performance win for both UP and SMP + systems. This results in a several percent improvement in a + number of user space benchmarks, and larger improvement for + kernel-only network forwarding and processing benchmarks.</li> + + <li>The malloc(9) allocator has been modified to store statistics + per-CPU instead of using a cross-CPU statistics pool, with each + per-CPU pool now using critical sections to synchronize access. + This results in a measurable performance win, especially on SMP + systems</li> + + <li>The netnatm ATM code is now MPSAFE.</li> + + <li>netipx MPSAFEty has been merged to RELENG_5.</li> + + <li>The netperf cluster has now been expanded to include two + additional quad-CPU systems (one dual dual-core AMD system, one + quad-CPU PIII system).</li> + + <li>libmemsetat(3) (see separate report) now corrects SMP-related + races in the measuring of mbuf allocator statistics, as well as + substantially improving kernel memory monitoring capabilities and + tools.</li> + + <li>A range of locking bug fixes, and general network stack bug + fixes.</li> + + <li>Significant updates to the SMPng web page (still more to + do!).</li> + + <li>Identification of all non-MPSAFE network device drivers, with + ultimatum issued, on freebsd-arch. Quite a bit of new driver + locking work as a result (if_ed, if_de, ...).</li> + + <li>Lots of other stuff.</li> + </ul> + + <p>In most cases, these changes will appear in FreeBSD 6.0-RELEASE; + some have been, or will be, merged to FreeBSD 5.x.</p> + + <p>On-going tasks include:</p> + + <ul> + <li>Review and improvement of ifnet locking, such as address + lists and flags.</li> + + <li>Optimization of interface start hand-off.</li> + + <li>Prototyping of queue-oriented packet hand-off in the + stack.</li> + + <li>Performance measurement and analysis.</li> + + <li>Prototype rewrite and simplification of socket locking.</li> + </ul> + </body> + </project> + + <project cat='misc'> + <title>TrustedBSD SEBSD</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/sebsd.html">TrustedBSD/SEBSD + web page</url> + </links> + + <body> + <p>The TrustedBSD Project has released a new snapshot of "SEBSD", a + port of NSA's SELinux FLASK and Type Enforcement implementation to + FreeBSD based on a late 2005 FreeBSD 6.x snapshot. The SEBSD + distribution has now been updated in Perforce to a recent 6.x + snapshot, and a new distribution will be made available in the near + future.</p> + + <p>Work has been performed to merge additional dependencies for + SEBSD back into the base FreeBSD tree, including most recently, + changes to devfs, and System V and POSIX IPC.</p> + </body> + + <help> + <task>Update to new NSA FLASK implementation, which has improved + MLS support.</task> + + <task>Merge remaining kernel changes to support SEBSD back to the + base FreeBSD CVS repository, including file descriptor labeling and + access control (in contrast to file labeling and access control), + and categorization of kernel privileges.</task> + </help> + </project> + + <project cat='kern'> + <title>TrustedBSD Audit</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Wayne</given> + + <common>Salamon</common> + </name> + + <email>wsalmon@FreeBSD.org</email> + </person> + + <person> + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.trustedbsd.org/components.html#audit" /> + </links> + + <body> + <p>In the past few months, significant work has been done relating + to the TrustedBSD audit implementation, including preparatory work + to merge audit into the FreeBSD CVS repository for FreeBSD 6.x. In + particular:</p> + + <ul> + <li>The user space components, such as libbsm, include files, and + command line utilities have been broken out into an OpenBSM + distribution in Perforce. Improvements in OpenBSM will be made + available separately for use by projects such as Darwin, and + imported into the contrib area of FreeBSD.</li> + + <li>The system call table format has been updated to include an + audit event identifier for each system call across all hardware + platforms and ABIs (merged), and all system calls have been + assigned event identifiers (not yet merged).</li> + + <li>The audit management daemon has been rewritten to run on + FreeBSD (originally derived from Darwin) using /dev/audit to + track kernel events.</li> + + <li>Many system calls now properly audit their arguments.</li> + + <li>The TrustedBSD audit3 branch has been updated to a recent + 6.x-CURRENT.</li> + + <li>Significant work has gone into synchronizing the audit event + tables between FreeBSD, Darwin, and OpenSolaris to make sure file + formats and events are portable.</li> + + <li>OpenBSM has been adapted to consume and generate + endian-independent event streams.</li> + + <li>OpenBSM documentation has been created.</li> + </ul> + + <p>The hope is still to provide audit as "experimental" in 6.0; the + primary blocking factor is our awaiting relicensing of the last + remaining audit files from Apple's APSL license to BSDL so that + they can be included in the FreeBSD kernel. This is anticipated to + complete in the near future. Once this is done, the changes can be + merged to CVS, and then MFC'd to RELENG_6. If this is not complete + by 6.0-RELEASE, the work will be merged shortly after the release, + as all ABI-sensitive data structures have been updated as + needed.</p> + </body> + </project> + + <project cat='kern'> + <title>libmemstat(3), UMA(9) and malloc(9) statistics</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.watson.org/~robert/freebsd/libmemstat/"> + libmemstat(3)-derived tools</url> + </links> + + <body> + <p>libmemstat(3) provides a user space library API to monitor + kernel memory allocators, currently uma(9) and malloc(9), with the + following benefits:</p> + + <ul> + <li>ABI-robust interface making use of accessor functions, in + order to divorce monitoring applications from kernel/user ABI + changes.</li> + + <li>Allocator-independent interfaces, allowing monitoring of + multiple allocators using the same interface.</li> + + <li>CPU-cache awareness, allowing tracking of memory use across + multiple CPUs for allocators aware of caches. Unlike previous + interfaces, libmemstat(3) coalesces per-CPU stats in user space + rather than kernel, and exposes per-CPU stats to interested + applications.</li> + + <li>Ability to track memory types over multiple queries, and + update existing structures, allowing easy tracking of statistics + over time.</li> + </ul> + + <p>libmemstat(3) and the appropriate allocator changes for + uma(9) and malloc(9) are currently in HEAD (7-CURRENT), and MFC has + been approved to RELENG_6 for inclusion in 6.0-RELEASE. These + changes may also be backported to 5.x.</p> + + <p>Sample applications include memstat(8), an allocator-independent + statistics viewing tool, memtop(8), which provides a top(1)-like + interface for monitoring kernel memory use and active memory types. + None of these are "pretty".</p> + + <p>netstat -mb has also been updated to use libmemstat(3) to track + network memory use using uma(9), rather than the less reliable mbuf + allocator statistics interface. As a result, the statistics are now + more reliable on SMP systems (this corrects the bug in which mbuf + statistics sometimes "leaked", even though memory didn't), and more + informative (cache information is now displayed, as well as mbuf + tag information).</p> + </body> + + <help> + <task>Teach libmemstat(3) to speak libkvm(3) in order to allow + tools linked -lmemstat to interogate kernel core dumps.</task> + + <task>Teach libmemstat(3) to interface with user space malloc and + track malloc allocations for user space applications.</task> + + <task>Update vmstat(8) -m and -z implementations to use + libmemstat(3) instead of the old monitoring interfaces. Code to do + this exists in the sample libmemstat(3) applications.</task> + + <task>Identify how to make streams or the library endian-aware so + that streams dumped from a kernel of alternative endian could be + processed using libmemstat(3) on another system.</task> + + <task>Identify any remaining caching allocators in the kernel, such + as the sfbuf allocator, and teach libmemstat(3) how to interface + with them.</task> + </help> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2005-07-2005-10.xml b/en_US.ISO8859-1/htdocs/news/status/report-2005-07-2005-10.xml new file mode 100644 index 0000000000..5bfc496289 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2005-07-2005-10.xml @@ -0,0 +1,2037 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<report> + <date> + <month>July-October</month> + + <year>2005</year> + </date> + + <section> + <title>Introduction</title> + + <p>After a long, exhausting, yet very productive third quarter of 2005 + FreeBSD 6.0 has been released. Many activities were put into the + background in order to make this release the success it has + become.</p> + + <p>Nonetheless, we received a tremendous amount of reports covering + various projects that either found their way into FreeBSD 6.0 already + or have started to develop in, what is now known as 7-CURRENT. The + EuroBSDCon and the Developer Summit in Basel next week will be a good + opportunity to help some of the ideas herein to take off.</p> + + <p>Last round we had the pleasure to introduce our accepted Google + Summer of Code projects. Now, that the summer is over, we are even + more pleased to include reports about the outcome of these projects. + Some already found their way into the tree or the general public + otherwise - most ocularly the new webdesign.</p> + + <p>Unfortunately, this publication has been delayed for various + reasons - the before mentioned release of 6.0 being one of them. + Thus, some of the reports might no longer be as up to date as they + were when we received them and we encourage you - even more this time + - to also visit the weblinks to get more recent information.</p> + + <p>Thanks again to everyone who submitted reports, and our sincere + apologies for running late this time.</p> + </section> + + <category> + <name>soc</name> + + <description>Google summer of code</description> + </category> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>doc</name> + + <description>Documentation</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>net</name> + + <description>Network infrastructure</description> + </category> + +<!-- + <category> + <name>bin</name> + + <description>Userland programs</description> + </category> +--> + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <category> + <name>vendor</name> + + <description>Vendor / 3rd Party Software</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='vendor'> + <title>Cronyx/Asterisk</title> + + <contact> + <person> + <name> + <given>Roman</given> + + <common>Kurakin</common> + </name> + + <email>rik@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.cronyx.ru/hardware/wan.html">Cronyx WAN + Adapters</url> + + <url href="http://www.freebsd.org/~rik">rik's Home Page</url> + </links> + + <body> + <p>A new netgraph-to-zaptel module that allows to use E1(ISDN PRI) + WAN adapters as an interface card for open source PBX - Asterisk. + All you need is an adapter that able to work in raw phone mode + (like Cronyx Tau-PCI/2E1), eq. without HDLC-like framing and that + has support of Netgraph.</p> + </body> + </project> + + <project cat='misc'> + <title>BSDCan</title> + + <contact> + <person> + <name> + <given>Dan</given> + + <common>Langille</common> + </name> + + <email>dan@langille.org</email> + </person> + </contact> + + <links> + <url href="http://www.bsdcan.org/">BSDCan</url> + </links> + + <body> + <p>We are in the process of recruiting new members for the program + committee. If you would like to volunteer before you are recruited, + please contact me.</p> + + <p>The dates for 2006 have been announced: May 12-13, 2006. The + venue will be the same as previous events: University of Ottawa. + The prices will not increase from 2005.</p> + + <p>Please start thinking about your papers. The call for papers + will go out soon.</p> + </body> + </project> + + <project cat='ports'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/ports/">The FreeBSD ports + collection</url> + + <url href="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD + ports unfetchable distfile survey (Bill Fenner's report)</url> + + <url href="http://edwin.adsl.barnet.com.au/~edwin/ports/">FreeBSD + ports updated distfile survey (Edwin Groothius' report)</url> + + <url href="http://portsmon.FreeBSD.org/index.html">FreeBSD ports + monitoring system</url> + + <url href="http://www.freebsd.org/portmgr/index.html">The FreeBSD + Ports Management Team</url> + </links> + + <body> + <p>A great deal of work has gone into the Ports Collection since + the last report in April, much of it behind-the-scenes.</p> + + <p>As this report was being written, the 6.0 release was ongoing. + Due to the amount of time that it has taken to get 6.0 through the + beta process and into RC, we have been in ports freeze or slush for + more than two months. Unfortunately this has held back needed work + on the ports infrastructure.</p> + + <p>The last major update to bsd.port.mk, in early May, was + coordinated by Kirill Ponomarew added a number of new features and + closed 15 PRs. Another similar set of changes has been tested and + is ready for commit after release.</p> + + <p>portmgr welcomed two new members to its team: Erwin Lansing (who + had previously served as secretary, a role in which he is + continuing) and Clement Laforet. Clement is interested in speeding + up the adoption of new changes into the infrastructure, an item I'm + sure that that everyone can support. He promises to bring some + fresh ideas to bear on this, including the revitalization of + devel/portmk as a testing ground for new changes to bsd.port.mk in + which the larger community can help test changes.</p> + + <p>The unfetchable distfile survey, which had been non-functional + for quite some time, was revitalized by Bill Fenner, with many new + pages of analysis added to it. Work is still ongoing. As a result + of this analysis, Bill and Mark Linimon eliminated nearly 100 lines + of bogus or outdated sites from bsd.sites.mk alone. They are + continuing to work through many other sites and ports as successive + iterations of the survey reveal more dimensions to the problem. We + still need more help from the larger community (see below).</p> + + <p>Edwin Groothius has instituted a similar but slightly different + survey. His program attempts to visit each listed mastersite for + each distfile and determine whether or not a newer version might be + available. The results are stored in a database. This is helping to + automate a function that had been left up to individual maintainers + to look through numerous websites to try to find these updates. The + survey has been hugely (if not universally) popular. Already, + dozens of port updates have been committed as a direct result of + this service.</p> + + <p>In addition, portsmon, which had been down due to a machine + change, was moved to portsmon.FreeBSD.org and updated during this + time. Many thanks to Erwin Lansing for providing the loan of this + machine, and Will Andrews for having provided the loan of the + previous incarnation.</p> + + <p>Both of the above surveys are now generating periodic email to + ports maintainers advising them of problems. This is in addition to + recurring email from portsmon. The surveys allow individual + maintainers to ask to receive no further email. portsmon does not + currently have this but it needs to be added. Although we have no + doubt the mail can in some cases be annoying (especially given the + fact that there will inevitably be some false positives), the fact + is that these emails have had a direct impact on the quality on the + ports. We ask for patience from the community while each of us + continues to fine-tune the algorithms controlling what email is + generated. (Because of the number of emails these systems generate, + it is impossible to go over every one individually for a sanity + check).</p> + + <p>As a result of bounces from the above email, we have also been + resetting maintainers who have become unreachable.</p> + + <p>Pav Lucistnik has done a great deal of work on the Porter's + Handbook, including some much needed reshuffling and cleanup. + Expanded sections include Apache and PHP; Configure Scripts; + Dealing With Shared Libraries; Dealing With User Configuration + Files; Handling Empty Directories; Python; and Ruby. In addition, + Edwin Groothius has contributed a section on OPTIONS, and numerous + other sections have been improved by good suggestions from various + other contributors.</p> + + <p>A new article, "Maintaining and contributing to the FreeBSD + Ports Collection", has been prepared by Sam Lawrance and has been + reviewed and is ready for commit. This document attempts to codify + the rights and responsibilities of ports maintainers, which until + now had merely been "community lore" as discussed on various + mailing lists.</p> + + <p>We continue to add new committers regularly, 8 since the last + report.</p> + + <p>The ports collection now contains over 13,500 ports. This is an + increase of over 750 since the last report in April.</p> + </body> + + <help> + <task>portmgr would like to ask maintainers and committers alike to + go through the status of their ports on the two distfile surveys, + both the one that shows unfetchable current distfiles and the one + that shows possibly updated distfiles. This is an effective way to + quickly help improve our user's perception of the state of the + ports.</task> + + <task>A great deal of progress has been made in cracking down on + ports that install files outside the approved directories and/or do + not deinstall cleanly (see "Extra files not listed in PLIST" on + <a href="http://pointyhat.freebsd.org/errorlogs/">pointyhat</a> + + ). These ports are now a small minority thanks to the dedicated + efforts of a large number of individuals.</task> + + <task>We still have a large number of PRs that have been assigned + to committers for some time (in fact, they constitute the + majority). portmgr members are now going through this list and + asking each committer to either commit them or release them to the + general pool so that someone else may work on them. In addition, + the existing policies for inactive maintainers (two weeks for + maintainer- timeout on PRs; three months for maintainer reset if no + activity) are going to be much more actively pursued than in the + past, where the policies were more honored in the breach than in + the observance. The goal is to try to bring the Ports Collection as + up-to-date as possible. (While there has been progress on many + fronts, there are still areas where ports are suffering from + bit-rot.)</task> + </help> + </project> + + <project cat='soc'> + <title>Improve Libalias</title> + + <contact> + <person> + <name> + <given>Paolo</given> + + <common>Pisati</common> + </name> + + <email>p.pisati@oltrelinux.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/moin.cgi/PaoloPisati"> + Wiki/Official project site</url> + + <url href="http://wiki.freebsd.org/moin.cgi/PaoloPisati" /> + </links> + + <body> + <p>The project met all the scheduled goals, and following are the + new features implemented in libalias: + <ul> + <li>integration with IPFW in kernel land</li> + + <li>support for 4.x and 5.x as kld</li> + + <li>converted from a monolithic to a modular architecture, added + the ability to load/unload at runtime support for new protocols + (modules work both in kernel and user land)</li> + + <li>added logging support in kernel land</li> + </ul> + + <br /> + + Fell free to suggest other improvements.</p> + </body> + + <help> + <task>Test and feedback are welcome</task> + </help> + </project> + + <project cat='ports'> + <title>FreshPorts</title> + + <contact> + <person> + <name> + <given>Dan</given> + + <common>Langille</common> + </name> + + <email>dan@langille.org</email> + </person> + </contact> + + <links> + <url href="http://www.freshports.org/">FreshPorts</url> + </links> + + <body> + <p>I'm in the process of adding personalized newsfeeds to the + website. For each of your Watch Lists, you will also have a news + feed just for that watch list. Any commit to any port in your watch + list will turn up on your newsfeed. This fantastic new feature is + available now for your RSS pleasure at + <a href="http://beta.freshports.org/">the BETA site</a> + + . I've also been doing some work in the area of supporting multiple + platforms and architectures. This will allow FreshPorts to + correctly report that a port is broken, for example, on i386, but + not the other platforms. This feature will take note of BROKEN, + FORBIDDEN, and IGNORE for the following architectures: + <ul> + <li>alpha</li> + + <li>amd64</li> + + <li>i386</li> + + <li>ia64</li> + + <li>sparc64</li> + </ul> + + And the following OSVERSIONS (subject to upgrade as new releases + come along): + <ul> + <li>492100</li> + + <li>504102</li> + + <li>600033</li> + + <li>700001</li> + </ul> + + Upcoming changes, in addition to the above, include: + <ol> + <li>NOT_FOR_ARCHS</li> + + <li>ONLY_FOR_ARCHS</li> + + <li>IS_INTERACTIVE</li> + </ol> + + I've been getting useful help from those on IRC. Thanks.</p> + </body> + + <help> + <task>Complete the above.</task> + </help> + </project> + + <project cat='soc'> + <title>Fuse for FreeBSD</title> + + <contact> + <person> + <name> + <given>Csaba</given> + + <common>Henk</common> + </name> + + <email>soc-chenk@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://fuse4bsd.creo.hu/">New home page</url> + + <url href="http://wiki.freebsd.org/moin.cgi/FuseFilesystem"> + FreeBSD wiki page</url> + + <url href="http://creo.hu/~csaba/projects/fuse4bsd/downloads/"> + Download location</url> + </links> + + <body> + <p>Fuse for FreeBSD is the outcome of my "ssh based networking + filesystem for FreeBSD" SoC project.</p> + + <p>The kernel interface for the comprehensive userspace filesystem + API provided by the ( + <a href="http://fuse.sourceforge.net">Fuse project</a> + + ) has been implemented for FreeBSD (6.x and 7.x), under the BSD + license. This has the benefit of opening up the possibility of + porting the rich collection of Fuse based filesystems to + FreeBSD.</p> + + <p>Now it's ready for consumption by a broader audience. The + <tt>sysutils/fusefs-kmod</tt> + + , + <tt>sysutils/fusefs-libs</tt> + + , + <tt>sysutils/fusefs-sshfs</tt> + + ports can be expected to be integrated into the FreeBSD ports tree + in the next few days (the ports were created and are maintained by + Anish Mistry, and Simon Barner's careful review also helps a + lot).</p> + </body> + + <help> + <task>Implement missing features like extended attributes and + attribute/name caching (with timeout).</task> + + <task>Resolve problems with autotools and integrate userspace + modifications into the Fuse codebase.</task> + + <task>Port Fuse based filesystems and language bindings to + FreeBSD.</task> + + <task>Create sysfs (Fuse based filesystem interface to + sysctl).</task> + + <task>Test, test, test among a broad variety of + circumstances.</task> + </help> + </project> + + <project cat='soc'> + <title>gvinum 'move', 'rename' support</title> + + <contact> + <person> + <name> + <given>Chris</given> + + <common>Jones</common> + </name> + + <email>soc-cjones@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/moin.cgi/GvinumMoveRename"> + gvinum 'move', 'rename' wiki</url> + </links> + + <body> + <p>Support for moving and renaming objects in gvinum was completed + at the end of August 2005. All gvinum objects (drives, subdisks, + plexes, and volumes) can be renamed, and subdisks can be moved from + drive to drive. Also, a man page for gvinum was created.</p> + </body> + + <help> + <task>Update FreeBSD Handbook chapter on vinum to reflect gvinum. + Slowly in progress, but hopefully done by the end of the year, + workload permitting.</task> + </help> + </project> + + <project cat='soc'> + <title>Integrated SNMP monitoring</title> + + <contact> + <person> + <name> + <given>Philip</given> + + <common>Paeps</common> + </name> + + <email>philip@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Shteryana</given> + + <common>Shopova</common> + </name> + + <email>soc-shteryana@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~harti/bsnmp/index.html" /> + + <url + href="http://wiki.freebsd.org/moin.cgi/ShteryanaShopova" /> + + <url + href="http://wiki.freebsd.org/moin.cgi/SnmpMonitoringModulesStatus" /> + </links> + + <body> + <p>This summer, we've had the pleasure of having two Google Summer + of Code students hacking on our SNMP monitoring machinery. Victor + worked on implementing the Host Resources, TCP and UDP MIBs in + bsnmpd while Shteryana started on client-side SNMP tools.</p> + + <p>With these modules and tools, a FreeBSD installation can be + monitored without having to install any (heavy!) third-party + tools.</p> + </body> + + <help> + <task> + <p>While the modules and the tools currently in Perforce are + generally functional, they still need some tidying up (style(9)) + and testing before they can be committed to CVS.</p> + + <p>At the time of this writing, the Hostres MIB is pretty much + commit-ready in Perforce (//depot/user/philip/bsnmp/...), the + other modules and tools live in + //depot/projects/soc2005/bsnmp/... They'll be branched for + tidying up and committing "Real Soon Now"[tm]</p> + </task> + + <task>Testers are very welcome. :-) Please let us know about any + bugs!</task> + </help> + </project> + + <project cat='soc'> + <title>Interface Cleanup</title> + + <contact> + <person> + <name> + <given>Anders</given> + + <common>Persson</common> + </name> + + <email>soc-anders@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://wiki.freebsd.org/moin.cgi/CleanupOfNetworkInterfaceApisProposal"> + SoC Proposal</url> + </links> + + <body> + <p>The dependencies to kernel-only datastructures in netstat + (ifnet, etc.) have been removed almost completely (AppleTalk and + IPX still needs work). In order to remove the dependencies, the + debugging features of netstat had to be removed. However, a project + to create a generic, modular 'data structure' examination tool is + ongoing, and the debugging features factor out of netstat have been + migrated to this tool.</p> + </body> + + <help> + <task>Refactoring of the netstat code, create a modular version in + the spirit of ifconfig.</task> + + <task>Data structure examination tool needs to be completed, + current state is more that of a prototype.</task> + </help> + </project> + + <project cat='soc'> + <title>UFS Journaling</title> + + <contact> + <person> + <name> + <given>Brian</given> + + <common>Wilson</common> + </name> + + <email>polytopes@gmail.com</email> + </person> + + <person> + <name> + <given>Scott</given> + + <common>Long</common> + </name> + + <email>scottl@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Scott has been working on inserting journalling hooks into the + ufs and ffs filesystem code. Brian has been balancing school and + redesigning various things that were deemed necessary to update + during the end of the actual SoC project.</p> + </body> + + <help> + <task>Finish the redesign of the internal block management + code.</task> + + <task>Integration and test of the ffs/ufs hooks and the journaling + code.</task> + + <task>Updating userland tools to be aware of and use the + journal.</task> + + <task>Journal buffer management wiring to VM subsystem a la + XFS.</task> + </help> + </project> + + <project cat='proj'> + <title>pfSense</title> + + <contact> + <person> + <name> + <given>Scott</given> + + <common>Ullrich</common> + </name> + + <email>sullrich@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://www.pfsense.com" /> + </links> + + <body> + <p>pfSense is a m0n0wall derived operating system platform with + radically different goals such as using Packet Filter, FreeBSD 6, + ALTQ for excellent packet queueing and finally an integrated + package management system for extending the environment with new + features.</p> + + <p>Work continues to stabilize pfSense in preparation for the + FreeBSD 6 release. Once FreeBSD 6 is released pfSense will enter + the final beta and release candidate phases in preparation for the + 1.0 release.</p> + </body> + + <help> + <task>Stabilize installer (cannot load kernel errors after + install)</task> + + <task>Finish outgoing load balancing monitoring</task> + + <task>Fix last minute bugs that turn up</task> + </help> + </project> + + <project cat='soc'> + <title>launchd(8) for FreeBSD</title> + + <contact> + <person> + <name> + <given>R. Tyler</given> + + <common>Ballance</common> + </name> + + <email>tyler@tamu.edu</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/moin.cgi/launchd">Project + Wiki</url> + </links> + + <body> + <p>In short, launchd can run perfectly fine on FreeBSD, and + combined with launchctl, it can be used to manage daemons through + the launchctl(1) interface. Jobs can be added and managed two ways + as of yet from launchctl(1). Using zarzycki@'s experimental + "submit" command within launchctl(1) or by using my + lame/rudimentary/etc "launcher" format (launchd/launchers/*.launch) + which uses property(3) to parse out three simple, and important + details. The program label, path, and any program flags. Using the + "load" command, one can load the data into launchctl(1) and then + start the processes with the..."start" command. Jobs can be + removed/stopped with the "remove" command. The "limit" command + still throws launchctl(1) into an infinite loop, and yes, I plan on + fixing this.</p> + + <p>There are some things that need to be fixed, first off, some + sort of boot time integration, whether as an init-replacement (i.e. + PID 1, a la Mac OS X) or as the first thing started from init, that + kicks all rcng things off. Along with, more importantly, a plist + parser, so we can have full compatibility with Mac OS X's launchd + via Core Foundation.</p> + + <p>I'm also trying to get launchd(8) relicensed with the BSD + license, as opposed to the APSL, anybody with tips, or methods for + achieving this goal, contact me at tyler@tamu.edu</p> + </body> + + <help> + <task>Writing a light-weight plist (non-XML) parser with lex and + yacc.</task> + </help> + </project> + + <project cat='arch'> + <title>Porting FreeBSD to the Xbox</title> + + <contact> + <person> + <name> + <given>Rink</given> + + <common>Springer</common> + </name> + + <email>rink@rink.nu</email> + </person> + + <person> + <name> + <given>Ed</given> + + <common>Schouten</common> + </name> + + <email>ed@fxq.nl</email> + </person> + </contact> + + <links> + <url href="http://www.xbox-bsd.nl" /> + </links> + + <body> + <p>As of 26th July 2005, it is possible to run FreeBSD on your Xbox + with minor patching effort. The framebuffer has initial support; + The USB ports, IDE- and audio controllers are fully supported; the + only part severely lacking now is the lack of support for the + NForce Ethernet controller.</p> + + <p>Currently, efforts are focussing on eliminating the XBOX kernel + option and make the port self-detecting; this means the x86 and + xbox kernels will be identical. The goal is to provide native xbox + support in 7-CURRENT.</p> + + <p>Furthermore, a porting effort is planned from Linux' GPL-ed + forcedeth.c; not only the Xbox port will benefit from this but also + all NForce motherboard owners. The resulting driver could be + kldload-ed to keep the kernel GPL-free.</p> + </body> + + <help> + <task>The xbox framebuffer driver should be merged in the VESA + framework, so it can use syscons(4). Assistance on this would be + very welcome!</task> + </help> + </project> + + <project cat='proj'> + <title>ggtrace</title> + + <contact> + <person> + <name> + <given>Ivan</given> + + <common>Voras</common> + </name> + + <email>ivoras@yahoo.com</email> + </person> + </contact> + + <links> + <url href="http://ivoras.sharanet.org/projects/ggtrace.html" /> + </links> + + <body> + <p>Ggtrace is "GEOM gate tracer", utility to track I/O requests on + a storage device on FreeBSD. It uses the ggate facility of FreeBSD + to attach to a file or device and produces a device that can be + used for any I/O, including hosting filesystems.</p> + + <p>I/O requests are presented in the form of a moving histogram + that can be used to discern which parts of the storage device are + used most often. One use of ggtrace is to analyze how filesystems + arrange and access data on storage devices.</p> + + <p>The project is working and usable only on the RELENG_6 + branch.</p> + </body> + </project> + + <project cat='soc'> + <title>gjournal</title> + + <contact> + <person> + <name> + <given>Ivan</given> + + <common>Voras</common> + </name> + + <email>ivoras@yahoo.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/moin.cgi/gjournal">gjournal + wiki page</url> + </links> + + <body> + <p>Gjournal provides GEOM-level journaling and COW capabilities to + storage devices. Unfortunately, it cannot be used as a substitute + for filesystem journaling (fsck is still needed when gjournal + device is used to host filesystems). Development has slowed down, + and the existing code needs much more testing. If there is + continued interest in it, I'll probably split the functionalities + into two projects, one handling COW and one handling the + journaling, in order to make the code cleaner.</p> + </body> + + <help> + <task>More testing is needed.</task> + </help> + </project> + + <project cat='net'> + <title>TCP & IP Routing Optimization Fundraise</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~andre/tcpoptimization.html" /> + + <url + href="http://www.freebsd.org/news/status/report-mar-2005-june-2005.html#Fundraising---TCP-&-IP-Routing-Optimization" /> + </links> + + <body> + <p>The fundraise has been very successful and I want to thank + everyone who has pledged their support and tipped the jar. The full + amount plus a little bit more has been raised in a very short + timeframe. More information on the exact amounts and their sponsors + can be found at the first link.</p> + + <p>Due to the extended (and unexpected long) code freeze for the + release process of FreeBSD 6.0 (which is very high quality btw.) + I've decided to push back on working full time until the freeze is + lifted. So far I've done some work in the mbuf handling area and + some other netinet cleanups in my local repository.</p> + + <p>Once FreeBSD 6.0 is released I resume my work on this project + and many changes and optimizations, as described in the first and + second link, will go into into FreeBSD-current.</p> + </body> + </project> + + <project cat='doc'> + <title>TODO list for volunteers</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The TODO list for volunteers (see the last report for more) is + now under review by some doc@ people.</p> + </body> + </project> + + <project cat='doc'> + <title>bridge.c retired</title> + + <contact> + <person> + <name> + <given>Max</given> + + <common>Laier</common> + </name> + + <email>mlaier@freebsd.org</email> + </person> + + <person> + <name> + <given>Andrew</given> + + <common>Thompson</common> + </name> + + <email>thompsa@freebsd.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>As of September 27, the old bridge(4) implementation has been + removed from HEAD and will not be part of FreeBSD 7 and later. + FreeBSD 6 will serve as transition period. The full functional + replacement if_bridge(4) is now available in FreeBSD 5 (not yet + part of 5.4 however), FreeBSD 6 and -CURRENT. Any problems should + be reported to Andrew Thompson, who is maintaining if_bridge in + FreeBSD.</p> + </body> + + <help> + <task>Document the change in the handbook and other reference + material.</task> + </help> + </project> + + <project> + <title>Problem Report Database</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>bugmeister_at_freebsd_dot_org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/support.html#gnats">GNATS</url> + </links> + + <body> + <p>Due to some good recent commit and cleanup work by both + Alexander Leidinger and Craig Rodrigues, the number of base-system + PRs has stabilized somewhat. The number of incoming ports PRs + continues to accelerate but except during freezes the ports + committers have been battling to commit them as quickly as they + come in. (The graphs very clearly show where the freezes are.) The + net result is that we are holding our own but it takes a great deal + of (mostly unheralded) effort to do so. Thanks are due to a large + number of individuals who are doing this ongoing work.</p> + + <p>There is ongoing work to ask committers who have had PRs + assigned to them for a significant period of time, whether they are + still interested in pursuing them or whether they should instead be + reassigned to the pool. This is being done to try to get as many + PRs 'unstuck' as possible to try to help improve our users' + perceptions of the project.</p> + + <p>As an experiment, Mark Linimon has been adding 'tags' to many of + the kern and bin PRs, including such things as '[nfs]', '[if_em]', + and so forth. The idea is to try allow searching and browsing based + on these terms so that committers will find it easier to work with + our current PR database. At the moment this is in the experimental + stage, although it is possible for committers to work with them + from the command line on systems with a database installed via + query-pr(1).</p> + </body> + </project> + + <project cat='net'> + <title>Removable interface improvements</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~brooks/pubs/eurobsdcon2004/" /> + + <url href="http://www.freebsd.org/projects/dingo/" /> + </links> + + <body> + <p>This project is an attempt to clean up handling of network + interfaces in order to allow interfaces to be removed reliably. + Current problems include panics if Dummynet is delaying packets to + an interface when it is removed.</p> + + <p>I have removed struct ifnet's and layer two common structures + from device driver structures. This will eventually allow them to + be managed properly upon device removal. This code has been + committed and will appear in 6.0. Popular drivers continue to + be fixed. jhb's locking work has identified and corrected many + issues. rwatson has also committed cleanups to the multicast code + which fixed some issues in this area.</p> + </body> + </project> + + <project cat='net'> + <title>OpenBSD dhclient import</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The OpenBSD rewrite of dhclient has been imported, replacing the + ISC dhclient. The OpenBSD client provides better support for + roaming on wireless networks and a simpler model of operation. + Instead of a single dhclient process per system, there is one per + network interface. This instance automatically goes away in the + even of link loss and is restarted via devd when link is + reacquired. To support this change, many aspects of the network + interface configuration process were overhauled.</p> + + <p>The current code works well in most circumstances, but more + testing and polishing is needed. A few bugs are being tracked, but + most of them are edge cases.</p> + + <p>Work on further interface configuration enhancements is underway + for FreeBSD 7.0.</p> + </body> + </project> + + <project cat='misc'> + <title>EuroBSDCon 2005 - Basel</title> + + <contact> + <person> + <name> + <given>Information</given> + </name> + + <email>info@eurobsdcon.org</email> + </person> + </contact> + + <links> + <url href="http://www.eurobsdcon.org/" /> + </links> + + <body> + <p>The fourth European BSD conference in Basel, Switzerland is a + great opportunity to present new ideas to the community and to meet + some of the developers behind the different BSDs.</p> + + <p>The two day conference program (Nov 26 and 27) will be + complemented by a tutorial day preceding the conference (Nov + 25).</p> + + <p>The FreeBSD developers will hold a DevSummit on Nov 24 and 25, + so several developers will be at the conference.</p> + + <p>The program is available for + <a + href="http://www.eurobsdcon.org/conference-schedule-saturday.php"> + Saturday</a> + + and + <a href="http://www.eurobsdcon.org/conference-schedule-sunday.php"> + Sunday</a> + + providing very interesting FreeBSD talks and topics.</p> + + <p>Today more than 160 people from 25 countries have registered for + the conference.</p> + </body> + </project> + + <project cat='ports'> + <title>FreeBSD GNOME Project</title> + + <contact> + <person> + <name> + <given>Joe Marcus</given> + + <common>Clarke</common> + </name> + + <email>marcus@FreeBSD.org</email> + </person> + + <person> + <name> + <given>FreeBSD GNOME</given> + + <common>Team</common> + </name> + + <email>gnome@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/gnome/">FreeBSD GNOME Project + Homepage</url> + </links> + + <body> + <p>Since our last status report, we have added a new member to the + team: Jean-Yves Lefort (jylefort). We have even spiced up our + <a href="http://www.FreeBSD.org/gnome/contact.html">contact + page</a> + + with pictures of ourselves and in some cases, a cute hippo. And our + very own Adam Weinberger (adamw) has been made a GNOME Project + committer heading up the Canadian English translation project.</p> + + <p>We have finished the port GNOME 2.12 to FreeBSD. However, due to + the ports slush in preparation for 6.0-RELEASE, the update has not + been merged into the official ports tree. If people are eager to + try out GNOME 2.12 while waiting for the ports tree to fully thaw, + we have + <a href="http://www.FreeBSD.org/gnome/docs/develfaq.html"> + instructions</a> + + on our website. GNOME 2.12 will be the first FreeBSD GNOME release + <em>not</em> + + to include support for FreeBSD 4.X. While 4.X is still a very + viable release for servers, it lacks many of the features needed + for a Desktop Environment such as GNOME. We do plan to continue + support of the GNOME development platform on 4.X, however. This + includes Glib, GTK+, libgnome, etc. A new porting component will be + introduced with GNOME 2.12 called, ``ltverhack''. This will help + with future upgrades by keeping shared library versions from + needlessly changing.</p> + + <p>The FreeBSD GNOME Project is also committed to providing our + users with a solid package experience. To that end, we have + extended our + <a href="http://www.freebsd.org/gnome/docs/faq2.html#q21"> + Tinderbox</a> + + to build amd64 packages for all supported versions of FreeBSD for + both the production and development releases of the GNOME Desktop. + The development packages are even built with debugging symbols to + better help with reporting problems.</p> + </body> + + <help> + <task>FreeBSD needs a + <a href="http://www.freedesktop.org/wiki/Software_2fhal">HAL</a> + + port. HAL will be vital for both GNOME and KDE in providing FreeBSD + users with a smooth, elegant desktop experience. Once GNOME 2.12 + has been merged into the ports tree, work will begin on making HAL + on FreeBSD a reality. Contact + <a href="mailto:gnome@FreeBSD.org">gnome@FreeBSD.org</a> + + if you are interested in helping.</task> + + <task>We need help with project documentation. In particular, we + need help auditing the + <a href="http://www.FreeBSD.org/gnome/docs/faq.html">FAQ</a> + + to make sure the content is still relevant, and we are not missing + any key items. If you're interested, please contact + <a href="mailto:gnome@FreeBSD.org">gnome@FreeBSD.org</a> + + .</task> + </help> + </project> + + <project cat='arch'> + <title>PowerPC Port</title> + + <contact> + <person> + <name> + <given>Peter</given> + + <common>Grehan</common> + </name> + + <email>grehan@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/platforms/ppc.html">FreeBSD/PPC + Platform page.</url> + </links> + + <body> + <p>The project has been following the 6.0 release schedule by + producing BETA-* builds and is now up to the RC1 build.</p> + + <p>Dario Freni successfully built a FreeSBIE/ppc iso for his + Summer-of-code project.</p> + </body> + </project> + + <project cat='proj'> + <title>iSCSI Initiator</title> + + <contact> + <person> + <name> + <given>Daniel</given> + + <common>Braniss</common> + </name> + + <email>danny@cs.huji.ac.il</email> + </person> + </contact> + + <links> + <url + href="ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-12.tar.bz2" /> + </links> + + <body> + <p>This iSCSI kernel module and its companion control program, are + still under development, but the main parts seem to be working. A + second round of public tests has started.</p> + </body> + + <help> + <task>login chap authentication</task> + + <task>digest</task> + + <task>network disconnect recovery</task> + </help> + </project> + + <project cat='kern'> + <title>The Kernel Stress Test Suite</title> + + <contact> + <person> + <name> + <given>Peter</given> + + <common>Holm</common> + </name> + + <email>pho@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~pho/stress/" /> + </links> + + <body> + <p>The current version of the test suite took form in the beginning + of the year after discussions with Jeff Roberson, during a long + period of testing Jeff's VFS SMP work.</p> + + <p>At that time, Daniel Seuffert donated a Thunder 7500 + motherboard complete with CPUs, RAM and coolers. This allowed me + to do some serious SMP testing.</p> + + <p>Mid July Murray Stokely suggested adding a link from the 6.0 + todo web page to the Stress Test Status Page. At that time there + were a few reoccurring panics that made it hard to test the kernel + for other problems. Numerous people put a lot of hard work in + fixing the panics and livelocks found during the next months. At + the same time others stepped in and ran the test suite on their own + hardware, thus increasing the focus on kernel stability.</p> + + <p>As of 6.0, the kernel stress test suite cannot panic the + kernel.</p> + </body> + </project> + + <project cat='soc'> + <title>Nsswitch / Caching daemon</title> + + <contact> + <person> + <name> + <given>Michael</given> + + <common>Bushkov</common> + </name> + </person> + </contact> + + <links> + <url + href="http://wiki.freebsd.org/moin.cgi/NsswitchAndCachingFinalReport" /> + + <url href="http://wiki.freebsd.org/moin.cgi/MichaelBushkov" /> + </links> + + <body> + <p>The nsswitch / caching daemon project was developed within the + Google's Summer Of Code program. Almost all goals of the project + were achieved. Thanks to Brooks Davis and Jacques Vidrine, who were + my mentors and greatly helped me.</p> + + <p>Nsswitch subsystem was extended to support new sources + (services, protocols, rpc, openssh and GT4). The testing of the + Globus Grid Toolkit 4 patch (which adds support for nsswitch to + GT4) is still to be done. For nsswitch to support caching, the + caching daemon was implemented on top of the caching library, which + was also developed during the SoC. The current version of the + daemon uses simple nscd-like configuration file and seems to be + stable. To complete the SoC project, the experimental version of + libc with in-process caching enabled was made. It's benchmarking + will be done in the nearest future.</p> + + <p>There were some requests for caching daemon to be able to act + like NSCD (to perform the actual nsswitch lookups by itself), so it + was modified to support this feature. But current implementation + has some restrictions and requires a lot of testing. Right now the + final polishing is being made to the project's sources, so that + they could be added to the CURRENT</p> + </body> + + <help> + <task>Extend caching daemon to support NSCD functionality</task> + + <task>Test Globus Grid Toolkit 4 patch</task> + + <task>Add support for MAC and audit related configuration files to + the nsswitch</task> + </help> + </project> + + <project cat='soc'> + <title>FreeBSD Web Site Redesign</title> + + <contact> + <person> + <name> + <given>Emily</given> + + <common>Boyd</common> + </name> + + <email>soc-emily@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Murray</given> + + <common>Stokely</common> + </name> + + <email>murray@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Web</given> + + <common>Team</common> + </name> + + <email>freebsd-www@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org" /> + + <url href="http://www.FreeBSD.org/old">Archived copy of old + site.</url> + </links> + + <body> + <p>The new website has gone live! Thanks to Emily Boyd for all her + hard work. We still have a lot of work to do to integrate + suggestions that have been made by users since we went live. The + new CSS design makes it much easier to rapidly change the look and + feel of the site, so it is easy to experiment. We're still looking + for more HTML/CSS designers to help us improve the site.</p> + </body> + </project> + + <project cat='kern'> + <title>NEWCARD</title> + + <contact> + <person> + <name> + <given>Warner</given> + + <common>Losh</common> + </name> + + <email>imp@freebsd.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Due to an email snafu, the June report was not submitted, so + this report covers since the last 6 months.</p> + + <p>Summary: The 16-bit part of NEWCARD has been greatly enhanced. + In addition, power control has become interrupt driven. Some + drivers make use of the new functionality.</p> + + <p>The pccard layer now exports the CIS for each device that is + present, even if there's no driver for the card or parts of the + card.</p> + + <p>The power up and reset sequence is now interrupt driven. This + has eliminated many of the long pauses that the system used to + experience after a card insertion. We can not play glitch-free + audio while inserting or removing a card.</p> + + <p>A number of additional cards are recognized by PC Card. In + addition, drivers now can read the CIS for more information about + the card. Drivers have been enhanced to read the CIS for MAC + addresses and the like where appropriate.</p> + + <p>The ed driver now attaches the mii bus of the AX88190 and + AX88790 fast ethernet PC Card chips. This allows better status + reporting and increased functionality for PHY chips that need some + help. The ed driver also supports the Tamarack TC5299J chipset + (including attaching its MII bus) now, the only open source OS that + does so (TC5299J cards will work with other open source OS, but + they won't report their status or attach a mii bus).</p> + + <p>A number of bugs have been fixed in the pccard or cardbus + drivers. Most of these changes have been merged into the + forthcoming 6.0. Others will be merged after the release.</p> + </body> + + <help> + <task>ExpressCard laptops have arrived with ExpressCard/54 and + ExpressCard/34 slots. It is unknown the extent of the work + necessary to support them.</task> + + <task>The ISA attachment of cbb needs work to make it fully + functional.</task> + + <task>A CIS parser in userland needs to be written. The pccardc + based CIS parser is OK, but it doesn't handle MFC cards too well. + Ideally the parser would produce output that is compatible with the + linux tool.</task> + + <task>A mechanism for CIS override is needed. We need a tool that + will take an ascii representation of the CIS and produce a binary. + We need a tool that will install the binary into the kernel and + kernel modifications to switch from the CIS that's in the card to + the faked up CIS.</task> + + <task>We need a mechanism for creating pseudo multi-function cards. + Initially, it seems that all we really need is the ability for an + arbitrary driver to add a sio companion, since that covers all the + cases I'm aware of. Resources would need to be 'donated' from the + creating driver to the sio card.</task> + + <task>It would be nice if we could move to a more common CIS + parsing and dispatch. The CardBus side is wide open at the moment + since none of the pci drivers use the CIS information outside of a + few that get their MAC address via a standard interface.</task> + + <task>The ep driver needs work to make the newer ep cards that have + mii bus on them actually probe and attach it. It needs to gain + media support for the non-mii based cards. The 3C1 still needs + work.</task> + + <task>The sn driver needs work to support many of the SMC91Cxxx PC + Card devices. These are typically combination cards that need + special, non-standard initialization.</task> + + <task>Power savings for 16-bit cards can be realized if we power + them up at 3.3V rather than at 5.0V. Not all cards can support + this, but many can and indicate this support in the CIS. Windows + tries the 3.3V configuration entries before the 5.0V ones. We + should do the same.</task> + + <task>Most of the changes that have been made to the pccard and + cardbus layers can be merged back into RELENG_5.</task> + </help> + </project> + + <project cat='vendor'> + <title>OpenBSD packet filter - pf</title> + + <contact> + <person> + <name> + <given>Max</given> + + <common>Laier</common> + </name> + + <email>mlaier@freebsd.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Further improvements have been made to pfsync to make it behave + well in SMP scenarios. All bug fixes have been MFCed to RELENG_5 + where applicable. A couple of bugfixes and feature improvements + have been imported via OpenBSD (originally suggested by FreeBSD + users).</p> + + <p>As described in the last report, FreeBSD 6.0 and future RELENG_6 + releases will be based on OpenBSD 3.7. Newer code will be imported + as soon as 6.0 has settled down a bit.</p> + </body> + </project> + + <project cat='soc'> + <title>BSD Installer</title> + + <contact> + <person> + <name> + <given>Andrew</given> + + <common>Turner</common> + </name> + + <email>soc-andrew@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.bsdinstaller.org/" /> + + <url href="http://wiki.freebsd.org/moin.cgi/BSDInstaller" /> + </links> + + <body> + <p>By the end of August I managed to modify the release building + process to build a live CD that loads the front and backends. It + could install all the distfiles, install the ports tree and had + minimal support to install and uninstall packages.</p> + + <p>Since the end of the Summer of Code I have worked to integrate + the new Lua backend. This has been successful, with it now past the + point of the BSDINSTALLER-BETA-1 release. It can install the + distfiles but not the ports tree or packages yet.</p> + </body> + </project> + + <project cat='kern'> + <title>Low-overhead performance monitoring for FreeBSD</title> + + <contact> + <person> + <name> + <given>Joseph</given> + + <common>Koshy</common> + </name> + + <email>jkoshy@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~jkoshy/projects/perf-measurement"> + Project home page</url> + </links> + + <body> + <p>This projects implements a kernel module (hwpmc(4)), an + application programming interface (pmc(3)) and a few simple + applications (pmcstat(8) and pmccontrol(8)) for measuring system + performance using event monitoring hardware in modern CPUs.</p> + + <p>The last three months have been spent in bug fixing and in + tweaking the code. A few more minor features and loose ends remain + to be taken care of. Once these are done, I hope to get started on + a graphical performance analyser.</p> + </body> + </project> + + <project cat='proj'> + <title>Realtime POSIX signal</title> + + <contact> + <person> + <name> + <given>David</given> + + <common>Xu</common> + </name> + + <email>davidxu@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The FreeBSD kernel is powerful, but it still lacks some realtime + POSIX facilities, for example, sigqueue. Most of the code is ready, + and I am testing it.</p> + </body> + + <help> + <task>POSIX timer, timer_xxx syscalls</task> + </help> + </project> + + <project cat='soc'> + <title>SNMP Monitoring</title> + + <contact> + <person> + <name> + <given>Harti</given> + + <common>Brandt</common> + </name> + + <email>harti@freebsd.org</email> + </person> + + <person> + <name> + <given>Philip</given> + + <common>Paeps</common> + </name> + + <email>philip@freebsd.org</email> + </person> + + <person> + <name> + <given>Victor</given> + + <common>Cruceru</common> + </name> + + <email>soc-victor@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/moin.cgi/VictorCruceru"> + FreeBSD wiki</url> + </links> + + <body> + <p>New MIBs are implmented for the BSNMP agent:</p> + + <ol> + <li> + <strong>HOST-RESOURCES-MIB</strong> + + ( + <a href="http://www.ietf.org/rfc/rfc2790.txt"> + http://www.ietf.org/rfc/rfc2790.txt</a> + + ). Philip is going to submit the code into the CVS + repository.</li> + + <li> + <strong>TCP-MIB with combined IPv4 & IPv6 support</strong> + + ( + <a href="http://www.ietf.org/rfc/rfc4022.txt"> + http://www.ietf.org/rfc/rfc4022.txt</a> + + ). This new TCP-MIB is 100% backward compatible with the old one + (v4 only). It adds a clear distinction between active and passive + tcp endpoints and for each endpoint info about the process it + belongs to.</li> + + <li> + <strong>UDP-MIB with combined IPv4 & IPv6 support</strong> + + ( + <a href="http://www.ietf.org/rfc/rfc4113.txt"> + http://www.ietf.org/rfc/rfc4113.txt</a> + + ). This new UDP-MIB is 100% backward compatible with the old one + (v4 only) and it adds multiple instances support for the UDP + endpoints and for each endpoint info about the processes using + it.</li> + </ol> + </body> + + <help> + <task>For HOST-RESOURCES-MIB we are going to add support for more + detailed memory stats based of libmemstat(3)</task> + + <task>The rest of the IPv6 MIBs.</task> + + <task>FreeBSD enterprise MIBs for supporting SNMP configuration + (via SNMP SETs) for FreeBSD.</task> + </help> + </project> + + <project cat='soc'> + <title>csup: cvs mode support</title> + + <contact> + <person> + <name> + <given>Christoph</given> + + <common>Mathys</common> + </name> + + <email>cmathys@bluewin.ch</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/moin.cgi/ChristophMathys"> + The wikipage with details about my SoC-project</url> + + <url href="http://mu.org/~mux/csup.html">csup project page</url> + </links> + + <body> + <p>During the "Summer of Code" I worked on csup (a rewrite of CVSup + in C). It already supported checkout-mode, so my task was to + implement support for cvs-mode. The biggest part of the project was + to implement support for rcs-files. As "byproducts" I also wrote + the necessary code to create nodes/hardlinks and to update files + using the rsync-algorithm. For what I know, the code works fine, + but errorhandling is practically inexistent.</p> + </body> + + <help> + <task>Errors should be properly handled</task> + + <task>Support to get fixups</task> + + <task>The hard part to support rcs file updates is done, but there + is no checksum, some options are not honored and the performance + could be improved</task> + </help> + </project> + + <project cat='kern'> + <title>Sound subsystem improvements</title> + + <contact> + <person> + <name> + <given>Multimedia</given> + + <common>Mailinglist</common> + </name> + + <email>multimedia@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ariff</given> + + <common>Abdullah</common> + </name> + + <email>skywizard@MyBSD.org.my</email> + </person> + + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Recently a lot of fixes, specially in handling format / rate + conversion and general stability was committed to -current. This + include fixes for most LOR's and new features (software volume + handling for soundcards without volume handling in hardware and the + possibility to switch to spdif).</p> + + <p>A lot of effort was expended by Ariff (and other people) to come up + with those improvements. For this reason Ariff was "punished" with a + commit bit, so he is able to commit further improvements on his + own.</p> + + <p>This work is not integrated into 6.0-RELEASE because of some + lose ends (see 'sndctl' below).</p> + + <p>You can help by looking at + <a + href="http://www.freebsd.org/cgi/query-pr-summary.cgi?category=&severity=&priority=&class=&state=&sort=none&text=sound&responsible=&multitext=&originator=&release="> + sound related PR's in GNATS</a> + + and making follow-up's which tell us if a problem still persists or + if a PR can be closed because the bug is fixed. Also feel free to + submit patches for anything on the TODO list below.</p> + </body> + + <help> + <task>Update manual pages to reflect new features.</task> + + <task>Fix driver specific issues (via, t4dwave, maestro).</task> + + <task>Make all drivers MPSAFE.</task> + + <task>Rewrite some parts (e.g. a new mixer subsystem with OSS + compatibility).</task> + + <task>sndctl(1): tool to control non-mixer parts of the sound + system (e.g. spdif switching, virtual-3D effects) by an user + (instead of the sysctl approach in -current); pcmplay(1), + pcmrec(1), pcmutil(1).</task> + + <task>Plugable FEEDER infrastructure. For ease of debugging various + feeder stuff and/or as userland library and test suite.</task> + + <task>Support for new hardware (envy24, Intel HDA).</task> + + <task>Performance enhancement (via 'slave'-channels, changes are + under review)?</task> + + <task>Closer compatibility with OSS, especially for the upcoming + OSS v4.</task> + + <task>Close a lot of PR's.</task> + + <task>Document the sound system in the + <a + href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/index.html"> + FreeBSD Architecture Handbook</a> + + .</task> + </help> + </project> + + <project cat='ports'> + <title>Ports Tinderbox</title> + + <contact> + <person> + <name> + <given>Joe Marcus</given> + + <common>Clarke</common> + </name> + + <email>marcus@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Tinderbox</given> + + <common>List</common> + </name> + + <email>tinderbox-list@marcuscom.com</email> + </person> + </contact> + + <links> + <url href="http://tinderbox.marcuscom.com">Tinderbox Homepage</url> + </links> + + <body> + <p>The Ports Tinderbox is a packaged system for building FreeBSD + ports in a clean environment. It can be used to test new ports, + updates to existing ports, or simply as a package building engine. + Tinderbox uses the same underlying code that the official FreeBSD + package build cluster, pointyhat, uses. So if a port builds under + Tinderbox, it is guaranteed to build on pointyhat.</p> + + <p>More and more FreeBSD committers and ports maintainers are + starting to use Tinderbox. We just released version 2.1.0 which + added much-requested PostgreSQL support as well as fixed many bugs. + We expect a 2.1.1 release soon with some additional bug fixes.</p> + + <p>With the 2.1.0 release of Tinderbox, we have branched the code + base so that we can focus on larger features in our HEAD branch + while still producing stable releases on a more frequent basis. The + biggest new feature planned for Tinderbox 3.0 is clustering support + which is being spearheaded by Ade Lovett (ade).</p> + </body> + + <help> + <task>At this point, we really need help with documentation. Work + has begun on creating man pages for the various Tinderbox commands, + but we need help to churn them out at as faster rate. If you have + strong mdoc fu, and interested in helping us out, please contact + <a href="mailto:marcus@marcuscom.com">marcus@marcuscom.com</a> + + .</task> + </help> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2005-10-2005-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2005-10-2005-12.xml new file mode 100644 index 0000000000..c3e261a62b --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2005-10-2005-12.xml @@ -0,0 +1,1370 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<report> + <date> + <month>October-December</month> + + <year>2005</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report is about the rather quiet last quarter of 2005, with + the release of FreeBSD 6.0 and the holiday season things evolved in + the background. Nonetheless, most exciting projects hit the tree (or + are going to very soon).</p> + + <p>Upcoming events, such as the release of FreeBSD 6.1/5.5 and the + third BSDCan conference with a big developer summit promise to + provide a busier start in 2006. The foundation for upcoming + development, however, are the projects that are described herein.</p> + + <p>We hope that you find interesting projects to look at or work on. + The next status report collection will be April 7 2006. We are + looking forward to your report then.</p> + + <p>Thanks again to everyone who submitted reports, and thanks to Brad + Davis who stepped up for an extensive spelling and grammar review. + Enjoy reading!</p> + </section> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>doc</name> + + <description>Documentation</description> + </category> + + <category> + <name>team</name> + + <description>FreeBSD team reports</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>net</name> + + <description>Network infrastructure</description> + </category> + + <category> + <name>bin</name> + + <description>Userland programs</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <category> + <name>vendor</name> + + <description>Vendor / 3rd Party Software</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='proj'> + <title>jemalloc</title> + + <contact> + <person> + <name> + <given>Jason</given> + + <common>Evans</common> + </name> + + <email>jasone@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>libc's malloc implementation has been replaced with an + implementation that is designed to scale well for multi-threaded + applications running on multi-processor systems. This is + accomplished by creating multiple allocation arenas that are + independent of each other, and permanently assigning threads to + these arenas. In the common case, threads do not access the same + allocator arena at the same time, which reduces contention and + cache sloshing.</p> + + <p>Single-threaded application performance is approximately + equivalent to what it was with phkmalloc, but for multi-threaded + applications that make heavy use of malloc, the performance + difference can be huge (orders of magnitude).</p> + + <p>As with phkmalloc, the new malloc implementation supports + runtime configuration via the MALLOC_OPTIONS environment variable. + See the malloc(3) manpage for details on supported options, as well + as more information about the allocator's architecture.</p> + </body> + </project> + + <project cat='bin'> + <title>OpenBSD dhclient</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The OpenBSD rewrite of dhclient has been imported, replacing the + ISC dhclient. The OpenBSD client provides better support for + roaming on wireless networks and a simpler model of operation. + Instead of a single dhclient process per system, there is one per + network interface. This instance automatically goes away in the + even of link loss and is restarted via devd when link is + reacquired. To support this change, many aspects of the network + interface configuration process were overhauled.</p> + + <p>Support for adding aliases to DHCP configured interfaces has + been committed to CURRENT and will be merged before 6.1-RELEASE. + Soon work will begin to merge changes from OpenBSD that have taken + place since the initial import.</p> + + <p>Work on further interface configuration enhancements is underway + for FreeBSD 7.0.</p> + </body> + </project> + + <project cat='net'> + <title>FAST_IPSEC Upgrade</title> + + <contact> + <person> + <name> + <given>George</given> + + <common>Neville-Neil</common> + </name> + + <email>gnn@freebsd.org</email> + </person> + + <person> + <name> + <given>Bjoern A.</given> + + <common>Zeeb</common> + </name> + + <email>bz@freebsd.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Currently splitting out the rest of the PF_KEY data-structures + from the key database. This will mean the user level applications + and the kernel will not share datastructures and that they can, + hopefully, advance on their own without being in lockstep.</p> + </body> + + <help> + <task>Calculate diffs between Kame IPv4 version of IPSec and + FAST_IPSEC and upgrade FAST to the latest standards.</task> + + <task>Add IPv6 support to FAST_IPSEC.</task> + </help> + </project> + + <project cat='doc'> + <title>FreeBSD list of projects and ideas for volunteers (TODO list + for volunteers)</title> + + <contact> + <person> + <name> + <given>Joel</given> + + <common>Dahl</common> + </name> + + <email>joel@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/ideas/" /> + </links> + + <body> + <p>The "TODO list for volunteers" is now committed as the "FreeBSD + list of projects and ideas for volunteers". So far the interest in + the list is high and some volunteers already took the opportunity + to start tackling some of the entries.</p> + + <p>Unfortunately the FreeBSD project does not have enough human + resources to provide a technical contact for every entry. + Interested volunteers should not be afraid to try to come up with a + solution for an entry without a technical contact. The people on + the hackers and current mailing list are typically very helpful + regarding answering specific questions (as long as they know the + answer...).</p> + + <p>We are looking forward to hear about new ideas, people willing + to be technical contacts for generic topics (e.g. USB) or specific + entries (already existing or newly created), suggestions for + existing entries or completion reports for (parts of) an entry.</p> + </body> + + <help> + <task>Add more ideas.</task> + + <task>Find more technical contacts.</task> + </help> + </project> + + <project cat='net'> + <title>KAME Project Status Report</title> + + <contact> + <person> + <name> + <given>SUZUKI</given> + + <common>Shinsuke</common> + </name> + + <email>suz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.kame.net/">KAME Project Homepage</url> + + <url href="http://www.kame.net/newsletter/20051107/" /> + + <url + href="http://www.wide.ad.jp/news/press/20051107-KAME-e.html" /> + + <url + href="http://ipv6style.jp/en/special/kame/20051205/index.shtml" /> + </links> + + <body> + <p>Most of the latest KAME code has been merged to 7-current and + 6-stable, to prepare for the project conclusion in March 2006. For + the same reason, we moved some ports applications (security/racoon, + net/pim6sd, net/pim6dd, net/dhcp6) from KAME to + sourceforge.net.</p> + + <p>Some of the items (e.g. IGMPv3/MLDv2, Mobile-IPv6/NEMO, SCTP, + DCCP, ISATAP) are not merged yet from the latest KAME code for + several reasons. Other projects will continue to merge their + work.</p> + </body> + + <help> + <task>remove __P() macros</task> + + <task>set net.inet6.ip6.kame_version to a more appropriate date + :-)</task> + + <task>update src/sys/netinet6/README</task> + </help> + </project> + + <project cat='kern'> + <title>Sound subsystem improvements</title> + + <contact> + <person> + <name> + <given>Ariff</given> + + <common>Abdullah</common> + </name> + + <email>ariff@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Multimedia</given> + + <common>Mailinglist</common> + </name> + + <email>multimedia@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~ariff/">Patches for + RELENG_5.</url> + + <url href="http://www.FreeBSD.org/projects/ideas/">The FreeBSD + Project Ideas List.</url> + </links> + + <body> + <p>A lot of changes have taken place in the sound system since the + last status report. They range from less hiccups and distortion by + disk accesses and/or driver bugs to new and improved features + (software volume control implemented for soundcards which do not + have hardware volume control). Additionally a new driver + (snd_atiixp) has seen the light and a lot of problem reports were + fixed.</p> + + <p>Most of those changes and the changes mentioned in the previous + status report are already merged to RELENG_6 and will be part of + 6.1-RELEASE.</p> + </body> + + <help> + <task>Have a look at the sound related entries on the ideas + list.</task> + + <task>Rewrite some parts (e.g. a new mixer subsystem with OSS + compatibility).</task> + + <task>sndctl(1): tool to control non-mixer parts of the sound + system (e.g. spdif switching, virtual-3D effects) by an user + (instead of the sysctl approach in -current); pcmplay(1), + pcmrec(1), pcmutil(1).</task> + + <task>Plugable FEEDER infrastructure. For ease of debugging various + feeder stuff and/or as userland library and test suite.</task> + + <task>Support for new hardware (envy24, Intel HDA).</task> + + <task>Performance enhancement (via 'slave'-channels).</task> + + <task>Closer compatibility with OSS, especially for the upcoming + OSS v4.</task> + </help> + </project> + + <project cat='doc'> + <title>Problem Report Database</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>bugmeister_at_freebsd_dot_org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/support.html#gnats">GNATS</url> + </links> + + <body> + <p>The experiment to add 'tags' to many of the kern and related + PRs, including such things as '[nfs]', '[fxp]', and so forth, + continues. In addition, PRs with patches have been more + consistently tagged with '[patch]'. Two new periodic reports based + on both functional tags and PRs with patches have been added, with + the goal of making these PRs more visible.</p> + </body> + </project> + + <project cat='team'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/ports/">The FreeBSD ports + collection</url> + + <url href="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD + ports unfetchable distfile survey (Bill Fenner's report)</url> + + <url href="http://edwin.adsl.barnet.com.au/~edwin/ports/">FreeBSD + ports updated distfile survey (Edwin Groothius' report)</url> + + <url href="http://portsmon.FreeBSD.org/index.html">FreeBSD ports + monitoring system</url> + + <url href="http://www.freebsd.org/portmgr/index.html">The FreeBSD + Ports Management Team</url> + + <url href="http://tinderbox.marcuscom.com">marcuscom + tinderbox</url> + </links> + + <body> + <p>During this time, the number of ports PRs briefly dipped below + 500 -- a number not seen since late 2000, when there were 4000 + ports instead of our new total of over 14,000 ports. This is due to + the hard work of a large number of individuals, including pav, + edwin, mnag, garga, and many others. Congratulations folks! Some of + this was due to more aggressively committing PRs where the + maintainer had not responded within the timeout period. Although + controversial, this new policy seems to be succeeding in its goal + of improving the Ports Collection.</p> + + <p>A new file, ports/KNOBS, was added by ahze to help bring some + order in the chaos that had been the OPTIONS namespace.</p> + + <p>dougb has changed the way that rc.d works in -HEAD to work more + like the base rc.d scripts. We are hoping that this change will + make ports maintenance easier in the future. However, in the + meantime a few bugs have been introduced (which we intend to have + fixed by the time 6.1 is released). While this regression is + unfortunate, it was decided that now was the best time to try to + make this change rather than waiting for 7.0. We hope our users can + be patient with us in the interim.</p> + + <p>Work continues to improve the marcuscom ports tinderbox, with + new features added by marcus, aDe, and edwin in particular. Several + ports committers are now running their own copies to test ports + changes.</p> + + <p>The www.FreeBSD.org/ports page, and the portmgr web pages, were + reworked as well.</p> + + <p>We have added 4 new committers since the last report.</p> + </body> + + <help> + <task>Progress has been made in cracking down on ports that do not + correctly install when LOCALBASE is not /usr/local, but some ports + remain.</task> + + <task>portmgr would like to remind committers that PRs for their + ports should be handled (either committed or marked 'suspended' or + 'analyzed') within the two week timeout period. In this way other + committers do not have to invoke the maintainer timeout and things + will work more smoothly.</task> + </help> + </project> + + <project cat='net'> + <title>Early Binding Updates and Credit-Based Authorization for the + Kame-Shisa Mobile IPv6 Software</title> + + <contact> + <person> + <name> + <given>Christian</given> + + <common>Vogt</common> + </name> + + <email>chvogt@tm.uka.de</email> + </person> + </contact> + + <links> + <url href="http://www.tm.uka.de/~chvogt/ebucba/">Download patch + here.</url> + + <url + href="http://doc.tm.uka.de/2005/draft-vogt-mobopts-early-binding-updates-00.txt"> + [1]</url> + + <url + href="http://doc.tm.uka.de/2005/draft-vogt-mobopts-credit-based-authorization-00.txt"> + [2]</url> + </links> + + <body> + <p>Based on the Kame-Shisa Mobile IPv6 Software for FreeBSD 5.4, we + implemented the performance optimization "Early Binding Updates" + and "Credit-Based Authorization". The combined optimizations + facilitate significant reductions in handoff delay without + compromising protocol security [1][2].</p> + </body> + </project> + + <project cat='misc'> + <title>A Comprehensive Delay Analysis for Reactive and Proactive + Handoffs with Mobile IPv6 Route Optimization</title> + + <contact> + <person> + <name> + <given>Christian</given> + + <common>Vogt</common> + </name> + + <email>chvogt@tm.uka.de</email> + </person> + </contact> + + <links> + <url + href="http://doc.tm.uka.de/2006/vogt-2006-delay-analysis-for-reactive-and-proactive-handoffs.pdf"> + Download document here.</url> + </links> + + <body> + <p>Optimizations to reduce handoff delays inherent in Mobile IPv6 + Route Optimization as well as IPv6 router discovery, address + configuration, and movement detection have so far been mostly + considered on an individual basis. This document evaluates three + integrated solutions for improved handoff experience in + surroundings with different preconditions: reactive handoffs with + unmodified routers, reactive handoffs with router support, and + movement anticipation and proactive handoff management.</p> + </body> + </project> + + <project cat='team'> + <title>FreeBSD Security Officer and Security Team</title> + + <contact> + <person> + <name> + <given>Security</given> + + <common>Officer</common> + </name> + + <email>security-officer@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Security</given> + + <common>Team</common> + </name> + + <email>security-team@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/security/" /> + + <url + href="http://www.freebsd.org/administration.html#t-secteam" /> + + <url href="http://vuxml.freebsd.org/" /> + </links> + + <body> + <p>This report covers the period July 2005 - January 2006, since + the FreeBSD Security Team did not submit a status report for July - + October 2005.</p> + + <p>In August 2005, the long-time Security Officer, Jacques Vidrine, + stepped down and was replaced by Colin Percival. Jacques remains + with the team as Security Officer Emeritus, and the team thanks him + for all his work over the past four years.</p> + + <p>Also in August 2005, Dag-Erling C. Smørgrav was replaced by + Simon L. Nielsen as Deputy Security Officer. In addition, Tom + Rhodes and Guido van Rooij retired from the team in September 2005 + and January 2006 respectively in order to devote their time to + other parts of the FreeBSD project. The current Security Team + membership is published on the web site.</p> + + <p>In the time since the last status report, ten security + advisories have been issued (five in 2005, five in 2006) concerning + problems in the base system of FreeBSD; of these, four problems + were in "contributed" code, while six were in code maintained + within FreeBSD. The Vulnerabilities and Exposures Markup Language + (VuXML) document has continued to be updated by the Security Team + and the Ports Committers documenting new vulnerabilities in the + FreeBSD Ports Collection; since the last status report, 117 new + entries have been added, bringing the total up to 636.</p> + + <p>The following FreeBSD releases are supported by the FreeBSD + Security Team: FreeBSD 4.10, FreeBSD 4.11, FreeBSD 5.3, FreeBSD + 5.4, and FreeBSD 6.0. Their respective End of Life dates are listed + on the web site.</p> + </body> + </project> + + <project cat='proj'> + <title>FreeSBIE</title> + + <contact> + <person> + <name> + <given>FreeSBIE</given> + + <common>staff</common> + </name> + + <email>staff@freesbie.org</email> + </person> + </contact> + + <links> + <url href="http://www.freesbie.org" /> + + <url href="http://torrent.freesbie.org" /> + + <url href="freesbie@gufi.org" /> + </links> + + <body> + <p>Development is going on after the complete rewrite of the + toolkit. There are many plugins available and we're testing a new + implementation of unionfs for 6.x. Since it's a bit unstable, it + won't be included in the release anyway. Developers hope to enter + the BETA state on February 1st, to release an -RC image around + February 15th and the RELEASE around March 1st. We need more people + to test the images we provide. Torrents for them are available at + <a href="http://torrent.freesbie.org">torrent.freesbie.org</a> + + .</p> + </body> + + <help> + <task>A new BETA Release, based on 6-STABLE, is available for + testing.</task> + </help> + </project> + + <project cat='proj'> + <title>variant symlinks</title> + + <contact> + <person> + <name> + <given>Andrey</given> + + <common>Elsukov</common> + </name> + + <email>bu7cher@yandex.ru</email> + </person> + </contact> + + <links> + <url href="http://butcher.heavennet.ru/patches/kernel/varsym/" /> + </links> + + <body> + <p>The port of DragonFly's variant symlinks ( + <a href="http://freebsd.org/projects/ideas/#p-magicsymlinks"> + project ideas</a> + + ) to FreeBSD. Variant symlinks is a dynamic symbolic link + implementation. Source file of a variant symlink may contain one or + more variable names. Each of these variable names is enclosed in + braces and preceded by a dollar sign in the style of variable + references in sh(1). Whenever a variant symlink is followed, each + variable found in source file is replaced by its associated value. + In this manner, a variant symlink may resolve to different paths + based on context.</p> + </body> + + <help> + <task>Document a new system calls.</task> + + <task>More testing.</task> + + <task>Write the rc.d script for the variant symlinks + initialization.</task> + </help> + </project> + + <project cat='misc'> + <title>BSDCan 2006</title> + + <contact> + <person> + <name> + <given>Dan</given> + + <common>Langille</common> + </name> + + <email>dan@langille.org</email> + </person> + </contact> + + <links> + <url href="http://www.bsdcan.org/" /> + </links> + + <body> + <p>We are well into the process of selecting the talks for BSDCan + 2006. Our new + <a href="http://www.bsdcan.org/2006/committee.php">program + committee</a> + + has a hard selection task over the new few weeks. The deadline for + the + <a href="http://www.bsdcan.org/2006/papers.php">Call For Papers</a> + + has passed, but it's not too late to submit a talk. Please see the + above URL for details. After the success of the + <a href="http://www.bsdcan.org/2005/activity.php?id=72">Work in + Progress last year</a> + + , we are going to do it again this year. If you are working on + something you'd like to tell the world about, considering giving a + 5 minute talk at BSDCan. The + <a href="http://www.bsdcan.org/2006/registration.php">registration + prices for BSDCan 2006</a> + + will be the same as they were for + <a href="http://www.bsdcan.org/2005/registration.php">2005</a> + + . We will be again in the SITE building at University of Ottawa and + you'll have lots of opportunity to meet with people from all over + the world. Be sure to make your travel plans now and don't miss out + on the biggest BSD event this year: BSDCan 2006.</p> + </body> + + <help> + <task>We're looking for volunteers to help out just before and + during the conference. Contact Dan at the above address.</task> + + <task>If you have a talk you'd like to present, contact Dan at the + above address.</task> + </help> + </project> + + <project cat='ports'> + <title>FreshPorts</title> + + <contact> + <person> + <name> + <given>Dan</given> + + <common>Langille</common> + </name> + + <email>dan@langille.org</email> + </person> + </contact> + + <links> + <url href="http://www.freshports.org/" /> + </links> + + <body> + <p> + <a href="http://www.freshports.org/">FreshPorts</a> + + recently moved to a new webserver. This should speed things up + considerably.</p> + + <p>You can read all about the new hardware on the recently + introduced + <a href="http://news.freshports.org/">FreshPorts Blog</a> + + . This blog will include technical discussions about ports and the + problems they present with respect to FreshPorts. Site + announcements will be posted there. As bugs are found, they will be + listed, as well as their fixes.</p> + + <p>Supporting multiple platforms and architectures is still in the + development stage. Lack of time is affecting progress.</p> + + <p>A fix for virtual ports is in the works. I'm also going to + implement more caching to speed things up. If interested in + discussing the options there, please get involved in the blog.</p> + </body> + </project> + + <project cat='doc'> + <title>The FreeBSD Dutch Documentation Project</title> + + <contact> + <person> + <name> + <given>Remko</given> + + <common>Lodder</common> + </name> + + <email>remko@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Siebrand</given> + + <common>Mazeland</common> + </name> + + <email>s.mazeland@xs4all.nl</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/doc/nl/books/handbook">FreeBSD + released handbook</url> + + <url href="http://www.freebsd-nl.org/doc/nl">Preview + documentation</url> + + <url href="http://www.freebsd-nl.org/www/nl/">Preview website</url> + </links> + + <body> + <p>The FreeBSD Dutch Documentation Project is an ongoing project, + focussed on translating the English documentation and website to + the Dutch language. Currently we are almost done with the FreeBSD + Handbook and started the initial translation of the FreeBSD + Website. We are always looking for people to help out, if you can + help, please contact Siebrand or me so that we can divide the work + amongst us.</p> + + <p>Recent publications: + <br /> + + Recently the Printing and the Serial Communications chapters were + added to the FreeBSD Dutch Handbook.</p> + + <p>Recently started items: + <br /> + + We started with the translation of the PPP and SLIP chapter and the + translation of the website.</p> + </body> + + <help> + <task>Translate the final parts of the FreeBSD handbook.</task> + + <task>Translate the FreeBSD Website</task> + </help> + </project> + + <project cat='arch'> + <title>FreeBSD/xbox</title> + + <contact> + <person> + <name> + <given>Rink</given> + + <common>Springer</common> + </name> + + <email>rink@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://xbox-bsd.nl">FreeBSD/xbox project page.</url> + </links> + + <body> + <p>FreeBSD/xbox support is nearing completion. Patches are + available for nve(4) ethernet support, as well as a + syscons(4)-capable console. I am working to integrate these in + CURRENT, a backport to 6.x is planned too.</p> + + <p>Work is under way to support X.Org as well; people with more + detailed knowledge of X.Org are welcome to assist.</p> + </body> + + <help> + <task>Enable framebuffer support in X.Org</task> + + <task>Figure out a way to use mfsroots without using + loader(8)</task> + </help> + </project> + + <project cat='kern'> + <title>LSI MegaRAID improvements</title> + + <contact> + <person> + <name> + <given>Scott</given> + + <common>Long</common> + </name> + + <email>scottl@freebsd.org</email> + </person> + + <person> + <name> + <given>Doug</given> + + <common>Ambrisko</common> + </name> + + <email>ambrisko@freebsd.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Major work has gone into improving both the performance of the + LSI MegaRAID (amr) driver, and in adding Linux compatibility + support. SMPng locking was added in Oct 2005 as well as a number of + performance improvements. The result is 138% performance + improvement in some local transaction tests.</p> + + <p>Throughout 2005 a lot of work has gone into adding Linux + compatibility to the driver. It is now possible to run many of the + LSI-provided management apps for Linux under FreeBSD. Both this + feature and the performance improvements are in the 7-CURRENT + development branch of FreeBSD and are scheduled to be backported in + time for the FreeBSD 6.1 release.</p> + </body> + </project> + + <project cat='kern'> + <title>E1000 driver improvements</title> + + <contact> + <person> + <name> + <given>Scott</given> + + <common>Long</common> + </name> + + <email>scottl@freebsd.org</email> + </person> + + <person> + <name> + <given>Andre</given> + + <common>Opperman</common> + </name> + + <email>andre@freebsd.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>In an effort to solve the 'interrupt aliasing' problem that + plagues many motherboards under FreeBSD, I modified the Intel e1000 + network driver (if_em) to use a combination of fast interrupts and + taskqueues. This technique avoids interrupt threads entirely, which + in turn avoids triggering the aliasing problem in the Intel APIC. + The result is that the driver now handles and masks interrupts + immediately, and a private taskqueue is then scheduled to run to + process the link events and rx/tx events. A side effect of this + asynchronous processing is that it acts much as traditional polling + does, in that the amount of work done in the taskqueue can be + controlled, and the taskqueue rescheduled to process work at a + later time. This leads to the driver having the low-latency + benefits of interrupts and the workload segmentation of polling, + all without complicated heuristics. Several users have reported + that the driver can handle higher loads than traditional polling + without deadlocks.</p> + + <p>Along with this work, I modified the SMPng locking in the driver + so that no lock is required for the RX path. Since this path is + already implicitly serialized by the interrupt and/or taskqueue + and/or polling handler (all of which are exclusive to each other), + there was no need for extra synchronization. This has two benefits. + The first is reduction in processing overhead to unlock and lock + the driver for every RX packet, and significant reduction in + contention of the driver lock when transmitting and receiving + packets at the same time. I believe that it is further possible to + run the TX-complete path without a lock, further reducing overhead + and contention for high transmit loads. The reduced contention also + greatly benefited the fast-forward bridging code in FreeBSD, with + up to 25% performance improvement seen, as well as lower CPU + utilization.</p> + + <p>The work can be found in FreeBSD 7-CURRENT for now. There are + still some rough edges relating to falling back to traditional + ithread and polling behavior, and I do not intend to merge the + changes back to FreeBSD 6.x until these are resolved. I also hope + to extend the INTR_FAST+taskqueue model into a general framework + for doing Mac OSX style filter interrupts. The work in the if_em + driver can also be extended to other high-performance network + drivers such as if_bge and if_ti. Any help with investigating these + topics is welcomed.</p> + </body> + </project> + + <project cat='team'> + <title>Release Engineering Status Report</title> + + <contact> + <person> + <name> + <given>RE</given> + + <common>Team</common> + </name> + + <email>re@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/releng" /> + + <url href="http://www.freebsd.org/releases" /> + </links> + + <body> + <p>Another very busy year for the FreeBSD Release Engineering Team. + Recognizing the problems, both technical and emotional, surrounding + the FreeBSD 5.x releases, our primary focus was in getting the bugs + out of FreeBSD 6.0 and getting it released. We succeeded at that + quite well, and the 6.0 release on Nov 18 was a huge success for + the project. Many thanks to all of the developers who put in + countless hours fixing bugs and improving performance, and to the + users who helped find, fix, and verify bugs.</p> + + <p>Moving forward to 2006, we plan on doing a joint release of + FreeBSD 5.5 and 6.1 in late March. The 5.5 release will mark the + end of active FreeBSD 5.x development and releases, and is intended + to help users who have not yet switched to FreeBSD 6. It consists + primarily of bug fixes and minor improvements. FreeBSD 6.1 will be + an upgrade to 6.0 and will include new drivers, better performance + in certain areas, as well as bug fixes. We expect to release + FreeBSD 6.2 and 6.3 later in 2006.</p> + </body> + </project> + + <project cat='net'> + <title>New Networking Features in FreeBSD 6.0</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~andre/New%20Networking%20Features%20in%20FreeBSD%206%20-%20Presentation.pdf"> + Presentation</url> + + <url + href="http://people.freebsd.org/~andre/New%20Networking%20Features%20in%20FreeBSD%206%20-%20Paper.pdf"> + Paper</url> + + <url href="http://www.eurobsdcon.org">EuroBSDCon 05</url> + </links> + + <body> + <p>FreeBSD 6 has evolved drastically in the development branch + since FreeBSD 5.3 and especially so in the network area. The + presentation and paper give an in-depth overview of all network + stack related enhancements, changes and new code with a narrative + on their rationale.</p> + </body> + </project> + + <project cat='net'> + <title>Optimizing the FreeBSD IP and TCP Stack</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~andre/Optimizing%20the%20FreeBSD%20IP%20and%20TCP%20Stack%20-%20Presentation.pdf"> + Presentation</url> + + <url + href="http://people.freebsd.org/~andre/Optimizing%20the%20FreeBSD%20IP%20and%20TCP%20Stack%20-%20Paper.pdf"> + Paper</url> + + <url href="http://www.eurobsdcon.org">EuroBSDCon 05</url> + + <url href="http://people.freebsd.org/~andre/tcpoptimization.html"> + TCP/IP Optimization Fundraiser 2005</url> + </links> + + <body> + <p>FreeBSD has gained fine grained locking in the network stack + throughout the 5.x-RELEASE series cumulating in 6.0-RELEASE. + Hardware architecture and performance characteristics have evolved + significantly since various BSD networking subsystems have been + designed and implemented. This paper gives a detailed look into the + implementation and design changes in FreeBSD 7-CURRENT to extract + the maximum network performance from the underlying hardware.</p> + + <p>Sponsored by: TCP/IP Optimization Fundraiser 2005</p> + </body> + </project> + + <project cat='misc'> + <title>TCP/IP Optimization Fundraiser Status</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~andre/tcpoptimization.html"> + TCP/IP Optimization Fundraiser 2005</url> + + <url + href="http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/em/if_em.c?rev=1.98&content-type=text/x-cvsweb-markup"> + em(4) driver commit</url> + + <url + href="http://www.freebsd.org/news/status/report-july-2005-oct-2005.html#TCP-&-IP-Routing-Optimization-Fundraise"> + Previous Status Report</url> + </links> + + <body> + <p>The fundraiser has been very successful and I want to thank + everyone who has pledged their support and tipped the jar. The full + amount plus a little bit more has been raised in a very short + timeframe. More information on the exact amounts and their sponsors + can be found at the first link.</p> + + <p>After the delays on this project caused by the FreeBSD 6.0 + Release cycle code freeze work has picked up and a paper was + written and a presentation held on "Optimizing the FreeBSD IP and + TCP Stack" for EuroBSDCon 05 on November 27th. See related status + report under that title.</p> + + <p>From December 21st to January 11th I received access to a + calibrated Agilent N2X gigabit tester and traffic generator. Stock + FreeBSD 7-current was tested and profiled extensively in this + timeframe. A first proof of concept optimization was developed in + cooperation with Scott Long. It involved converting the Intel + Gigabit ethernet em(4) driver to make use of fast interrupt + handlers, taskqueues and lockless RX ring handling. This improved + the performance from 570kpps to 750kpps, a 25% improvement, with IP + fastforwarding enabled.</p> + </body> + + <help> + <task>A large number of profiles and measurements was taken and a + detailed report on the performance characteristics and remaining + bottlenecks is under preparation.</task> + + <task>Further optimizations and new features described on the + Optimization Fundraiser page.</task> + </help> + </project> + + <project cat='kern'> + <title>Bt878 Audio Driver (aka FusionHDTV 5 Lite)</title> + + <contact> + <person> + <name> + <given>John-Mark</given> + + <common>Gurney</common> + </name> + + <email>jmg@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fbktrau%2F...&ignore=GO%21"> + Perforce source repository</url> + </links> + + <body> + <p>Basic audio capture is working. All of the parameters are set by + userland, while the RISC program generation is by kernel. No real + audio has been captured as there are no drivers for the tuner yet. + Someone with a real Bt878 NTSC card that is supported by bktr(4) + could use this to capture audio w/o using the sound card.</p> + + <p>The real goal of this driver is to make HD capture possible with + the DViCO FusionHDTV5 Lite card that I have. I have some of the + documentation that I need, but I'm still missing two key docs. The + docs for the LGDT3303 ATSC/8VSB/QAM demodulator chip and a block + diagram of the board showing which GPIO lines go where and how the + chips are interconnected. DViCO has been responsive in + acknowledging my emails, but they have yet to produced any data + besides pointing me to the Linux driver (which is difficult to + figure out stuff by).</p> + </body> + + <help> + <task>Complete basic capture driver.</task> + + <task>Make the bktr(4) drive cleanly attach to the card, and + possibly add support for analog capture.</task> + </help> + </project> + + <project cat='vendor'> + <title>SysKonnect/Marvell Yukon device driver</title> + + <contact> + <person> + <name> + <given>Karim</given> + + <common>Jamal</common> + </name> + + <email>support@syskonnect.de</email> + </person> + </contact> + + <links> + <url href="http://www.marvell.com" /> + + <url href="http://www.syskonnect.de" /> + </links> + + <body> + <p>This project provides support for SysKonnect's SK-98xx, + SK-95xx,SK-9Exx and SK-9Sxx PCI/PCI-Express Gigabit Ethernet + adapters via the yk(4) driver, as well as Marvell's Yukon LOM + Gigabit Ethernet controllers via the myk(4) driver. Driver source + has been made available to selected members of the FreeBSD + project.</p> + </body> + </project> + + <project cat='arch'> + <title>FreeBSD on Xen 3.0</title> + + <contact> + <person> + <name> + <given>Kip</given> + + <common>Macy</common> + </name> + + <email>kip.macy@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://www.fsmware.com/xenofreebsd/7.0/STATUS">current + status</url> + </links> + + <body> + <p>Full domU support in p4 branch of -CURRENT, except suspend / + restore. Dom0 work is in progress. Scott Long is working on xenbus + integration with newbus. After newbus integration it will go into + CVS. I hope to see it MFCed to RELENG_6 so it will be available for + 6.1.</p> + </body> + + <help> + <task>Port the backend drivers from Linux.</task> + + <task>Port the domain management tools from Linux.</task> + + <task>Add multiboot support to loader(8) to support it booting + xen.</task> + + <task>SMP, x86_64, and PAE support.</task> + </help> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2006-01-2006-03.xml b/en_US.ISO8859-1/htdocs/news/status/report-2006-01-2006-03.xml new file mode 100644 index 0000000000..74d7ce8226 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2006-01-2006-03.xml @@ -0,0 +1,1467 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<report> + <date> + <month>January-March</month> + + <year>2006</year> + </date> + + <section> + <title>Introduction</title> + + <p>The highlights of this quarters report certainly include the + availability of native Java binaries thanks to the + <a href="http://www.freebsdfoundation.org/">FreeBSD Foundation</a> + + , as well as progress has been made with Xen support and Sun's + Ultrasparc T1. Furthermore we are looking forward to FreeBSD 6.1 and + TrustedBSD audit support has been imported into FreeBSD 7-CURRENT. + All in all, a very exiting start to 2006.</p> + + <p>In just under a month the developers will be gathering at + <a href="http://www.bsdcan.org/2006/">BSDCan 2006</a> + + for, FreeBSD Dev Summit, a two day meeting of FreeBSD developers. + Once again the + <a href="http://www.bsdcan.org/2006/schedule.php">BSDCan schedule</a> + + is filled with many interesting talks.</p> + + <p>We hope you enjoy reading and look forward to hear from you for + the next round. Consult the list of + <a href="http://www.freebsd.org/projects/ideas/">projects and + ideas</a> + + for ways to get involved. The submission date for the second quarter + reports will be July, 7th 2006.</p> + + <p>Thanks to everybody who submitted a report and to Brad Davis, who + joined the Status Report team, for proof reading.</p> + </section> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>net</name> + + <description>Network infrastructure</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>doc</name> + + <description>Documentation</description> + </category> + + <category> + <name>bin</name> + + <description>Userland programs</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <category> + <name>vendor</name> + + <description>Vendor / 3rd Party Software</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='misc'> + <title>FreeBSD Security Officer and Security Team</title> + + <contact> + <person> + <name> + <given>Security</given> + + <common>Officer</common> + </name> + + <email>security-officer@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Security</given> + + <common>Team</common> + </name> + + <email>security-team@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/security/" /> + + <url + href="http://www.freebsd.org/administration.html#t-secteam" /> + + <url href="http://vuxml.freebsd.org/" /> + </links> + + <body> + <p>In March 2006, Marcus Alves Grando, George Neville-Neil, and + Philip Paeps joined the FreeBSD Security Team. The current Security + Team membership is published on the web site.</p> + + <p>In the time since the last status report, eight security + advisories have been issued concerning problems in the base system + of FreeBSD; of these, three problems were in "contributed" code, + while five were in code maintained within FreeBSD. The + Vulnerabilities and Exposures Markup Language (VuXML) document has + continued to be updated by the Security Team and the Ports + Committers documenting new vulnerabilities in the FreeBSD Ports + Collection; since the last status report, 50 new entries have been + added, bringing the total up to 686.</p> + + <p>The following FreeBSD releases are supported by the FreeBSD + Security Team: FreeBSD 4.10, FreeBSD 4.11, FreeBSD 5.3, FreeBSD + 5.4, and FreeBSD 6.0. Upon their release, FreeBSD 5.5 and FreeBSD + 6.1 will also be supported. The respective End of Life dates of + supported releases are listed on the web site; of particular note, + FreeBSD 4.10 and FreeBSD 5.4 will cease to be supported at the end + of May 2006.</p> + </body> + </project> + + <project cat='net'> + <title>FreeBSD NFS Status Report</title> + + <contact> + <person> + <name> + <given>Chuck</given> + + <common>Lever</common> + </name> + + <email>cel@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Support for NFS in FreeBSD received a boost this quarter as a + kernel developer from Network Appliance has volunteered to help + with the clients. Chuck Lever is now a src committer, mentored by + Mike Silbersack. Mohan Srinivasan and Jim Rees have ended their + apprenticeships and are now full committers. Mohan continues his + effort to make the NFSv2/3 client SMP safe. He expects to make the + changes available for review soon.</p> + + <p>FreeBSD gained presence at the annual NFS interoperability event + known as Connectathon. Rick Macklem's FreeBSD NFSv4 server is + pretty stable now and available via anonymous ftp. NFSv4.1 features + are not a part of it yet and are not likely to happen until at + least the end of 2006. Contact rick@snowhite.cis.uoguelph.ca for + details.</p> + </body> + </project> + + <project cat='misc'> + <title>BSDCan</title> + + <contact> + <person> + <name> + <given>Dan</given> + + <common>Langille</common> + </name> + + <email>dan@langille.org</email> + </person> + </contact> + + <links> + <url href="http://www.bsdcan.org/2006/" /> + </links> + + <body> + <p>The + <a href="http://www.bsdcan.org/2006/schedule.php">schedule</a> + + for BSDCan 2006 demonstrates just how strong and popular BSDCan has + become in a very short time. Three concurrent streams of talks make + sure that there is something for everyone. We provide high quality + talks at very affordable + <a href="http://www.bsdcan.org/2006/registration.php">prices</a> + + .</p> + + <p>BSDCan is the biggest BSD event of 2006. Ask others who attended + in past years how much they enjoyed their time in Ottawa. Ask them + who they met, who they talked to, the contacts they made, the + information they learned.</p> + + <p>Remember to bring your wife/husband/spouse/etc because we will + have things for them to do while you are attending the conference. + Ottawa is a fantastic tourist destination.</p> + + <p>See you at BSDCan 2006!</p> + </body> + + <help> + <task> + <a href="http://www.bsdcan.org/2006/activity.php?id=110">Works in + Progress</a> + + - if you want to talk about your project for 5 minutes, this is + your chance. Get in touch with us ASAP to reserve your spot.</task> + + <task>We're looking for volunteers to help out just before and + during the conference. Contact Dan at the above address.</task> + </help> + </project> + + <project cat='ports'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/ports/">The FreeBSD Ports + Collection</url> + + <url + href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"> + Contributing to the FreeBSD Ports Collection</url> + + <url href="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD + ports unfetchable distfile survey (Bill Fenner's report)</url> + + <url href="http://edwin.adsl.barnet.com.au/~edwin/ports/">FreeBSD + ports updated distfile survey (Edwin Groothius' report)</url> + + <url href="http://portsmon.FreeBSD.org/index.html">FreeBSD ports + monitoring system</url> + + <url href="http://www.freebsd.org/portmgr/index.html">The FreeBSD + Ports Management Team</url> + + <url href="http://tinderbox.marcuscom.com">marcuscom + tinderbox</url> + </links> + + <body> + <p>During this time, the number of ports PRs rose dramatically from + its impressive low number seen late last quarter. This was due to + the holidays, the freeze for the 5.5/6.1 release cycle, and the + aggressive work several submitters have been doing to correct + long-standing problems with stale distfiles, stale WWW sites, port + that only work on i386, and so forth. Over 200 new ports have also + been added. The statistics do not truly reflect the state of the + Ports Collection, which continues to improve despite the increased + number of ports.</p> + + <p>We now have 3 people who are qualified to run the 5-exp + regression tests. Due to this, we were able to run several cycles, + resulting in a series of commits that retired more than 3 dozen + portmgr PRs. There were a few snags during one commit due to some + unintended consequences, but the breakage was fixed in less than + one day. Notable changes include the addition of physical category + net-p2p and virtual categories hamradio and rubygems. Once 5.5 and + 6.1 are released, portmgr hopes to be able to run regression tests + more often.</p> + + <p>We have added 5 new committers since the last report.</p> + </body> + + <help> + <task>We need help getting back to our modern low of 500 + PRs.</task> + + <task>We have over 4,000 unmaintained ports (see, for instance, + <url + href="http://portsmon.freebsd.org/portsconcordanceformaintainer.py?maintainer=ports@FreeBSD.org"> + the list on portsmon</url> + + ). We are always looking for dedicated volunteers to adopt at least + a few ports.</task> + </help> + </project> + + <project cat='bin'> + <title>OpenBSD dhclient</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>All dhclient changes in HEAD have been merged to 6-STABLE for + 6.1-RELEASE. New patches currently in testing include startup + script support for fully asynchronous starting of dhclient which + eliminates the wait for link during startup and support for sending + the system hostname to the server when non is specified.</p> + </body> + </project> + + <project cat='net'> + <title>FAST_IPSEC Upgrade</title> + + <contact> + <person> + <name> + <given>George</given> + + <common>Neville-Neil</common> + </name> + + <email>gnn@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Bjoern A.</given> + + <common>Zeeb</common> + </name> + + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://sources.zabbadoz.net/freebsd/ipv6/fast-ipsec.html" /> + </links> + + <body> + <p>Split out of PF_KEY code between the kernel and user space has + been completed and committed to CVS.</p> + + <p>The diff between Kame IPv4 based IPSec and FAST_IPSEC IPv4 did + not show any glaring issues.</p> + + <p>Moving on to making IPv6 work in FAST_IPSEC including being able + to run the kernel with the following variations: + <ul> + <li>FAST_IPSEC in v4 only</li> + + <li>KAME IPv6 and IPSec</li> + + <li>KAME IPv6 and FAST_IPSEC</li> + </ul> + </p> + </body> + + <help> + <task>Any patches for FAST_IPSEC, KAME IPsec of either variant (v4 + or v6) should be forwarded to bz@ and gnn@.</task> + + <task>Build a better TAHI. TAHI, the test framework, will not be + maintained and is not the easiest system to use and understand. A + better test harness is possible and is necessary for other + networking projects as well. Contact gnn@ if you have time to work + on this as he has some code and ideas to start from.</task> + </help> + </project> + + <project cat='proj'> + <title>FreeSBIE</title> + + <contact> + <person> + <name> + <given>FreeSBIE</given> + + <common>Staff</common> + </name> + + <email>staff@FreeSBIE.org</email> + </person> + + <person> + <name> + <given>FreeSBIE</given> + + <common>Mailing List</common> + </name> + + <email>freesbie@gufi.org</email> + </person> + </contact> + + <links> + <url href="http://www.freesbie.org">Website</url> + + <url href="http://liste.gufi.org/mailman/listinfo/freesbie">ML + Subscribe Page</url> + </links> + + <body> + <p>The project is alive and plans to release an ISO image of + FreeSBIE 2.0 based on FreeBSD 6.1-RELEASE few day after the same + has been release. FreeSBIE 2.0 will be available for i386 and amd64 + archs. Tests images can be download via BitTorrent from + <a href="http://torrent.freesbie.org">torrent.freesbie.org</a> + + .</p> + </body> + + <help> + <task>Test "test ISO images" for both amd64 and i386</task> + + <task>Suggest packages to be added to the ISO image.</task> + + <task>Suggestions needed for Xfce and fluxbox look.</task> + + <task>Suggestions needed for applications' configuration + files.</task> + </help> + </project> + + <project cat='vendor'> + <title>HPLIP (Full HP Printer and MFD support)</title> + + <contact> + <person> + <name> + <given>Anish</given> + + <common>Mistry</common> + </name> + + <email>amistry@am-productions.biz</email> + </person> + </contact> + + <links> + <url href="http://am-productions.biz/docs/hplip.php">HPLIP FreeBSD + Information</url> + + <url href="http://hplip.sourceforge.net/">Official Site</url> + </links> + + <body> + <p>A preliminary version of HP's hplip software for their printers + and multi-function devices has been ported. This allows viewing of + the status informantion from the printer. Such as ink levels, error + messages, and queue information. If you have an Officejet you can + also fax and scan. Photocard and Copies functionality is + untested.</p> + </body> + + <help> + <task>General Testing</task> + + <task>Photocard Testing</task> + + <task>Various ugen fixes</task> + + <task>Fix Officejet Panel Display</task> + + <task>Run hpiod and hpssd as unprivileged users</task> + + <task>Banish the Linuxisms in the Makefile</task> + + <task>Fix "Make Copies"</task> + + <task>Automatically Setup Scanner</task> + </help> + </project> + + <project cat='kern'> + <title>Low-overhead performance monitoring for FreeBSD</title> + + <contact> + <person> + <name> + <given>Joseph</given> + + <common>Koshy</common> + </name> + + <email>jkoshy@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~jkoshy/projects/perf-measurement"> + Project home page</url> + </links> + + <body> + <p>This projects implements a kernel module (hwpmc(4)), an + application programming interface (pmc(3)) and a few simple + applications (pmcstat(8) and pmccontrol(8)) for measuring system + performance using event monitoring hardware in modern CPUs.</p> + + <p>New features since the last status report:</p> + + <ul> + <li>Support for profiling dynamically loaded kernel and user + objects has been added.</li> + + <li>pmcstat(8) now supports command-line syntax for logging to a + network socket.</li> + </ul> + </body> + </project> + + <project cat='doc'> + <title>FreeBSD list of projects and ideas for volunteers</title> + + <contact> + <person> + <name> + <given>Joel</given> + + <common>Dahl</common> + </name> + + <email>joel@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/ideas/" /> + </links> + + <body> + <p>The FreeBSD list of projects and ideas for volunteers is doing + well. Several items were picked up by volunteers and have found + their way into the tree. Others are under review or in + progress.</p> + + <p>We are looking forward to hear about new ideas, people willing + to be technical contacts for generic topics (e.g. USB) or specific + entries (already existing or newly created), suggestions for + existing entries or completion reports for (parts of) an entry.</p> + </body> + + <help> + <task>Add more ideas.</task> + + <task>Find more technical contacts.</task> + + <task>Find people willing to review/test implementations of + (somewhat) finished items.</task> + </help> + </project> + + <project cat='vendor'> + <title>Java Binaries</title> + + <contact> + <person> + <name> + <given>Deb</given> + + <common>Goodkin</common> + </name> + + <email>deb@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsdfoundation.org/downloads/java.shtml"> + FreeBSD Foundation Java Homepage</url> + </links> + + <body> + <p>The FreeBSD Foundation released official certified JDK and JRE + 1.5 binaries for the official FreeBSD 5.4 and FreeBSD 6.0 releases + on the i386 platform. + <br /> + + We were able to accomplish this by hiring a contractor to run the + Sun certification tests and fixing the problems found. This could + not have been completed without the support from the BSD Java + Team.</p> + + <p>We provided financial support for Java development and funded + the certification process. We spent a significant amount of time + and money on legal issues from contract and NDA creation for our + contractor to license agreements from Sun and creating our own for + the binaries. We worked with OEMs who would like to use the + binaries, but needed to understand what they need to do legally to + be able to redistribute the binaries. This is an area we are still + working on at our end. We are waiting for a letter from Sun to put + on our website to OEMs. We are also in the process of updating our + OEM license agreement. This should be available by mid-April.</p> + + <p>We have received a positive response from the FreeBSD community + regarding the release of the binaries. We received a few requests + to support the FreeBSD 6.1/amd64 platform. We have decided to move + forward and support this too. We currently are working with a + contractor to provide Java support on 5.5/i386, 6.1/i386, and + 6.1/amd64. Once 5.5 and 6.1 are released, we'll update the FreeBSD + Foundation website with the Java status. Regular updates to the + website will continue.</p> + </body> + </project> + + <project cat='ports'> + <title>Update of the linux infrastructure in the Ports + Collection</title> + + <contact> + <person> + <name> + <given>Emulation</given> + + <common>Mailinglist</common> + </name> + + <email>freebsd-emulation@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Boris</given> + + <common>Samorodov</common> + </name> + + <email>bsam@ipt.ru</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Work is underway to use the new linux_base-fc3 as the new + default linux base. Since there's some infrastructure work to do + before it can be made the new default, this will not happen before + the release of FreeBSD 5.5 and 6.1. At the same time a new X.org + based linux port will replace the outdated XFree86 based linux X11 + port.</p> + + <p>The use of fc3 instead of fc4 or fc5 is to make sure we have a + smooth transition with as less as possible breakage. We already use + several fc3 RPM's with the current default of linux_base-8, so + there should be not much problems to solve.</p> + </body> + + <help> + <task>Mark all old linux_base ports as DEPRECATED (after making fc3 + the default linux_base port).</task> + + <task>Have a look at a linux-dri version which works with the + update to X.org.</task> + + <task>When everything is switched to fc3 and everything works at + least as good as before, have a look at porting fc4 or fc5.</task> + </help> + </project> + + <project cat='bin'> + <title>Mouse Driver Framework</title> + + <contact> + <person> + <name> + <given>Jordan</given> + + <common>Sissel</common> + </name> + + <email>jls@csh.rit.edu</email> + </person> + </contact> + + <links> + <url href="http://www.semicomplete.com/projects/newpsm">mouse + framework project</url> + </links> + + <body> + <p>The current mouse system is a mess with moused, psm, ums, and + mse supporting, individually, multiple kinds of mice. This project + aims to move all driver support into moused modules in userland. In + addition, many features lacking in the existing mouse + infrastructure are being added. It is my hope that this new system + will make both using mice and writing drivers easier down the + road.</p> + </body> + + <help> + <task>Testing. Contact if interested.</task> + </help> + </project> + + <project cat='net'> + <title>SMPng Network Stack</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/netperf/">FreeBSD + Netperf Project</url> + </links> + + <body> + <p>The FreeBSD netperf project has recently focused on revising the + socket and protocol control block reference counts to define and + enforce reference and memory management invariants, allowing the + removal of unnecessary checks, error handling, and locking. Use of + global pcbinfo locks has now been eliminated from the socket send + and receive paths into all network protocols, including netipx, + netnatm, netatalk, netinet, netinet6, netgraph, and others. Checks + have generally been replaced with assertions; so_pcb is now + guaranteed to be non-NULL. This should improve performance by + reducing lock contention and unnecessary checks, as well as + facilitate future work to eliminate long holding of pcbinfo locks + in the TCP input path through proper reference counting for pcbs. + These changes have been committed to FreeBSD 7-CURRENT, and will be + merged in a few months once they have stabilized.</p> + </body> + </project> + + <project cat='proj'> + <title>pfSense</title> + + <contact> + <person> + <name> + <given>Scott</given> + + <common>Ullrich</common> + </name> + + <email>sullrich@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://www.pfsense.com">pfSense website</url> + </links> + + <body> + <p>pfSense continues to grow and fix bugs. Since the last report we + have grown to 14 developers working part and full time on bringing + pfSense to 1.0. Beta 3 is scheduled for release on 4/15/2006.</p> + </body> + + <help> + <task>Fix remaining bugs listed in CVSTrac</task> + + <task>Fine tune existing code</task> + </help> + </project> + + <project cat='proj'> + <title>Symbol Versioning</title> + + <contact> + <person> + <name> + <given>Daniel</given> + + <common>Eischen</common> + </name> + + <email>deischen@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~deischen/symver/library_versioning.html"> + Symbol Versioning in FreeBSD.</url> + + <url href="http://docs.sun.com/app/docs/doc/817-1984">Symbol + Versioning in Solaris.</url> + + <url href="http://people.redhat.com/~drepper/symbol-versioning"> + Symbol Versioning in Linux</url> + </links> + + <body> + <p>Symbol versioning libraries allows us to maintain binary + compatibility without bumping library version numbers. Recently, + symbol versioning for libc, libpthread, libthread_db, and libm was + committed to -current. It is disabled by default, and can be + enabled by adding "SYMVER_ENABLED=true" to/etc/make.conf. A final + version bump for libc and other affected libraries (perhaps all) + should be done before enabling this by default.</p> + </body> + + <help> + <task>Determining the impact on ports - portmgr (Kris) is running a + portbuild to identify any problems. I am working to resolve the few + problems that were found.</task> + + <task>Making our linker link to libc and libpthread (when using + (-pthread)) when building shared libraries. This is needed so that + symbol version dependencies are recorded in the shared library. I + think kan@ is working on this.???</task> + + <task>Identify and symbol version any other libraries that should + be symbol versioned. If anyone has any suggestions, I'm all + ears.</task> + </help> + </project> + + <project cat='kern'> + <title>Status Report ATA project</title> + + <contact> + <person> + <name> + <given>Søren</given> + + <common>Schmidt</common> + </name> + + <email>sos@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The last months has mostly been about stabilizing ATA for + 6.1-RELEASE, and adding support for new chipsets. On that front + JMicron has raised the bar for vendors as they have provided not + only hardware but documentation on both their hardware and their + software RAID implementation, making it a breeze to add support for + their, by the way excellent, products. Other vendors can join in + here. :) Otherwise I'm always in the need for any amount of time or + means to get it if nothing else.</p> + + <p>ATA has grown a USB backend so that fx. flash keys and external + HD/CD/DVD drives can be used directly without atapicam/CAM etc. + This is very handy on small (embedded) systems where resources are + limited and kernel space at a premium. burncd(8) is in the process + of being updated so it will support this along with SATA ATAPI + devices, and if time permits adding DVD support.</p> + + <p>The next months will be used to (hopefully) work on getting ATA + to work properly on systems with > 4G of memory and utilize the + 64bit addressing of controllers that support it. RAID5 support for + ataraid is on the list together with hardening of the RAID + subsystem to help keep data alive and well.</p> + </body> + </project> + + <project cat='proj'> + <title>BSDInstaller</title> + + <contact> + <person> + <name> + <given>Andrew</given> + + <common>Turner</common> + </name> + + <email>soc-andrew@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/moin.cgi/BSDInstaller" /> + </links> + + <body> + <p>The BSDInstaller integration work has progressed since the + previous report. The backend has been changed to the new Lua + version. This is to ensure the version we use will be maintained. + The release Makefile now uses the Lua package rather the local copy + in Perforce. Ports are also being created for the required modules + to remove the need to bring Lua into the base.</p> + </body> + + <help> + <task>Create a port for all the Lua modules required</task> + </help> + </project> + + <project cat='ports'> + <title>libpkg - Package management library</title> + + <contact> + <person> + <name> + <given>Andrew</given> + + <common>Turner</common> + </name> + + <email>andrew@fubar.geek.nz</email> + </person> + </contact> + + <links> + <url href="http://libpkg.berlios.de/" /> + + <url href="http://developer.berlios.de/projects/libpkg/" /> + </links> + + <body> + <p>Libpkg is a package management library using libarchive to + extract the package files. It is able to download, install and get + a list of installed packages. Work has also been started on + implementing the package tools from the base system. Most of + pkg_info has been implemented and pkg_add has been started.</p> + </body> + + <help> + <task>Support for more command line options in pkg_info and + pkg_add</task> + + <task>Creating a package</task> + + <task>Test pkg_add works as expected for all implemented command + line options</task> + </help> + </project> + + <project cat='net'> + <title>Bridge STP Improvements</title> + + <contact> + <person> + <name> + <given>Andrew</given> + + <common>Thompson</common> + </name> + + <email>thompsa@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work has been started to implement the Rapid Spanning Tree + Protocol which supersedes STP. RSTP has a much faster link failover + time of around one second compared to 30-60 seconds for STP, this + is very important on modern networks. Some progress has been made + but a RSTP capable switch will be needed soon to proceed, see + <a href="http://www.freebsd.org/donations/wantlist.html"> + http://www.freebsd.org/donations/wantlist.html</a> + + .</p> + </body> + + <help> + <task>Donation of a RSTP switch</task> + </help> + </project> + + <project cat='kern'> + <title>TMPFS (Filesystem) for FreeBSD</title> + + <contact> + <person> + <name> + <given>Rohit</given> + + <common>Jalan</common> + </name> + + <email>rohitj@purpe.com</email> + </person> + </contact> + + <links> + <url href="http://download.purpe.com/tmpfs">Project Home</url> + + <url href="http://download.purpe.com/tmpfs/bmark.html">I/O + Benchmarks</url> + </links> + + <body> + <p>Three betas have been released so far. The code is operational + and seems to be stable but it is not MPSAFE yet.</p> + + <p>The second and third betas used different mechanisms for data + I/O. (sfbuf vs. kernel_map+vacache) and at present I am in the + process on selecting one mechanism over the other. Your opinion is + solicited.</p> + </body> + </project> + + <project cat='kern'> + <title>Sound subsystem improvements</title> + + <contact> + <person> + <name> + <given>Multimedia</given> + + <common>Mailinglist</common> + </name> + + <email>freebsd-multimedia@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ariff</given> + + <common>Abdullah</common> + </name> + + <email>ariff@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.leidinger.net/FreeBSD/hdac-20060313.tbz"> + Start of Intel HDA support.</url> + </links> + + <body> + <p>A lot of fixes (bugs, LORs, panics) and improvements + (performance, compatibility, a new driver, 24/32bit samples + support, ...) have been merged to RELENG_6. FreeBSD 6.1 is the + first release which ships with the much improved sound system. + Additionally there's work underway: + <ul> + <li>To make the sound system API endianess clean. This should + make it easier (for a developer) to make the sound drivers usable + on all architectures.</li> + + <li>To rework character device allocation. This way someone can + choose a specific channel, e.g. /dev/dsp0.r0 or /dev/dsp0.p0 to + access the first recording or play channel respectively). With + the "current" sound system (as in FreeBSD 6.1) this is not + possible (accessing /dev/dsp0.0 and /dev/dsp0.1 may give you the + first or the second channel, the number is just an enumeration, + not a channel-chooser).</li> + + <li>To add multi-channel support/processing.</li> + + <li>To add Intel HDA support. There's already some code to look + at (see URL referenced above), but is far from usable for an + enduser (we need some programmers, but no testers ATM, since + there are no user testable parts yet). Interested volunteers + should contact the multimedia mailinglist.</li> + </ul> + + Parts of this work may be already in 6.1, but there's still a good + portion which isn't even in -current as of this writing.</p> + </body> + + <help> + <task>Style(9) cleanup, survive against WARNS=2 (at least).</task> + + <task>Have a look at the sound related entries on the ideas + list.</task> + + <task>Rewrite some parts (e.g. a new mixer subsystem with OSS + compatibility).</task> + + <task>sndctl(1): tool to control non-mixer parts of the sound + system (e.g. spdif switching, virtual-3D effects) by an user + (instead of the sysctl approach in -current); pcmplay(1), + pcmrec(1), pcmutil(1).</task> + + <task>Plugable FEEDER infrastructure. For ease of debugging various + feeder stuff and/or as userland library and test suite.</task> + + <task>Closer compatibility with OSS, especially for the upcoming + OSS v4.</task> + </help> + </project> + + <project cat='misc'> + <title>Fundraising for FreeBSD security development</title> + + <contact> + <person> + <name> + <given>Colin</given> + + <common>Percival</common> + </name> + + <email>cperciva@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~cperciva/funding.html" /> + </links> + + <body> + <p>Since 2003, I have introduced the (now quite widely used) + FreeBSD Update and Portsnap tools, but rarely had time to make + improvements or add requested features. Consequently, on March + 30th, I sent email to the freebsd-hackers, freebsd-security, + and freebsd-announce lists announcing that I was seeking funding to + allow me to spend the summer working full-time on these and my role + as FreeBSD Security Officer. Assuming that some cheques arrive as + expected, I have reached my donation target and will start work at + the beginning of May.</p> + </body> + + <help> + <task>The work which I'm aiming to do is listed at the URL + above.</task> + </help> + </project> + + <project cat='arch'> + <title>FreeBSD on Xen 3.0</title> + + <contact> + <person> + <name> + <given>Scott</given> + + <common>Long</common> + </name> + + <email>scottl@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Kip</given> + + <common>Macy</common> + </name> + + <email>kmacy@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>We had hoped to finish a prototype of Xen DomU and possible Dom0 + in time for FreeBSD 6.1. The primary work was focused on bringing + Xen into the FreeBSD 'newbus' framework. Unfortunately, an + architectural problem in FreeBSD has stopped us. Xen relies on + message passing between to child and parent domains to communicate + device configuration, and this message passing requires that tsleep + and wakeup work early in boot. That doesn't seem to be the case, + and it's unclear what it would take to make it work. Without the + newbus work, it's hard to complete the Dom0 code, and impossible to + support Xen 3.0 features like domain suspension.</p> + </body> + + <help> + <task>Make tsleep and wakeup work during early boot</task> + + <task>Continue DomU newbus work</task> + + <task>Continue Dom0 work</task> + </help> + </project> + + <project cat='proj'> + <title>TrustedBSD Audit</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <email>trustedbsd-audit@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/audit.html">TrustedBSD Audit + Web Page</url> + </links> + + <body> + <p>In the past three months, the TrustedBSD CAPP audit + implementation has been merged to the FreeBSD 7-CURRENT development + tree in CVS, and the groundwork has been laid for a merge to 6.X. + OpenBSM, a BSD-licensed implementation of Sun's Basic Security + Module (BSM) API and file format, as well as extensions to support + intrusion detect applications. New features included support for + audit pipes, a pseudo-device that provides a live audit record + trail interface for intrusion detection applications, and an audit + filter daemon that allows plug-in modules to monitor live + events.</p> + </body> + + <help> + <task>Complete audit coverage of non-native system call ABIs, some + more recent base system calls.</task> + + <task>Integrate OpenBSM 1.0 alpha 6, which includes auditfilterd + and the audit filter API.</task> + </help> + </project> + + <project cat='proj'> + <title>TrustedBSD OpenBSM</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <email>trustedbsd-audit@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.OpenBSM.org/">TrustedBSD OpenBSM Web + Page</url> + </links> + + <body> + <p>OpenBSM is a BSD-licensed implementation of Sun's Basic Security + Module (BSM) API and file format, based on Apple's Darwin + implementation. OpenBSM 1.0 alpha 5 is now available, and includes + significant bugfixes, documentation, and feature enhancements over + previous releases, including 64-bit token support, + endian-independent operation, improved memory management, and bug + fixes resulting from the static analysis tools provided by Coverity + and FlexeLint. Recent versions are now built and configured using + autoconf and automake, and have been built and tested with FreeBSD, + Mac OS X, and Linux.</p> + </body> + + <help> + <task>Complete OpenBSM file format validation test suite.</task> + + <task>Finalize audit filter API.</task> + + <task>Complete file format documentation; record documentation for + new record types associated with Mac OS X, FreeBSD, and Linux + specific events not present in documented Solaris record + format.</task> + </help> + </project> + + <project cat='arch'> + <title>ARM Support for TS-7200</title> + + <contact> + <person> + <name> + <given>John-Mark</given> + + <common>Gurney</common> + </name> + + <email>jmg@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.embeddedarm.com/epc/ts7200-spec-h.html"> + TS-7200 Board</url> + + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/jmg/arm&HIDEDEL=NO"> + Perforce Code Location</url> + + <url href="http://people.freebsd.org/~jmg/dmesg.ts7200">FreeBSD/arm + TS-7200 dmesg output</url> + </links> + + <body> + <p>This is just an update to note that TS-7200 is building and + running with a recent -current.</p> + + <p>I have been working on getting FreeBSD/arm running on the + TS-7200. So far the board boots, and has somewhat working ethernet + (some unexplained packet loss). I can netboot from a FreeBSD/i386 + machine, and I can also mount msdosfs's on CF.</p> + </body> + + <help> + <task>Figuring out why some small packets transmit with error (if + someone can get Technologic Systems to pay attention to me and this + issue, that'd be great!)</task> + + <task>EP93xx identification information to properly attach various + onboard devices</task> + </help> + </project> + + <project cat='arch'> + <title>Ultrasparc T1 support</title> + + <contact> + <person> + <name> + <given>Kip</given> + + <common>Macy</common> + </name> + + <email>kmacy@FreeBSD.org</email> + </person> + + <person> + <name> + <given>John</given> + + <common>Gurney</common> + </name> + + <email>jmg@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://opensparc-t1.sunsource.net/index.html">T1 + processor and hypervisor documentation.</url> + + <url href="http://www.fsmware.com/sun4v/todo.txt">TODO list</url> + </links> + + <body> + <p>FreeBSD has been ported the T1, Sun's newest processor. FreeBSD + currently runs multi-user SMP. JMG is actively working on improving + device support.</p> + + <p>The port has taken several weeks longer than initially + anticipated as the majority of the current sparc64 port could not + be re-used.</p> + </body> + </project> + + <project cat='vendor'> + <title>OpenBSD packet filter - pf</title> + + <contact> + <person> + <name> + <given>Max</given> + + <common>Laier</common> + </name> + + <email>mlaier@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Work towards importing the upcoming OpenBSD 3.9 version of pf is + starting slowly. There are a couple of infrastructural changes + (e.g. interface groups) that need to be imported beforehand. This + work is in the final stage of progress.</p> + + <p>A couple of bugfixes have happened since the last report and will + be available in FreeBSD 6.1/5.5. pf users are strongly encouraged + to upgrade to RELENG_6 as the version present in RELENG_5 is + collecting dust.</p> + </body> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2006-04-2006-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2006-04-2006-06.xml new file mode 100644 index 0000000000..f8a92fd1c6 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2006-04-2006-06.xml @@ -0,0 +1,2141 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> + +<!-- $FreeBSD: www/en/news/status/report-2006-04-2006-06.xml,v 1.7 2008/08/16 21:55:59 pgj Exp $ --> +<report> + <date> + <month>April-June</month> + + <year>2006</year> + </date> + + <section> + <title>Introduction</title> + + <p>With the release of FreeBSD 5.5 and FreeBSD 6.1, the second + quarter of 2006 has been productive. Google is sponsoring 14 students + to work on FreeBSD as part of their Summer of Code Program (most of + which already submitted a report for elaboration on their + projects).</p> + + <p>Sun's open-source software is starting to make its way into + FreeBSD as a port of DTrace is nearing completion and a port to the + UltraSparc T1 processor (which gives a great push to the ongoing SMP + efforts). Having a powerful debugging tool combined with a CPU that + can run up to 32 concurrent threads helps to identify scalability + issues.</p> + + <p>BSDCan 2006 was yet again a smashing success and much was covered + in the 2-day developer summit. As a product of the conference, a new + focus on FreeBSD for the embedded sector has started. Various ARM + boards are targeted, a MIPS32 port is gearing up and people are + looking for other interesting platforms to port FreeBSD to. + Preparation for the EuroBSDCon (in Milan, Italy) on November has + already issued a call for papers.</p> + + <p>In addition, a lot of spring cleaning is taking place in the + network stack. After conclusion of the KAME project, IPv6 code + integration has been refocused and a fully locked port of SCTP is in + the final stage of integration. Of course, all this goes without + noting all the progress made with the other network projects.</p> + + <p>Please read below for more detailed news on the projects that + happened in FreeBSD during the last three months. If you are + interested in helping, consider the "Open Tasks lists" provided with + some reports. In addition we would like to point you at the + <a href="http://www.freebsd.org/projects/ideas/">list of projects and + ideas for volunteers</a> + + and hope to receive a status report from you next time.</p> + + <p>Thanks to all reporters for your excellent work and timing! Enjoy + reading.</p> + </section> + + <category> + <name>soc</name> + + <description>Google summer of code</description> + </category> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>net</name> + + <description>Network infrastructure</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <category> + <name>bin</name> + + <description>Userland programs</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <category> + <name>vendor</name> + + <description>Vendor / 3rd Party Software</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='misc'> + <title>BSDCan</title> + + <contact> + <person> + <name> + <given>Dan</given> + + <common>Langille</common> + </name> + + <email>dan@langille.org</email> + </person> + </contact> + + <links> + <url href="http://www.bsdcan.org/">BSDCan</url> + </links> + + <body> + <p> + <a href="http://www.bsdcan.org/">BSDCan 2006</a> + + continues to impress. Again this year, we had a good collection of + talks from a wide range of speakers. In all, we had over 200 people + from 14 different countries.</p> + + <p>Our sponsorship pool continues to grow. This year we had + sponsorship from: + <ul> + <li> + <a href="http://www.usenix.org/">USENIX</a> + </li> + + <li> + <a href="http://www.freebsdfoundation.org/">The FreeBSD + Foundation</a> + </li> + + <li> + <a href="http://www.parse.com/">PARSE</a> + </li> + + <li> + <a href="http://www.ixsystems.com/">iXsystems</a> + </li> + + <li> + <a href="http://www.oreilly.com/">O'Reilly</a> + </li> + + <li> + <a href="http://www.stevens-tech.edu/">Stevens Institute of + Technology</a> + </li> + + <li> + <a href="http://www.ncircle.com/">nCircle</a> + </li> + </ul> + + <br /> + + The + <a href="http://www.bsdcan.org/2006/images/t-shirt.jpg"> + t-shirts</a> + + were very popular, with all of them going in very short time. Of + course, it helped that this year they were free, courtesy of + PARSE.</p> + + <p>The 2007 planning has already begun and we look forward to + another popular and successful event.</p> + + <p>My thanks to the 2006 program committee, the speakers, the + volunteers, the sponsors, and, of course, the attendees.</p> + + <p>See you at BSDCan 2007.</p> + </body> + </project> + + <project cat='misc'> + <title>Release Engineering</title> + + <contact> + <person> + <name> + <common>Release Engineering Team</common> + </name> + + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/releng/" /> + + <url href="http://www.freebsd.org/releases/" /> + + <url href="http://www.freebsd.org/snapshots/" /> + </links> + + <body> + <p>The release engineering (RE) team announced the availability of + FreeBSD 5.5 and 6.1, both in May 2006. FreeBSD 5.5 is the last + planned release from the RELENG_5 branch in CVS. For the most part, + its main features consist of bugfixes, security patches, and minor + updates. We encourage users to move towards the 6.x series of + releases whenever practical. FreeBSD 6.1 is the latest of the + releases to come from the RELENG_6 branch in CVS. It includes + (among many other things) improved support for WiFi devices, + additional network and disk controller drivers, and a number of + fixes for filesystem stability. The next release to be issued from + this branch will be FreeBSD 6.2, which is currently scheduled for + September 2006.</p> + + <p>The RE team is currently in a ``between releases'' mode. Current + activities include working with security-team@ on some errata fixes + for the RELENG_6_1 branch and producing snapshots of HEAD and + RELENG_6 at the start of each month.</p> + + <p>Several personnel changes have taken place recently. Scott Long + has stepped down from his position on the RE team; we thank him for + his considerable efforts over the past four years. In his place, + Ken Smith has taken over the role of lead release engineer. Bruce + A. Mah has rejoined the RE team after a two-year sabbatical.</p> + </body> + </project> + + <project cat='kern'> + <title>Giant-Less USB framework</title> + + <contact> + <person> + <name> + <given>Hans Petter</given> + + <common>Sirevaag Selasky</common> + </name> + + <email>hselasky@c2i.net</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&HIDEDEL=NO"> + Current files</url> + + <url href="http://www.turbocat.net/~hselasky/usb4bsd">Easy to + install tarballs</url> + </links> + + <body> + <p>For some time now I have been working on converting the existing + USB device drivers to my new and mutex enabled USB API. I have + converted "ulpt", "ums", "uhid", "ukbd", "ugen", "uaudio", and a + few others. Around 10 USB device drivers are left to convert. Most + of these are network device drivers.</p> + + <p>At the present moment I am working on getting scatter and + gathering support working for all USB host controllers. Scatter and + gathering means that one allocates PAGE_SIZE bytes of memory at a + time, and then fills these memory blocks up as much as possible + with USB host controller structures and buffers. This should solve + problems allocating DMA-able memory when the system memory becomes + fragmented.</p> + </body> + + <help> + <task>If anyone wants to help convert the remaining USB device + drivers, please drop me an e-mail.</task> + </help> + </project> + + <project cat='kern'> + <title>SSE2 Kernel support</title> + + <contact> + <person> + <name> + <given>Attilio</given> + + <common>Rao</common> + </name> + + <email>attilio@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/projects/ideas/#p-memcpy">Project + details</url> + + <url + href="http://unix.derkeiler.com/Mailing-Lists/FreeBSD/arch/2006-05/msg00109.html"> + Ongoing development</url> + </links> + + <body> + <p>Some + <strong>FPU system</strong> + + and + <strong>kernel memcpy/copyin/copyout</strong> + + changes have been performed. In particular, a per-CPU save area has + been introduced (protected with an interlock) in order to assure a + stable saving mechanism. + <strong>copyout/copyin</strong> + + have changed in order to use vectorised version of + <strong>memcpy</strong> + + and an xmm version of memcpy has been provided.</p> + </body> + + <help> + <task>Benchmarks on different versions of xmm copy, in particular + showing differences between UP and SMP architectures (evaluating + possibility to add block prefetch, non-temporal hints usage, + etc.)</task> + + <task>Modifying npxdna trap handler in order to recognise xmm + environment usage and replace fxsave with 8-movdqa</task> + </help> + </project> + + <project cat='soc'> + <title>BSNMP Bridge module</title> + + <contact> + <person> + <name> + <given>Shteryana</given> + + <common>Shopova</common> + </name> + + <email>shteryana@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/soc%2dshteryana/bsnmp/usr.sbin/bsnmpd/modules/snmp%5fbridge"> + P4 workspace</url> + + <url href="http://wiki.freebsd.org/SnmpBridgeModule">Wiki + page</url> + </links> + + <body> + <p>As part of my SoC 2006 project I am working on implementing a + BRIDGE monitoring module for FreeBSD's BSNMP daemon. Initial + prototyping is done and some kernel changes are coming to be able + to access all needed data. In addition to IETF RFC 4188, which was + designed for monitoring a single bridge, this snmp module will + support monitoring of multiple bridge devices as supported by + FreeBSD.</p> + </body> + + <help> + <task>Finish kernel changes and the code for the snmp + module.</task> + + <task>Testing.</task> + </help> + </project> + + <project cat='proj'> + <title>DTrace</title> + + <contact> + <person> + <name> + <given>John</given> + + <common>Birrell</common> + </name> + + <email>jb@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~jb/dtrace/index.html" /> + </links> + + <body> + <p>Anonymous enablings now work. There is a new option in the boot + loader menu to load the DTrace modules and trace the kernel boot + process.</p> + + <p>Sun Microsystems has been very supportive of the FreeBSD port + and has generously provided a Sun Fire T2000 server to allow Kip + Macy's sun4v port to be merged into the DTrace project tree.</p> + + <p>The DTrace project tree sources are now exported to + cvsup10.freebsd.org</p> + + <p>Refer to the project page for more details.</p> + </body> + + <help> + <task>Current effort centres around making DTrace useful for the + sun4v porting effort which has shown up scalability issues with the + current FreeBSD SMP implementation. DTrace should be ideal for + analysing those issues.</task> + </help> + </project> + + <project cat='proj'> + <title>Embedded FreeBSD</title> + + <contact> + <person> + <name> + <given>George</given> + + <common>Neville-Neil</common> + </name> + + <email>gnn@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://www.embeddedfreebsd.org/">Main Site</url> + </links> + + <body> + <p>There are several projects moving forward in the embedded area. + For now the main location for new information is + www.embeddedfreebsd.org. We have also created a new mailing list, + <a + href="http://lists.freebsd.org/mailman/listinfo/freebsd-embedded"> + freebsd-embedded@freebsd.org</a> + + , which is meant to eventually replace the freebsd-small. A call + was put out on small for people to move to embedded.</p> + </body> + + <help> + <task>Update Developers Handbook with information on building + embedded versions of FreeBSD</task> + + <task>Help with the MIPS port</task> + + <task>Help with the ARM port</task> + + <task>Investigate an SH port (requested by folks in Japan where the + Hitachi SH processor is quite popular in embedded)</task> + </help> + </project> + + <project cat="misc"> + <title>EuroBSDCon 2006 - November 10th - 12th, Milan, Italy</title> + + <contact> + <person> + <name> + <given>Massimiliano</given> + + <common>Stucchi</common> + </name> + + <email>stucchi@eurobsdcon.org</email> + </person> + </contact> + + <links> + <url href="http://www.eurobsdcon.org">Official Website</url> + </links> + + <body> + <p>This year's EuroBSDCon will be held in Milan, Italy, on November + 10th through 12th.</p> + + <p>Hosted in the foggy northern Italy, the fifth EuroBSDCon aims at + being a new successful chapter in the itinerant series of European + BSD conferences.</p> + + <p>EuroBSDCon represents the biggest gathering for BSD developers + from the old continent, as well as users and passionates from + around the World. It is also a chance to share experiences, + know-how, and cultures.</p> + + <p>For the first time, parallel to the main event, an event for + wives/girlfriends/friends will be organised. It will consist of + guided tours of the city of Milan, a probable trip to Como and + visits to various museums. We're also working towards offering a + show at the Teatro alla Scala.</p> + + <p>The FreeBSD developer summit will be also held on November + 10th.</p> + </body> + + <help> + <task>The Call For Papers is out, so everybody is invited to send + in papers or tutorials that might be of interest to the + community</task> + + <task>The Conference Organisers are also looking for sponsors. Feel + free to contact oc@eurobsdcon.org in order to discover the + different sponsoring opportunities.</task> + </help> + </project> + + <project cat='net'> + <title>FAST_IPSEC Upgrade</title> + + <contact> + <person> + <name> + <given>George</given> + + <common>Neville-Neil</common> + </name> + + <email>gnn@freebsd.org</email> + </person> + + <person> + <name> + <given>Bjoern A.</given> + + <common>Zeeb</common> + </name> + + <email>bz@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://sources.zabbadoz.net/freebsd/ipv6/fast-ipsec.html" /> + </links> + + <body> + <p>Continuing to add IPv6 support to FAST_IPSEC. Test environment + is now stable. Can build and run kernels with FAST_IPSEC and INET6 + enabled but IPSec in IPv6 is now broken and being worked on.</p> + </body> + + <help> + <task>Complete move to FAST_IPSEC type processing for IPv6. This is + complicated by the structure of the IPv6 code itself which, unlike + IPv4 splits transport and tunnel mode processing across the output + routine.</task> + </help> + </project> + + <project cat='ports'> + <title>FreshPorts</title> + + <contact> + <person> + <name> + <given>Dan</given> + + <common>Langille</common> + </name> + + <email>dan@langille.org</email> + </person> + </contact> + + <links> + <url href="http://www.freshports.org/">FreshPorts</url> + </links> + + <body> + <p>FreshPorts has seen several new features recently: + <ul> + <li>caching implemented at web application level to reduce load + on the database server and to serve pages faster</li> + + <li>searching expanded to find all the ports that this maintainer + maintains, and all the commits by a particular committer</li> + </ul> + + <br /> + + Most of the work lately has been optimisation, either at the + database level or at the web application level.</p> + + <p>A 2U server was recently donated to the + <a href="http://www.freshports.org">FreshPorts</a> + + / + <a href="http://www.freshsource.org">FreshSource</a> + + / + <a href="http://www.freebsddiary.org/">FreeBSD Diary</a> + + / + <a href="http://www.bsdcan.org/">BSDCan</a> + + group. We have also received a RAID card. Now we're looking for + some hard drives.</p> + + <p>Over the past few weeks, work has concentrated on benchmarking + the new server and getting it ready for production. Eventually it + will need a new home as I don't really want it running in my + basement all the time (it's really loud!).</p> + + <p>Thanks to + <a href="http://www.ixsystems.com">iXsystems</a> + + and + <a href="http://www.3ware.com">3Ware</a> + + for their contributions to this project.</p> + </body> + + <help> + <task>We would like some more hardware (CPUs and HDD). Details + <a href="http://www.freebsddiary.org/sponsors-wanted.php">here</a> + </task> + </help> + </project> + + <project cat='kern'> + <title>GJournal</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + + <common>Dawidek</common> + </name> + + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://lists.freebsd.org/pipermail/freebsd-fs/2006-June/001962.html"> + Announce.</url> + + <url href="http://people.freebsd.org/~pjd/patches/gjournal.patch"> + Patches for HEAD.</url> + + <url href="http://people.freebsd.org/~pjd/patches/gjournal6.patch"> + Patches for RELENG_6.</url> + </links> + + <body> + <p>GJournal is a GEOM class which provides journaling for GEOM + providers. It can also be used to journal various file systems with + just a minimal filesystem-specific portion of code. Currently only + UFS journaling is implemented on top of gjournal. Being + filesystem-independent and operating below the file system level, + gjournal has no way to distinguish data from metadata, thus it + journals both. One of the nice things about gjournal is that it + works reliable even on disks with enabled write cache, which is + often not the case for journalled file systems. And remember... fsck + no more.</p> + </body> + + <help> + <task>I'm looking for feedback from users who can test gjournal in + various workloads.</task> + </help> + </project> + + <project cat='soc'> + <title>gvirstor</title> + + <contact> + <person> + <name> + <given>Ivan</given> + + <common>Voras</common> + </name> + + <email>ivoras@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/gvirstor" /> + </links> + + <body> + <p>The purpose of + <em>gvirstor</em> + + module is to provide the ability to create a virtual storage device + of arbitrarily large size (typically several terabytes) which + consists of an arbitrary number of physical storage devices + (actually any lower-level GEOM providers, including RAID devices) + of arbitrary size (typically 50 GB - 400 GB hard drives). Storage + space from these components is carved into small chunks (for + example 4 MB) and allocated (committed) to the virtual device on + as-needed basis.</p> + + <p>Development has started and is progressing as planned (though a + little bit slow). Metadata format and virtual storage allocation + formats have been defined and more serious coding is in + progress.</p> + </body> + + <help> + <task>Much user testing will be needed (though not + currently)</task> + </help> + </project> + + <project cat='docs'> + <title>FreeBSD list of projects and ideas for volunteers</title> + + <contact> + <person> + <name> + <given>Joel</given> + + <common>Dahl</common> + </name> + + <email>joel@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/ideas/" /> + </links> + + <body> + <p>The FreeBSD list of projects and ideas for volunteers is doing + well. Several items were picked up by volunteers and have found + their way into the tree. Others are under review or in progress. We + are looking forward to hear about new ideas, people willing to act + as technical contacts for generic topics such as USB or specific + entries (already existing or newly created) and suggestions for + existing entries or completion reports for (parts of) an entry.</p> + </body> + + <help> + <task>Add more ideas.</task> + + <task>Find more technical contacts.</task> + + <task>Find people willing to review/test implementations of + (somewhat) finished items.</task> + </help> + </project> + + <project cat='net'> + <title>IPv6 cleanup</title> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + + <common>Zeeb</common> + </name> + + <email>bz@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://sources.zabbadoz.net/freebsd/ipv6/">Project + summary</url> + + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/bz/ipv6"> + P4 workspace for future changes</url> + </links> + + <body> + <p>Initial changes include: + <ul> + <li>Changed ip6_sprintf to no longer return a static buffer.</li> + + <li>Started to adopt in6_pcb* code to what we have for legacy + IP.</li> + </ul> + + <br /> + + Next steps will be to reduce the number of global variables and + caches.</p> + </body> + + <help> + <task>Cleanup code.</task> + + <task>Make everything MPSafe.</task> + + <task>Enhance things and add new features.</task> + </help> + </project> + + <project cat='soc'> + <title>IPv6 Vulnerabilities</title> + + <contact> + <person> + <name> + <given>George</given> + + <common>Neville-Neil</common> + </name> + + <email>gnn@freebsd.org</email> + </person> + + <person> + <name> + <given>Clément</given> + + <common>Lecigne</common> + </name> + + <email>clemun@GMAIL.COM</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/ClementLecigne" /> + </links> + + <body> + <p>Clement has been working both with libnet and gnn's Python based + packet library (PCS) to produce code to test for vulnerabilities in + IPv6. To Clement has found some issues, all of which have been + reported to his mentor and to Security Officer at FreeBSD.org + Vulnerabilities will not be reported here.</p> + </body> + + <help> + <task>Get 0.1 of PCS on to SourceForge for wider use.</task> + </help> + </project> + + <project cat='soc'> + <title>Jail Resource Limits</title> + + <contact> + <person> + <name> + <given>Chris</given> + + <common>Jones</common> + </name> + + <email>cdjones@freebsd.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Project is in development with initial working software expected + mid-July 2006. CPU limits will be implemented with a hierarchical + scheduler: (initially) using a round-robin scheduler to select + which jail to run a task in and then delegating which task in the + jail to be run to a per-jail scheduler.</p> + </body> + + <help> + <task>Complete round-robin inter-jail scheduler (with existing 4BSD + schedulers implemented per jail).</task> + + <task>Add hooks for memory tracking.</task> + </help> + </project> + + <project cat='soc'> + <title>K Kernel Meta-Language</title> + + <contact> + <person> + <name> + <given>Spencer</given> + + <common>Whitman</common> + </name> + + <email>joecat@cmu.edu</email> + </person> + + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.ORG</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/SpencerWhitman" /> + </links> + + <body> + <p>A simple lexer and parser have almost been completed. Also + significant planing for future additions to K have been thought + up.</p> + </body> + + <help> + <task>Finish the lexer and parser</task> + + <task>Implement the #! preprocessor function</task> + + <task>Add lint like functionality to the preprocessor</task> + + <task>Add style(9) checking to the preprocessor</task> + + <task>Allow for detection of unused #includes</task> + </help> + </project> + + <project cat='soc'> + <title>Linuxolator kernel update to match functionality of + 2.6.x</title> + + <contact> + <person> + <name> + <given>Roman</given> + + <common>Divacky</common> + </name> + + <email>rdivacky@freebsd.org</email> + </person> + + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/RomanDivacky">Summer of Code + proposal</url> + </links> + + <body> + <p>FreeBSD linux emulation layer (linuxolator) currently implements + most of the functionality necessary to emulate 2.4.2 linux kernel, + but linux world has moved forward and current linux world requires + 2.6.x features. The aim of this SoC task is to make Fedora Core 4 + linux-base to be able to run with 2.6.x kernel. Currently this + means extending clone() syscall and implement pthread related + things. This involves TLS implementation (sys_set_thread_area + syscall) and possibly tid manipulation (used for pthread_join etc.) + and finally futexes (linux fast user-space mutexes implementation). + This should enable pthread-linked programs to work. After this is + done there may be other things necessary to implement however, only + time will tell. I am funded by google.com in their SoC to do this + work and I'll continue to work on this after the summer hopefully + as a part of my MSc. thesis.</p> + </body> + + <help> + <task>Finish the TLS thing + other thread related things (tid comes + to mind and looks necessary for pthread to work)</task> + + <task>Futexes also look necessary for pthread to work</task> + + <task>maybe other things to be able to run basic programs under + 2.6.16 linuxolator</task> + </help> + </project> + + <project cat='soc'> + <title>Improving Ports Collection</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://wiki.freebsd.org/G%C3%A1borK%C3%B6vesd%C3%A1n"> + Wiki page about the project</url> + + <url href="http://wiki.freebsd.org/DESTDIR">Explaining + DESTDIR</url> + + <url href="http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/98105"> + ports/98105</url> + </links> + + <body> + <p>The improved support for the i386 binaries are ready for -exp + run. It only allows installing such ports on amd64 and ia64 when + there's a compatibility layer compiled into the kernel and the + 32-bit libraries are installed under /usr/lib32.</p> + + <p>The DESTDIR support are in progress. It works for the simplest + ports without USE_* that don't have a [pre|do|post]-install target. + There are more complicated issues with e.g. conflict checking in + DESTDIR, deinstalling from DESTDIR, those have to be fixed as + well.</p> + </body> + + <help> + <task>DESTDIR issues should be fixed.</task> + + <task>All ports should be examined whether they respect CC/CFLAGS, + and the erroneous ones should be fixed.</task> + + <task>Fetch scripts should be taken out of bsd.port.mk to be + separate scripts.</task> + + <task>A tool should be written that makes possible to cross-compile + ports.</task> + + <task>A good plist generator tool should be written for porters or + the old one in ports/Tools/scripts should be updated.</task> + </help> + </project> + + <project cat='docs'> + <title>Hungarian translation of the webpages</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://gabor.t-hosting.hu/data/hu/">Current status</url> + </links> + + <body> + <p>The translated webpage is almost ready now. This Hungarian + translation is a "lite" version of the original English webpages, + since there are parts that are irrelevant for the Hungarian + community, or has pieces of data that change quickly, so it's no + use to translate these pages now, maybe later, if we have more + Hungarian contributors, but this webpage would be a good starting + point in translating the documentations, and we need a good place + to put translated documentations anyway.</p> + + <p>I'm going to be very busy with SoC this summer, but I'll try to + find people that can help me out in this project. Any help + appreciated.</p> + </body> + + <help> + <task>The remaining important pages should be translated.</task> + + <task>The press/media/news sections should be restructured somehow + to being fed from the English webapges, since we don't have too + much Hungarian resource to make these up to date.</task> + + <task>There's a rendering issue when browsing the pages with + JavaScript enabled, but this can be server-side for me, this should + be investigated as well.</task> + </help> + </project> + + <project cat='net'> + <title>Multi-IP v4/v6 jails</title> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + + <common>Zeeb</common> + </name> + + <email>bz@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/bz/jail"> + P4 workspace</url> + </links> + + <body> + <p>As an intermediate step until FreeBSD will have full network + stack virtualisation this work shall provide support for multi-IP + IPv4/v6 jails.</p> + + <p>These changes are based on Pawel Jakub Dawidek's work for + multi-IPv4 jails and some initial work from Olivier Houchard for + single-IPv6 jails.</p> + + <p>The changes need some more testing but basically things + work.</p> + + <p>This is not considered to be the right thing todo so do + <b>not</b> + + ask for official support or if this will be committed to the + FreeBSD source repository. + <br /> + + After some more cleanup of non-jail related IPv6 changes I will + publish a patch for HEAD and perhaps RELENG_6 for everyone who + wants to give it a try anyway.</p> + </body> + + <help> + <task>(IPv6) related security checks.</task> + + <task>Write some tests. Especially IPv6 changes need more + testing.</task> + + <task>Check what general changes might need merging to HEAD.</task> + </help> + </project> + + <project cat='net'> + <title>FreeBSD NFS Status Report</title> + + <contact> + <person> + <name> + <given>Chuck</given> + + <common>Lever</common> + </name> + + <email>cel@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Mohan Srinivasan committed his changes to make the NFSv2/3 client + MP safe to HEAD this quarter. Changes may be back-ported to 6.x + soon.</p> + + <p>Robert Watson and Chuck Lever held a discussion about the future + of the in-kernel NFSv4 client during BSDCan 2006. The current NFSv4 + client is unmaintained. Chuck also pointed out the long series of + unfixed PRs against the legacy client (NFSv2/3). These are at the + top of his priority list. Robert is also interested in making + NFSv4-style ACLs the lingua franca for FreeBSD file systems. There + was some discussion about integrating Rick MacKlem's NFSv4 server + into 7.x.</p> + + <p>Chuck Lever became a full source committer during this + quarter.</p> + </body> + </project> + + <project cat='soc'> + <title>Nss-LDAP importing and nsswitch subsystem improvement</title> + + <contact> + <person> + <name> + <given>Michael</given> + + <common>Bushkov</common> + </name> + + <email>bushman@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://wiki.freebsd.org/LdapCachedDetailedDescription"> + Wiki-pages containing an up-to-date information about project + implementation details.</url> + + <url href="http://wiki.freebsd.org/MichaelBushkov" /> + </links> + + <body> + <p>The basic goals of this SoC 2006 project are moving + nsswitch-modules out of the libc, extending the caching daemon and + importing nss_ldap into the base source tree. 2 milestones of the + project are currently completed.</p> + + <p>1. Nss-modules were successfully moved out of the libc into the + separate dynamic libraries. In order for static binaries to work + properly (they can't use dynamic nss-modules), nss-modules are + linked statically into the libc.a. As the side-effect of + nss-modules separation, getipnodeby***() functions were rewritten + to use gethostby***() functions and not the nsdispatch(3) call. + Caching daemon's "perform-actual-lookups" option was extended to + support all implemented nsswitch databases.</p> + + <p>2. A set of regressions tests was made to test nsswitch-related + functions. These tests are also capable of testing the stability of + these functions' behaviour after the system upgrade.</p> + </body> + + <help> + <task>Import nss_ldap into the sources tree.</task> + + <task>Improve the caching daemon's performance.</task> + </help> + </project> + + <project cat='vendor'> + <title>pfSense</title> + + <contact> + <person> + <name> + <given>Scott</given> + + <common>Ullrich</common> + </name> + + <email>sullrich@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://www.pfsense.com" /> + </links> + + <body> + <p>pfSense is rapidly approaching release. We are down to a + handfull of bugs that should be fixed in the coming weeks. We + should have a release around the time of our 2nd annual hackathon + which is taking place on July 21st - July 28th. Many exciting + sub-projects are taking place within pfSense and the project is + gaining new developers monthly.</p> + </body> + + <help> + <task> + <a href="http://cvstrac.pfsense.com/rptview?rn=6"> + http://cvstrac.pfsense.com/rptview?rn=6</a> + + lists the remaining open bugs.</task> + </help> + </project> + + <project cat='bin'> + <title>Low-overhead performance monitoring tools</title> + + <contact> + <person> + <name> + <given>Joseph</given> + + <common>Koshy</common> + </name> + + <email>jkoshy@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/LibElf">Wiki page tracking + LibELF</url> + + <url href="http://wiki.freebsd.org/PmcTools">Wiki page for + PmcTools</url> + + <url + href="http://people.freebsd.org/~jkoshy/projects/perf-measurement/"> + PMC Tools Project</url> + </links> + + <body> + <p>As an intermediate step towards implementing support for + callgraphs and cross-architecture performance measurements, I am + creating a BSD-licensed library for ELF parsing & manipulation. + This library will implement the SysV/SVR4 (g)ELF[3] API.</p> + + <p>Current status: Implementation of the library is in progress. A + TET-based test suite for the API and manual pages documenting the + library's interfaces are being concurrently created.</p> + + <p>Work is being done in FreeBSD's Perforce repository. I hope to + be ready for general review by the end of July '06.</p> + </body> + + <help> + <task>Reviewers are needed for the code and the test suite. If you + have extensions to the stock SysV/SVR4 ELF(3) API that you would + like to see in -lelf, please send mail.</task> + </help> + </project> + + <project cat='ports'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Erwin</given> + + <common>Lansing</common> + </name> + + <email>erwin@FreeBSD.org</email> + </person> + </contact> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/ports/">The FreeBSD Ports + Collection</url> + + <url + href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"> + Contributing to the FreeBSD Ports Collection</url> + + <url href="http://portsmon.FreeBSD.org/index.html">FreeBSD ports + monitoring system</url> + + <url href="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD + ports unfetchable distfile survey (Bill Fenner's report)</url> + + <url href="http://beta.inerd.com/portscout/">portscout</url> + + <url href="http://www.freebsd.org/portmgr/index.html">The FreeBSD + Ports Management Team</url> + + <url href="http://tinderbox.marcuscom.com">marcuscom + tinderbox</url> + </links> + + <body> + <p>During this time, a huge number of ports PRs were committed, + bringing us back down below 800 for the first time since the + 5.5/6.1 release cycle. This is due to a great deal of work, + especially from some of our newest committers.</p> + + <p>This is all the more notable given the fact that we have been + adding new ports at a rapidly accelerating rate. We have now + exceeded the 15,000 port mark!</p> + + <p>Three sets of changes have been added to the infrastructure, + including updates of default versions of MySQL, PHP, LDAP, and + linux_base, and numerous bugfixes and improvements. About 2 dozen + portmgr PRs were closed due to this.</p> + + <p>In addition, a large-impact commit was made that attempts to + move us to a single libtool that is as unmodified from 'stock' + libtool as we can. Plans are also in place to do this for the + autotools.</p> + + <p>Several people are at work on implementing the modularised xorg + ports. Most of the work is done but several key pieces remain. Once + this is finished, an -exp regression test will be needed (most + likely, more than one :-) ) It is possible that before this we will + need to do a regression test that moves X11BASE back into + LOCALBASE. This is still under study.</p> + + <p>Gábor Kövesdán started a Google Summer of Code + project on some highly needed improvements on the ports infrastructure + (see elsewhere in this report). As this is a long term project, gtetlow + kindly imported the most important ports infrastructure files into + perforce to ease development. Other developers are encouraged to + use perforce for ports development, especially as it can help + keeping patches up-to-date while going stale in GNATS. Even though + linimon has been pushing hard on running experimental builds on the + test cluster, it will take some time to work through the + backlog.</p> + + <p>erwin added a ports section to the list of projects and ideas + for volunteers at the FreeBSD website. Have a look if you want to + work on the ports system. Don't hesitate to send additional ideas, + and committers are encouraged to add themselves as technical + contacts.</p> + + <p>sem adopted portupgrade after it had been neglected for some + time and has been very active on upgrades and bugfixing.</p> + + <p>dougb has continued to enhance his portmaster script and people + are finding success with it; although not designed to be as + full-featured as portupgrade, it does seem to be easier to + understand and use.</p> + + <p>shaun has contributed portscout, a scanner for updated + distfiles, to the ports collection.</p> + + <p>marcus upgraded GNOME to 2.14.1.</p> + + <p>As well, there have been new releases of the ports tinderbox + code.</p> + + <p>edwin has been hard at work on a PR-autoassigner for ports PRs, + which has saved a lot of time and been well-received. It has now + been installed on a freebsd.org machine (hub).</p> + + <p>linimon has been more active in pursuing maintainer-timeouts, + and has reset a number of inactive maintainers, with more in the + pipeline. The intent is to try to reduce the number of PRs that sit + around unanswered for two weeks. In almost all cases the resets are + due to no response at all; maintainers who are merely "busy" are + not the source of most of these problems, and deserve the benefit + of the doubt. Some of the maintainers that have been reset haven't + contributed in months or even years.</p> + + <p>We have added 10 (!) new committers since the last report.</p> + </body> + + <help> + <task>We need help getting back to our modern low of 500 + PRs.</task> + + <task>We have over 4,000 unmaintained ports (see, for instance, + <a + href="http://portsmon.freebsd.org/portsconcordanceformaintainer.py?maintainer=ports@FreeBSD.org"> + the list on portsmon</a> + + ). We are always looking for dedicated volunteers to adopt at least + a few ports.</task> + + <task>We can always use help with infrastructural enhancements. See + the ports section of + <a href="http://www.freebsd.org/projects/ideas/">the list of + projects and ideas</a> + + .</task> + </help> + </project> + + <project cat='vendor'> + <title>BSDInstaller</title> + + <contact> + <person> + <name> + <given>Andrew</given> + + <common>Turner</common> + </name> + + <email>soc-andrew@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/moin.cgi/BSDInstaller" /> + </links> + + <body> + <p>Since the last status report ports have been created for all + parts of the BSDInstaller except the backend.</p> + + <p>A snapshot of the BSDInstaller was released during this quarter. + This has shown a number of bugs with the installation process. Most + have now been fixed.</p> + </body> + </project> + + <project cat='kern'> + <title>Giant-Less UFS with Quotas</title> + + <contact> + <person> + <name> + <given>Konstantin</given> + + <common>Belousov</common> + </name> + + <email>kib@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~kib/quotagiant" /> + </links> + + <body> + <p>The patches to allow UFS operate with quotas in Giant-less mode + are brewed for long now. Since recent huge pile of fixes into + snapshots code, I think the problems you could encounter are caused + solely by the patch.</p> + + <p>Aside performance benefits, patch has another one, much more + valuable. It makes UFS operating in one locking regime whatever + options are compiled into kernel. I think, in long term, that would + lead to better stability of the system.</p> + </body> + + <help> + <task>I need testers feedback. Both stability reports and + performance measurements are welcomed !</task> + </help> + </project> + + <project cat='ports'> + <title>Update of the Linux userland infrastructure in the Ports + Collection</title> + + <contact> + <person> + <name> + <given>Boris</given> + + <common>Samorodov</common> + </name> + + <email>bsam@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Emulation</given> + + <common>Mailinglist</common> + </name> + + <email>emulation@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>We updated the default linux base port to Fedora Core 4 and the + default linux X11 libs port to the X.org RPM in FC4.</p> + + <p>An update to FC5 or FC6 has to wait until the kernel got support + for syscalls of a newer linux kernel. See the corresponding SoC + project report for more.</p> + </body> + </project> + + <project cat='kern'> + <title>Sound subsystem improvements</title> + + <contact> + <person> + <name> + <given>Ariff</given> + + <common>Abdullah</common> + </name> + + <email>ariff@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Multimedia</given> + + <common>Mailinglist</common> + </name> + + <email>multimedia@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~ariff/">Some patches.</url> + + <url href="http://www.FreeBSD.org/projects/ideas/">The FreeBSD + Project Ideas List.</url> + + <url href="http://www.leidinger.net/FreeBSD/hdac_20060525.tbz"> + Rudimentary HDA support.</url> + </links> + + <body> + <p>Since the last status report we fixed some more bugs, added + basic support for envy24 chips and cleaned up the source for the + emu10kx driver in the ports to make it ready for import into the + base system.</p> + + <p>We also got some patches with a little bit of infrastructure for + Intel HDA support. It's not finished and also not usable by end + users yet.</p> + </body> + + <help> + <task>Have a look at the sound related entries on the ideas + list.</task> + + <task>sndctl(1): tool to control non-mixer parts of the sound + system (e.g. spdif switching, virtual-3D effects) by an user + (instead of the sysctl approach in -current); pcmplay(1), + pcmrec(1), pcmutil(1).</task> + + <task>Plugable FEEDER infrastructure. For ease of debugging various + feeder stuff and/or as userland library and test suite.</task> + + <task>Support for new hardware (envy24, Intel HDA).</task> + </help> + </project> + + <project cat='kern'> + <title>XFS for FreeBSD</title> + + <contact> + <person> + <name> + <given>Russell</given> + + <common>Cattelan</common> + </name> + + <email>cattelan@xfs.org</email> + </person> + + <person> + <name> + <given>Alexander</given> + + <common>Kabaev</common> + </name> + + <email>kan@freebsd.org</email> + </person> + + <person> + <name> + <given>Craig</given> + + <common>Rodrigues</common> + </name> + + <email>rodrigc@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~rodrigc/xfs/">XFS for + FreeBSD</url> + </links> + + <body> + <p>The XFS for FreeBSD project is an effort to port the publicly + available GPL'd sources to SGI's XFS filesystem to FreeBSD.</p> + + <p>In December, we imported a version of XFS into FreeBSD-CURRENT + which allows FreeBSD to mount an XFS filesystem as read-only.</p> + + <p>As a side effort, we have been continuing on the work that PHK + started to clean up the mount code in FreeBSD. We can use the + existing FreeBSD mount(8) utility to mount an XFS partition, + without introducing a new mount_xfs utility.</p> + </body> + + <help> + <task>We need to implement support for writing to XFS + partitions</task> + </help> + </project> + + <project cat='net'> + <title>SCTP Integration</title> + + <contact> + <person> + <name> + <given>George</given> + + <common>Neville-Neil</common> + </name> + + <email>gnn@freebsd.org</email> + </person> + + <person> + <name> + <given>Randall</given> + + <common>Stewart</common> + </name> + + <email>rrs@cisco.com</email> + </person> + </contact> + + <links> + <url href="http://www.sctp.org/">Stream Transmission Control + Protocol</url> + </links> + + <body> + <p>For the last several months Randall Stewart has been working in + HEAD and STABLE to get us ready to integrate the SCTP protocol + (Stream Transmission Control Protocol) into FreeBSD. He is + currently working on a patch to share with a wider audience but + needs to do some integration work first. Randall has a provisional + commit bit and will be working with gnn on getting code committed + to the HEAD of the tree.</p> + </body> + + <help> + <task>When this gets integrated it needs lots of testers.</task> + </help> + </project> + + <project cat='misc'> + <title>FreeBSD Security Officer and Security Team</title> + + <contact> + <person> + <name> + <given>Security</given> + + <common>Officer</common> + </name> + + <email>security-officer@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Security</given> + + <common>Team</common> + </name> + + <email>security-team@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/security/" /> + + <url + href="http://www.freebsd.org/administration.html#t-secteam" /> + + <url href="http://vuxml.freebsd.org/" /> + </links> + + <body> + <p>In the time since the last status report, four security + advisories have been issued concerning problems in the base system + of FreeBSD; of these, one problem was "contributed" code, while + three were in code maintained within FreeBSD. The Vulnerabilities + and Exposures Markup Language (VuXML) document has continued to be + updated by the Security Team and Ports Committers documenting new + vulnerabilities in the FreeBSD Ports Collection; since the last + status report, 71 new entries have been added, bringing the total + up to 757.</p> + + <p>The following FreeBSD releases are supported by the FreeBSD + Security Team: FreeBSD 4.11, FreeBSD 5.3, FreeBSD 5.4, FreeBSD 5.5, + FreeBSD 6.0, and FreeBSD 6.1. The respective End of Life dates of + supported releases are listed on the web site; of particular note, + FreeBSD 5.3 and FreeBSD 5.4 will cease to be supported at the end + of October 2006, while FreeBSD 6.0 will cease to be supported at + the end of November 2006.</p> + </body> + </project> + + <project cat='kern'> + <title>Gvinum improvements</title> + + <contact> + <person> + <name> + <given>Ulf</given> + + <common>Lilleengen</common> + </name> + + <email>lulf@stud.ntnu.no</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>I have been working on porting missing features in gvinum from + vinum, as well as adding new features.</p> + + <p>So far the resetconfig, detach, dumpconfig, setstate (on plexes + and volumes) and stop commands have been implemented, as well as + some other minor fixes. The attach command is currently being + implemented, and started on disk-grouping. Currently most of this + is in p4, but patches will be submitted as soon as possible.</p> + </body> + </project> + + <project cat='net'> + <title>Wireless Networking</title> + + <contact> + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@errno.com</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The wireless support has been stable for a while so most work has + focused on bug fixing and improving legacy drivers.</p> + + <p>Max Laier and I worked on improving support for Intel wireless + cards. The results of this work included significant improvements + to the iwi(4) driver (for 2195/2200 parts) and the firmware(9) + facility for managing loadable device firmware. There is also an + updated ipw(4) that has improvements similar to those done for iwi + that is in early test. Support for the latest Intel devices, the + 3945 pci-express cards, is planned for later this summer.</p> + + <p>Atheros support was updated with a new hal that fixes a few + minor issues and provides known working builds for SPARC, PPC, and + ARM platforms. There is also working MIPS support that will be used + when the MIPS port is ready to test. Otherwise one useful bug was + fixed that affected AP operation with associated stations operating + in power save mode.</p> + + <p>wpa_supplicant and hostapd were updated to the latest stable + build releases from Jouni Malinen.</p> + + <p>Experimental changes to support injection of raw 802.11 frames + using bpf were posted for comment. This work was done in + collaboration with Andrea Bittau.</p> + </body> + + <help> + <task>Legacy drivers such as wi are languishing and need + maintainers. This is prerequisite to bringing in new 802.11 + features such as improved scanning and virtual ap.</task> + </help> + </project> + + <project cat='vendor'> + <title>xscale board buy</title> + + <contact> + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@errno.com</email> + </person> + </contact> + + <links> + <url href="http://www.gateworks.com/avila_gw2348_4.htm" /> + + <url href="http://www.netgate.com" /> + </links> + + <body> + <p>With the help of Jim Thompson of Netgate ( + <a href="http://www.netgate.com/">http://www.netgate.com/</a> + + ) the FreeBSD Foundation arranged a purchase of xscale-based boards + for folks interested in ARM support. Developers were able to + purchase boards at a reduced cost. The goals were to accelerate + and/or improve support for the ARM platform and to set forth at + least one board as a reference platform for the ARM support. + Netgate will be stocking lower-cost models of the board later in + the year (a special order was made for boards with only 2 mini-pci + slots).</p> + </body> + </project> + + <project cat='soc'> + <title>Interrupt handling</title> + + <contact> + <person> + <name> + <given>Paolo</given> + + <common>Pisati</common> + </name> + + <email>piso@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>With the introduction of fine grained locking in the SMPng + project, the FreeBSD kernel went under a major redesign, and many + subsystem changed significantly with it. In particular, device + driver's interrupt context ("the bottom half") had the necessity to + synchronise with process context ("the top half") and share data in + a consistent manner without using spl*(). To overcome this problem, + a new interrupt model based around interrupt threads was employed, + together with a fast interrupt model dedicated to particular driver + handlers that don't block on locks (i.e. serial port, clock, + etcetc). Unfortunately, even if the interrupt thread model proved + to be a reliable solution, its performance was not on par with + the pre SMPng era (4.x), and thus others solutions were + investigated, with interrupt filtering being one of that.</p> + + <p>As part of my Summer of Code 2006 work, I'm implementing + interrupt filtering for FreeBSD, and when the framework will be in + place I'll compare the performance of filters, against all the + previous models: pre-SMPng(4.x), ithread and polling.</p> + + <p>The most important modifications to the src tree so far were: + <ul> + <li>made PPC accept more than one FAST handler per irq line + (previously INTR_FAST implied INTR_EXCL)</li> + + <li>converted all the INTR_FAST handlers to be filters: return an + error code to note what they did (FILTER_HANDLED/FILTER_STRAY) + and if they need more work to do (FILTER_SCHEDULE_THREAD)</li> + + <li>moved part of the interrupt execution code from MD code to + kern_intr.c::intr_filter_loop()</li> + + <li>broke newbus API: bus_setup_intr() grew a new filter + parameter of type "int driver_filter_t(void*)".</li> + + <li>converted all the buses that override bus_setup_intr() to + handle filters</li> + + <li>converted all the normal ithread drivers to provide a NULL + filter funcion</li> + </ul> + + <br /> + + The next milestone is to have all the different models (filters + only, ithread only and filter + ithread) work together + reliably.</p> + </body> + + <help> + <task>Arm is largely untested</task> + + <task>Sparc64 needs more work on low level (.s) interrupt + routine</task> + </help> + </project> + + <project cat='arch'> + <title>PowerPC Port</title> + + <contact> + <person> + <name> + <given>Peter</given> + + <common>Grehan</common> + </name> + + <email>grehan@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/platforms/ppc.html" /> + </links> + + <body> + <p>The project is slowly starting to ramp up after a long + move-induced hiatus.</p> + + <p>Alan Cox has almost completed making the pmap module + Giant-free.</p> + </body> + </project> + + <project cat='proj'> + <title>TrustedBSD Audit</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Wayne</given> + + <common>Salamon</common> + </name> + + <email>wsalamon@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Christian</given> + + <common>Peron</common> + </name> + + <email>csjp@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/audit.html">TrustedBSD Audit + Web Page</url> + </links> + + <body> + <p>TrustedBSD Audit provides fine-grained security event auditing + in FreeBSD 7.x, with a planned merge to 6.x for FreeBSD 6.2. Work + performed in the last three months: + <ul> + <li>Per audit pipe preselection allows IDS applications to + configure audit record selection per-pipe, new auditpipe.4 + document.</li> + + <li>audit_submit library call to reduce complexity of adding + audit support to applications.</li> + + <li>Significant cleanup, bug fixing, locking improvements, token + parsing and generation improvements.</li> + + <li>Solaris subject token compatibility, extended address + support.</li> + + <li>Auditing of extended attributes calls, ACL support a work in + progress.</li> + + <li>OpenBSM 1.0 alpha 7 integrated into CVS.</li> + + <li>OpenBSM test tools in progress.</li> + + <li>Experimental auditeventd which allows shared object plug-ins + to subscribe to live audit events via a shared pipe in order to + support the easy authoring of simple intrusion detection and + monitoring components.</li> + </ul> + </p> + </body> + + <help> + <task>Bring audit event daemon API and implementation to maturity. + Currently these are not installed by default in the CVS-merged + version.</task> + + <task>Complete system call coverage.</task> + + <task>Allow finer-grained configuration of what is audited: + implement control flags regarding paths, execve arguments, + environmental variables.</task> + + <task>Support for auditing MAC policy data.</task> + + <task>Additional user space application coverage, such as + application layer audit events from adduser, rmuser, pw, + etc.</task> + </help> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2006-06-2006-10.xml b/en_US.ISO8859-1/htdocs/news/status/report-2006-06-2006-10.xml new file mode 100644 index 0000000000..12272d0605 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2006-06-2006-10.xml @@ -0,0 +1,2625 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status +Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2006-06-2006-10.xml,v 1.6 2008/08/16 21:55:59 pgj Exp $ --> +<report> + <date> + <month>July-September</month> + + <year>2006</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report covers FreeBSD related projects between June and + October 2006. This includes the conclusion of this year's Google + Summer of Code with 13 successful students. Some of last year's and + the current SoC participants have meanwhile joined the committer + ranks, kept working on their projects, and improving FreeBSD in + general.</p> + + <p>This year's + <a href="http://www.eurobsdcon.org/">EuroBSDCon</a> + + in Milan, Italy has meanwhile published an exciting program. Many + developers will be there to discuss these current and future projects + at the Developer Summit prior the conference. Next year's + conference calendar has a new entry - in addition to the now well + established + <a href="http://www.bsdcan.org/">BSDCan</a> + + in Ottawa - + <a href="http://www.asiabsdcon.org/">AsiaBSDCon</a> + + will take place in Tokyo at the beginning of March.</p> + + <p>As we are closing in on FreeBSD 6.2 release many bugs are being + fixed and new features have been MFCed. On the other hand a lot of + the projects below already are focusing on FreeBSD 7.0 and promise + a lot of exciting news and features to come.</p> + + <p>Thanks to all the reporters for the excellent work! We hope you + enjoy reading.</p> + </section> + + <category> + <name>soc</name> + + <description>Google Summer of Code</description> + </category> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>team</name> + + <description>FreeBSD Team Reports</description> + </category> + + <category> + <name>net</name> + + <description>Network Infrastructure</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <category> + <name>bin</name> + + <description>Userland Programs</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='bin'> + <title>OpenBSD dhclient</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Most dhclient changes in HEAD have been merged to 6-STABLE for + 6.2-RELEASE. The highlight of these changes is a fix for runaway + dhclient processes when packets are not 4 byte aligned. Further + changes including always sending client identifiers are scheduled + for merge before the release. Work is ongoing to improve dhclient's + interaction with alternate methods of setting interface + addresses.</p> + </body> + </project> + + <project cat='arch'> + <title>FreeBSD/arm on Atmel AT91RM9200</title> + + <contact> + <person> + <name> + <given>Warner</given> + + <common>Losh</common> + </name> + + <email>imp@freebsd.org</email> + </person> + + <person> + <name> + <given>Olivier</given> + + <common>Houchard</common> + </name> + + <email>cognet@freebsd.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The FreeBSD/arm port has grown support for the Atmel AT91RM9200. + Boards based on this machine are booting to multiuser off either + NFS or an SD card. The onboard serial ports, PIO, ethernet and + SD/MMC card controllers are well supported. Support for the SSC, + IIC and SPI flash parts in the kernel will be forthcoming + shortly.</p> + + <p>In addition to normal kernel support, the port includes a boot + loader that can initialize memory and boot off IIC eeprom, SPI + DataFlash, BOOTP/TFTP and SD memory cards.</p> + + <p>The port will be included in forthcoming commercial + products.</p> + </body> + + <help> + <task>Add support for other members of the AT91 family of arm9 + processors.</task> + + <task>Finish support for AT45D* flash parts.</task> + + <task>Finish support for USB ports</task> + + <task>Write support for USB Device functionality</task> + </help> + </project> + + <project cat='soc' summary='t'> + <title>Summer of Code Summary</title> + + <contact> + <person> + <name> + <given>Murray</given> + + <common>Stokely</common> + </name> + + <email>murray@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/summerofcode-2006.html"> + FreeBSD Summer of Code 2006</url> + + <url href="http://wiki.freebsd.org/SummerOfCode2006">SoC 2006 + Student wiki</url> + + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2006/"> + SoC 2006 Perforce trees</url> + </links> + + <body> + <p>We had another successful summer taking part in the Google + Summer of Code. By all accounts, the FreeBSD participation in this + program was an unqualified success. We received over 150 + applications for student projects, amongst which 13 were selected + for funding. All successful students received the full $4,500.</p> + + <p>These student projects included security research, improved + installation tools, new utilities, and more. Many of the students + have continued working on their FreeBSD projects even after the + official close of the program. At least 2 of our FreeBSD mentors + will be meeting with Google organizers in Mountain View this month + to discuss the program at the Mentor Summit.</p> + </body> + </project> + + <project cat='team'> + <title>Release Engineering</title> + + <contact> + <person> + <name> + <common>Release Engineering Team</common> + </name> + + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/" /> + + <url href="http://www.FreeBSD.org/releases/" /> + + <url href="http://www.FreeBSD.org/snapshots/" /> + </links> + + <body> + <p>The FreeBSD Release Engineering team is currently working on + FreeBSD 6.2-RELEASE, which is scheduled for release in early + November 2006. Some notable features of this release include the + debut of security event auditing as an experimental feature, Xbox + support, the FreeBSD Update binary updating utility, and of course + many fixes and updates for existing programs. Pre-release images + for all Tier-1 architectures are available for testing now; + feedback on these builds is greatly appreciated. More information + about release engineering activities can be found at the links + above.</p> + </body> + </project> + + <project cat='soc'> + <title>IPv6 Stack Vulnerabilities</title> + + <contact> + <person> + <name> + <given>George</given> + + <common>Neville-Neil</common> + </name> + + <email>gnn@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Clement</given> + + <common>Lecigne</common> + </name> + + <email>clem1@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/ClementLecigne">SoC Student + Wiki</url> + + <url href="http://pcs.sf.net">PCS Library</url> + </links> + + <body> + <p>The focus of this project was to review past vulnerabilities, + create vulnerability testing tools and to discover new + vulnerabilities in the FreeBSD IPv6 stack which is derived from the + KAME project code. During the summer Clement took two libraries, + the popular libnet, and his mentor's Packet Construction Set (PCS) + and created tools to find security problems in the IPv6 code. + Several issues were found, bugs filed, and patches created. At the + moment Clement and George are editing a 50 page paper that + describes the project which will be submitted for conference + publication.</p> + + <p>All of the code from the project, including the tools, is + online and is described in the paper.</p> + + <p>By all measures, this was a successful project. Both student and + mentor gained valuable insight into a previously externally + maintained set of code. In addition to the new tools development in + this effort, the FreeBSD Project has gained a new developer to help + work on the code.</p> + </body> + </project> + + <project cat='soc'> + <title>Analyze and Improve the Interrupt Handling + Infrastructure</title> + + <contact> + <person> + <name> + <given>Paolo</given> + + <common>Pisati</common> + </name> + + <email>pisati@FreeBSD.org</email> + </person> + + <person> + <name> + <given>John</given> + + <common>Baldwin</common> + </name> + + <email>jhb@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/Interrupts">SoC Student + Wiki</url> + </links> + + <body> + <p>This project consisted in the improvement of the Interrupt + Handling System in FreeBSD: while retaining backward compatibility + with the previous models (FAST and ITHREAD), a new method called + 'Interrupt filtering' was added. With interrupt filtering, the + interrupt handler is divided into 2 parts: the filter (that checks + if the actual interrupt belong to this device) and the ithread + (that is scheduled in case some blocking work has to be done). The + main benefits of interrupt filtering are:</p> + + <ul> + <li>Feedback from filters (the system finally knows if any + handler has serviced an interrupt or not, and can react + consequently).</li> + + <li>Lower latency/overhead for shared interrupt line.</li> + + <li>Previous experiments with interrupt filtering showed an + increase in performance against the plain ithread model</li> + </ul> + + <p>Moreover, during the development of interrupt filtering, some MD + dependent code was converted into MI code, PPC was fixed to support + multiple FAST handlers per line and an interrupt stray storm + detection logic was added. While the framework is done, there are + still machine dependent bits to be written (the support for ppc, + sparc64, arm and itanium has to be written/reviewed) and a serious + analysis of the performance of this model against the previous one + is a work-in-progress</p> + </body> + </project> + + <project cat='soc'> + <title>Jail Resource Limits</title> + + <contact> + <person> + <name> + <given>Chris</given> + + <common>Jones</common> + </name> + + <email>cdjones@freebsd.org</email> + </person> + + <person> + <name> + <given>Kip</given> + + <common>Macy</common> + </name> + + <email>kmacy@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/JailResourceLimits">SoC + Student Wiki</url> + </links> + + <body> + <p>We now have support for limiting CPU and memory use in jails. + This allows fairer sharing of a systems' resources between divergent + uses by preventing one jail from monopolizing the available memory + and CPU time, if other users and jails have processes to run.</p> + + <p>The code is currently available as patches against RELENG_6, and + Chris is in the process of applying it to -CURRENT. More details + can be found at JailResourceLimits on the wiki.</p> + </body> + + <help> + <task>Port patches against -CURRENT.</task> + </help> + </project> + + <project cat='soc'> + <title>Bundled PXE Installer</title> + + <contact> + <person> + <name> + <given>Markus</given> + + <common>Boelter</common> + </name> + + <email>m@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Paul</given> + + <common>Saab</common> + </name> + + <email>ps@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/MarkusBoelter">SoC Student + Wiki</url> + </links> + + <body> + <p>For me, the Google Summer of Code was a new and very exciting + experience. I got actively involved in doing Open Source Software + and giving something back to the community. Facing some + challenges within the project forced me to look behind the scenery + of FreeBSD. The result was a better understanding of the overall + project. Working with a lot of developers directly also + gave a very special spirit to the Google Summer of Code.</p> + + <p>I really enjoyed the time and will continue to work on the + project after the deadline. For me, it was a great chance to get + involved in active development and not just some scripts and hacks + at home. Getting paid for the work was just a small part of the + overall feeling.</p> + + <p>Thanks to the people at the FreeBSD Project and Google for the + really, really great time!</p> + </body> + </project> + + <project cat='soc'> + <title>Nss-LDAP importing and nsswitch subsystem improvement</title> + + <contact> + <person> + <name> + <given>Michael</given> + + <common>Bushkov</common> + </name> + + <email>bushman@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Hajimu</given> + + <common>UMEMOTO</common> + </name> + + <email>ume@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/MichaelBushkov">SoC Student + Wiki</url> + + <url href="http://wiki.freebsd.org/LdapCachedOriginalProposal"> + Original Project Proposal</url> + + <url + href="http://wiki.freebsd.org/LdapCachedDetailedDescription"> + Detailed Description of the Completed Project</url> + </links> + + <body> + <p>The Project consisted of five parts:</p> + + <ol> + <li>Nsswitch modules and libc separation. The idea was to move + the source code for different nsswitch sources (such as "files", + "dns", "nis") out of the libc into the separate shared libraries. + This task was successfully finished and the patch is + available.</li> + + <li>Regression tests for nsswitch. A set of regression tests to + test the correctness of all nsswitch-related functions and the + invariance of their behavior between system upgrades. The task + can be considered successfully completed, the patch is + available.</li> + + <li>Rewriting nss_ldap. Though, this task was not clearly + mentioned in the original proposal, during the SoC we found + it would be easier, not to simply import PADL's nss_ldap, but + to rewrite it from scratch (licensing issues were among the + basic reasons for this). The resulting module behaves similarly + to PADL's module, but has a different architecture that is more + flexible. Though it's basically finished, several useful + features from the PADL's nss_ldap still need to be implemented. + Despite the lack of some features, this task can be considered + successfully completed. Missing features will be implemented as + soon as possible, hopefully during September.</li> + + <li>Importing nss_ldap into the Base System. The task was to + prepare a patch, that will allow users to use nss_ldap from the + base system. The task was successfully completed (the patch is + available), but required importing OpenLDAP into the base in + order for nss_ldap to work properly, and it had led to a long + discussion in the mailing list. This discussion, however, have + concluded with mostly positive opinions about nss_ldap and + OpenLDAP importing.</li> + + <li>Cached performance optimization. The caching daemon + performance needs to be as high as possible in order for cached + to be as close (in terms of speed) to "files" nsswitch source as + possible. Cached's performance analysis was made and nsswitch + database pre-caching was introduced as the optimization. This + task was completed (the patch is available). However there is + room for improvement. More precise and extensive performance + analysis should be made and more optimizations need to be + introduces. This will be done in the near future.</li> + </ol> + + <p>Though none of the code was committed yet into the official + FreeBSD tree, my experience from the previous year makes me think + that this situation is normal. I hope, that the code will be + reviewed and committed in the coming months.</p> + </body> + </project> + + <project cat='soc'> + <title>Porting the seref policy and setools to SEBSD</title> + + <contact> + <person> + <name> + <given>Dongmei</given> + + <common>Liu</common> + </name> + + <email>dongmei@freebsd.org</email> + </person> + + <person> + <name> + <given>Christian</given> + + <common>Peron</common> + </name> + + <email>csjp@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/DongmeiLiu">SoC Student + Wiki</url> + </links> + + <body> + <p>Dongmei Liu spent the summer working on the basic footwork + required to port the SEREF policy to SEBSD. This work has been + submitted and can be viewed in the soc2006/dongmei_sebsd Perforce + branch. This work was originated from the SEBSD branch: + //depot/projects/trustedbsd/sebsd. Additionally setools-2.3 was + ported from Linux and can be found in contrib/sebsd/setools + directory. It is hoped that this work will be merged into the main + SEBSD development branch.</p> + </body> + </project> + + <project cat='net'> + <title>SCTP Integration</title> + + <contact> + <person> + <name> + <given>Randall</given> + + <common>Stewart</common> + </name> + + <email>randall@freebsd.org</email> + </person> + + <person> + <name> + <given>George</given> + + <common>Neville-Neil</common> + </name> + + <email>gnn@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://www.sctp.org/" /> + </links> + + <body> + <p>There are currently patches available for testing. A planned + integration to HEAD is set to happen in October.</p> + </body> + + <help> + <task>The code still needs plenty of testing. See patches on + <a href="http://www.sctp.org/">sctp.org</a> + + and in -CURRENT soon.</task> + </help> + </project> + + <project cat='proj'> + <title>Embedded FreeBSD</title> + + <contact> + <person> + <name> + <given>George</given> + + <common>Neville-Neil</common> + </name> + + <email>gnn@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://www.embeddedfreebsd.org/" /> + </links> + + <body> + <p>Moved the HTML pages into the project CVS tree.</p> + </body> + + <help> + <task>Setup the web site to be served from projects CVS so that it + can be updated by others.</task> + + <task>Complete the ARM port.</task> + + <task>Work on the MIPS port.</task> + + <task>Update the documentation to include common tasks for embedded + engineers.</task> + </help> + </project> + + <project cat='net'> + <title>FAST_IPSEC Upgrade</title> + + <contact> + <person> + <name> + <given>George</given> + + <common>Neville-Neil</common> + </name> + + <email>gnn@freebsd.org</email> + </person> + + <person> + <name> + <given>Bjoern</given> + + <common>Zeeb</common> + </name> + + <email>bz@freebsd.org</email> + </person> + </contact> + + <links> + <url href="www.freebsd.org/~gnn/fast_ipv6.patch">CURRENT patch to + enable FAST_IPSEC and IPv6</url> + </links> + + <body> + <p>First working version of code. Does not pass all TAHI tests, but + does pass packets correctly and does not panic.</p> + </body> + + <help> + <task>More testing of the patch needed.</task> + </help> + </project> + + <project cat='proj'> + <title>USB</title> + + <contact> + <person> + <name> + <given>Hans Petter</given> + + <common>Sirevaag Selasky</common> + </name> + + <email>hselasky@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&HIDEDEL=NO"> + Current USB files</url> + + <url href="http://www.turbocat.net/~hselasky/usb4bsd">My USB + homepage</url> + </links> + + <body> + <p>During the last three months I have finished reworking nearly + all USB device drivers found in FreeBSD-7-CURRENT. Only two USB + drivers are left and that is ubser(4) and slhci. Some still use + Giant, but most have been brought out of Giant. At the moment I am + looking for testers that can test the various USB device drivers. + Some have already been tested, and confirmed to work, while others + have problems which need to be fixed. If you want to test, checkout + the USB perforce tree or download the SVN version of the USB driver + that is available on my homepage. At the moment the tarballs are a + little out of date.</p> + + <p>Ideas and comments with regard to the new USB API are welcome + at: + + <a href="mailto:freebsd-usb@freebsd.org"> + freebsd-usb@freebsd.org</a>.</p> + </body> + </project> + + <project cat='proj'> + <title>iSCSI Initiator</title> + + <contact> + <person> + <name> + <given>Damiel</given> + + <common>Braniss</common> + </name> + + <email>danny@cs.huji.ac.il</email> + </person> + </contact> + + <links> + <url + href="ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-17.5.tar.bz2 " /> + </links> + + <body> + <p>This iSCSI initiator kernel module and its companion control + program are still under development, but the main parts are + working.</p> + </body> + + <help> + <task>Network Disconnect Recovery.</task> + + <task>Sysctl Interface and Instrumentation.</task> + + <task>Rewrite the userland side of iscontrol.</task> + </help> + </project> + + <project cat='proj'> + <title>GJournal</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + + <common>Dawidek</common> + </name> + + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~pjd/patches/gjournal_20060930.patch"> + Patches against HEAD.</url> + + <url + href="http://people.freebsd.org/~pjd/patches/gjournal6_20060930.patch"> + Patches against RELENG_6.</url> + </links> + + <body> + <p>GJournal seems to be finished. I fixed the last serious bug and + it is now stable and reliable in our tests. I'm planning to commit + it really soon now.</p> + + <p>The work was sponsored by home.pl</p> + </body> + </project> + + <project cat='misc'> + <title>AsiaBSDCon 2007</title> + + <contact> + <person> + <name> + <given>Hiroki</given> + + <common>Sato</common> + </name> + + <email>hrs@freebsd.org</email> + </person> + + <person> + <name> + <given>George</given> + + <common>Neville-Neil</common> + </name> + + <email>gnn@freebsd.org</email> + </person> + + <person> + <email>secretary@asiabsdcon.org</email> + </person> + </contact> + + <links> + <url href="http://www.asiabsdcon.org/">Conference Web Site</url> + </links> + + <body> + <p>Web site is up and we're soliciting papers and presentations. + Some tutorials are already scheduled. Email + <a href="mailto:secretary@asiabsdcon.org"> + secretary@asiabsdcon.org</a> + + if you have questions or submissions.</p> + </body> + + <help> + <task>Send in more papers!</task> + </help> + </project> + + <project cat='docs'> + <title>Chinese (Simplified) Project</title> + + <contact> + <person> + <name> + <given>Xin</given> + + <common>LI</common> + </name> + + <email>delphij@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://cnsnap.cn.FreeBSD.org/zh_CN/">Latest snapshot for + translated website</url> + + <url href="http://cnsnap.cn.FreeBSD.org/doc/zh_CN.GB2312/">Latest + snapshot for translated documentation</url> + </links> + + <body> + <p> + <p>In the previous quarter we primarily focused on overall + quality of the translation rather than just increasing the number + of translations, and we have strived to make sure that these + translated stuff are up-to-date with their English revisions. + Also, we have merged the translated website into the central + repository.</p> + + <p>In the next quarter we will focus on developing + documentation that will help to attract more developers.</p> + </p> + </body> + + <help> + <task>Translate more development related documentation.</task> + + <task>Review more of the currently translated documentation.</task> + </help> + </project> + + <project cat='misc'> + <title>EuroBSDCon 2006</title> + + <contact> + <person> + <name> + <given>EuroBSDCon Organizing Committee</given> + + <common> + </common> + </name> + + <email>info@eurobsdcon.org</email> + </person> + </contact> + + <links> + <url href="http://www.eurobsdcon.org/">EuroBSDCon Home Page</url> + + <url href="http://www.eurobsdcon.org/register/">Registration + Page</url> + </links> + + <body> + <p>EuroBSDCon 2006 is taking place in Milan (Italy), from the 10th + to the 12th of November.</p> + + <p>EuroBSDCon represents the biggest gathering for BSD developers + from the old continent, as well as users and passionates from + around the World. It is also a chance to share experiences, + know-how, and cultures.</p> + + <p>The program is rich in talks about FreeBSD, with topics ranging + from "How the FreeBSD ports collection works" to "Interrupt + Filtering in FreeBSD". This means that both the novice and the + hacker can enjoy the conference.</p> + + <p>Registration is open. The EuroBSDCon Organizing Committee hopes + to see you in Milan.</p> + </body> + </project> + + <project cat='docs'> + <title>Hungarian translation of the webpages</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://gabor.t-hosting.hu/data/hu/">Snapshot</url> + </links> + + <body> + <p>Since the last status report, there has been a lot of progress. + I investigated a lot of charset issues and found out that HTML tidy + breaks some entities when using iso-8859-2, so HTML tidy had to be + disabled for Hungarian pages.</p> + </body> + + <help> + <task>Translate 4 pages.</task> + + <task>Review, fix typos and improve the wording where + necessary.</task> + </help> + </project> + + <project cat='team'> + <title>FreeBSD Security Officer and Security Team</title> + + <contact> + <person> + <name> + <given>Security</given> + + <common>Officer</common> + </name> + + <email>security-officer@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Security</given> + + <common>Team</common> + </name> + + <email>security-team@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/security/" /> + + <url + href="http://www.freebsd.org/administration.html#t-secteam" /> + + <url href="http://vuxml.freebsd.org/" /> + </links> + + <body> + <p>In the time since the last status report, six security + advisories have been issued concerning problems in the base system + of FreeBSD; of these, five problems were in "contributed" code, + while one was in code maintained within FreeBSD. The + Vulnerabilities and Exposures Markup Language (VuXML) document has + continued to be updated by the Security Team and Ports Committers + documenting new vulnerabilities in the FreeBSD Ports Collection; + since the last status report, 57 new entries have been added, + bringing the total up to 814.</p> + + <p>The following FreeBSD releases are supported by the FreeBSD + Security Team: FreeBSD 4.11, FreeBSD 5.3, FreeBSD 5.4, FreeBSD 5.5, + FreeBSD 6.0, and FreeBSD 6.1. The respective End of Life dates of + supported releases are listed on the web site; of particular note, + FreeBSD 5.3 and FreeBSD 5.4 will cease to be supported at the end + of October 2006, while FreeBSD 6.0 will cease to be supported at + the end of November 2006 (or possibly a short time thereafter in + order to allow time for upgrades to the upcoming FreeBSD 6.2).</p> + </body> + </project> + + <project cat='proj'> + <title>Summer of FreeBSD security development</title> + + <contact> + <person> + <name> + <given>Colin</given> + + <common>Percival</common> + </name> + + <email>cperciva@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~cperciva/funding.html" /> + + <url + href="http://www.daemonology.net/freebsd-upgrade-6.0-to-6.1/" /> + </links> + + <body> + <p>I spent the months of May through August working on improving + Portsnap, FreeBSD Update, and devoting more time to my (continuing) + role as Security Officer. FreeBSD Update is now part of the FreeBSD + base system and is fully supported by the FreeBSD Security Team; + updates are currently only being built for the i386 architecture, + but AMD64 updates will become available soon.</p> + + <p>In an attempt to reduce the number of people running out of date + (and unsupported) FreeBSD releases, I wrote an automatic binary + upgrade script for upgrading systems from FreeBSD 6.0 to FreeBSD + 6.1; I will be releasing a new script for upgrading to FreeBSD + 6.2-(RC*|RELEASE) soon (possibly before this status report is + published).</p> + + <p>Further improvements to Portsnap are still ongoing.</p> + </body> + </project> + + <project cat='proj'> + <title>Porting ZFS to FreeBSD</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + + <common>Dawidek</common> + </name> + + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs"> + Source code.</url> + + <url href="http://www.opensolaris.org/os/community/zfs/porting/"> + ZFS porting site.</url> + + <url + href="http://docs.freebsd.org/cgi/mid.cgi?20060822104516.GB16033"> + ZFS port announce.</url> + </links> + + <body> + <p>My work is moving slowly forward. ZVOL is, I believe, fully + functional (I recently fixed snapshots and clones on zvols), which + means you can put UFS on top of RAID-Z volume, take a snapshot of + the volume, clone it if needed, etc. Very cool. The hardest part is + the ZPL layer, I'm still working on it. Most file system methods + work, but probably need detailed review and many fixes. Most of the + time these days I'm spending on implementing mmap(2) correctly. It + works more or less in simple tests but fails under fsx program. On + the other hand, 'fsx -RW' works very stable and reliable. Other + test programs (those that don't use mmap(2)) also work quite well. + There is still a lot of work to do, mostly in ZPL area, many + clean-ups, etc. Some functionality (like ACLs) I haven't even tried + to touch yet.</p> + </body> + </project> + + <project cat='net'> + <title>TSO - TCP Segmentation Offload committed</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://lists.freebsd.org/pipermail/cvs-src/2006-September/068524.html"> + TSO commit to tcp_output.c</url> + + <url + href="http://lists.freebsd.org/pipermail/cvs-src/2006-September/068610.html"> + TSO em(4) hardware support</url> + + <url + href="http://lists.freebsd.org/pipermail/cvs-src/2006-September/069493.html"> + Enhanced em(4) TSO hw setup for IPv6 and future protocols</url> + </links> + + <body> + <p>TSO - TCP Segmentation Offload support has been committed to the + network stack of FreeBSD-current in September 2006. With TSO, TCP + can send data in the send socket buffer in bulk down to the network + card which then does the splitting into MTU sized packets. On bulk + high speed sending the performance is increased by 25% (normal + writes) to 108% (sendfile). Jack Vogel and Prafulla Deuskar of + Intel committed the driver changes for TSO hardware support of + em(4) based network cards.</p> + + <p>These changes are scheduled to be backported to FreeBSD 6-STABLE + shortly after FreeBSD 6.2-RELEASE is published to appear in + upcoming FreeBSD 6.3 early next year.</p> + + <p>This work was sponsored by the TCP/IP Optimization Fundraiser + 2005.</p> + </body> + + <help> + </help> + </project> + + <project cat='net'> + <title>Highly improved implementations of sendfile(2), sosend_*() and + soreceive_stream()</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://lists.freebsd.org/pipermail/freebsd-current/2006-September/065997.html"> + sendfile(2) patch with detailed performance figures</url> + + <url + href="http://lists.freebsd.org/pipermail/freebsd-current/2006-September/066199.html"> + sosend_*() patch with detailed performance figures</url> + + <url + href="http://people.freebsd.org/~andre/sendfile+sosend+soreceive-20061006.diff"> + Combined sendfile(2), sosend_*() and soreceive_stream() patch</url> + </links> + + <body> + <p>The addition of TSO (TCP Segmentation Offload) has highlighted + some shortcomings in the sendfile(2) and sosend_*() kernel + implementations.</p> + + <p>The current sendfile(2) code simply loops over the file, turns + each 4K page into an mbuf and sends it off. This has the effect + that TSO can only generate 2 packets per send instead of up to 44 + at its maximum of 64K. kern_sendfile() has been rewritten to work + in two loops, the inner which turns as many pages into mbufs as it + can -- up to the free send socket buffer space. The outer loop then + drops the whole mbuf chain into the send socket buffer, calls + tcp_output() on it and then waits until 50% of the socket buffer + are free again to repeat the cycle. This way tcp_output() gets the + full amount of data to work with and can issue up to 64K sends for + TSO to chop up in the network adapter without using any CPU cycles. + Thus it gets very efficient especially with the readahead the VM + and I/O system do.</p> + + <p>Looking at the benchmarks we see some very nice improvements: + 181% faster with new sendfile vs. old sendfile (non-TSO), 570% + faster with new sendfile vs. old sendfile (TSO).</p> + + <p>The current sosend_*() code uses a sosend_copyin() function that + loops over the supplied struct uio and does interleaved mbuf + allocations and uiomove() calls. m_getm() has been rewritten to be + simpler and to allocate PAGE_SIZE sized jumbo mbuf clusters (4k on + most architectures). m_uiotombuf() has been rewritten to use the + new m_getm() to obtain all mbuf space in one go. It then loops over + it and copies the data into the mbufs by using uiomove(). + sosend_dgram() and sosend_generic() have been changed to use + m_uiotombuf() instead of sosend_copyin().</p> + + <p>Looking at the benchmarks we see some very nice improvements: + 290% faster with new sosend vs. old sosend (non-TSO), 280% faster + with new sosend vs. old sosend (TSO).</p> + + <p>Newly written is a specific soreceive_stream() function for + stream protocols (primarily TCP) that does only one socket buffer + lock per socket read instead of one per data mbuf copied to + userland. When doing netperf tests with WITNESS (full lock tracking + and validation enabled) the receive performance increases from + ~360Mbit/s to ~520Mbit/s. Without WITNESS I could not measure any + statistically significant improvement on a otherwise unloaded + machine. The reason is two-fold: 1) per packet we do a wakeup and + readv() is pretty much as many times as packets come it, thus the + general overhead dominates; 2) the packet input path has a pretty + high overhead too. On heavily loaded machines which do a lot of + high speed receives a performance increase should be + measureable.</p> + + <p>The patches are scheduled to be committed to FreeBSD-current at + end of October or early November 2006.</p> + + <p>This work was sponsored by the TCP/IP Optimization Fundraiser + 2005.</p> + </body> + </project> + + <project cat='soc'> + <title>Porting Xen to FreeBSD</title> + + <contact> + <person> + <name> + <given>Jue</given> + + <common>Yuan</common> + </name> + + <email>yuanjue@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.yuanjue.net/xen/howto.html">Step-by-step + tutorial for installing and using FreeBSD as domU</url> + + <url href="http://wiki.freebsd.org/YuanJue">Wiki page for this + project</url> + </links> + + <body> + <p>As a participant of Google's Summer of Code 2006, I am focusing + on porting + <a href="http://www.cl.cam.ac.uk/Research/SRG/netos/xen/" + target="_blank">Xen</a> + + to FreeBSD these months. The result of this summer's work include a + domU kernel that could be used for installation, a + <a href="http://www.yuanjue.net/xen/howto.html" target="_blank"> + guide</a> + + for getting started with FreeBSD on Xen, and some other trivial + improvements. But there are still a lot of work needing to be done + in this area, e.g, the long-expeted dom0 support. So I will + continue my work here and try to keep up with the update of Xen + itself.</p> + </body> + + <help> + <task>dom0 support is the most urgent</task> + </help> + </project> + + <project cat='soc'> + <title>Gvirstor</title> + + <contact> + <person> + <name> + <given>Ivan</given> + + <common>Voras</common> + </name> + + <email>ivoras@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/gvirstor">gvirstor home + page</url> + </links> + + <body> + <p>Gvirstor is a GEOM class providing virtual ("overcommit") + storage devices larger than physical available storage, with + possibility to add physical storage on-line when the need arises. + Current status is that it's done and waiting commit to HEAD, + scheduled for some time after 6.2 is released.</p> + </body> + + <help> + <task>The project is in need of testing! If you have the equipment + and time, please give it a try so possible bugs can be fixed before + it goes into -CURRENT.</task> + </help> + </project> + + <project cat='team'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/ports/">The FreeBSD Ports + Collection</url> + + <url + href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"> + Contributing to the FreeBSD Ports Collection</url> + + <url href="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD + ports unfetchable distfile survey (Bill Fenner's report)</url> + + <url href="http://portsmon.FreeBSD.org/index.html">FreeBSD ports + monitoring system</url> + + <url href="http://www.freebsd.org/portmgr/index.html">The FreeBSD + Ports Management Team</url> + + <url href="http://tinderbox.marcuscom.com/">marcuscom + tinderbox</url> + </links> + + <body> + <p>The ports PRs surged (especially due to a large number of new + port submissions), but with some hard work we have been able to get + back down to around 900. We are rapidly approaching 16,000 + ports.</p> + + <p>Due to this acceleration in adding new ports, portmgr is now + very concerned that we are outstripping the capacity of both the + build infrastructure and our volunteers to keep up with build + errors and port updates. Accordingly, we've added a guideline (not + a rule) that ports should be of more than just theoretical use to + be added to the Ports Collection (e.g. we can't support all of CPAN + + all of Sourceforge + everything else). Basically, use common + sense as a guideline; certainly no one wants to see any kind of + "gateway" procedure to get incoming ports approved.</p> + + <p>Seven sets of changes have been added to the infrastructure, + mostly refactoring and bugfixing.</p> + + <p>As part of a Summer of Code project, we have also incorporated + some of gabor@'s changes to incorporate better DESTDIR support. + However, due to some unanticipated side-effects, more work is going + to be needed in this area. gabor@ is continuing to work on the + changes.</p> + + <p>netchild@ and bsam@ have been doing a great deal of work to + bring the linux emulator ports closer to sanity, including bringing + up a regression-test suite.</p> + + <p>The long-anticipated import of X.Org 7 has stalled due to + developer time, mostly to deal with documentation and upgrade + instructions. Hopefully this can get done in the early 6.3 + development cycle. See the wiki for more information.</p> + + <p>As a part of that work, the decision has been made to move away + from using X11BASE and just put everything into LOCALBASE; + /usr/X11R6 is simply an artifact at this point. A plan for a + transition process is underway; a great deal of testing will need + to be done, but in the end the ports tree will be much cleaner. The + GNOME team has already done the work to move all of their ports + over, and it will be incorporated after the 6.2 release is + shipped.</p> + + <p>tmclaugh@ is looking for someone to take over the C# ports. He + has maintained them for over a year and wants more time to be able + to work on other projects.</p> + + <p>Some work has been done to get rid of FreeBSD 2.X cruft in + ports. Further work is needed to get the 3.X cruft removed.</p> + + <p>linimon@ did another pass through resetting inactive + maintainers. Another list is waiting in the wings.</p> + + <p>linimon@ is also working on adding the ability for portsmon to + analyze successful packages (not just failed ones), so that queries + such as "show me packages that build on i386 but not amd64" and + "show me why dependent package foo was not built on bar". This is + currently in alpha testing.</p> + + <p>We have added 4 new committers since the last report.</p> + </body> + + <help> + <task>We still need help getting back to our modern low of 500 + PRs.</task> + + <task>We have nearly 4400 unmaintained ports (see, for instance, + <url + href="http://portsmon.freebsd.org/portsconcordanceformaintainer.py?maintainer=ports@FreeBSD.org"> + the list on portsmon</url> + + ). Although there has been a welcome upsurge in new maintainers + recently which has dropped the percentage down below 28%, we still + need much more help.</task> + + <task>A test run of gcc4.1 on the ports tree showed around 1000 new + build errors. Kris@ has posted some results so that people can + start working on the problems now. In particular, it seems that + certain older versions of GCC cannot be built with GCC 4.1, so + ports that depend on those older versions are going to have to be + fixed as well. Although the import of GCC 4.1 to -CURRENT is not + imminent, the time to start planning is now.</task> + + <task>The state of the packages on AMD64 and sparc64 significantly + lags that of i386. In many of these cases, packages are not + attempted because NOT_FOR_ARCH is used instead of more accurately + only setting BROKEN based on ARCH. (pointyhat can be forced to + build packages that are marked BROKEN, but not NOT_FOR_ARCH). + NOT_FOR_ARCH is supposed to denote only "will never work on this + ARCH". Although we have volunteers who have expressed interest in + sparc64 (and ia64), we need more people who are running amd64 + (especially as a desktop) to help us get more packages + working.</task> + </help> + </project> + + <project cat='proj'> + <title>CScout on the FreeBSD Source Code Base</title> + + <contact> + <person> + <name> + <given>Diomidis</given> + + <common>Spinellis</common> + </name> + + <email>dds@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/CScout">The CScout project + page on the FreeBSD wiki.</url> + </links> + + <body> + <p>CScout is a refactoring editor and source code browser for + collections of C code. The aim of the project is to make it easy + for FreeBSD developers to use CScout and to improve the FreeBSD + source code quality through CScout-based queries and + refactorings.</p> + + <p>CScout was first applied to the FreeBSD kernel in 2003. Its + application at that point involved substantial tinkering with the + build system. The version released in October 2006 makes the + running of CScout on the three Tier-1 architectures a fairly + straightforward procedure. The current version can also draw a + number of call graphs; this might help developers better understand + foreign code.</p> + </body> + + <help> + <task>Use CScout to locate problematic code areas (for example + unused or too liberaly visible objects).</task> + + <task>Use CScout to globaly rename identifiers in a more consistent + fashion.</task> + + <task>Apply CScout to the userland code.</task> + + <task>Identify CScout extensions that would help us improve the + quality of our code.</task> + + <task>Arrange for the continuous availability of a live CScout + kernel session on the current version of the source code.</task> + </help> + </project> + + <project cat='bin'> + <title>Libelf</title> + + <contact> + <person> + <name> + <given>Joseph</given> + + <common>Koshy</common> + </name> + + <email>jkoshy@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/LibElf">Wiki page tracking + LibELF</url> + + <url href="http://wiki.freebsd.org/PmcTools">Wiki page for + PmcTools</url> + + <url + href="http://people.freebsd.org/~jkoshy/projects/perf-measurement/"> + PMC Tools Project</url> + </links> + + <body> + <p>Libelf is a BSD-licensed library for ELF parsing & + manipulation implementing the SysV/SVR4 (g)ELF[3] API.</p> + + <p>Current status: Implementation of the library is nearly + complete. A TET-based test suite for the API is being worked + on.</p> + </body> + + <help> + <task>Reviewers are needed for the code and the test suite. If you + have extensions to the stock SysV/SVR4 ELF(3) API that you would + like to see in -lelf, please send Joseph an email.</task> + </help> + </project> + + <project cat='proj'> + <title>DTrace</title> + + <contact> + <person> + <name> + <given>John</given> + + <common>Birrell</common> + </name> + + <email>jb@freebsd.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Progress this month has been limited due to my sea-change, + moving house to the country.</p> + + <p>Sun's OpenSolaris developers have followed through and released + the DTrace test suite as part of the OpenSolaris distribution.</p> + + <p>jkoshy@'s work on libbsdelf is nearing feature completion for + DTrace and will make life easier in FreeBSD for DTrace, given that + we have more architectures to support than Sun has.</p> + + <p>The FreeBSD project has made available a dual processor AMD64 + machine for DTrace porting.</p> + + <p>I am currently working through the diffs between the DTrace + project in P4 and -current, committing files to -current if they + are ready.</p> + </body> + </project> + + <project cat='proj'> + <title>TrustedBSD Audit</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Christian</given> + + <common>Peron</common> + </name> + + <email>csjp@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Wayne</given> + + <common>Salamon</common> + </name> + + <email>wsalamon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/audit.html">TrustedBSD Audit + Page</url> + + <url href="http://www.OpenBSM.org/">OpenBSM Page</url> + </links> + + <body> + <p> + <p>The TrustedBSD audit implementation provides fine-grained + security event logging throughout the FreeBSD operating system. + The big news for the last quarter is that the TrustedBSD audit + implementation has been merged into RELENG_6 branch, and appeared + in 6.2-BETA2. Over the past few months, work has also occurred in + the following areas:</p> + + <ul> + <li>OpenBSM 1.0 alpha 8 through alpha 12 have been released and + merged into FreeBSD CVS. Changes include significant numbers of + bug fixes, documentation improvements, and feature + enhancements. These include regular expression based matching + for auditreduce, auditd management of kernel audit policy (such + as maximum trail file size), improvements in printing support + for a variety of tokens including execve argument support.</li> + + <li>Significant enhancements to the FreeBSD Handbook chapter on + Audit.</li> + + <li>Full audit support for execve events, including optional + auditing of command line arguments and environmental variables, + as well as audit support for a broad range of other additional + kernel events.</li> + + <li>Kqueue support for audit pipes.</li> + + <li>Robustness improvements in the presence of low disk space + conditions.</li> + + <li>Support for system call capture on additional platforms, + such as ppc and ia64.</li> + + <li>Improved support for very large audit record sizes (as + required for extensive execve support).</li> + + <li>id(1) now supports a -A argument to query audit state for + the process.</li> + + <li>An audit_warn(5) event for trail rotation, which can be + used for archiving, reduction, and other administrative + activities.</li> + </ul> + + <p>Lots of testing as part of the 6.2-BETA cycle would be much + appreciated. Audit support will be considered an experimental + feature in FreeBSD 6.2-RELEASE, but we hope that it will be a + production feature in 6.3-RELEASE.</p> + </p> + </body> + + <help> + <task>Continue expanding auditing of syscall arguments.</task> + + <task>Continue expanding auditing of administrative tools.</task> + + <task>More testing!</task> + + <task>Continue to explore improvements of the administrative model + for audit trails, etc.</task> + </help> + </project> + + <project cat='kern'> + <title>MMC/SD Support</title> + + <contact> + <person> + <name> + <given>Warner</given> + + <common>Losh</common> + </name> + + <email>imp@freebsd.org</email> + </person> + + <person> + <name> + <given>Bernd</given> + + <common>Walter</common> + </name> + + <email>tisco@freebsd.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The MMC/SD stack got a significant boost this quarter. Warner + Losh and Bernd Walter have written a generic MMC/SD flash card + stack for FreeBSD, and have implemented a host controller for the + AT91RM9200 embedded ARM controller they are each using in separate + projects.</p> + + <p>The stack is presently experimental in quality. It is being used + as the root file system for these embedded projects. There's been + no work done to support hot insertion and removal of cards (neither + board wires up the pins necessary, and besides, / disappearing is + very bad). There are still many rough edges.</p> + + <p>This is a freshly written stack. It has been written using the + SD 1.0 (and recently 2.0) simplified specification, with the + SanDisk MMC application notes supplementing. The Linux stack looks + good, although not entirely standards conforming (there's work in + progress that I've not seen that is supposed to fix this) and it + is contaminated with the GPL. The OpenBSD stack also looks + interesting, but Warner's experience porting NEWCARD over from + NetBSD suggested that a fresh rewrite may be faster, at least for + the bus and driver level. Since MMC is fairly simple, a port of the + sdhci driver might be possible.</p> + + <p>Please see the open tasks list.</p> + </body> + + <help> + <task>Write sdhci driver, and integrate it into the current + stack.</task> + + <task>Add support for hot plugging of cards.</task> + + <task>Add support for MMC cards (SD cards were the first + target).</task> + + <task>Expand SD support to include SDIO cards as well as the new + SDHC standard cards.</task> + + <task>Export stats via sysctl for each of the cards that are found + as a debugging and usage monitoring aid.</task> + + <task>Add support for reading/writing multiple blocks at a time to + improve performance.</task> + + <task>Implement any other host controller.</task> + + <task>Add proper support for timeouts.</task> + </help> + </project> + + <project cat='arch'> + <title>Sun Niagara port</title> + + <contact> + <person> + <name> + <given>Kip</given> + + <common>Macy</common> + </name> + + <email>kmacy@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Support for the UltraSparc T1 (Niagara) continues to improve. + The code has recently been checked into public CVS under + sys/sun4v.</p> + + <p>It isn't clear whether or not I will have time to implement full + logical domaining support before the APIs become publicly + available. Testing indicates that substantial work will be needed + before FreeBSD can take full advantage of all 32 threads.</p> + </body> + + <help> + <task>Random testing and bug fixes.</task> + + <task>Import and extend improved mutex profiling support.</task> + + <task>Virtual network and virtual disk device drivers for logical + domains.</task> + </help> + </project> + + <project cat='arch'> + <title>Xen Port</title> + + <contact> + <person> + <name> + <given>Kip</given> + + <common>Macy</common> + </name> + + <email>kmacy@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work on Xen support has slowly been continuing in perforce. The + SOC student fixed several bugs and is continuing to work on it. + Someone is needed who has the time to complete dom0 support and + shepherd it production level stability.</p> + + <p>Sufficient interest has been expressed in it that it probably + makes sense to check it in to public CVS so that more people can + try it out. Time permitting, I will bring it up to date and check + it in the next month.</p> + </body> + + <help> + <task>dom0 support.</task> + + <task>General testing and bug fixing.</task> + </help> + </project> + + <project cat='proj'> + <title>FreeSBIE</title> + + <contact> + <person> + <name> + <given>FreeSBIE</given> + + <common>Staff</common> + </name> + + <email>staff@FreeSBIE.org</email> + </person> + + <person> + <name> + <given>Matteo</given> + + <common>Riondato</common> + </name> + + <email>matteo@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeSBIE.org">FreeSBIE Website</url> + + <url href="http://liste.gufi.org/mailman/listinfo/freesbie"> + FreeSBIE ML Subscription Form</url> + + <url href="http://people.freebsd.org/~matteo/GMV/GMVAnnounce.txt"> + FreeSBIE GMV Announcement</url> + </links> + + <body> + <p>FreeSBIE is a FreeBSD based LiveCD.</p> + + <p>On August 19th, Matteo Riondato, a member of the FreeSBIE staff, + released an unofficial ISO, codename FreeSBIE GMV, based on FreeBSD + -CURRENT (read the Announcement to download it). This is supposed + to be the first in a series of four ISOs that will end up with the + release of FreeSBIE 2.0. Matteo is now working on another ISO, + codename FreeSBIE LVC, which is scheduled to be released October 12th.</p> + + <p>FreeSBIE 2.0 will be based on FreeBSD 6.2-RELEASE and will + hopefully be released at EuroBSDCon 2006 in Milan. It will be + available for the i386 and AMD64 platforms.</p> + </body> + + <help> + <task>Test the released ISO in preparation for the release.</task> + + <task>Suggest software to include in the ISO.</task> + + <task>Submit a simple and clear but complete fluxbox + configuration.</task> + </help> + </project> + + <project cat='soc'> + <title>Update of the Linux compatibility environment in the + kernel</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Roman</given> + + <common>Divacky</common> + </name> + + <email>rdivacky@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Emulation</given> + + <common>Mailinglist</common> + </name> + + <email>emulation@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/linux-kernel">Wiki page about + the linux compatibility environment.</url> + </links> + + <body> + <p>Roman Divacky participated in the Google Summer of Code 2006 and + implemented a major part of the syscall compatibility to the 2.6.16 + Linux kernel. The work has been committed to -CURRENT (the default + compatibility still being a 2.4.2 Linux kernel) and we are working + on fixing the remaining bugs as time permits.</p> + + <p>"Intron" submitted an implementation for the linux aio syscalls. + His work has been committed to the Perforce repository.</p> + + <p>We also started to consolidate a list of known bugs, open issues + and helpful stuff (e.g. regression tests and their status) in + -CURRENT on a page in the FreeBSD wiki (see the links-section). It + also contains a link to a more or less up-to-date patch with stuff + we have in the Perforce repository so that interested people can + help with testing. Thanks to the help of Marcin Cieslak we already + fixed some bugs (some of the fixes are already MFCed to + -STABLE).</p> + + <p>Thanks to the nice regression tests of the Linux Test Project + (LTP) we have a list of small (and not so small) things which need + to be looked at. This list makes up for a quick start into kernel + hacking. So if you have a little bit of knowledge about C + programming, and if you want to help us a little bit in improving + FreeBSD, feel free to have a look at the list and to try to fix a + problem or two. Sometimes it is as easy as "if (error condition) + return Esomething;" (but you should coordinate with the emulation + mailinglist, so that nobody does some work someone else just did + too). Even if you do not know how to program, you can help. Have a + look at the wiki page and tell us about things which should get + mentioned there too. Or download the patch and test it.</p> + </body> + </project> + + <project cat='kern'> + <title>Sound Subsystem Improvements</title> + + <contact> + <person> + <name> + <given>Ariff</given> + + <common>Abdullah</common> + </name> + + <email>ariff@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ryan</given> + + <common>Beasley</common> + </name> + + <email>ryanb@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Multimedia</given> + + <common>Mailinglist</common> + </name> + + <email>multimedia@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~ariff/">Some patches.</url> + + <url href="http://www.FreeBSD.org/projects/ideas/">The FreeBSD + Project Ideas List.</url> + + <url href="http://wiki.FreeBSD.org/soundsystem">Wiki page about the + sound system.</url> + </links> + + <body> + <p>Since the last status report we added basic support for envy24ht + chips, imported the emu10kx driver into the base system and added + support for High Definition Audio (HDA) compatible chips.</p> + + <p>Additionally the work of Ryan Beasley as part of his Google + Summer of Code 2006 participation is committed. It adds + compatibility to the Open Sound System (OSS) v4 API as far as this + was possible. This allows for more sophisticated programs to be + written. For example it is now possible to synchronize the start of + multiple sound channels. It is also possible for a driver to + support more than the AC97 mixer devices, but so far no driver has + been extended to support this yet. More about it can be found in + the wiki and in the official OSS documentation.</p> + + <p>The wiki page about the sound system was started to describe + the current status of the sound system and to provide some + information about where we are heading. But more work needs to be + done to reach this goal. So far we collected some information about + the status of the most recent work in the soundsystem. So if you + have a look at it and you think that something important is + missing, just tell us about it. While fully prepared content is + very welcome, we are even happy about some ideas what we should + list on the wiki page.</p> + </body> + + <help> + <task>Have a look at the sound related entries on the ideas + list.</task> + + <task>sndctl(1): tool to control non-mixer parts of the sound + system (e.g. spdif switching, virtual-3D effects) by an user + (instead of the sysctl approach in -current); pcmplay(1), + pcmrec(1), pcmutil(1).</task> + + <task>Plugable FEEDER infrastructure. For ease of debugging various + feeder stuff and/or as userland library and test suite.</task> + + <task>Extend the wiki page.</task> + </help> + </project> + + <project cat='net'> + <title>Bridge Spanning Tree Protocol Improvements</title> + + <contact> + <person> + <name> + <given>Andrew</given> + + <common>Thompson</common> + </name> + + <email>thompsa@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work is almost finished to implement the Rapid Spanning Tree + Protocol (RSTP) which supersedes Spanning Tree Protocol (STP). + RSTP has a much faster link failover time of around one second + compared to 30-60 seconds for STP, this is very important on + modern networks. The code will be posted shortly for testing and + feedback.</p> + </body> + </project> + + <project cat='ports'> + <title>OCaml language support in ports</title> + + <contact> + <person> + <name> + <given>Stanislav</given> + + <common>Sedov</common> + </name> + + <email>stas@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/lang/ocaml/bsd.ocaml.mk?rev=1.3&content-type=text/plain"> + Framework include file</url> + </links> + + <body> + <p>There were a number of OCaml ports in our tree, and each of them + was doing the same work by maintaining OCaml ld.conf in the correct + state, installing/removing their files/entries etc. To simplify the + task of OCaml-language ports creation, the special framework + (bsd.ocamk.mk) was developed and most of the ports were converted to + use this framework. This allowed a lot of duplicate code to be + removed. This new framework handles all the things required to + install an OCaml-language library and properly register it. + bsd.ocaml.mk also contains knobs to deal with findlib-powered + libraries, modify ld.conf in the proper way, etc. Also, a lot of + new Ocaml-related ports were added.</p> + </body> + </project> + + <project cat='ports'> + <title>Enlightenment DR17 support in the ports tree</title> + + <contact> + <person> + <name> + <given>Stanislav</given> + + <common>Sedov</common> + </name> + + <email>stas@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Integration of the new innovative e17 window manager into the + ports tree is almost completed. A lot of new e17-related + applications was ported, all old ports were updated to the latest + stable cvs snapshot. The special framework (bsd.efl.mk) was created + to support the whole thing and simplify the creation of dependent + ports. I'll commit the changes in the days before the ports + freeze.</p> + + <p>Thanks to Sergey Matveychuk (sem@) for providing a machine to + place CVS snapshots on. Without his help it will be impossible.</p> + </body> + + <help> + <task>Port Entrance (xdm-like app, but very appealing).</task> + + <task>Port Net and Wlan e17 module.</task> + + <task>Develop FreeBSD-specific e17 apps/modules to use The + Ports Collection, system configs, etc.</task> + </help> + </project> + + <project cat='arch'> + <title>CPU Microcode Update Software</title> + + <contact> + <person> + <name> + <given>Stanislav</given> + + <common>Sedov</common> + </name> + + <email>stas@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Last month I was working on a driver/module to update the + microcode of Intel or AMD CPUs that support having their + microcode updated. As you might know these processors are + microcode-driven and this firmware can be updated. Intel(R) + often releases microcode updates, and AMD(R) updates can be + found in BIOS programs. The work is almost finished now, I just + need to find a bit of time to test it on AMD64 systems and + perform some code cleanup. The driver also provide a way for + userland programs to access the Machine Specific Registers (MSR) + and CPUID info for a certain cpu. This will allow some programs + like x86info to provide more accurate information about cpus in + SMP systems and make assumptions based on the contents of the + MSR.</p> + + <p>Thanks to John Baldwin, Kostik Belousov, John-Mark Gurney and + Divacky Roman for helping during development.</p> + </body> + + <help> + <task>Perform testing on the AMD64-based systems.</task> + + <task>Write manpage.</task> + + <task>Code cleanup/checks.</task> + </help> + </project> + + <project cat='ports'> + <title>Improving FreeBSD Ports Collection Infrastructure</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <contact> + <person> + <name> + <given>Erwin</given> + + <common>Lansing</common> + </name> + + <email>erwin@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://wiki.freebsd.org/G%C3%A1borK%C3%B6vesd%C3%A1n"> + Gábors wiki page.</url> + </links> + + <body> + <p>During the Google Summer of Code 2006, Gábor worked on several + ideas to improve the ports infrastructure:</p> + + <ol> + <li>New handling for i386 binary ports.</li> + + <li>Cleanup: use ECHO_CMD and ECHO_MSG in bsd.port.mk + properly.</li> + + <li>Add basic infrastructure support for debugging.</li> + + <li>Installing ports with different destination (DESTDIR + macro).</li> + + <li>Cleanup: Move fetch shell scripts out of bsd.port.mk.</li> + + <li>Make ports respect CC and CFLAGS.</li> + + <li>Cross-compiling Ports.</li> + + <li>Plist generator tool.</li> + </ol> + + <p>The first three items have been completed and the next two + items are being worked on. The DESTDIR support was more + complicated than presumed and took more time than expected to + complete. Gábor will continue working to finish these tasks and + other ports related tasks. FreeBSD is happy to have interested + him to keep working on ports and ports infrastructure.</p> + </body> + </project> + + <project cat='kern'> + <title>Gvinum improvements</title> + + <contact> + <person> + <name> + <given>Ulf</given> + + <common>Lilleengen</common> + </name> + + <email>lulf@pvv.ntnu.no</email> + </person> + </contact> + + <links> + <url + href="http://folk.ntnu.no/lulf/patches/freebsd/gvinum/gvinum_all_current.diff" /> + </links> + + <body> + <p>I thought that since I sent a status report the last time, I + might as well send one now.</p> + + <p>Since the last status report I have done work on several of the + remaining commands as attach, detach, and finally the concat + command to be able to create concatenated volumes with one easy + command. The mirror and stripe commands are the next step after + this.</p> + + <p>The most important thing I've been working on is maybe the + implementation of drivegroups. I have posted a bit information on + this mailinglists, but basically, it's a way to group drives with + the same configuration. This way, you can make many commands + operate on groups instead of drives, and the group-abstraction will + handle how the underlying subdisks are created on the drives. + In the future one will be able to move groups to different + machines, etc.</p> + + <p>I've created a patch of all my work that is not in HEAD yet here + (this is a snapshot of my development branch, so how thing's are + done might be changed quite fast): + <a + href="http://folk.ntnu.no/lulf/patches/freebsd/gvinum/gvinum_all_current.diff"> + http://folk.ntnu.no/lulf/patches/freebsd/gvinum/gvinum_all_current.diff</a> + </p> + + <p>Be aware that a there will probably be bugs in the code, + so don't use it in production yet!</p> + + <p>Thanks to Greg Lehey for offering to help me on getting this + into CVS, and all feedback on this has been good.</p> + </body> + + <help> + <task>Remaining components, mirror, stripe and some info + commands.</task> + </help> + </project> + + <project cat='misc'> + <title>FreeBSD Multimedia Resources List</title> + + <contact> + <person> + <name> + <given>Edwin</given> + + <common>Groothuis</common> + </name> + + <email>edwin@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.mavetju.org/unix/multimedia.php" /> + + <url href="http://www.mavetju.org/unix/multimedia-rss.php">RSS + version</url> + </links> + + <body> + <p>I have setup the FreeBSD Multimedia Resources List, a + one-stop-shop for FreeBSD related podcasts, vodcasts and + audio/video resources. Hopefully this list will make it easier for + people to find and keep up to date with these recordings. The + overview is available as a normal HTML page and as an XML/RSS + feed.</p> + + <p>The ultimate goal is to have this list to reside under the + www.FreeBSD.org umbrella.</p> + </body> + </project> + + <project cat='soc'> + <title>SNMP monitoring (BSNMP)</title> + + <contact> + <person> + <name> + <given>Shteryana</given> + + <common>Shopova</common> + </name> + + <email>shteryana@FreeBSD.org</email> + </person> + </contact> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + + <common>Zeeb</common> + </name> + + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/soc%2dshteryana/bsnmp&HIDEDEL=NOe"> + P4 workspace</url> + + <url href="http://wiki.freebsd.org/CategorySNMP">SNMP-related + pages on FreeBSD Wiki</url> + + <url href="http://wiki.freebsd.org/SnmpBridgeModule">A wiki page on + if_bridge(4) monitoring module</url> + + <url href="http://www.freshports.org/net-mgmt/bsnmptools/"> + bsnmptools port</url> + </links> + + <body> + <p>A BRIDGE monitoring module for FreeBSD's BSNMP daemon has been + implemented. In addition to RFC 4188 single bridge support and + extending the kernel to get access to all the information, a + private MIB was designed in order to be able to monitor multiple + bridges supported by FreeBSD. The kernel part has already been + committed to -CURRENT (thanks to thompsa@), for -STABLE a patch is + available (see the wiki), code has already been reviewed.</p> + + <p>SoC 2005 work on SNMP client tools is now available too via port + (net-mgmt/bsnmptools), thanks to Andrew Pantyukhin for the port.</p> + </body> + + <help> + <task>More testing is very welcome.</task> + + <task>if_vlan(4) monitoring module.</task> + + <task>jail(8) monitoring module.</task> + </help> + </project> + + <project cat='misc'> + <title>BSDCan 2007</title> + + <contact> + <person> + <name> + <given>Dan</given> + + <common>Langille</common> + </name> + + <email>dan@langille.org</email> + </person> + </contact> + + <links> + <url href="http://www.bsdcan.org/" /> + </links> + + <body> + <p>The dates for + <a href="http://www.bsdcan.org/2007/">BSDCan 2007</a> + have been set: 11-12 May 2007. As is usual, BSDCan will be held at + University of Ottawa, with two days of tutorials prior to the + conference starting.</p> + + <p>The + <a href="http://www.bsdcan.org/2007/papers.php">call for papers</a> + + will go out in mid December. Start thinking about your submissions + now!</p> + </body> + </project> + + <project cat='ports'> + <title>FreshPorts</title> + + <contact> + <person> + <name> + <given>Dan</given> + + <common>Langille</common> + </name> + + <email>dan@langille.org</email> + </person> + </contact> + + <links> + <url href="http://www.freshports.org/">FreshPorts - The Place For + Ports</url> + </links> + + <body> + <p>The new 2U server mentioned in the last report now has a + collection of Raptor drives in a RAID-10 configuration. Thanks to + very generous donations from the community, I purchased eight of + these drives at very good prices. The server will be deployed in + the next few weeks.</p> + + <p>There has been quite a bit of work since the last report in + June. Some highlights include:</p> + + <ul> + <li>New news feed + <a href="http://www.freshports.org/backend/">formats</a>, + + including newsfeeds for your watch list.</li> + + <li>Better pages caching for faster response.</li> + + <li>Sanity Test Failures now available + <a + href="http://news.freshports.org/2006/10/11/sanity-test-failures/"> + online.</a> + </li> + + <li>Ability to + <a + href="http://news.freshports.org/2006/10/15/all-commits-under-a-point- in-the-tree/"> + search for all commits</a> + + (ports, doc, src, etc) under a given point in the tree.</li> + </ul> + + <p>For more detail, please review the + <a href="http://news.freshports.org/">FreshPorts Blog</a> + + .</p> + </body> + </project> + + <project cat="team"> + <title>The FreeBSD Foundation</title> + + <contact> + <person> + <name> + <given>Deb</given> + + <common>Goodkin</common> + </name> + + <email>deb@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsdfoundation.org" /> + </links> + + <body> + <p>The FreeBSD Foundation continued to support the FreeBSD project + and community through various activities. These activities include + creating strategies for fund development and actively seeking + funding for the FreeBSD community, coordinating a new IBM + Bladeserver project, and protecting the image and integrity of + FreeBSD by governing the use of the trademarks. We are pleased to + be a sponsor of EuroBSDCon and will be sponsoring a few developers + to attend the conference through our travel grant program. And + finally, we have secured funds for a major project that will be + announced later this month.</p> + </body> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2006-10-2006-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2006-10-2006-12.xml new file mode 100644 index 0000000000..68547a2c00 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2006-10-2006-12.xml @@ -0,0 +1,2546 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status +Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2006-10-2006-12.xml,v 1.4 2007/04/11 06:57:13 brd Exp $ --> +<report> + <date> + <month>October-December</month> + + <year>2006</year> + </date> + + <section> + <title>Introduction</title> + + <p>Happy New Year. This Report covers the last quarter of a exciting + year 2006 for FreeBSD development. FreeBSD 6.2 is finally out of the + door and work towards FreeBSD 7.0 is gearing up. Some of the projects + in this report will be part of that effort, others are already in the + tree. Many projects need your help with testing and otherwise. Please + see the "Open tasks" sections for more information.</p> + + <p>The BSD crowd will meet at + <a href="http://www.asiabsdcon.org/">AsiaBSDCon</a> + March 8-10th in Tokyo and a two day FreeBSD developer summit will be + held at + <a href="http://www.bsdcan.org/">BSDCan</a> + + May 16-19th in Ottawa. Finally, + <a href="http://2007.eurobsdcon.org/">EuroBSDCon</a> + + September 14-15th in Copenhagen is already looking for papers.</p> + + <p>Thanks to all the reporters for the excellent work! We hope you + enjoy reading.</p> + </section> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>team</name> + + <description>FreeBSD Team Reports</description> + </category> + + <category> + <name>net</name> + + <description>Network Infrastructure</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>drv</name> + + <description>Hardware Drivers</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <category> + <name>bin</name> + + <description>Userland Programs</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='kern'> + <title>GEOM Multipath</title> + + <contact> + <person> + <name> + <given>Matthew</given> + + <common>Jacob</common> + </name> + + <email>mjacob@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>A toy implementation of GEOM based active/passive multipath is + now done and in a perforce repository. Seems to work.</p> + </body> + </project> + + <project cat='ports'> + <title>FreshPorts</title> + + <contact> + <person> + <name> + <given>Dan</given> + + <common>Langille</common> + </name> + + <email>dan@langille.org</email> + </person> + </contact> + + <links> + <url href="http://www.freshports.org/">FreshPorts</url> + + <url href="http://news.freshports.org/">FreshPorts News</url> + </links> + + <body> + <p>There have been a number of improvements to FreshPorts over the + last quarter of 2006. The following are just a few of them. The + links take you to the relevant article within the + <a href="http://news.freshports.org">FreshPorts News website</a> + + . + <ul> + <li>Better + <a href="http://news.freshports.org/index.php?s=pagination"> + pagination</a> + + of larger result sets</li> + + <li>Listing of + <a + href="http://news.freshports.org/2006/10/11/sanity-test-failures/"> + sanity test failures</a> + </li> + + <li>Inclusion of + <a + href="http://news.freshports.org/2006/10/01/the-latest-and-greatest-vulnerabilities/"> + latest vulnerabilities</a> + + on the front page</li> + + <li>Started working on adding tools to make + FreshSource/FreshPorts more useful as a + <a + href="http://news.freshports.org/2006/11/29/freshsourcefreshports-as-a-developer-platform/"> + developer tool</a> + </li> + + <li>The new + <a href="http://www.freebsddiary.org/topics.php?aid=589#opteron"> + dual opteron server</a> + + has been + <a + href="http://news.freshports.org/2006/11/09/opti-has-left-the-building/"> + deployed!</a> + </li> + </ul> + </p> + + <p>My thanks to the many people who have contributed suggestions, + ideas, and code over the years. Most of you are documented at the + above URLs.</p> + </body> + + <help> + <task>FreshPorts/FreshSource as a developer tool</task> + </help> + </project> + + <project cat='misc'> + <title>BSDCan 2007</title> + + <contact> + <person> + <name> + <given>Dan</given> + + <common>Langille</common> + </name> + + <email>dan@langille.org</email> + </person> + </contact> + + <links> + <url href="http://www.bsdcan.org/2007/">BSDCan 2007</url> + </links> + + <body> + <p>Folks! + <br /> + + It is that time of year. You may have missed the + <a href="http://www.bsdcan.org/2007/papers.php">call for papers</a> + + , but please put in your proposal right away. This is often a busy + time of year, but please take the time to consider presenting at + BSDCan.</p> + + <p>Please read the + <a href="http://www.bsdcan.org/2007/submissions.php">submission + instructions</a> + + and send in your proposal today!</p> + + <p>You may be interested in our sister conference: PGCon. If you + have an interest in + <a href="http://www.postgresql.org">PostgreSQL</a> + + , a leading relational database, which just happens to be open + source, then we have the conference for you! + <a href="http://www.pgcon.org/2007/">PGCon 2007</a> + + will be held immediately after BSDCan 2007, at the same venue, and + will follow a similar format.</p> + </body> + + <help> + <task>Waiting for papers</task> + </help> + </project> + + <project cat='proj'> + <title>FreeSBIE</title> + + <contact> + <person> + <name> + <given>Matteo</given> + + <common>Riondato</common> + </name> + + <email>matteo@FreeBSD.org</email> + </person> + + <person> + <name> + <given>FreeSBIE</given> + + <common>Staff</common> + </name> + + <email>staff@FreeSBIE.org</email> + </person> + + <person> + <name> + <given>FreeSBIE</given> + + <common>Mailing List</common> + </name> + + <email>freesbie@gufi.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeSBIE.org" /> + + <url href="http://users.gufi.org/~rionda/20relnotes/">FreeSBIE 2.0 + Release Notes Preview</url> + + <url href="http://users.gufi.org/~rionda/20screen/">FreeSBIE 2.0 + Screenshots Preview</url> + </links> + + <body> + <p>FreeSBIE is approaching the 2.0-RELEASE. The first release + candidate proved to be good enough but a second one will probably + be released. An external developer is working on integrating + BSDInstaller in FreeSBIE 2.0 and this may cause a little delay of + the release date. Release Notes were written and need to be updated + with the current list of packages. A script which allows to switch + Tor+Privoxy on and off was added and its usage was documented. The + 2.0-RELEASE is near, hopefully near the end of January but this + will also depend on when FreeBSD 6.2-RELEASE will be released.</p> + </body> + </project> + + <project cat='drv'> + <title>MPT LSI-Logic Host Adapters: mpt</title> + + <contact> + <person> + <name> + <given>Matthew</given> + + <common>Jacob</common> + </name> + + <email>mjacob@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The 'mpt' project is support for the MPT LSI-Logic Host Adapters + (SCSI, Fibre Channel, SAS).</p> + + <p>The last quarter saw a lot of change supported by Yahoo! and + LSI-Logic and many others as things settled out for better support + for U320. Some initial Big Endian support was offered by John + Birrel and Scott Long.</p> + </body> + + <help> + <task>Finish SAS Integrated RAID support.</task> + + <task>Try and get U320 RAID working better than it currently + does.</task> + + <task>Finish Big Endian support, including that for target + mode.</task> + </help> + </project> + + <project cat='drv'> + <title>QLogic SCSI and Fibre Channel: isp</title> + + <contact> + <person> + <name> + <given>Matthew</given> + + <common>Jacob</common> + </name> + + <email>mjacob@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>This project is for support for QLogic SCSI and Fibre Channel + host adapters.</p> + + <p>The last quarter saw the addition of 4Gb Fibre Channel support + and a complete rewrite of fabric management (which is still + settling out).</p> + </body> + </project> + + <project cat='drv'> + <title>Bt878 Audio Driver (aka FusionHDTV 5 Lite driver)</title> + + <contact> + <person> + <name> + <given>John-Mark</given> + + <common>Gurney</common> + </name> + + <email>jmg@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fbktrau%2F...&ignore=GO%21"> + Perforce source repository</url> + </links> + + <body> + <p>Basic audio capture is working. All of the parameters are set by + userland, while the RISC program generation is by kernel. No real + audio has been captured as there are no drivers for the NTSC tuner + yet. Someone with a real Bt878 NTSC card that is supported by + bktr(4) could use this to capture audio without using the sound + card.</p> + + <p>Due to lack of documentation from DViCO and LG, I have copied + magic values from the Linux driver and managed to get ATSC + capturing working. There was a bug in the capture driver that was + releasing buffers to userland early causing what appeared to be + reception issues. Now that we use the RISC status bits as buffer + completion bits, capture works cleanly. This does mean that even if + you provide more than 4 buffers to the driver, the buffers will be + divided into four segments, and returned in segments.</p> + + <p>A Python module is available, along with a sample capture + application using it. The module is now known to work well with + threads so that tuning (expensive due to i2c ioctls) can happen in + another thread without causing program slow down. The module is + working well with a custom PVR backend.</p> + + <p>Additional ioctls have been added to get sibling devices. This + allows one to open a bktrau device, and get the correct bktr(4) + device that is in the same slot. This is necessary so that when + adjusting GPIO pins or sending i2c commands, they are to the + correct device.</p> + </body> + + <help> + <task>Provide support for NTSC and FM tuning.</task> + + <task>Add support for other cards and tuners that use the Bt878 + chip.</task> + </help> + </project> + + <project cat='proj'> + <title>Past and Future PR Closing Events</title> + + <contact> + <person> + <name> + <given>Florent</given> + + <common>Thoumie</common> + </name> + + <email>flz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/Bugathons" /> + </links> + + <body> + <p>Following the example of our NetBSD friends, we organized a + couple of Bugathons to help decreasing the open PR count. At first, + it was decided to make it a monthly event focused on both src, + ports and doc. Audience decreased with each Bugathon organized and + less non-ports committers attended the events. So from now on, we + will focus on ports (making it a Portathon) and organize a new + event after the end of each ports freeze (that should be twice a + year, at most).</p> + </body> + </project> + + <project cat='ports'> + <title>Updating X.org FreeBSD Ports to 7.2</title> + + <contact> + <person> + <name> + <given>Florent</given> + + <common>Thoumie</common> + </name> + + <email>flz@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Eric</given> + + <common>Anholt</common> + </name> + + <email>anholt@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Dejan</given> + + <common>Lesjak</common> + </name> + + <email>lesi@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://xorg.freedesktop.org/">X.org Official + Website</url> + + <url + href="http://git.xbsd.org/?p=freebsd/ports.git;a=shortlog;h=xorg"> + Experimental X.org Ports Tree</url> + + <url href="http://blog.xbsd.org/">Latest news about FreeBSD X.org + Porting Efforts</url> + + <url href="http://lists.freebsd.org/pipermail/freebsd-x11/"> + FreeBSD-X11 Mailing List Archives</url> + </links> + + <body> + <p>X.org 7.2 release has been delayed more than a month, which gave + us more time to fix build failures, to work on a few runtime issues + and to determine the easiest way to upgrade from 6.9 to 7.2 (mostly + with the help of people on the + <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-x11"> + freebsd-x11@ mailing list</a> + + ). Everything is in a rather good shape but there's still a little + amount of work to do. The merge of new ports is most likely to + happen before the end of January.</p> + </body> + + <help> + <task>Do a global review of the diff between the original tree and + the experimental one (git-diff origin xorg for git users)</task> + + <task>Fix the remaining (9 I think, 3 being lang/jdk's) build + errors</task> + + <task>Continue testing</task> + + <task>Do another experimental build on pointyhat</task> + </help> + </project> + + <project cat='proj'> + <title>New USB Stack</title> + + <contact> + <person> + <name> + <given>Hans Petter</given> + + <common>Sirevaag Selasky</common> + </name> + + <email>hselasky@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb"> + Current USB files</url> + + <url href="http://www.turbocat.net/~hselasky/usb4bsd">My USB + homepage</url> + </links> + + <body> + <p>During the last three months there has not been so much activity + in the USB project. Some regression issues have been reported and + fixed. Bernd Walter reports that he has got the new USB stack + working on ARM processors with some minor tweaks. Markus Brueffer + reports that he is working on the USB HID parser and support. A + current issue with the new USB stack is that the EHCI driver does + not work on the Sparc64 architecture. If someone has got a Sparc64 + with FreeBSD 7-CURRENT on and can lend the USB project the root + password, a serial console and a USB test device, for example a USB + memory stick, that would be much appreciated. Another unresolved + issue is that the ural(4) USB device driver does not always work. + This is currently being worked on.</p> + + <p>If you want to test the new USB stack, check out the USB + perforce tree or download the SVN version of the USB driver from my + USB homepage. At the moment the tarballs are a little out of + date.</p> + + <p>Ideas and comments with regard to the new USB API are welcome at + + <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-usb"> + freebsd-usb@FreeBSD.org</a> + + .</p> + </body> + </project> + + <project cat='net'> + <title>Multi-link PPP daemon (MPD)</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Motin</common> + </name> + + <email>mav@alkar.net</email> + </person> + + <person> + <name> + <given>Archie</given> + + <common>Cobbs</common> + </name> + + <email>archie@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://sourceforge.net/projects/mpd/">Project home</url> + + <url + href="http://mpd.cvs.sourceforge.net/*checkout*/mpd/mpd/doc/changes.sgml"> + ChangeLog</url> + </links> + + <body> + <p>MPD is moving to the next major release - mpd4_0. At the end of + October one more beta version (4_0b5) was released and first RC is + planned soon.</p> + + <p>Since 3_18 and 4_0b4 numerous bugs and cases of incorrect + internal handling have been fixed. Performance has been increased + and system requirements reduced.</p> + + <p>Many new features have been implemented: + <ul> + <li>IPv6 support</li> + + <li>NAT (using the ng_nat(4) node)</li> + + <li>integrated web server</li> + + <li>Deflate and Predictor-1 CCP compression</li> + </ul> + </p> + + <p>Some historically broken features have been reimplemented: + <ul> + <li>TCP and UDP link types</li> + + <li>CCP compression</li> + + <li>ECP encryption</li> + </ul> + </p> + + <p>To support compression, two new Netgraph nodes ng_deflate and + ng_pred1 have been created and the ng_ppp node has been + modified.</p> + </body> + + <help> + <task>ng_ppp node refactoring.</task> + + <task>Implement packet loss notification in related Netgraph nodes + (ng_ppp, ng_pptp, ng_async, ng_deflate, ng_pred1, ng_vjc, ...) to + reduce recovery time and probability of incorrect packet + decompression.</task> + + <task>MPD auth subsystem refactoring.</task> + </help> + </project> + + <project cat='kern'> + <title>Update of the Linux Compatibility Environment in the + Kernel</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Roman</given> + + <common>Divacky</common> + </name> + + <email>rdivacky@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Emulation</given> + + <common>Mailinglist</common> + </name> + + <email>emulation@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/linux-kernel">Wiki page about + the Linux compatibility environment.</url> + </links> + + <body> + <p>Since the last status report we made good progress in improving + the compatibility environment. We fixed more than 30 testcases on + i386 (130 testcases = 16% still failing) and more than 60 testcases + on amd64 (140 testcases = 17% still failing) in the Linux 2.4 + compatibility. These numbers compare FreeBSD 6.2 with -CURRENT. + Some of those fixes are edge cases in the error handling, and some + of them fix real issues -- e.g. hangs -- and improve the stability + and correctness of the emulation.</p> + + <p>Regarding the Linux 2.6 compatibility there are 140 testcases + (17%) on i386 and 150 testcases (18%) on amd64 still failing in + -CURRENT. After fixing some showstopper problems with real + applications, we should be able to give the 2.6 emulation a more + widespread exposure "soon" to find more bugs and to determine the + importance of those Linux syscalls which we did not implement + yet.</p> + + <p>The severity of the broken testcases varies, and some of them + will never be fixed, e.g., we will never be able to load Linux + kernel modules into a FreeBSD kernel, being able to add swap with a + Linux command has very low priority, and fixing stuff which is used + by applications like IPC type 17 has high priority.</p> + + <p>Some differences in the 2.6 compatibility are because not all + i386 changes are merged into the amd64 code, and some testcases are + already fixed in our perforce repository but need more review + before they can be committed to -CURRENT.</p> + + <p>We need some more testers and bug reporters. So if you have a + little bit of time and a favorite Linux application, please play + around with it on -CURRENT. If there is a problem, have a look at + the wiki if we already know about it and report on + <a + href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation"> + emulation@</a> + + . We are especially interested in reports about the 2.6 + compatibility (sysctl compat.linux.osversion=2.6.16), but only with + the most recent -CURRENT and maybe with some patches we have in the + perforce repository (mandatory on amd64).</p> + + <p>We thank all people who tested the changes / submitted patches + and thus helped improving the Linux compatibility environment.</p> + </body> + </project> + + <project cat='kern'> + <title>Sound Subsystem Improvements</title> + + <contact> + <person> + <name> + <given>Ariff</given> + + <common>Abdullah</common> + </name> + + <email>ariff@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Multimedia</given> + + <common>Mailinglist</common> + </name> + + <email>multimedia@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~ariff/">Some patches / binary + modules.</url> + + <url href="http://www.FreeBSD.org/projects/ideas/">The FreeBSD + Project Ideas List.</url> + + <url href="http://wiki.FreeBSD.org/soundsystem">Wiki page about the + sound system.</url> + </links> + + <body> + <p>Since the last status report there were improvements to the + emu10kx driver for High Definition Audio (HDA) compatible chips. + Some more chips are supported now and already supported chips + should provide a better zero-configuration experience.</p> + + <p>The generic sound code got some very nice low latency changes, + and fixes which make it multichannel/endian/format safe. We do not + support multichannel operation yet, but this work is a prerequisite + to work on implementing multichannel operation. This work also + fixed some bugs which people may experience as clicks, hickups, + truncation or similar behavior in the sound-output.</p> + + <p>So far there is no merge to 5.x or 6.x planned for this code, + especially because there are API/ABI changes, e.g., several sysctls + changed. People who do not care about this can download binary + sound modules from Ariff's download page for 6.x and 5.x.</p> + + <p>We thank all people who tested the changes / submitted patches + and thus helped improving the sound system.</p> + </body> + + <help> + <task>Have a look at the sound related entries on the ideas + list.</task> + + <task>Add multichannel support.</task> + + <task>sndctl(1): tool to control non-mixer parts of the sound + system (e.g. spdif switching, virtual-3D effects) by a user + (instead of the sysctl approach in -CURRENT); pcmplay(1), + pcmrec(1), pcmutil(1).</task> + + <task>Plugable FEEDER infrastructure. For ease of debugging various + feeder stuff and/or as userland library and test suite.</task> + + <task>Extend the wiki page.</task> + </help> + </project> + + <project cat='docs'> + <title>Hungarian Translation of the Webpages</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Giorgos</given> + + <common>Keramidas</common> + </name> + + <email>keramida@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/hu/">Hungarian webpages</url> + </links> + + <body> + <p>Gábor Kövesdán (gabor@) has submitted the Hungarian translation + of the webpages and Giorgos Keramidas (keramida@) has reviewed and + committed the pages. The initial rendering issues have also been + fixed and the webpage is in a pretty good shape now.</p> + + <p>As usual, this translation does not contain every part of the + English version, but the most important and useful parts are there. + Gábor will maintain this translation and regularly sync the content + with the English version and add new translations if such become + available.</p> + </body> + + <help> + <task>Fix typos and mistakes that will be revealed after a deeper + review by the public</task> + + <task>Get more people involved</task> + </help> + </project> + + <project cat='drv'> + <title>Intel 3945ABG Wireless LAN Driver: wpi</title> + + <contact> + <person> + <name> + <given>Benjamin</given> + + <common>Close</common> + </name> + + <email>benjsc@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/benjsc/wpi" /> + + <url href="http://www.clearchain.com/wiki/wpi" /> + </links> + + <body> + <p>An initial port of the NetBSD wpi driver has been done and + development is happening fast to get this driver ready for the + tree. At present basic functionality works. The driver can + associate with a non encrypted peer and pass data in 11b and 11g + modes. There is still lots to do and testing is welcome.</p> + + <p>Many thanks have to go to Sam, Max and Kip for helping the + driver reach this point.</p> + </body> + + <help> + <task>Solve bus dma alignment issues</task> + + <task>Support WEP and WPA</task> + + <task>Testing and more testing</task> + </help> + </project> + + <project cat='proj'> + <title>iSCSI Initiator</title> + + <contact> + <person> + <name> + <given>Daniel</given> + + <common>Braniss</common> + </name> + + <email>danny@cs.huji.ac.il</email> + </person> + </contact> + + <links> + <url + href="ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.0.1.tar.bz2" /> + </links> + + <body> + <p>Though it is still a work in progress, it now supports more + targets, has login CHAP authentication and header/data digest. It + will also recover from a lost connection - most of the time.</p> + </body> + + <help> + <task>instrumentation</task> + + <task>task management support</task> + + <task>improve the error recovery</task> + </help> + </project> + + <project cat='arch'> + <title>FreeBSD/powerpc on Freescale MPC8555</title> + + <contact> + <person> + <name> + <given>Rafal</given> + + <common>Jaworowski</common> + </name> + + <email>raj@semihalf.com</email> + </person> + + <person> + <name> + <given>Marcel</given> + + <common>Moolenaar</common> + </name> + + <email>xcllnt@mac.com</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Platform summary: + <ul> + <li>PowerQuiccIII integrated controller</li> + + <li>e500 CPU core</li> + + <li>compliant with PowerPC BookE specification (significantly + different from the 'traditional' PowerPC architecture the current + FreeBSD/powerpc supports, particularly in the areas of MMU + design, exceptions model, specific e500 machine instructions + etc.)</li> + </ul> + </p> + + <p>Currently the machine is booting FreeBSD 6.1-RELEASE-p10 and + operating both single- and multi-user modes; below are highlights + of available functionality: + <ol> + <li>Low-level support</li> + + <ul> + <li>booting from U-Boot bootloader</li> + + <li>locore machine initialization</li> + + <li>e500 exceptions</li> + + <li>VM: a new pmap module developed</li> + </ul> + + <li>On-chip peripherals</li> + + <ul> + <li>introduced ocpbus hierarchy (nexus and descendants)</li> + + <li>interrupt controller: using generic OpenPIC driver</li> + + <li>serial console: using uart(4) driver</li> + + <li>barebones serial support using the QUICC's SCC</li> + + <li>host/PCI bridge: a new driver developed for the built-in + bridge</li> + + <li>networking: a new driver developed for TSEC (3-speed + Ethernet)</li> + </ul> + + <li>Booting</li> + + <ul> + <li>from ATA disk and USB memory stick (both through a + secondary PCI VIA82C686B controller)</li> + + <li>from network (NFS-mounted rootfs)</li> + </ul> + + <li>Basic TCP/IP protocols and apps work (DHCP, NFS, SSH, FTP, + Telnet etc.)</li> + + <li>Userland</li> + + <ul> + <li>integrated SoftFloat emulation lib (required due to e500 + not being equipped with the old-style PowerPC FPU)</li> + + <li>almost all applications seem to work</li> + </ul> + </ol> + </p> + </body> + + <help> + <task>Work out extensible layout for sys/powerpc architecture + directory so we can easily add support for new core variations and + platforms to come in the future.</task> + + <task>Integrate with FreeBSD source tree.</task> + + <task>Release and tinderbox related options and settings.</task> + </help> + </project> + + <project cat='proj'> + <title>Network Stack Virtualization</title> + + <contact> + <person> + <name> + <given>Marko</given> + + <common>Zec</common> + </name> + + <email>zec@fer.hr</email> + </person> + </contact> + + <links> + <url href="http://imunes.tel.fer.hr/virtnet/" /> + </links> + + <body> + <p>The network stack virtualization project aims at extending the + FreeBSD kernel to maintain multiple independent instances of + networking state. This will allow for complete networking + independence between jails on a system, including giving each jail + its own firewall, virtual network interfaces, rate limiting, + routing tables, and IPSEC configuration.</p> + + <p>The prototype currently virtualizes the basic INET and INET6 + kernel structures and subsystems, including the TCP machinery and + the IPFW firewall. The focus is currently being kept on resolving + bugs and sporadic lockups, and defining the internal and management + APIs. It is expected that within the next month the code will + become sufficiently complete and stable for testing by early + adopters.</p> + </body> + </project> + + <project cat='bin'> + <title>BSNMP Bridge Module</title> + + <contact> + <person> + <name> + <given>Shteryana</given> + + <common>Shopova</common> + </name> + + <email>syrinx@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/SnmpBridgeModule" /> + </links> + + <body> + <p>The BSNMP bridge module for FreeBSD's BSNMP daemon, which was + implemented during SoC 2006, was committed to HEAD. In addition to + RFC 4188 single bridge support it also supports monitoring multiple + bridges via a private MIB. Since SoC 2006 Rapid Spanning Tree + (RSTP) support (RSTP-MIB defined in RFC4318 and additions to the + private MIB) was added to the module as well.</p> + + <p>A patch for RELENG_6 is available and will be merged to STABLE + the next weeks.</p> + </body> + + <help> + <task>MFC to RELENG_6.</task> + + <task>More feedback from users is always welcome.</task> + </help> + </project> + + <project cat='bin'> + <title>BSNMP Client Tools</title> + + <contact> + <person> + <name> + <given>Shteryana</given> + + <common>Shopova</common> + </name> + + <email>syrinx@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Bjoern A.</given> + + <common>Zeeb</common> + </name> + + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/BsnmpTools">Wiki Page</url> + + <url + href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/syrinx/ bsnmp/contrib/bsnmp/snmptools"> + Shteryana's P4 tree</url> + + <url + href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/bz/ bsnmp%5fsyrinx/usr.sbin/bsnmpd/tools"> + Bjoern's P4 tree (rewrite)</url> + </links> + + <body> + <p>During SoC 2005 BSNMP client tools (bsnmptools) were implemented + and have since then been available via Shteryana's P4 tree or port + net-mgmt/bsnmptools.</p> + + <p>In order to finally get the code committed some cleanup was + needed which ended in a partly rewrite to minimize duplicate code + and to reduce the size of the binaries. This ongoing work is + available via Bjoern's P4 tree and will be merged back to upstream + trees before it will be committed to HEAD.</p> + </body> + + <help> + <task>Update Wiki Page to reflect latest work.</task> + + <task>Finish cleanup and have it reviewed.</task> + + <task>User feedback is always welcome.</task> + </help> + </project> + + <project cat='bin'> + <title>BSNMP - More Ongoing and Upcoming Work</title> + + <contact> + <person> + <name> + <given>Shteryana</given> + + <common>Shopova</common> + </name> + + <email>syrinx@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Harti</given> + + <common>Brandt</common> + </name> + + <email>harti@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Bjoern A.</given> + + <common>Zeeb</common> + </name> + + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/BsnmpTODO">BSNMP TODO Wiki + page</url> + </links> + + <body> + <p>In addition to other more detailed reports this is intended to + give a summary about other ongoing or upcoming BSNMP related work. + To collect some ideas from users and coordinate work a BSNMP TODO + Wiki page was created. Feel free to add your ideas or let us know + about them.</p> + + <p> + <ul> + <li>A contributor, Tsvetan Erenditsov, has volunteered to + implement a VLAN module for BSNMP. Shteryana is helping + him.</li> + + <li>Sam Leffler has asked for a wireless networking monitoring + module, which will most likely be the next module to be + implemented.</li> + + <li>Some major work is currently going on in the main BSNMP + tree: + <ul> + <li>SNMP transports have been factored out into loadable + modules. The old port tables are still there and will remain + at least for the next release. Later they will be removed. + The following modules and transports are already implemented + as loadable modules: + <ul> + <li>snmp_trans_udp: SNMP over UDP over IPv4, IPv6 and + scoped IPv6</li> + + <li>snmp_trans_tcp: SNMP over TCP over IPv4, IPv6 and + scoped IPv6</li> + + <li>snmp_trans_ldgram: SNMP over local datagram + sockets</li> + + <li>snmp_trans_lstream: SNMP over local stream sockets</li> + </ul> + </li> + + <li>Some I/O functions have been moved from the daemon to + libbsnmp.</li> + + <li>libisa has been imported into the bsnmp tree. This + library aims at easy implementation of command line tools for + remote and local system administration with a special focus + on administration via SNMP. The library contains command line + parsing functions, a function for automatically handling help + text. Actual administration modules are implemented as + loadable modules. The atmconfig tool in the FreeBSD tree + contains some old parts of this library.</li> + + <li>lisa_snmp is a module which implements SNMP functionality + for libisa.</li> + + <li>lisa_snmpd is a module for remote administration of the + bsnmpd.</li> + + <li>The config file parser of bsnmpd has been rewritten so + that each section of the file is handled as a transaction (in + contrast to the previous behavior where the entire file was + one transaction).</li> + </ul> + </li> + </ul> + </p> + </body> + </project> + + <project cat='team'> + <title>Release Engineering</title> + + <contact> + <person> + <name> + <given>Release Engineering Team</given> + </name> + + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/" /> + + <url href="http://www.FreeBSD.org/releases/6.2R/announce.html" /> + + <url href="http://www.FreeBSD.org/snapshots/" /> + </links> + + <body> + <p>The recent activities of the Release Engineering team have + centered around FreeBSD 6.2-RELEASE, which is now available for + downloading. This is the latest release from the RELENG_6 branch, + and includes many new performance and stability improvements, bug + fixes, and new features. The release notes and errata notes for + FreeBSD 6.2 contain more specific information about what's new in + this version. We thank the FreeBSD developer and user community for + their efforts towards making this release possible.</p> + + <p>The Release Engineering Team also produced snapshots of FreeBSD + CURRENT in November 2006 and January 2007. These snapshots have not + received extensive testing, and should not be used in production + environments. However, they can be used for testing or + experimentation, and show the kinds of functionality that can be + expected in future FreeBSD releases.</p> + </body> + </project> + + <project cat='bin'> + <title>Libelf</title> + + <contact> + <person> + <name> + <given>Joseph</given> + + <common>Koshy</common> + </name> + + <email>jkoshy@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/LibElf">Wiki page tracking + LibELF</url> + + <url href="http://wiki.FreeBSD.org/PmcTools">Wiki page for + PmcTools</url> + + <url + href="http://people.FreeBSD.org/~jkoshy/projects/perf-measurement/"> + PMC Tools Project</url> + </links> + + <body> + <p>Libelf is a BSD-licensed library for ELF parsing & + manipulation implementing the SysV/SVR4 (g)ELF[3] API.</p> + + <p>Current status: The library is now in -CURRENT. Work continues + on its test suite and tutorial, and on deploying it in + PmcTools.</p> + </body> + </project> + + <project cat='docs'> + <title>The FreeBSD Dutch Documentation Project</title> + + <contact> + <person> + <name> + <given>Remko</given> + + <common>Lodder</common> + </name> + + <email>remko@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/doc/nl/books/handbook" /> + + <url href="http://www.evilcoder.org/content/section/6/39/" /> + + <url href="http://www.FreeBSD-nl.org/doc/nl/" /> + + <url href="http://www.FreeBSD-nl.org/www/" /> + </links> + + <body> + <p>The FreeBSD Dutch Documentation Project is an ongoing project to + translate the FreeBSD Handbook to the Dutch Language.</p> + + <p>Currently we almost translated the entire handbook, and we + translated parts of the website, sadly the project went into a + slush lately, so we seek out for fresh and new translators that are + willing to join the team to continue the effort.</p> + </body> + + <help> + <task>Translate the rest of the handbook</task> + + <task>Make the documentation up to date</task> + + <task>Translate the rest of the website</task> + </help> + </project> + + <project cat='ports'> + <title>FreeBSD GNOME Project</title> + + <contact> + <person> + <name> + <given>FreeBSD</given> + + <common>GNOME Project</common> + </name> + + <email>gnome@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/gnome/" /> + </links> + + <body> + <p>Where have we been?! Not doing status reports, that's for sure. + But the FreeBSD GNOME project has been very busy with regular GNOME + releases, and other side projects. We are currently shipping GNOME + 2.16.2 in the ports tree, and we are testing GNOME 2.17.5 in the + <a href="http://www.FreeBSD.org/gnome/docs/develfaq.html"> + MarcusCom</a> + + tree.</p> + + <p>Most recently, work has completed on a cleanup of the FreeBSD + backend to libgtop. This module has needed a lot of work, and + should now be reporting correct system statistics. The cleaned up + version is currently being tested in the MarcusCom tree, and will + make it into the FreeBSD ports tree along with GNOME 2.18.</p> + + <p>The GStreamer framework has been taken out of direct + <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-gnome"> + gnome@</a> + + maintainership, and put under a new + <a + href="http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia"> + multimedia@</a> + + umbrella. This will give multimedia-savvy developers a chance to + collaborate on this important piece of the GNOME Desktop along with + other important audio and video components.</p> + + <p>The biggest accomplishment of 2006 for the FreeBSD GNOME team + had to have been the port of + <a href="http://www.freedesktop.org/wiki/Software_2fhal">HAL</a> + + . This effort was started to give FreeBSD users a richer desktop + experience. Since the initial FreeBSD release of HAL with GNOME + 2.16, it has been incorporated into the FreeBSD release of KDE + 3.5.5 as well as PC-BSD 1.3. The FreeBSD backend has also made it + upstream into the HAL git repository so future releases of HAL will + have FreeBSD support out-of-the-box.</p> + + <p>Finally, it is with sadness that we say good-bye to one of our + team members. Adam Weinberger stepped down from the FreeBSD GNOME + team to save lives instead (priorities, man!). His splash screens + and grammar nit-picking will be missed.</p> + </body> + + <help> + <task>Now that HAL has been ported to FreeBSD, there is a strong + desire to see + <a href="http://www.gnome.org/projects/NetworkManager/"> + NetworkManager</a> + + ported. The big parts will be porting NM to use our 80211 + framework, and extending some of the base utilities such as + ifconfig. Contact + <a href="mailto:marcus@FreeBSD.org">marcus@FreeBSD.org</a> + + if you are interested in helping.</task> + + <task>Our system-tools-backends module needs some attention. This + module is responsible for system configuration tasks in GNOME such + as user management, network shares administration, etc. A knowledge + of Perl is highly recommended. Contact + <a href="mailto:marcus@FreeBSD.org">marcus@FreeBSD.org</a> + + if you are interested in helping.</task> + + <task>We need good documentation writers to help update our + <a href="http://www.FreeBSD.org/gnome/docs/faq2.html">FAQ</a> + + and other documentation. If you would like to take on the + responsibility full-time, or just contribute some pieces, please + notify + <a href="mailto:gnome@FreeBSD.org">gnome@FreeBSD.org</a> + + .</task> + + <task>We are always in need of GNOME development testers. See our + <a href="http://www.FreeBSD.org/gnome/docs/develfaq.html"> + development branch FAQ</a> + + for ways on how you can help make the next release of GNOME the + best release.</task> + </help> + </project> + + <project cat='net'> + <title>ipfw NAT and libalias</title> + + <contact> + <person> + <name> + <given>Paolo</given> + + <common>Pisati</common> + </name> + + <email>piso@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Support for in-kernel NAT, redirect and LSNAT for ipfw was + committed to HEAD, and i encourage people to test it so we can + quickly discover/fix bugs.</p> + + <p>To add these features to ipfw, compile a new kernel adding + "options IPFIREWALL_NAT" to your kernel config or, in case you use + modules, add "CFLAGS += -DIPFIREWALL_NAT" to your make.conf.</p> + </body> + + <help> + <task>Teach libalias to handle mbufs (this will fix TSO-capable + NICs).</task> + + <task>Add support for hardware checksum offloading.</task> + </help> + </project> + + <project cat='kern'> + <title>Interrupt Filtering</title> + + <contact> + <person> + <name> + <given>Paolo</given> + + <common>Pisati</common> + </name> + + <email>piso@FreeBSD.org</email> + </person> + + <person> + <name> + <given>John</given> + + <common>Baldwin</common> + </name> + + <email>jhb@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Scott</given> + + <common>Long</common> + </name> + + <email>scottl@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/Interrupts" /> + </links> + + <body> + <p>Interrupt filtering is a new method to handle interrupts in + FreeBSD that retains backward compatibility with the previous + models (FAST and ITHREAD), while improving over them in some + aspects. With interrupt filtering, the interrupt handler is divided + into 2 parts: the filter (that checks if the actual interrupt + belongs to a device) and a private per-handler ithread (that is + scheduled in case some blocking work has to be done). The main + benefits of this work are: + <ul> + <li>Feedback from filters (the operating system finally knows + what's the state of an event and can react consequently).</li> + + <li>Lower latency/overhead for shared interrupt line.</li> + + <li>Previous experiments with interrupt filtering showed an + increase in performance against the plain ithread model in some + cases.</li> + + <li>General shrink of the machine dependent code - part of the + interrupting handling code was turned into machine independent + code.</li> + </ul> + </p> + + <p>During the last quarter many improvements were made up to the + point where 3 archs (i386, amd64 and arm) are reported to work, and + the project can be considered feature complete.</p> + + <p>I definitely want to make it part of the 7.0 release.</p> + </body> + + <help> + <task>Define a road map to commit the code into the tree.</task> + + <task>Rethink the interrupt stray handling (?!?!).</task> + + <task>Finish off support for powerpc, sparc64 and ia64 (sun4v + support is known to be broken now).</task> + </help> + </project> + + <project cat='team'> + <title>FreeBSD Bugbusting Team</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ceri</given> + + <common>Davies</common> + </name> + + <email>ceri@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Remko</given> + + <common>Lodder</common> + </name> + + <email>remko@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://www.FreeBSD.org/doc/en/articles/pr-guidelines/" /> + + <url + href="http://www.FreeBSD.org/doc/en/articles/problem-reports/" /> + </links> + + <body> + <p>The FreeBSD Bugbusting team is a team of volunteers keeping + track of various PR tickets in the GNATS application. Currently the + Bugbusting team is investigating old PR tickets, checking whether + they are still accurate, checking what needs to be done to fix the + issues reported and make sure that the developers team can focus on + the latest releases.</p> + + <p>The team is always in need of volunteers willing to give a hand + to resolve the old tickets and get the best feedback that is needed + for the open tickets.</p> + + <p>Please contact + <a href="mailto:FreeBSD-bugbusters@FreeBSD.org"> + FreeBSD-bugbusters@FreeBSD.org</a> + + if you want more information about the things that need to be + done.</p> + </body> + + <help> + <task>Checkout old PR tickets, getting the proper feedback and + finally fix and/or resolve the tickets.</task> + </help> + </project> + + <project cat='team'> + <title>The FreeBSD Foundation</title> + + <contact> + <person> + <name> + <given>Deb</given> + + <common>Goodkin</common> + </name> + + <email>deb@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSDFoundation.org">The FreeBSD + Foundation</url> + </links> + + <body> + <p>The FreeBSD Foundation ended 2006 raising over $100,000. We + received commitments for another $55,000 in donations for the Fall + Fundraiser. We fell short of our goal of raising $200,000. But, we + are working hard to fill this gap, early in 2007, so we can + continue with the same level of support for the project and + community. Please go to + <a href="http://www.freebsdfoundation.org/donate/"> + http://www.freebsdfoundation.org/donate/</a> + + to find out how to make a donation to the foundation.</p> + + <p>We added a donors page to our website to acknowledge our + generous donors. We negotiated and are now actively managing a + joint technology project with NLNet and the University of Zagreb to + develop virtualized network stack support for FreeBSD. We sponsored + AsiaBSDCon and are now accepting travel grant applications for this + conference.</p> + + <p>We are working to upgrade the project's network testbed with + 10Gigabit interconnects. Cisco has generously donated a 10Gigabit + switch and we have received network adapters from Myricom, + Neterion, Intel, and Chelsio. Adapters from other vendors are being + solicited so that we can do interoperability testing.</p> + + <p>For more information on what we've been up to, check out our + end-of-year newsletter at + <a + href="http://www.freebsdfoundation.org/press/2006Dec-newsletter.shtml"> + http://www.freebsdfoundation.org/press/2006Dec-newsletter.shtml</a> + + .</p> + </body> + </project> + + <project cat='ports'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ports/">The FreeBSD Ports + Collection</url> + + <url + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/"> + Contributing to the FreeBSD Ports Collection</url> + + <url href="http://people.FreeBSD.org/~fenner/portsurvey/">FreeBSD + ports unfetchable distfile survey (Bill Fenner's report)</url> + + <url href="http://portsmon.FreeBSD.org/index.html">FreeBSD ports + monitoring system</url> + + <url href="http://www.FreeBSD.org/portmgr/index.html">The FreeBSD + Ports Management Team</url> + + <url href="http://tinderbox.marcuscom.com">marcuscom + Tinderbox</url> + </links> + + <body> + <p>The ports count has jumped to 16347. The PR count, despite a + jump, has gone back down to around 700.</p> + + <p>Not much work has been committed on the ports infrastructure due + to the long 6.2 release cycle. However, many test runs have been + done for several upcoming features, such as making sure that ports + will work with the new release of gcc (4.1), and do not have + /usr/X11R6 hard-coded into them. The intention of the latter is to + move all ports to $LOCALBASE, which can then be selected by the + user. This should help consistency going forwards, albeit at the + cost of a one-time conversion.</p> + + <p>GNOME was updated to 2.16 during the release cycle.</p> + + <p>In addition, we are in the process of moving the FORTRAN default + from f77 to gfortran. See the ports mailing list for details.</p> + + <p>The new xorg ports are still being worked on as well; they are + intended to all live in $LOCALBASE. Hopefully this can get done in + the early 6.3 development cycle. See the wiki for more + information.</p> + + <p>A new version of the ports Tinderbox code is available, which is + mostly a bugfix release.</p> + + <p>We have also added Pav Lucistnik as a new portmgr member, who we + hope will help us work on the portmgr PR backlog. Welcome!</p> + + <p>We have also added 8 new committers since the last report.</p> + + <p>linimon continues to work on resetting committers who are no + longer interested in their ports; as well, several ports commit + bits have been stored for safekeeping. This is part of an attempt + to keep the best match between volunteers and work to be done.</p> + </body> + + <help> + <task>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.</task> + + <task>Although we have added many maintainers, we still have many + unmaintained ports. As well, the packages on amd64 and sparc64 are + lagging behind.</task> + </help> + </project> + + <project cat='team'> + <title>FreeBSD Security Officer and Security Team</title> + + <contact> + <person> + <name> + <given>Security</given> + + <common>Officer</common> + </name> + + <email>security-officer@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Security</given> + + <common>Team</common> + </name> + + <email>security-team@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/security/" /> + + <url + href="http://www.FreeBSD.org/administration.html#t-secteam" /> + + <url href="http://vuxml.FreeBSD.org/" /> + </links> + + <body> + <p>In the time since the last status report, four security + advisories have been issued concerning problems in the base system + of FreeBSD (three in 2006 and one in 2007); of these, one problem + was in "contributed" code, while the remaining three were in code + maintained within FreeBSD. The Vulnerabilities and Exposures Markup + Language (VuXML) document has continued to be updated by the + Security Team and Ports Committers documenting new vulnerabilities + in the FreeBSD Ports Collection; since the last status report, 55 + new entries have been added, bringing the total up to 869.</p> + + <p>In order to streamline security team operations and ensure that + incoming emails are promptly acknowledged, Remko Lodder has been + appointed the security team secretary.</p> + + <p>The following FreeBSD releases are supported by the FreeBSD + Security Team: FreeBSD 4.11, FreeBSD 5.5, FreeBSD 6.0, FreeBSD 6.1, + and FreeBSD 6.2. The respective End of Life dates of supported + releases are listed on the web site; of particular note, FreeBSD + 4.11 and FreeBSD 6.0 will cease to be supported at the end of + January 2007.</p> + </body> + </project> + + <project cat='kern'> + <title>Cryptographic Subsystem</title> + + <contact> + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Michael Richardson has been spearheading work to improve the + crypto subsystem used by various parts of the kernel including Fast + IPSec and geli. This work is sponsored by Hifn and has been + happening outside the CVS repository. A main focus of this work is + to add support for higher-level hardware operations that can + significantly improve the performance of IPSec and SSL + protocols.</p> + + <p>Results of this work are now being readied for CVS. These + redesign the core/driver APIs to use the kobj facilities and recast + software crypto drivers as pseudo devices. The changes greatly + improve the system and permit new functionality such as specifying + which crypto device to use when multiple are available. The + redesign will also enable load balancing of crypto work across + multiple devices and the addition of virtual crypto sessions by + which small operations can be done in software when the overhead to + set up a hardware device is too costly.</p> + + <p>In addition to the changes to the core crypto system several + crypto drivers have been updated to improve their operation. Top of + this list is the hifn(4) driver where many longstanding bugs have + been fixed for 7955/756 parts.</p> + </body> + </project> + + <project cat='arch'> + <title>ARM/XScale Port</title> + + <contact> + <person> + <name> + <given>Olivier</given> + + <common>Houchard</common> + </name> + + <email>cognet@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>FreeBSD is running multi-user on a variety of Gateworks Avila + boards with most of the on-board devices supported. These include + the compact flash/IDE slot, wired network interfaces, realtime + clock, and environmental sensors. Several different minipci cards + have been tested including those supported by the ath(4) and + hifn(4) drivers. Remaining devices that need support are the + onboard flash, optional 4-port network switch, and optional USB + interface. Crypto acceleration for IXP425 parts is planned but will + likely be done at a later time.</p> + + <p>The Network Processor Engine (NPE) support is done with an + entirely new replacement for the Intel Access Layer (IAL). The most + important hardware facilities are supported (e.g. the hardware Q + manager) and the wired NIC driver was also done from scratch. The + resulting code is approximately 1/10th the number of lines of the + equivalent IAL code.</p> + </body> + + <help> + <task>Bootstrap support needs work to enable booting from the + compact flash device.</task> + </help> + </project> + + <project cat='proj'> + <title>Porting ZFS to FreeBSD</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + + <common>Dawidek</common> + </name> + + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs"> + Source code.</url> + + <url href="http://www.opensolaris.org/os/community/zfs/porting/"> + ZFS porting site.</url> + + <url + href="http://docs.FreeBSD.org/cgi/mid.cgi?20060822104516.GB16033"> + ZFS port announce.</url> + </links> + + <body> + <p>The ZFS file system works quite well on FreeBSD now. The first + patchset has already been published on the + <a herf="http://lists.freebsd.org/mailman/listinfo/freebsd-fs"> + freebsd-fs@FreeBSD.org mailing list</a> + + .</p> + + <p>All file system methods are already implemented (except + ACL-related). Basically all stress tests I tried work, even under + very high load. There is still a problem with memory allocation, + which can get out of control, but from what I know the SUN guys + also work on this.</p> + + <p>Recently I have been working on a file system regression test + suite. From what I found, there are no such test suites for free. + I've already more than 3000 tests and I'm testing correctness of + most file system related syscalls (chflags, chmod, chown, link, + mkdir, mkfifo, open, rename, rmdir, symlink, truncate, unlink). I'm + also working to make it usable on other operating systems (like + Solaris, where it already works and Linux).</p> + + <p>Few days ago I also (almost) finished NFS support. You can't use + the 'zfs share' command yet, but you can export file systems via + /etc/exports and you can also access snapshots. It was quite hard, + because snapshots are separate file systems and after exporting the + main file system, we need to also serve data from snapshots under + it.</p> + + <p>The one big thing which is missing is ACL support. This is not + an easy task, because we first have to make some decisions. + Currently we use POSIX ACLs in our UFS, but the market is moving + slowly to NTFS/NFSv4-type ACLs. In Solaris they use POSIX ACLs for + UFS and NFSv4-type ACLs for ZFS and we probably also want to use + NFSv4-type ACLs in our ZFS, which requires some work outside + ZFS.</p> + </body> + </project> + + <project cat='proj'> + <title>TrustedBSD priv(9)</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/">TrustedBSD Project</url> + </links> + + <body> + <p>TrustedBSD priv(9) replaces suser(9) as an in-kernel interface + for checking privilege in FreeBSD 7.x. Each privilege check now + takes a specific named privilege. This allows both centralization + of jail logic relating to privilege, which is currently distributed + around the kernel at the point of each call to suser(9), and allows + instrumentation of the privilege logic by the MAC Framework. Two + new MAC Framework entry points, one to grant and the other to limit + privilege, are now available, providing fine-grained control of + kernel privilege by policy modules. This lays the kernel + infrastructure groundwork for further refinement and extension of + the kernel privilege model. The priv(9) implementation has been + committed to FreeBSD 7-CURRENT.</p> + + <p>This software was developed by Robert N. M. Watson for the + TrustedBSD Project under contract to nCircle Network Security, + Inc.</p> + </body> + + <help> + <task>Complete review of kernel privilege checks, removal of + suser(9) jail flag now that checks are centralized.</task> + + <task>Explore possible changes to kernel privilege model along + lines of POSIX.1e privileges, the Solaris privilege interface, etc. + This has been explored previously as part of the TrustedBSD + Capabilities project also.</task> + </help> + </project> + + <project cat='proj'> + <title>TrustedBSD MAC Framework</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/mac.html">TrustedBSD + Project</url> + </links> + + <body> + <p>Most work on the MAC Framework during this period, other than as + relates to the priv(9) project described in a separate status + report, has been in refinement of the structure of the framework. + <ul> + <li>Add two new entry points allowing MAC Framework policy + modules to grant or limit fine-grained system privileges.</li> + + <li>A sample mac_priv(4) policy module has been created + demonstrating how a MAC Framework policy module can grant + specific system privileges to specific users.</li> + + <li>Commenting throughout the MAC Framework significantly + extended.</li> + + <li>Correct a bug in which the original ifnet label was copied to + user space via ioctl, rather than the thread-local copy.</li> + + <li>mac_enforce_subsystem debugging sysctls removed, as some + policies rely on access control checks being called even when + non-enforcing (specifically, information flow related + policies).</li> + + <li>Break out mac.h include file into mac.h (user API, system + calls) and mac_framework.h (in-kernel interface to the MAC + Framework). Move non-user MAC include files from src/sys to + src/sys/security/mac. Move and break out kern_mac.c into + mac_framework.c and mac_syscalls.c. The MAC Framework is now + entirely located in src/sys/security/mac.</li> + + <li>Export the MAC Framework version via a read-only sysctl and + provide a #define version usable by policies.</li> + + <li>MAC Framework locking optimized to optimistically expect no + write lock contention during read locking.</li> + </ul> + </p> + </body> + + <help> + <task>Now that the MAC Framework has been fully moved to + src/sys/security/mac, embark on the 'mac2' interface cleanup, in + which many MAC Framework entry points are renamed for consistency. + This will require most MAC Framework policy modules to be modified + between FreeBSD 6.x and FreeBSD 7.x, although in a way that can be + largely done using sed.</task> + + <task>Add accessor functions for policies retrieving per-policy + label data from labels, so that policy modules do not compile in + the binary layout of struct label. This will allow future + optimization of the label layout.</task> + + <task>Complete integration of audit and MAC support, allowing MAC + policy modules to control access to audit interfaces, and allowing + them to annotate audit records.</task> + </help> + </project> + + <project cat='proj'> + <title>TrustedBSD Audit</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Christian</given> + + <common>Peron</common> + </name> + + <email>csjp@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Wayne</given> + + <common>Salamon</common> + </name> + + <email>wsalamon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/audit.html">TrustedBSD Audit + Page</url> + + <url href="http://www.OpenBSM.org/">OpenBSM Page</url> + </links> + + <body> + <p>FreeBSD 6.2-RELEASE, the first release of FreeBSD with + experimental audit support is now available. The plan is to make + audit a full production feature as of FreeBSD 6.3-RELEASE, with + "options AUDIT" compiled in by default. A TODO list has been posted + to trustedbsd-audit.</p> + + <p>OpenBSM 1.0 alpha 13, which includes support for XML record + printing, additional 64-bit token types, additional audit events, + and more cross-platform build support, has been released. OpenBSM + 1.0 alpha 14, which adds support for warnings clean building with + gcc 4.1, will be released shortly. The new OpenBSM release will be + merged to FreeBSD CVS in late January or early February.</p> + </body> + + <help> + <task>Complete assignment of audit events to non-native and a few + remaining native system calls. Add additional system call argument + auditing.</task> + + <task>Merge MAC Framework hooks allowing MAC modules to control + access to kernel audit services. Refine and merge MAC labeling + support in audit, including support for MAC annotations in the + audit trail.</task> + + <task>Complete pass through user space services adding audit + support to system management tools (and ftpd). Work with third + party software maintainers to add audit support for applications + like xdm/kdm/gdm.</task> + + <task>Merge latest OpenBSM, including XML output support.</task> + </help> + </project> + + <project cat='net'> + <title>FAST_IPSEC Upgrade</title> + + <contact> + <person> + <name> + <given>George</given> + + <common>Neville-Neil</common> + </name> + + <email>gnn@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Bjoern</given> + + <common>Zeeb</common> + </name> + + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~gnn/fast_ipv6.patch">Host only + patch</url> + + <url href="http://blogs.FreeBSDish.org/gnn/">gnn's networking + blog</url> + </links> + + <body> + <p>Just this week I got routing working for the FAST_IPSEC and IPv6 + code. Now there are memory smash problems, and then we need to + remove the old GIANT lock. I hope to produce another patch with the + routing code working in the next week.</p> + </body> + + <help> + <task>Test the patch!!!!</task> + </help> + </project> + + <project cat='net'> + <title>Automatic TCP Send and Receive Socket Buffer Sizing</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://people.FreeBSD.org/~andre/tcp_auto_buf-20061212.diff"> + Patch against 7-CURRENT</url> + + <url + href="http://people.FreeBSD.org/~andre/tcp_auto_buf-20061212-RELENG_6.diff"> + Patch against RELENG_6</url> + </links> + + <body> + <p>Normally the socket buffers are static (either derived from + global defaults or set with setsockopt) and do not adapt to real + network conditions. Two things happen: a) your socket buffers are + too small and you can't reach the full potential of the network + between both hosts; b) your socket buffers are too big and you + waste a lot of kernel memory for data just sitting around.</p> + + <p>With automatic TCP send and receive socket buffers we can start + with a small buffer and quickly grow it in parallel with the TCP + congestion window to match real network conditions.</p> + + <p>FreeBSD has a default 32K send socket buffer. This supports a + maximal transfer rate of only slightly more than 2Mbit/s on a 100ms + RTT trans-continental link. Or at 200ms just above 1Mbit/s. With + TCP send buffer auto scaling and the default values below it + supports 20Mbit/s at 100ms and 10Mbit/s at 200ms. That's an + improvement of factor 10, or 1000%. For the receive side it looks + slightly better with a default of 64K buffer size.</p> + + <p>The automatic send buffer sizing patch is currently running on + one half of the FTP.FreeBSD.ORG cluster w/o any problems so far. + Against this machine with the automatic receive buffer sizing patch + I can download at 5.7 MBytes per second. Without patch it maxed out + at 1.6 MBytes per second as the delay bandwidth product became + equal to the static socket buffer size without hitting the limits + of the physical link between the machines. My test machine is about + 35ms from that FTP.FreeBSD.ORG and connected through a moderately + loaded 100Mbit Internet link.</p> + + <p>New sysctls are: + <ul> + <li>net.inet.tcp.sendbuf_auto=1 (enabled)</li> + + <li>net.inet.tcp.sendbuf_inc=8192 (8K, step size)</li> + + <li>net.inet.tcp.sendbuf_max=262144 (256K, growth limit)</li> + + <li>net.inet.tcp.recvbuf_auto=1 (enabled)</li> + + <li>net.inet.tcp.recvbuf_inc=16384 (16K, step size)</li> + + <li>net.inet.tcp.recvbuf_max=262144 (256K, growth limit)</li> + </ul> + </p> + </body> + </project> + + <project cat='net'> + <title>Wireless Networking</title> + + <contact> + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@errno.com</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Work on wireless support has continued to evolve in the public + CVS tree while other work has been going on behind the scenes in + the developer's perforce repository.</p> + + <p>Support was recently added to HEAD for half- and quarter-rate + channels as found in the 4.9 GHz FCC Public Safety Band. This work + was a prerequisite to adding similar support in the 900 MHz band as + found in Ubiquiti's SR9 cards. Adding this functionality was + straightforward due to the design of the net80211 layer, requiring + only some additions to handle the unusual mapping between + frequencies and IEEE channel numbers. The ath(4) driver currently + supports hardware capable of operating on half- and quarter-rate + channels.</p> + + <p>Kip Macy recently made significant advances preparing legacy + drivers for the re-architected net80211 layer that has been + languishing in perforce. With his efforts this code is nearly ready + for public testing after which it can be merged into CVS. Our goal + is to complete this merge in time for the 7.x branch (otherwise it + will be forced to wait for 8.0 before it appears in a public + release). This revised net80211 layer includes advanced station + mode facilities such as background scanning and roaming and support + for Atheros' SuperG extensions. Getting the revised scanning work + into CVS will greatly simplify public distribution of the Virtual + AP (VAP) code as a patch as well as enable addition of 802.11n + support.</p> + + <p>Benjamin Close is working on support for the Intel 3945 parts + commonly found in laptops. The work is going on in the perforce + repository with public code drops for testing.</p> + + <p>Atheros PCI/Cardbus support was updated with a new HAL that + fixes a few minor issues and corrects a problem that kept AR2424 + parts from working. The new HAL also enables more efficient use of + the hardware keycache for TKIP keys; on newer hardware you can now + support up to 57 stations without faulting keys into the cache. + Support for the latest 802.11n parts found in the new Lenovo and + Apple laptops (among others) is in development; initial release + will support only legacy operation.</p> + + <p>Support for Atheros USB devices is coming. Atheros has agreed to + license their firmware with the same license applied to the HAL + which means it can be committed to the tree and distributed as part + of releases. The driver is still in development.</p> + + <p>wpa_supplicant and hostapd were updated to the latest stable + build releases from Jouni Malinen. Shortly the in-tree code base + will switch to the 0.5.x tree which will bring in much new + functionality including dynamic VLAN tagging that will be + especially useful once the multi-bss support is available.</p> + + <p>The support for injection of raw 802.11 frames was committed to + HEAD. This work was done in collaboration with Andrea Bittau. At + this point there are no plans to commit this to the STABLE branch + as it requires API changes.</p> + </body> + </project> + + <project cat='misc'> + <title>EuroBSDCon 2007</title> + + <contact> + <person> + <name> + <given>Sidsel</given> + + <common>Jensen</common> + </name> + + <email>info@EuroBSDCon.dk</email> + </person> + </contact> + + <links> + <url href="http://2007.EuroBSDCon.org/" /> + + <url href="http://www.EuroBSDCon.dk/" /> + </links> + + <body> + <p>The sixth EuroBSDCon will take place in Copenhagen, Denmark on + <strong>Friday the 14th and Saturday 15th of September + 2007</strong> + + . The conference will be held at + <a href="http://www.symbion.dk/">Symbion Science Park</a> + + . Sunday the 16th there will be an optional tour to LEGOland.</p> + + <p>The + <a href="http://2007.eurobsdcon.org/cfp.html">call for papers</a> + + was sent out right after EuroBSDCon 2006 in Milan in November and + abstracts are due February 1st! So hurry up and send in all your + fantastic and amazing papers to papers at eurobsdcon dot dk.</p> + </body> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2007-01-2007-03.xml b/en_US.ISO8859-1/htdocs/news/status/report-2007-01-2007-03.xml new file mode 100644 index 0000000000..3e3115d35a --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2007-01-2007-03.xml @@ -0,0 +1,1117 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status +Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2007-01-2007-03.xml,v 1.3 2007/04/11 04:11:09 brd Exp $ --> +<report> + <date> + <month>January-March</month> + + <year>2007</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report covers FreeBSD related projects between January and + March 2007. This quarter ended with a big bang as a port of Sun's + critically acclaimed ZFS was added to the tree and thus will be + available in the upcoming FreeBSD 7.0 release. Earlier this year + exciting benchmark results showed the fruits of our SMP work. Read + more on the details in the "SMP Scalability" report.</p> + + <p>During the summer, FreeBSD will once again take part in Google's + Summer of Code initiative. Student selection is underway and we are + looking forward to a couple of exciting projects to come.</p> + + <p> + <a href="http://www.bsdcan.org/">BSDCan</a> + + is approaching rapidly, and will be held May 16-19th in Ottawa.</p> + + <p>Thanks to all the reporters for the excellent work! We hope you + enjoy reading.</p> + </section> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>team</name> + + <description>FreeBSD Team Reports</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>net</name> + + <description>Network Infrastructure</description> + </category> + + <category> + <name>bin</name> + + <description>Userland Programs</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='misc'> + <title>BSDCan 2007</title> + + <contact> + <person> + <name> + <given>Dan</given> + + <common>Langille</common> + </name> + + <email>dan@langille.org</email> + </person> + </contact> + + <links> + <url href="http://www.bsdcan.org/2007/">BSDCan 2007</url> + </links> + + <body> + <p>The + <a href="http://www.bsdcan.org/2007/schedule/">Schedule</a> + + and the + <a + href="http://www.bsdcan.org/2007/schedule/track/Tutorial/index.en.html"> + Tutorials</a> + + have been released. Once again, we have a very strong collection of + + <a href="http://www.bsdcan.org/2007/schedule/speakers.en.html"> + Speakers</a> + + .</p> + + <p>BSDCan: Low Cost. High Value. Something for Everyone.</p> + + <p>Everyone is going to be there. Make your plans now.</p> + </body> + </project> + + <project cat='team'> + <title>Problem Report Database</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>bugmeister_at_freebsd_dot_org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/support.html#gnats">GNATS</url> + </links> + + <body> + <p>We have added Remko Lodder to the bugmeister team. Remko has + been doing a great deal of work to go through antique PRs, + especially in the i386 category, and it was time to recognize that + hard work. As a result of his work the i386 count is at a + multi-year low.</p> + + <p>Remko has also been instrumental in working with some new + volunteers who are interested in finding out how they can + contribute. Our current plans are to ask them to look through the + PR backlog and, firstly, ask for feedback from the submitters, and + secondly, identify PRs that need action by committers. We also have + some committers who have volunteered to review those PRs. If you + are interested in helping, please subscribe to + bugbusters@FreeBSD.org. Our thanks to our current helpers, + including Harrison Grundy.</p> + + <p>The overall PR count has dropped to around 5100, a significant + reduction.</p> + </body> + </project> + + <project cat='misc'> + <title>EuroBSDCon 2007</title> + + <contact> + <person> + <name> + <given>EuroBSDCon 2007 Organizing Committee</given> + </name> + + <email>info@EuroBSDCon.dk</email> + </person> + </contact> + + <links> + <url href="http://2007.EuroBSDCon.org/" /> + </links> + + <body> + <p>The sixth EuroBSDCon will take place at + <a href="http://uk.symbion.dk/">Symbion</a> + + in Copenhagen, Denmark on Friday the 14th and Saturday 15th of + September 2007.</p> + + <p>The + <strong>estimated</strong> + + price for the two day conference is 200EUR, excluding + <a href="http://www.legoland.dk/">Legoland</a> + + trip and social event. The whole-day trip to Legoland is expected + to cost around 130EUR including transportation, some food on the + way, and entry fee. Arrangements have been made with a newly + renovated + <a href="http://danhostel.dk/vandrerhjem.asp?lan=uk&id=144"> + Hostel</a> + + which offers beds for 23EUR per night and 10EUR breakfast. A lounge + with sponsored Internet connection will be available at the Hostel. + Staying at the hostel is of course entirely optional and several + Hotels exists in the area. Reservation for the conference and exact + prices are expected to be ready no later than 1st of May.</p> + + <p>As of this writing 10 presentations have been accepted and more + are in the process of being evaluated.</p> + + <p>For FreeBSD Developers, a by invitation Developers summit will + be held in connection with the conference. Exactly when this will + take place has not yet been decided.</p> + + <p>We are still looking for more sponsors.</p> + + <p>A public IRC channel + <strong>#eurobsdcon</strong> + + on EFnet has been created for discussion and questions about the + conference.</p> + + <p>More details will follow on the + <a href="http://2007.EuroBSDCon.org/">EuroBSDCon 2007 web site</a> + + as they become available.</p> + </body> + </project> + + <project cat='net'> + <title>FAST_IPSEC Upgrade</title> + + <contact> + <person> + <name> + <given>George</given> + + <common>Neville-Neil</common> + </name> + + <email>gnn@freebsd.org</email> + </person> + + <person> + <name> + <given>Bjoern</given> + + <common>Zeeb</common> + </name> + + <email>bz@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~gnn/fast_ipv6.20070430.diff"> + Latest patch against CURRENT</url> + </links> + + <body> + <p>There are currently two p4 branches being used for this work: + gnn_fast_ipsec: a dual stack branch which contains both Kame and + FAST_IPSEC with v6 enabled. gnn_radical_ipsec: a single stack + branch, still in progress, where Kame IPsec has been removed and + only FAST remains.</p> + </body> + + <help> + <task>Test the patch!</task> + </help> + </project> + + <project cat="team"> + <title>The FreeBSD Foundation</title> + + <contact> + <person> + <name> + <given>Deb</given> + + <common>Goodkin</common> + </name> + + <email>deb@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsdfoundation.org">The FreeBSD + Foundation</url> + </links> + + <body> + <p>The FreeBSD Foundation ended Q1 raising over $65,000. We're a + quarter of the way to our goal of raising $250,000 this year. We + continued our mission of supporting developer communication by + helping FreeBSD developers attend AsiaBSDCon. We are a sponsor of + BSDCan and are currently accepting travel grant applications for + this conference.</p> + + <p>The foundation provided support that helped the ZFS file system + development. We continued working to upgrade the project's network + testbed with 10Gigabit interconnects. We attended SCALE where we + received an offer from No Starch Press to include a foundation ad + in their BSD books. Our first ad will appear in the book "Designing + BSD Rootkits."</p> + + <p>For more information on what we've been up to, check out our + website at + <a href="http://www.freebsdfoundation.org"> + http://www.freebsdfoundation.org</a> + + .</p> + </body> + </project> + + <project cat='bin'> + <title>GCC 4.1 integration</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Kabaev</common> + </name> + + <email>kan@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Kris</given> + + <common>Kennaway</common> + </name> + + <email>kris@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>A version of GCC 4.1 is being prepared for inclusion into + FreeBSD 7.0-CURRENT. Work was started late in 2006 but progress on + certain technical points (e.g. correctly integrating and + bootstrapping a shared libgcc_s into the build) was slow due to + lack of developer time. The remaining outstanding issue is that + compiling with -O2 is shown to lead to runtime failures of certain + binaries (e.g. some port builds); it is not currently known whether + these are due to application errors or GCC miscompilations. It is + believed that the current snapshot is otherwise ready for + inclusion, and this will likely happen within a week or two.</p> + </body> + </project> + + <project cat='kern'> + <title>Building Linux Device Drivers on FreeBSD</title> + + <contact> + <person> + <name> + <given>Luigi</given> + + <common>Rizzo</common> + </name> + + <email>rizzo@icir.org</email> + </person> + </contact> + + <links> + <url + href="http://info.iet.unipi.it/~luigi/FreeBSD/linux_bsd_kld.html" /> + </links> + + <body> + <p>The above URL documents some work done around January to build + an emulation layer for the Linux kernel API that would allow Linux + device driver to be built on FreeBSD with as little as possible + modifications. Initially the project focused on USB webcams, a + category of devices for which there was basically no support so + far. The emulation layer, available as a port ( + <b>devel/linux-kmod-compat</b> + + ) simulates enough of the Linux USB stack to let us build, from + unmodified Linux sources, two webcam drivers, also available as + ports ( + <b>multimedia/linux-gspca-kmod</b> + + and + <b>multimedia/linux-ov511-kmod</b> + + ), with the former supporting over 200 different cameras.</p> + + <p>While some of the functions map one-to-one, for others it was + necessary to build a full emulation (e.g. collecting input from + various function calls, and then mapping sets of Linux data + structures into functionally equivalent sets of FreeBSD data + structures). But overall, this project shows that the software + interfaces are reasonably orthogonal to each other so one does not + need to implement the full Linux kernel API to get something + working. More work is necessary to cover other aspects of the Linux + kernel API, e.g. memory mapping, PCI bus access, and the network + stack API, so we can extend support to other families of + peripherals.</p> + </body> + + <help> + <task>Implement more subsystems (e.g. the network interface API; + the memory management/pci bus access API).</task> + + <task>Address licensing issues. In the current port, the C code is + entirely new and under a FreeBSD license. Many of the headers have + been rewritten (and documented) from scratch (and so under a + FreeBSD license as well). Some of the other headers are still taken + from various Linux distributions and need to be rewritten to + generate BSD-licensed code that can be imported in the kernel + instead of being made available as a port. While this is not a + concern with GNU drivers, it may be an important feature for + drivers that are available under a dual license.</task> + </help> + </project> + + <project cat='kern'> + <title>Update of the Linux compatibility environment in the + kernel</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Leidinger</common> + </name> + + <email>netchild@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Roman</given> + + <common>Divacky</common> + </name> + + <email>rdivacky@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Emulation</given> + + <common>Mailinglist</common> + </name> + + <email>emulation@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/linux-kernel">Wiki page about + the linux compatibility environment.</url> + + <url href="http://wiki.FreeBSD.org/linux-kernel/ltp">Wiki page + about the linux test project testsuite success reports.</url> + </links> + + <body> + <p>Since the last status report AMD64 was feature synced with i386. + Notably TLS and futexes are now available on AMD64. Many thanks to + Jung-Uk Kim for doing the TLS work.</p> + + <p>Currently the focus is to implement the *at() family of linux + syscalls and to find and fix the remaining futex problems.</p> + + <p>We need some more testers and bug reporters. So if you have a + little bit of time and a favorite linux application, please play + around with it on -CURRENT. If there is a problem, have a look at + the Wiki if we already know about it and report on emulation@. We + are specially interested in reports about the 2.6 compatibility + (sysctl compat.linux.osversion=2.6.16), but only with the most + recent -current and maybe with some patches we have in the perforce + repository (available from the wiki).</p> + + <p>We would like to thank all the people which tested the changes / + submitted patches and thus helped improve the linux compatibility + environment.</p> + </body> + </project> + + <project cat='bin'> + <title>malloc(3)</title> + + <contact> + <person> + <name> + <given>Jason</given> + + <common>Evans</common> + </name> + + <email>jasone@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://lists.freebsd.org/pipermail/freebsd-current/2007-March/070303.html"> + malloc(3) (hopefully) set for 7.0</url> + </links> + + <body> + <p>malloc(3) has recently been enhanced to reduce memory overhead, + fragmentation, and mapped memory retention. As an added bonus, it + tends to be a bit faster. See the above URL for my email to the + -current mailing list for a more detailed description of the + enhancements.</p> + </body> + </project> + + <project cat='net'> + <title>Multi-link PPP daemon (MPD)</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Motin</common> + </name> + + <email>mav@alkar.net</email> + </person> + </contact> + + <links> + <url href="http://sourceforge.net/projects/mpd/">Project home</url> + + <url href="http://mpd.sourceforge.net/doc/mpd5.html"> + ChangeLog</url> + </links> + + <body> + <p>Stable release 4.1 of mpd4 branch was released in February + providing many new features and fixes. Mpd3 branch was declared + legacy.</p> + + <p>Since the release several new features have been implemented in + CVS:</p> + + <ul> + <li>Link repeater functionality (aka L2TP/PPTP Access + Concentrator),</li> + + <li>Per-interface traffic filtering using ng_bpf,</li> + + <li>Very fast traffic shaping/rate-limiting using ng_car.</li> + </ul> + + <p>ng_car node has been updated, to support shaping and very fast + Cisco-like rate-limiting. ng_ppp node has been completely + re-factored to confirm to the protocol stack model.</p> + </body> + + <help> + <task>LAC/PAC testing.</task> + + <task>Traffic filtering/shaping/rate-limiting testing.</task> + + <task>PPTP modification for multiple bindings support.</task> + + <task>Dynamic link/bundle creation.</task> + </help> + </project> + + <project cat='ports'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/ports/">The FreeBSD Ports + Collection</url> + + <url + href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"> + Contributing to the FreeBSD Ports Collection</url> + + <url href="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD + ports unfetchable distfile survey (Bill Fenner's report)</url> + + <url href="http://portsmon.FreeBSD.org/index.html">FreeBSD ports + monitoring system</url> + + <url href="http://www.freebsd.org/portmgr/index.html">The FreeBSD + Ports Management Team</url> + + <url href="http://tinderbox.marcuscom.com">marcuscom + tinderbox</url> + </links> + + <body> + <p>The ports count is nearing 17,000. The PR count has been stable + at around 700. The 'new port' PR backlog is at a multi-year low. We + appreciate all the hard work of our ports committers.</p> + + <p>Since the long 6.2 release cycle ended, portmgr has once again + been able to do experimental ports runs. As a result of six + run/commit cycles, the portmgr PR count is now the lowest in quite + some time. Please see the CHANGES and UPDATING files for details. + Many thanks to Pav among others for keeping the build cluster + busy.</p> + + <p>We have received new hardware, resulting in a significant + speedup of our package building capability: the AMD64 package + builds now use 4 8-core machines (and one lonely UP system), which + means a full AMD64 build is about 5 times faster than it was. Also, + the i386 cluster gained an 8-core and roughly doubled its + performance too. Two of the sparc64 build machines have recently + brought back online, so package builds there have been restarted + there after a long period offline.</p> + + <p>linimon continues to work on improvements to portsmon to allow + graphing of the dependent ports of ignored/failed ports. This work + will be presented at BSDCan. In addition, pages that show the state + of port uploads on ftp*.FreeBSD.org have been added, as well as + ports that have NO_PACKAGE set. Also, the individual port overview + page now shows the latest package that has been uploaded to the ftp + servers for each buildenv.</p> + + <p>A number of absent maintainers have been replaced by some new + volunteers who had been sending PRs to update and/or fix their + ports. Welcome! This helps to spread the workload.</p> + + <p>Since the last report, support for FreeBSD 4.X has been dropped + from the Ports Collection. Anyone still using RELENG_4 should have + stayed with the ports infrastructure as of the RELEASE_4_EOL tag, as + later commits remove that support. 4.X served us long and well but + the burden of trying to support 4 major branches finally became too + much to ask of our volunteers. Use of 4.X, even with the + RELEASE_4_EOL tag, is no longer recommended; we recommend either + 6.2-RELEASE or RELENG_6, depending on your needs.</p> + + <p>There have been new releases of the ports tinderbox code, the + portmaster update utility, and portupgrade. A new utility, + pkgupgrade, has been introduced by Michel Talon, which appears + interesting.</p> + + <p>KDE was updated to 3.5.6.</p> + + <p>GNOME was updated to 2.18.</p> + + <p>XFree86 version 3 was removed as being years out of date.</p> + + <p>We have added 3 new committers since the last report.</p> + </body> + + <help> + <task>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.</task> + + <task>Although we have added many maintainers, we still have many + unmaintained ports. The number of buildable packages on AMD64 lags + behind a bit; sparc64 requires even more work.</task> + </help> + </project> + + <project cat='team'> + <title>Release Engineering</title> + + <contact> + <person> + <name> + <given>Release Engineering Team</given> + </name> + + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/" /> + + <url href="http://www.FreeBSD.org/snapshots/" /> + </links> + + <body> + <p>During the past quarter, the Release Engineering team has begun + planning and preparing for FreeBSD 7.0, which is scheduled for + release later in 2007. The HEAD codeline has been placed in a + "slush" mode, meaning that large changes should be coordinated with + the Release Engineering team before being committed.</p> + + <p>The RE team also produced snapshots of FreeBSD 6.2-STABLE and + 7.0-CURRENT for February and March 2007, corresponding roughly to + the state of those development branches at the start of the + respective months. While they have not had the benefit of extensive + testing, and should not be used in production, they can be useful + for experimenting with or testing new features.</p> + </body> + </project> + + <project cat='team'> + <title>FreeBSD Security Officer and Security Team</title> + + <contact> + <person> + <name> + <given>Security</given> + + <common>Officer</common> + </name> + + <email>security-officer@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Security</given> + + <common>Team</common> + </name> + + <email>security-team@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/security/" /> + + <url + href="http://www.freebsd.org/administration.html#t-secteam" /> + + <url href="http://vuxml.freebsd.org/" /> + </links> + + <body> + <p>In the time since the last status report, one security advisory + has been issued concerning a problem in the base system of FreeBSD; + this problem was in "contributed" code maintained outside of + FreeBSD. In addition, several Errata Notices have been issued in + collaboration with the release engineering team, including one + concerning FreeBSD Update. The Vulnerabilities and Exposures Markup + Language (VuXML) document has continued to be updated by the + Security Team and Ports Committers documenting new vulnerabilities + in the FreeBSD Ports Collection; since the last status report, 21 + new entries have been added, bringing the total up to 890.</p> + + <p>The following FreeBSD releases are supported by the FreeBSD + Security Team: FreeBSD 5.5, FreeBSD 6.1, and FreeBSD 6.2. Of + particular note, FreeBSD 4.11 and FreeBSD 6.0 are no longer + supported. The respective End of Life dates of supported releases + are listed on the web site.</p> + </body> + </project> + + <project cat='proj'> + <title>SMP Scalability</title> + + <contact> + <person> + <name> + <given>Kris</given> + + <common>Kennaway</common> + </name> + + <email>kris@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Jeff</given> + + <common>Roberson</common> + </name> + + <email>jeff@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Attilio</given> + + <common>Rao</common> + </name> + + <email>attilio@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~kris/scaling/mysql.html"> + MySQL scaling</url> + + <url href="http://wiki.freebsd.org/SMPTODO">Remaining Giant-locked + code</url> + </links> + + <body> + <p>Over the past few months there has been a substantially + increased focus on improving scalability of FreeBSD on large SMP + hardware. This has been driven in part by the new availability of + 8-core hardware to the project, which allows easy profiling of + scalability bottlenecks and benchmarking of proposed changes. + Significant progress has been made on certain application workloads + such as MySQL and PostgreSQL, with the result that FreeBSD 7 now + has excellent scaling to at least 8-CPU systems with prospects for + further improvements. Progress with other application workloads has + been limited by the need to set up a suitable test case; please + contact me if you are interested in helping. As part of this + general effort, work is progressing steadily on removing the last + remaining Giant-locked code from the kernel. A complete list of + remaining Giant-locked code is found here: + <a href="http://wiki.freebsd.org/SMPTODO"> + http://wiki.freebsd.org/SMPTODO</a> + + Many of these sub-tasks have owners, but some do not. The major + remaining Giant-locked subsystem with no owner is the TTY + subsystem. In parallel, profiling of contention and bottlenecks in + other subsystems has lead to a number of experimental changes which + are being developed. Work is in progress by Jeff Roberson and + Attilio Rao to break up the global scheduler spinlock in favor of a + set of per-CPU scheduling locks, which is expected to improve + performance on systems with many CPUs. Experimental changes by + Robert Watson to allow for multiple netisr threads show good + promise for improving loopback IP performance on large SMP systems, + which can otherwise easily saturate a single netisr thread. A + variety of other changes are being profiled and evaluated to + improve SMP performance under various workloads. The majority of + these changes are collected in the //depot/user/kris/contention/ + Perforce branch.</p> + </body> + </project> + + <project cat='net'> + <title>Importing trunk(4) from OpenBSD</title> + + <contact> + <person> + <name> + <given>Andrew</given> + + <common>Thompson</common> + </name> + + <email>thompsa@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://people.freebsd.org/~thompsa/if_trunk-20070402.diff" /> + </links> + + <body> + <p>Work has completed to port over trunk(4) from OpenBSD and this + also includes merging 802.3ad LACP from agr(4) in NetBSD. This + driver allows aggregation of multiple network interfaces as one + virtual interface using a number of different + protocols/algorithms.</p> + + <ul> + <li>failover - Sends traffic through the secondary port if the + master becomes inactive.</li> + + <li>fec - Supports Cisco Fast EtherChannel.</li> + + <li>lacp - Supports the IEEE 802.3ad Link Aggregation Control + Protocol (LACP) and the Marker Protocol.</li> + + <li>loadbalance - Static loadbalancing using an outgoing + hash.</li> + + <li>roundrobin - Distributes outgoing traffic using a round-robin + scheduler through all active ports.</li> + </ul> + + <p>This will be committed shortly, further testing is welcome.</p> + </body> + </project> + + <project cat='proj'> + <title>USB</title> + + <contact> + <person> + <name> + <given>Hans Petter</given> + + <common>Sirevaag Selasky</common> + </name> + + <email>hselasky@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&HIDEDEL=NO"> + Current USB files</url> + + <url href="http://www.turbocat.net/~hselasky/usb4bsd">My USB + Homepage</url> + + <url + href="http://www.turbocat.net/~hselasky/usb4bsd/dev_new_usb.pdf"> + Code reference for the new USB stack and USB device drivers</url> + </links> + + <body> + <p>During the last three months not too much has changed. Here is a + quick list of changes:</p> + + <ol> + <li>There has been some cleanups in the UCOM layer, generally to + to create a context for all the callbacks so that they can call + sleeping functions. This is achieved using the USB config thread + system. The reason for this is that the code becomes simpler when + synchronous operation is applied versus asynchronous. But + asynchronous behavior is the most secure, hence then all USB + resources are preallocated for each transfer. After the change, + only data transfers are done asynchronously. All configuration is + now done synchronously. This makes the USB device drivers look + more like in the old USB stack.</li> + + <li>moscom.c has been imported from OpenBSD. It is called + umoscom.c under FreeBSD.</li> + + <li>ugensa.c has been imported from NetBSD.</li> + + <li>f_axe.c has now has support for Ax88178 and Ax88772, which is + derived from OpenBSD.</li> + </ol> + + <p>In my last status report I asked for access to Sparc64 boxes + with FreeBSD installed. Testing is ongoing and some problems remain + with EHCI PCI Cards. I am not exactly sure where the problem is, + but it appears that DMA-able memory does not get synced + properly.</p> + + <p>Markus Brueffer is still working on the USB HID parser and + support. Nothing has been committed yet.</p> + + <p>Several people have reported success with my new USB stack. Some + claim 2x improvements, others have seen more. But don't expect too + much.</p> + + <p>If you want to test the new USB stack, checkout the USB perforce + tree or download the SVN version of the USB driver from my USB + homepage. At the moment the tarballs are a little out of date.</p> + + <p>Ideas and comments with regard to the new USB API are welcome at + freebsd-usb@freebsd.org .</p> + </body> + </project> + + <project cat='net'> + <title>Intel 3945ABG Wireless LAN Driver: wpi</title> + + <contact> + <person> + <name> + <given>Benjamin</given> + + <common>Close</common> + </name> + + <email>benjsc@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/benjsc/wpi" /> + + <url href="http://www.clearchain.com/wiki/Wpi" /> + </links> + + <body> + <p>Work is slowly continuing on this driver, focusing mainly on + dealing with the newly released firmware for the card. The old + firmware was not redistributable, the new firmware can be + redistributed but has a completely different API. With the new + firmware changes almost complete, the driver is approaching a state + ready for -CURRENT.</p> + </body> + + <help> + <task>Fix mbuf leakage (potential fix pending).</task> + + <task>Integrate s/w control of radio transmitter.</task> + </help> + </project> + + <project cat='ports'> + <title>X.Org 7.2 integration</title> + + <contact> + <person> + <name> + <given>Florent</given> + + <common>Thoumie</common> + </name> + + <email>flz@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Dejan</given> + + <common>Lesjak</common> + </name> + + <email>lesi@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Kris</given> + + <common>Kennaway</common> + </name> + + <email>kris@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/ModularXorg" /> + </links> + + <body> + <p>X.Org 7.2 is now on final approach for landing into the ports + tree. Work had proceeded at a slow pace for the first few months of + the year due to reduced availability of flz@, the single developer + working on integration. Recently lesi@ was recruited back into the + task and readiness of the ports collection was pushed to completion + (i.e. there are no major regressions apparent on package builds). + The remaining tasks which need to be completed are a review of the + diff to make sure no unintentional changes or regressions slip in + to the CVS tree in the big merge, and completion of an upgrade + script to manage the migration from X.Org 6.9 (X.Org 7.2 is so + fundamentally different that it cannot be upgraded "automatically" + using the existing tools like portupgrade). We hope to have these + finished within a week or two, at which stage the ports collection + will be frozen for the integration, and we will likely remain in a + ``mini-freeze'' for a week or two in order to focus committer + attention on resolving the inevitable undetected problems which + will emerge from this major change.</p> + </body> + </project> + + <project cat='proj'> + <title>FreeBSD and ZFS</title> + +<!-- Required section --> + <contact> + <person> + <name> + <given>Pawel Jakub</given> + + <common>Dawidek</common> + </name> + + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs"> + Source code.</url> + + <url href="http://www.opensolaris.org/os/community/zfs/"> + OpenSolaris ZFS site.</url> + + <url + href="http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070544.html"> + ZFS commit announce.</url> + + <url + href="http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070616.html"> + ZFS - Quick Start.</url> + </links> + + <body> + <p>The ZFS file system in now part of the FreeBSD operating system. + ZFS was ported from the OpenSolaris operating system and is under + CDDL license. As an experimental feature ZFS will be available in + FreeBSD 7.0-RELEASE.</p> + </body> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2007-04-2007-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2007-04-2007-06.xml new file mode 100644 index 0000000000..2caa2c4df9 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2007-04-2007-06.xml @@ -0,0 +1,2796 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for +Status Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2007-04-2007-06.xml,v 1.4 2008/08/16 21:55:59 pgj Exp $ --> +<report> + <date> + <month>April-June</month> + + <year>2007</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report covers FreeBSD related projects between April and + June 2007. Again an exciting quarter for FreeBSD. In May we saw one + of the biggest developers summits to date at + <a href="http://www.bsdcan.org/2007/">BSDCan</a> + + , our 25 Google Summer of Code students started working on + <a href="http://www.freebsd.org/projects/summerofcode-2007.html"> + their projects</a> + + - progress reports are available below, and finally the 7.0 release + cycle was started three weeks ago.</p> + + <p>If your are curious about what's new in FreeBSD 7.0 we suggest + reading Ivan Voras' excellent summary at: + <a href="http://ivoras.sharanet.org/freebsd/freebsd7.html"> + http://ivoras.sharanet.org/freebsd/freebsd7.html</a> + + and of course these reports.</p> + + <p>The next gathering of the BSD community will be at + <a href="http://2007.eurobsdcon.org/">EuroBSDCon in Copenhagen</a> + + , September 14-15. More details about the conference and the + developer summit are available in the respective reports below.</p> + + <p>Thanks to all the reporters for the excellent work! We hope you + enjoy reading.</p> + </section> + + <category> + <name>soc</name> + + <description>Google summer of code</description> + </category> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>team</name> + + <description>FreeBSD Team Reports</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>net</name> + + <description>Network Infrastructure</description> + </category> + + <category> + <name>vendor</name> + + <description>Vendor / 3rd Party Software</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='net'> + <title>Multi-link PPP daemon (MPD)</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Motin</common> + </name> + + <email>mav@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://sourceforge.net/projects/mpd/">Project + home</url> + + <url href="http://mpd.sourceforge.net/doc/mpd5.html"> + ChangeLog</url> + </links> + + <body> + <p>Mpd-4.2 has been released. It includes many new features, + performance improvements and fixes.</p> + + <p>The most significant and unique new feature is a link repeater + functionality. It allows mpd to accept incoming connection of any + supported type and forward it out as same or different type + outgoing connection. As example, this functionality allows mpd to + implement real LAC with accepting incoming PPPoE connection from + client and forwarding it using L2TP tunnel to LNS. All other + software L2TP implementations I know is only a LAC emulators + without real incoming calls forwarding abilities.</p> + + <p>Also mpd-4.2 presents:</p> + + <ul> + <li>PPTP listening on multiple different IPs,</li> + + <li>L2TP tunnel authentication with shared secret,</li> + + <li>fast traffic filtering, shaping and rate-limiting using + ng_bpf and ng_car,</li> + + <li>new 'ext-auth' auth backend as full-featured local + alternative to 'radius-auth',</li> + + <li>NetFlow generation for both incoming and outgoing packets + same time.</li> + </ul> + + <p>Replacing external ifconfig and route calls with their + internal implementations and other optimizations in 4.2 gave + significant performance boost in session management. Newly + implemented overload protection mechanism partially drops + incoming connection requests for periods of critical load by + monitoring daemon's internal message queue. As result, simple + 2GHz P4 system is now able to accept, authenticate and completely + process spike of 1000 concurrent PPPoE connections in just a 30 + seconds.</p> + </body> + + <help> + <task>Implement dynamic link/bundle creation.</task> + + <task>Auth proxying support in repeater mode. It is required for + some LAC/PAC and Tunnel Switching Aggregator (TSA) setups.</task> + + <task>Remove static phys - link - bundle and phys - repeater + relations. Implement ability to differentiate incoming + connections processing depending on user login, domain and/or + other parameters.</task> + </help> + </project> + + <project cat='soc'> + <title>Distributed Logging Daemon</title> + + <contact> + <person> + <name> + <given>Alexey</given> + + <common>Mikhailov</common> + </name> + + <email>karma@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Bjoern</given> + + <common>Zeeb</common> + </name> + + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://docs.freebsd.org/cgi/getmsg.cgi?fetch=232192+0+/usr/local/www/db/text/2007/freebsd-hackers/20070527.freebsd-hackers"> + Description of the project design</url> + + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/karma%5faudit/dlog&HIDEDEL=NO"> + Perforce repository for project hosting</url> + </links> + + <body> + <p>The basic idea behind this project is to implement secure and + reliable log file shipping to remote hosts. While the + implementation focuses on audit logs, the goal is to build tools + that will make it possible to perform distributed logging for any + application by using a simple API and linking with a shared + library.</p> + </body> + + <help> + <task>Network protocol implementation</task> + + <task>Spooling</task> + + <task>SSL support</task> + </help> + </project> + + <project cat='soc'> + <title>Porting OpenBSD's sysctl Hardware Sensors Framework to + FreeBSD</title> + + <contact> + <person> + <name> + <given>Constantine A.</given> + + <common>Murenin</common> + </name> + + <email>cnst@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Shteryana</given> + + <common>Shopova</common> + </name> + + <email>syrinx@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://mojo.ru/us/GSoC2007.FreeBSD.cnst-sensors.proposal.html"> + Port OpenBSD's sysctl hw.sensors framework to FreeBSD, original + proposal for GSoC2007</url> + + <url href="http://cnst.livejournal.com/tag/GSoC2007">cnst's + GSoC2007 blog</url> + + <url href="http://cnst.livejournal.com/data/atom?tag=GSoC2007"> + cnst's GSoC2007 atom feed</url> + + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/cnst-sensors/"> + cnst-sensors in soc2007 in perforce</url> + </links> + + <body> + <p>OpenBSD includes sysctl hw.sensors framework since 2003; since + 2005 the frameworks supports raid drives and most known i2c + sensors; since 2006 the framework is redesigned with a sensor + device concept in mind to accommodate continued growth. Consists + of kernel api, sysctl(3)/sysctl(8), sensorsd(8), ntpd(8), + systat(1), ports/sysutils/symon and 51 drivers as of + 2007-07-07.</p> + + <p>This GSoC2007 project is to port the underpinnings of this + unified hardware monitoring interface to FreeBSD. Whilst it won't + be possible to port all of the drivers due to architecture + differences, we aim at porting all other parts of the framework + and accompanying userland utilities.</p> + + <p>At this time, lm(4) at isa and some kernel api have already + been ported. The next big step is to complete sysctl(3) glue code + so that further work on porting userland utilities could be + accomplished. Details about sysctl are being discussed on + arch@.</p> + </body> + + <help> + <task>sysctl(3) glue code</task> + </help> + </project> + + <project cat='soc'> + <title>Porting Linux KVM to FreeBSD</title> + + <contact> + <person> + <name> + <given>Fabio</given> + + <common>Checconi</common> + </name> + + <email>fabio@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Luigi</given> + + <common>Rizzo</common> + </name> + + <email>luigi@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://wiki.freebsd.org/FabioChecconi/PortingLinuxKVMToFreeBSD" /> + </links> + + <body> + <p>The Linux kernel-based Virtual Machine (KVM) is a mechanism to + exploit the virtualization extensions present in some modern CPUs + (e.g., Intel VT and AMD-V). Virtualization extensions let + ordinary processes execute a subset of privileged instructions in + a controlled way at near-native speed. This in turn may improve + the performance of system emulators such as qemu, xen, vmware, + vkernel, User Mode Linux (UML), etc.</p> + + <p>This project consists in porting to FreeBSD the Linux KVM, + implemented as a loadable module, lkvm.ko. We use the approach in + ports/devel/linux-kmod-compat to reuse the original Linux source + code almost unmodified. We will also port a modified version of + qemu which exploits the facilities made available by the Linux + KVM to speed up emulation.</p> + + <p>The URL above links to progress report detailing the exact + project goals, milestones reached, and commit log details.</p> + + <p>As of end of June 2007, we have mainly extended + linux-kmod-compat to support the kernel API used by the Linux KVM + code. The required functions have been implemented at various + degrees, from simple stubs to fully functional ones. We have also + imported the modified qemu and the libraries that are used to + build the Linux KVM userspace client. In the second half of the + SoC work we plan to complete the implementation of the kernel API + and have a fully functional Linux KVM module, together with its + client (qemu).</p> + </body> + </project> + + <project cat='soc'> + <title>Multicast DNS and Service Discovery</title> + + <contact> + <person> + <name> + <given>Fredrik</given> + + <common>Lindberg</common> + </name> + + <email>fli@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/MulticastDNS" /> + </links> + + <body> + <p>This project aims to create a multicast DNS daemon and service + discovery utilities suitable for the base system. Multicast DNS + is a part of Zero Configuration Networking (Zeroconf) and + provides the ability to address hosts using DNS-like names + without the need of an existing (unicast), managed DNS server. + Work on the responder daemon is well underway and the only large + missing piece of the puzzle is a way for local clients to do + queries. The code can be found in the p4 branch + projects/soc2007/fli-mdns_sd if anyone would like to give it a + spin, even though it's incomplete. The project plan can be found + on the wiki.</p> + </body> + </project> + + <project cat="soc"> + <title>FreeBSD-update front end</title> + + <contact> + <person> + <name> + <given>Andrew</given> + + <common>Turner</common> + </name> + + <email>andrew@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/FreeBSDUpdateFrontend"> + </url> + </links> + + <body> + <p>The project is split up with a front end to interact with the + user and a back end to interact with freebsd-update. The back and + front ends are able to communicate with each other using an XML + protocol. The GUI is almost at the point it can take a command + from the user and send it to the back end. The back end is able + to detect when updates are ready.</p> + </body> + </project> + + <project cat='misc'> + <title>EuroBSDcon 2007</title> + + <contact> + <person> + <name> + <common>EuroBSDCon 2007 Organizing Committee</common> + </name> + + <email>info@EuroBSDCon.dk</email> + </person> + </contact> + + <links> + <url href="http://2007.EuroBSDCon.org/" /> + </links> + + <body> + <p>The sixth EuroBSDCon will take place at Symbion in Copenhagen, + Denmark on Friday the 14th and Saturday 15th of September + 2007.</p> + + <p>The programme is ready and online at the webpage. Registration + is open. Details about tutorials and Legoland trip are ready too. + + <br /> + + The keynote will be John Hartman: Real men's pipes</p> + + <p>If you share a room with friends at the hostel, then lodging + is really inexpensive, and the lounge has high speed Internet + access. Staying at the hostel is of course optional, and the area + has several hotels.</p> + + <p>KD85.com and O'Reilly will each have a booth at the + conference.</p> + + <p>We are still looking for more sponsors.</p> + + <p>A public IRC channel #eurobsdcon on EFnet has been created for + discussion and questions about the conference.</p> + </body> + </project> + + <project cat='vendor'> + <title>FreeSBIE</title> + + <contact> + <person> + <name> + <given>Matteo</given> + + <common>Riondato</common> + </name> + + <email>matteo@FreeBSD.org</email> + </person> + + <person> + <name> + <given>FreeSBIE</given> + + <common>Staff</common> + </name> + + <email>staff@freesbie.org</email> + </person> + + <person> + <name> + <given>FreeSBIE</given> + + <common>ML</common> + </name> + + <email>freesbie@gufi.org</email> + </person> + </contact> + + <links> + <url href="http://www.freesbie.org">FreeSBIE Website</url> + + <url href="http://liste.gufi.org/mailman/listinfo/freesbie"> + Freesbie ML Subscription</url> + </links> + + <body> + <p>After the success of FreeSBIE-2.0.1-RELEASE, development slew + down a bit, but we have a big task for the summer: enable unionfs + again and trying the new efficient memory filesystem, tmpfs.</p> + + <p>For all new ISO images we will be following RELENG_7, with the + hope to release a stable image once 7.0-RELEASE have been + released.</p> + </body> + + <help> + <task>Build and test an ISO image with + FreeSBIE+unionfs+tmpfs.</task> + </help> + </project> + + <project cat='soc'> + <title>Ports Collection infrastructure improvements</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Andrew</given> + + <common>Pantyukhin</common> + </name> + + <email>sat@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/G%C3%A1borSoC2007"> + Gábor's SoC 2007 wiki page</url> + </links> + + <body> + <p>Gábor Kövesdán is working on some + improvements for the Ports Collection infrastructure. This year, + he aimed to work on long-standing issues, which are tracked in + GNATS, but we have not had a volunteer for recently. With the + mentorship of Andrew Pantyukhin, he is also reimplementing the + DESTDIR support for Ports Collection in a more practical way. The + complete description and status of this project is available on + Gábor's SoC 2007 Wiki page.</p> + </body> + + <help> + <task>Please see the Wiki page for the current status.</task> + </help> + </project> + + <project cat='misc'> + <title>The Hungarian Documentation Project</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/hu/docproj/hungarian.html">Info + for volunteers</url> + + <url href="http://www.freebsd.org/hu/">Hungarian Webpages</url> + + <url + href="http://www.freebsd.org/doc/hu_HU.ISO8859-2/articles/linux-comparison/"> + Latest translation</url> + </links> + + <body> + <p>We have added one translated article since the last status + report about this project. The infrastructure is ready to support + localized articles and books as well, we just lack of human + resource. New volunteers are highly welcome! Please see the link + below and contact Gábor if you are interested.</p> + </body> + + <help> + <task>Translate more articles and books.</task> + </help> + </project> + + <project cat='soc'> + <title>tarfs: A tar File System</title> + + <contact> + <person> + <name> + <given>Eric</given> + + <common>Anderson</common> + </name> + + <email>anderson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.googlebit.com/doku.php?id=tarfs">TarFS + Wiki</url> + </links> + + <body> + <p>Tarfs is a simple tar file system implementation for + FreeBSD.</p> + + <p>The current goals are:</p> + + <ul> + <li>Support all standard read-only operations</li> + + <li>Support large tar files (several gb's)</li> + + <li>Use minimal memory</li> + + <li>Allow using tar file as a root file system</li> + + <li>Fast enough to actually use</li> + </ul> + + <p>Here's the current state of things:</p> + + <ul> + <li>Can mount most tar files</li> + + <li>Can do most operations (open,lookup,stat,readdir,etc)</li> + + <li>Supports large tar files (tested up to 2GB)</li> + + <li>Uses a relatively small amount of memory - proportional to + number of files/dirs</li> + </ul> + </body> + + <help> + <task>No `..' directory in root of mounted tar file system</task> + + <task>Locking issues regarding `..' in subdirs off root of + fs</task> + + <task>No block/char special device support. Needed?</task> + + <task>Needs a directory hashing method</task> + + <task>More testing needed.</task> + </help> + </project> + + <project cat='net'> + <title>FAST_IPSEC Upgrade</title> + + <contact> + <person> + <name> + <given>George</given> + + <common>Neville-Neil</common> + </name> + + <email>gnn@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Bjoern</given> + + <common>Zeeb</common> + </name> + + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>FAST_IPSEC has now replaced Kame IPsec as the IPsec stack in + HEAD. This will be part of the 7.0 release. The merge happened in + early July with George handling the kernel bits and Bjoern + handling user space.</p> + + <p>The kernel option IPSEC is now the ONLY option for IPsec + support in the FreeBSD kernel.</p> + </body> + + <help> + <task>Test test test!!!!</task> + </help> + </project> + + <project cat='proj'> + <title>USB</title> + + <contact> + <person> + <name> + <given>Hans Petter</given> + + <common>Sirevaag Selasky</common> + </name> + + <email>hselasky@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&HIDEDEL=NO"> + Current USB files</url> + + <url href="http://www.turbocat.net/~hselasky/usb4bsd">My USB + Homepage</url> + + <url + href="http://www.turbocat.net/~hselasky/usb4bsd/dev_new_usb.pdf"> + Code reference for the new USB stack and USB device drivers</url> + </links> + + <body> + <p>During the last three months there has been several changes to + the USB stack. Here is a quick list of the most important + changes:</p> + + <ol> + <li>FULL speed isochronous devices over HIGH speed USB Hubs are + now fully supported. Due to various reasons the maximum + isochronous bandwidth has been limited to 6MBit/s. This limit + is tunable.</li> + + <li>There is now full support for Linux USB device drivers + through a Linux USB API emulation layer.</li> + + <li>Various cleanups and fixes.</li> + </ol> + + <p>Markus Brueffer is still working on the USB HID parser and + support. Nothing has been committed yet.</p> + + <p>If you want to test the new USB stack, checkout the USB + perforce tree or download the SVN version of the USB driver from + my USB homepage. At the moment the tarballs are a little out of + date.</p> + + <p>Ideas and comments with regard to the new USB API are welcome + at freebsd-usb@FreeBSD.org .</p> + </body> + </project> + + <project cat='kern'> + <title>gvirstor</title> + + <contact> + <person> + <name> + <given>Ivan</given> + + <common>Voras</common> + </name> + + <email>ivoras@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/gvirstor" /> + </links> + + <body> + <p>Gvirstor is a GEOM class which provides virtual storage + capacity (something like virtual memory for storage devices). + It's ready to be committed to HEAD (the plan is for it to get + into 7.0-RELEASE).</p> + </body> + + <help> + <task>Any interested testers are welcome!</task> + </help> + </project> + + <project cat='soc'> + <title>finstall</title> + + <contact> + <person> + <name> + <given>Ivan</given> + + <common>Voras</common> + </name> + + <email>ivoras@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/finstall" /> + </links> + + <body> + <p>Project "finstall" aims to create a next-generation FreeBSD + installer that will make use of the newest features present in + the system. The project should yield something usable for + 7.0-RELEASE, but the intention is to keep it as a "second" + installer system during 7.x, alongside sysinstall. In any case, + sysinstall will be kept for architectures not supported by + finstall (e.g. all except i386 and amd64).</p> + </body> + + <help> + <task>The work is progressing well and on plan. There's a small + setback currently with X11 applications executing of a read-only + file system (at least that's the currently recognizable + symptom).</task> + + <task>Any interested testers are very much welcome!</task> + </help> + </project> + + <project cat='proj'> + <title>HDTV Drivers (ATSC)</title> + + <contact> + <person> + <name> + <given>John-Mark</given> + + <common>Gurney</common> + </name> + + <email>jmg@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fbktrau%2F...&ignore=GO%21"> + bktrau Perforce source repository</url> + + <url + href="http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fcxd%2F...&ignore=GO%21"> + cxd Perforce source repository</url> + </links> + + <body> + <p>This entry was previously the Bt878 Audio Driver (aka + FusionHDTV 5 Lite driver) announcement, but as work expanded + slightly, it's a bit more generic now.</p> + + <p>A few bugs in bktrau has been fixed since January. If you have + been running an earlier version, it is recommended to upgrade as + the driver could panic. The driver works with multiple cards in + the same machine (tested with two).</p> + + <p> + <b>FusionHDTV 5 Lite</b> + + -- Due to lack of documentation from DViCO and LG, I have copied + magic values from the Linux driver to get ATSC capturing + working.</p> + + <p> + <b>ATI HDTV Wonder</b> + + -- After years of trying to get into the ATI developer program, + they have finally suspended it, so no support from ATI. I have + started work on a driver, cxd, for the Conexant CX2388x based + cards. The ATI HDTV Wonder uses ATI's own demodulator, and I was + able to get it to tune, after cribbing from the Linux driver. + When capturing, I get some valid data, but not all the data. Due + to lack of support from ATI and linux-dvb the project has been + put on indefinite hold.</p> + + <p>If someone has another CX2388x based card, it shouldn't be too + hard to take the driver and get it working with a different + tuner.</p> + + <p>A Python module is available for both drivers/cards, along w/ + a sample capture application using it. The module is now known to + work well with threads so that tuning (expensive due to i2c + ioctl's) can happen in another thread without causing program + slow down. The module is working well with a custom PVR + backend.</p> + </body> + + <help> + <task>Provide support for NTSC and FM tuning.</task> + + <task>Add support for other cards and tuners that use the Bt878 + chip.</task> + + <task>Add support for other cards and tuners that use the CX2388x + chip.</task> + </help> + </project> + + <project cat='team'> + <title>Problem Report Database</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>bugmeister_at_FreeBSD_dot_org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/support.html#gnats">GNATS</url> + + <url href="http://people.freebsd.org/~bsd/prstats/">PR + statistics</url> + </links> + + <body> + <p>Gavin Atkinson has joined the bugbuster team via getting a + GNATS account on the FreeBSD cluster. He is following in the + footsteps of Matteo Riondato, who later graduated to a full src + commit bit. So far, he has helped close nearly 150 PRs, including + many that had become stale. Welcome!</p> + + <p>Our short-term goal is to try to identify bugs that we might + be easily able to fix before the 6.3/7.0 simultaneous release. So + far, great progress has been made on ata- and usb-related + PRs.</p> + + <p>The goal for the rest of this year is to generate more + developer interest in fixing bugs. To do this, we are, first, + trying to do more work on triaging PRs as they come in, to help + flag ones that seem to be valid problems (especially if they + include patches.) Secondly, we have started a new weekly periodic + posting to the freebsd-bugbusters@FreeBSD.org mailing list, which + is a short list of PRs that we feel are ready for committer + action. This posting is automatically generated from a text-file + list that we maintain.</p> + + <p>We are continuing to try to manage our community's + expectations of what we can do with the incoming PRs. In + particular, we are trying to discourage submissions of the form + "I cannot get the XYZ function to work". In practice, these PRs + are not worked on. Instead, we are now encouraging these postings + to go to one of the mailing lists such as freebsd-questions@, + freebsd-x11@, and so forth. The idea is to emphasize GNATS as a + "Problem Report" method, rather than a "general FreeBSD support" + method. I feel that, otherwise, we were creating a false + expectation.</p> + + <p>The overall PR count has dropped to below 5000, despite the + extra PRs still not cleared up from the ports freeze for the + xorg7.2 import. Significant progress has been made on the i386, + kern, and bin PRs, as well as PRs in the 'feedback' state. In + addition, Warner Losh has made progress on closing many of the + usb PRs.</p> + </body> + + <help> + <task>Please join us on the freebsd-bugbusters@ mailing list, or + on #freebsd-bugbusters on EFNet, to help us triage PRs as they + come in and also help us to work through the backlog, and help us + to try to create a bugbusting "community".</task> + </help> + </project> + + <project cat='team'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/ports/">The FreeBSD Ports + Collection</url> + + <url + href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"> + Contributing to the FreeBSD Ports Collection</url> + + <url href="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD + ports unfetchable distfile survey (Bill Fenner's report)</url> + + <url href="http://portsmon.FreeBSD.org/index.html">FreeBSD ports + monitoring system</url> + + <url href="http://www.freebsd.org/portmgr/index.html">The FreeBSD + Ports Management Team</url> + + <url href="http://tinderbox.marcuscom.com">marcuscom + tinderbox</url> + </links> + + <body> + <p>The ports count is over 17,300. The PR count has been stable + at around 800; we have not quite cleared up the backlog that + showed up during the freeze to import xorg7.2.</p> + + <p>There have been 4 experimental runs on the build cluster, most + notably resulting in some speedups for package registration. A + further experimental run to genericize autotools handling is in + progress.</p> + + <p>One of the most sweeping ports commits to happen in years was + the upgrade of xorg from 6.9 to 7.2. This involved a complete + rework of the internals of the port, as X.org itself has + effectively pushed the responsibility for packaging to the OSes + that incorporate it. The idea was to be able for them to update + individual code (such as video drivers) without having to reroll + the entire distribution. This commit caused us to have the + longest period of preparation work, and actual tree lockdown, + that I am aware of. The commit continues to be controversial, + partly due to the fact that none of our port upgrade tools was up + to the task of doing the upgrade without manual intervention.</p> + + <p>At the same time that xorg was upgraded, we moved the + installation directory from the obsolete /usr/X11R6 to our + default /usr/local. This further complicated the upgrade.</p> + + <p>There have been new releases of the ports tinderbox code, the + portmaster update utility, and portupgrade.</p> + + <p>GNOME was updated to 2.18.2.</p> + + <p>We have added 7 new committers since the last report. We + appreciate all the new help. However, a few committers have + turned in their commit bits for safekeeping, due to lack of + time.</p> + + <p>Unfortunately, Clement Laforet has also had to step down from + portmgr due to lack of time. We thank him for his help so + far.</p> + + <p>Erwin, Kris and Mark met up at BSDCan and reviewed all the + portmgr-owned PRs. A large number were closed, or suspended + pending more work from the submitter. After closing the PRs that + were committed after the -exp builds, the number of portmgr owned + PRs came down to an all time low of 48 from around 70. We hope to + make further progress during the rest of the year.</p> + </body> + + <help> + <task>gcc4.2 has been imported to the base for 7.0. + Unfortunately, this breaks a large number of ports. We need + committer and maintainer help to get these in good shape for the + release.</task> + + <task>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.</task> + + <task>Although we have added many maintainers, we still have many + unmaintained ports. The packages on amd64 are lagging behind a + bit; those on sparc64 require even more work.</task> + </help> + </project> + + <project cat='net'> + <title>Network Stack Virtualization</title> + + <contact> + <person> + <name> + <given>Marko</given> + + <common>Zec</common> + </name> + + <email>zec@fer.hr</email> + </person> + </contact> + + <links> + <url href="http://imunes.tel.fer.hr/virtnet/" /> + </links> + + <body> + <p>The network stack virtualization project aims at extending the + FreeBSD kernel to maintain multiple independent instances of + networking state. This will allow for complete networking + independence between jails on a system, including giving each + jail its own firewall, virtual network interfaces, rate limiting, + routing tables, and IPSEC configuration.</p> + + <p>I believe that the prototype, which is kept in sync with + FreeBSD -CURRENT, is now sufficiently stable for testing. It + virtualizes the basic INET and INET6 kernel structures and + subsystems, including IPFW and PF firewalls, and more. In the + next month I plan to have the IPSEC code fully virtualized, and + refine and document the management APIs. The short-term goal is + to deliver production-grade kernel support for virtualized + networking for FreeBSD 7.0-RELEASE (as a snap-in kernel + replacement), while continuing to keep the code in sync with + -CURRENT for possible merging at a later date.</p> + </body> + </project> + + <project cat='soc'> + <title>mtund - Magic Tunnel Daemon</title> + + <contact> + <person> + <name> + <given>Matus</given> + + <common>Harvan</common> + </name> + + <email>mharvan@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/SuperTunnelDaemon">mtund wiki + page</url> + </links> + + <body> + <p>IP can easily be tunneled over a plethora of network protocols + at various layers, such as IP, ICMP, UDP, TCP, DNS, HTTP, SSH. + While a direct connection may not always be possible due to a + firewall, the IP packets could be encapsulated as payload in + other protocols, which would get through. However, each such + encapsulation requires the setup of a different program and the + user has to manually probe different encapsulations to find out + which of them works in a given environment.</p> + + <p>mtund is a tunneling daemon using run-time loadable plugins + for the different encapsulations. It automagically selects the + best encapsulation in each environment and fails over to another + encapsulation in case the environment changes. There already is + running code available, capable of tunneling via TCP and UDP with + a working failover mechanism. As this is a Summer of Code + project, rapid changes and addition of new features can be + expected during the summer. Please see the wiki page for more + details and up-to-date information.</p> + + <p>Note that the project originally started under the name of + Super Tunnel Daemon, but was later renamed to mtund for Magic + Tunnel Daemon.</p> + </body> + + <help> + <task>I am always happy to hear from others trying out the code + and providing feedback, both positive and negative.</task> + </help> + </project> + + <project cat='kern'> + <title>Fine grain thread locking</title> + + <contact> + <person> + <name> + <given>Jeff</given> + + <common>Roberson</common> + </name> + + <email>jeff@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Attilio</given> + + <common>Rao</common> + </name> + + <email>attilio@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Kris</given> + + <common>Kennaway</common> + </name> + + <email>kris@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Over the past 6 months several developers undertook an effort + to replace the global scheduler lock with a finer-grain interface + modeled on the Solaris container lock approach. This + significantly reduces contention on higher-end multiprocessor + machines.</p> + + <p>This patch went into 7.0-CURRENT and has proven to be very + stable. The last remaining bugs are in rusage and effect only + process time accounting statistics.</p> + </body> + </project> + + <project cat='kern'> + <title>SCHED_SMP and SCHED_ULE</title> + + <contact> + <person> + <name> + <given>Jeff</given> + + <common>Roberson</common> + </name> + + <email>jeff@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://jeffr-tech.livejournal.com/">Benchmarks and + SCHED_SMP discussion.</url> + </links> + + <body> + <p>SCHED_SMP is a fork of the ULE scheduler which makes use of + the new fine grain scheduler locking in 7.0-CURRENT to + significantly improve SMP performance on some workloads. It has + improved and stronger affinity, smarter CPU load balancing, + structural improvements and many sysctl tunables. This can be + considered ULE 3.0. Discussions are ongoing as to whether this + will go into 7.0 as SCHED_SMP or as SCHED_ULE in 7.0 or 7.1.</p> + + <p>SCHED_ULE has had many bugfixes and performance improvements + over the 7.0 development cycle and should no longer be considered + unstable or experimental. On most workloads it significantly + outperforms SCHED_4BSD on SMP and even slightly outperforms it on + UP. There are some pathlogical workloads which exhibit as much as + a 5% performance penalty. Many thanks to Kris Kennaway and + current users for bug reports and performance testing.</p> + </body> + </project> + + <project cat='proj'> + <title>Kernel contention reduction using mysql</title> + + <contact> + <person> + <name> + <given>Jeff</given> + + <common>Roberson</common> + </name> + + <email>jeff@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://jeffr-tech.livejournal.com/">mysql benchmarks + and discussion.</url> + </links> + + <body> + <p>FreeBSD developers have been using mysql as a testbed to find + kernel contention hotspots in the kernel. As a result of this we + have seen a 5x performance improvement over 6.0 on 8way machines. + Recent changes include finer locking in fcntl(), removing Giant + from flock and fcntl F_SETLK. These changes will be available in + 7.0 and primarily improve write performance. Experimental changes + to select() have also been discussed on arch@ that solve + contention issues there however these will not be ready in the + 7.0 timeframe.</p> + </body> + </project> + + <project cat='vendor'> + <title>PC-BSD</title> + + <contact> + <person> + <name> + <given>Kris</given> + + <common>Moore</common> + </name> + + <email>kris@pcbsd.com</email> + </person> + </contact> + + <links> + <url href="http://www.pcbsd.org/">PC-BSD Homepage</url> + </links> + + <body> + <p>The last major updates are currently being made to PC-BSD 1.4, + which will include KDE 3.5.7, Beryl, Flash, Intel Wireless, + Nvidia Drivers and more! This release will also include new + utilities to make running PC-BSD on the desktop easier than ever, + including:</p> + + <ul> + <li>Network Manager with WIFI Support</li> + + <li>Add / Remove Components</li> + + <li>Firewall Manager for PF</li> + + <li>Xorg Display setup wizard</li> + </ul> + + <p>Once any final major issues are resolved, we will be issuing a + public beta of PC-BSD 1.4 to ensure compatibility across a + variety of platforms.</p> + </body> + </project> + + <project cat='misc'> + <title>EuroBSDCon 2007 Developer Summit</title> + + <contact> + <person> + <name> + <given>Poul-Henning</given> + + <common>Kamp</common> + </name> + + <email>phk@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/200709DevSummit" /> + </links> + + <body> + <p>The next developer summit will be different from the previous + ones.</p> + + <p>Very different.</p> + + <p>Gone are the auditorium style seating, beamers, endless + presentations and soggy sandwiches.</p> + + <p>Instead we head out to an old village school in the + beautiful Danish countryside, we hang around all over the place, + sleep in the old science room, cook our own food and hack the + living daylights out of anything we care for.</p> + + <p>September 17th and 18th, right after EuroBSDcon2007 in + Copenhagen. (Well, right after the optional trip to + legoland...)</p> + + <p>Be there!</p> + + <p>PS: Yes, it's not uncivilized, there is a full speed ADSL and + WLAN.</p> + </body> + </project> + + <project cat='soc'> + <title>http support for PXE</title> + + <contact> + <person> + <name> + <given>Alexey</given> + + <common>Tarasov</common> + </name> + + <email>taleks@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/taleks-pxe_http"> + Project repository.</url> + + <url href="http://wiki.freebsd.org/http_support_for_PXE">Project + related Wiki-page.</url> + </links> + + <body> + <p>Main goal of project is to introduce code working in PXE + preboot environment, able to download from web server via direct + connection or http proxy and prepare booting of FreeBSD + kernel.</p> + + <p>Already implemented, but haven't thoroughly tested: PXE + wrappers core code, ARP, ICMP echo request/reply, sockets code + similar to common sockets (UDP and TCP modules). On base of + sockets: simple DHCP client, DNS client.</p> + + <p>Currently working on http client, TCP testing, kernel booting + and documenting main concepts of project modules.</p> + </body> + + <help> + <task>Testing PXE API related code in different PXE + implementations.</task> + + <task>Testing of implemented protocols.</task> + </help> + </project> + + <project cat='team'> + <title>Release Engineering</title> + + <contact> + <person> + <name> + <given>Release Engineering Team</given> + </name> + + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/" /> + + <url href="http://www.FreeBSD.org/snapshots/" /> + </links> + + <body> + <p>Code freeze in preparation for FreeBSD 7.0 began on June 18th. + There are several large projects still being finished up as well + as some issues that resulted as "fallout" from the work done just + before the code freeze started (e.g. things resulting from the + GCC 4.2 import). A schedule for the 7.0 release has not been set + yet but the hope is that the first BETA build will be done near + the end of July with a "fairly normal" release cycle (a few BETA + builds followed by two or three RCs, each separated by around two + weeks).</p> + + <p>We are planning to release FreeBSD 6.3 around the same time as + FreeBSD 7.0 is released so the release schedule for that will be + set at the same point we set the release cycle for 7.0, hopefully + late in July.</p> + </body> + </project> + + <project cat='net'> + <title>10Gigabit Network Support</title> + + <contact> + <person> + <name> + <given>Kip</given> + + <common>Macy</common> + </name> + + <email>kmacy@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Andrew</given> + + <common>Gallatin</common> + </name> + + <email>gallatin@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Jack</given> + + <common>Vogel</common> + </name> + + <email>jfv@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Support was added for two more 10gigabit network drivers and + there were major advances on improving system performance over + 10g media.</p> + + <p>Kip Macy committed a new driver for the Chelsio adapters. The + cxgb driver supports all current 10g adapters, as well as the new + four-port gigabit model. The cxgb driver work was supported by + Chelsio.</p> + + <p>Drew Gallatin made significant improvements to the Myricom 10g + driver mxge. With these updates the driver does line rate + transfers with less system overhead.</p> + + <p>Neterion contributed the nxge driver to support all their + Xframe 10Gbe Server/Storage adapters. The initial driver import + was done by Sam Leffler; a switch over to vendor support will + happen soon.</p> + + <p>Jack Vogel is preparing a driver to support the latest Intel + 10g hardware devices. The new driver - ixgbe - will complement + the existing ixgb driver that supports older Intel 10g cards.</p> + + <p>Kip and Drew worked with other folks on performance analysis + and tuning. This work improved cpu affinity and reduced overhead + for managing network resources. Work is also underway to define a + common Large Receive Offlaod (LRO) infrastructure. LRO is + analogous to TSO on the receive side enabling drivers to receive + at near line rate with normal sized frames. This common code base + will help replace driver-specific code.</p> + </body> + </project> + + <project cat='soc'> + <title>A GUI audit analyzer for FreeBSD</title> + + <contact> + <person> + <name> + <given>Dongmei</given> + + <common>Liu</common> + </name> + + <email>ldm@ercist.iscas.ac.cn</email> + </person> + </contact> + + <links> + <url href=""> + </url> + </links> + + <body> + <p>This project is due to provide a GUI audit log analysis tool + for FreeBSD. Refer to ethereal/wireshark packet parsing engine + and its framework to view and parse audit logs.</p> + </body> + + <help> + <task>Get a GUI framework using GTK2.0 include menu bar, toolbar, + list view and tree view.</task> + + <task>Parse and display audit log in the trailer file in the list + view and tree view.</task> + + <task>Online capture audit log and parse and display them in the + list view and tree view</task> + + <task>Add the filter mechanism</task> + + <task>Add the statistic mechanism</task> + + <task>Remote audit log analysis mechanism</task> + </help> + </project> + + <project cat='soc'> + <title>BSD Bintools project</title> + + <contact> + <person> + <name> + <given>Kai</given> + + <common>Wang</common> + </name> + + <email>kaiw27@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/BSDBintools" /> + </links> + + <body> + <p>A basic implementation of ar(1) (include ranlib) was finished + and available in the perforce repository. Currently it provides + all the main functions an ar(1) should have and it is based on + the libarchive and libelf library thus is expected to have a + better and simpler structure than the GPL'ed version. The work + left in this part of the project is to perform a elaborate test + and add additional functions.</p> + </body> + </project> + + <project cat='proj'> + <title>Stack trace capture in PMCTools</title> + + <contact> + <person> + <name> + <given>Joseph</given> + + <common>Koshy</common> + </name> + + <email>jkoshy@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/PmcTools">PMCTools Wiki + page.</url> + </links> + + <body> + <p>The kernel/hwpmc(4) bits of stack trace capture have been + implemented and are available in Perforce under path + '//depot/user/jkoshy/projects/pmc/...'. I'm currently enhancing + pmcstat(8) to extract and summarize this information. Support by + Google Inc. for this project is thankfully acknowledged.</p> + </body> + </project> + + <project cat='soc'> + <title>Linuxulator update</title> + + <contact> + <person> + <name> + <given>Roman</given> + + <common>Divacky</common> + </name> + + <email>rdivacky@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Konstantin</given> + + <common>Belousov</common> + </name> + + <email>kib@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/linux-soc2007">Linuxulator + update 2007</url> + </links> + + <body> + <p>Just like last year I got the opportunity to work on updating + the Linuxulator to Linux version 2.6. This year I work on + finishing futexes, *at syscalls and epoll/inotify.</p> + + <p>I, cooperating with Konstantin Belousov, have managed to fix + futexes to the state of passing the official futex testing + program. The fix was committed and 7.0R will ship with correct + futex implementation. Work is planned on removing Giant locking + from futexes. This only needs some careful review and + testing.</p> + + <p>These days I mostly focus on *at syscalls, the patch is almost + finished for committing and I hope that it will make it into 7.0R. + As a part of this work I implemented native FreeBSD syscalls as + well. Watch arch mailing list as I post the patch there.</p> + + <p>I also finished writing my master thesis describing how the + Linuxulator works and Gábor Kövesdán is working + on integrating it into official FreeBSD articles.</p> + + <p>No work has happened in the epoll/inotify area but I hope to + work on it right after I finish the *at syscalls.h</p> + </body> + + <help> + <task>Finishing *at syscalls.</task> + + <task>Start the epoll/inotify work.</task> + + <task>Finish removal of Giant from futexes.</task> + </help> + </project> + + <project cat='soc'> + <title>Security Regression Test</title> + + <contact> + <person> + <name> + <given>Zhouyi</given> + + <common>Zhou</common> + </name> + + <email>zhouzhouyi@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/zhouzhouyi%5fmactest%5fsoc"> + Perforce Repository.</url> + </links> + + <body> + <p>Security Regression Test is supported by the project of Google + summer code 2007. The main objective of this stage is to test the + correctness of FreeBSD Mandatory Access Control Framework + including correctly passing the security label from userland to + kernel and non-bypassibility of Mandatory Access Control + Hooks.</p> + + <p>Work performed in the last month:</p> + + <ol> + <li>Constructed a pair of pseudo ethernet drivers used for + testing network related hooks. To avoid the packet go through + the lo interface, the IP address in the packet is twisted in + the driver.</li> + + <li>Constructed a framework for logging Mandatory Access + Control hooks which is got called during a period of time. + <ul> + <li>In kernel, every non-null label is got externalized into + human readable string and recorded in a tail queue together + with the name of hook that got called and possible flags or + modes (etc. VREAD/VWRITE for mac_check_vnode_open hook). + There is a thread much like audit subsystem's audit_worker + logging the queue into a userspace file. The userland program + use open, ioctl and close the /dev/mactest node to trigger + and stop the logging. The logging file is truncated to zero + every time the logging mechanism is triggered.</li> + + <li>In userland, a bison based parsing tool is used to parse + the logged file and reconstruct the record chain which will + be compared with testsuite supplied configuration file to + examine if expected hooks is got called and the + label/flags/modes are correct. c) The testsuite mainly + follows src/tools/regression/fstest, modified to adapt to + test Mandatory Access Control Framework and include tests for + signals</li> + </ul> + </li> + </ol> + </body> + + <help> + <task>The code is quick and dirty. For example, a call to vn_open + without checking its return value which is not fault tolerance. + The coding style also needs modifications.</task> + + <task>Although a test framework is completely constructed, the + detailed test cases still need to be written, the test cases + beside fstest and signal need to be add.</task> + + <task>Testing of audit subsystem has not begin.</task> + + <task>Other parts of Security Subsystem in FreeBSD also need + concern.</task> + </help> + </project> + + <project cat='proj'> + <title>TrustedBSD Audit</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Christian</given> + + <common>Peron</common> + </name> + + <email>csjp@FreeBSD.org</email> + </person> + + <person> + <email>trustedbsd-audit@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/audit.html">TrustedBSD Audit + Page</url> + </links> + + <body> + <p>General cleanups in preparation for 7.0.</p> + + <p>Process audit state moved to the credential to allow it to be + accessed lock-free in most cases, as well as allowing it to be + used in asynchronous contexts.</p> + + <p>OpenBSM 1.0a14 has been imported, which: fixes IPv6 endian + issues, makes OpenBSM gcc41 warnings clean, teaches + audit_submit(3) about getaudit_addr(), adds zonename tokens; + other changes since the existing CVS 1.0a12 release previously + imported include man page improvements, XML printing support, + better audit.log.5 documentation, additional 64-bit token types, + and new audit event identifiers.</p> + + <p>MAC checks have been added so that MAC policies can control + use of audit system calls.</p> + + <p>Additional system call arguments are now audited.</p> + + <p>Audit now provides a security.audit sysctl node in order to + determine if audit support is compiled in; boot-time console + printfs have been removed.</p> + + <p>"options AUDIT" is now in the 7-CURRENT GENERIC kernel, so + AUDIT support will be available out of the box in 7.0 without a + kernel recompile. Manually enabling audit support in rc.conf will + still be required. With FreeBSD 7.0, AUDIT will be a fully + supported, rather than experimental, feature.</p> + </body> + </project> + + <project cat='team'> + <title>The FreeBSD Foundation</title> + + <contact> + <person> + <name> + <given>Deb</given> + + <common>Goodkin</common> + </name> + + <email>deb@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsdfoundation.org">The FreeBSD + Foundation</url> + </links> + + <body> + <p>The FreeBSD Foundation ended Q2 raising over $116,000. We're + almost half way to our goal of raising $250,000 this year! We + continued our mission of supporting developer communication by + helping FreeBSD developers attend BSDCan. We were also a sponsor + of BSDCan and the developer summit. We are a sponsor of + EuroBSDCon 2007 and are now accepting travel grant applications + for this conference. Foundation board members met with + representatives of companies that use or are thinking of using + FreeBSD both in the bay area and Ottawa.</p> + + <p>The Foundation has negotiated a joint development agreement + with Google, Inc. to sponsor FreeBSD developer Joseph Koshy to + improve FreeBSD's HWPMC implementation, including adding + stacktrace support, and a donation of SMP hardware for future SMP + scalability work. We greatly appreciate Google's support for this + project, which will facilitate performance measurement and + optimization of both the FreeBSD operating system and + applications running on it.</p> + + <p>To learn more about what we're doing, go to our website at + <a href="http://www.freebsdfoundation.org/"> + http://www.FreeBSDFoundation.org/</a> + + . Our July newsletter will be published soon to update you on how + we've been supporting the project and community worldwide.</p> + </body> + </project> + + <project cat='proj'> + <title>TrustedBSD MAC Framework</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/mac.html">TrustedBSD MAC + Page</url> + </links> + + <body> + <p>Cleanup of MAC Framework API/KPI layers: mac.h is now just the + user and user<->kernel API; mac_framework.h is the + kernel<->MAC Framework KPI, and mac_policy.h is the MAC + Framework<->MAC policy module KPI. Along similar lines, + mac_label_get() and mac_label_set() accessor functions now allow + policies to access label data without encoding struct label + binary layout into policy modules, opening the door to more + efficient layouts. struct label is now in mac_internal.h and used + only inside the MAC Framework.</p> + + <p>General MAC policy cleanup, including removing no-op entry + points and sysctls for some sample policies. mac_test(4) has been + cleaned up significantly, and counters for all entry points + added.</p> + + <p>A MAC check for UNIX domain socket connect has been added.</p> + + <p>MAC checks have been added so that MAC policies can control + use of audit system calls.</p> + + <p>MAC checks that duplicate existing privileges but add no + additional context have been removed (such as sysarch_ioperm, + kld_unload, settime, and system_nfsd) -- checks aligned with + privileges but that do provide additional context, such as + additional arguments, have been kept.</p> + + <p>The Biba and LOMAC policies now implement priv(9) checks, + differentiating between privileges that may compromise system + integrity models, and those that don't.</p> + + <p>The essentially unused mnt_fslabel / mnt_label distinction has + been eliminated by moving to a single mnt_label. No functional + change to any policy.</p> + + <p>Several MAC-related interfaces have been modified to + synchronize with the naming conventions present in the version of + the MAC Framework adopted in Mac OS X Leopard; significant + further changes are in the pipeline to complete this + synchronization. While it will not be possible to reuse a policy + between the two platforms without careful thinking and + modification, this makes porting much easier.</p> + </body> + </project> + + <project cat='net'> + <title>Multiprocessor Network Stack</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <email>net@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/netperf/">Netperf + Project Page</url> + </links> + + <body> + <p>The custom file descriptor array lock has been replaced with + an optimized sx lock, resulting in 2x-4x improvement in MySQL + transaction rates on 8-core MySQL benchmarks. This improvement is + due to moving to shared locking for frequent fd lookup + operations, as well as significant optimization of the case where + the filedesc lock is highly contended (as occurs in the threaded + MySQL server performing constant socket I/O).</p> + + <p>The custom socket buffer I/O serialization lock (sblock), + previously created by interlocking SB_WANT and SB_LOCK flags with + the socket buffer mutex, has been replaced with an optimized sx + lock, leading to a 10% performance improvement in MySQL and + PostgreSQL benchmarks on 8-core systems. As part of this change, + sx locks now have interruptible sleep primitives to allow the + SB_NOINTR flag to work properly.</p> + + <p>These changes also correct a long-standing bug in socket + buffer lock contention and SB_NOWAIT reported by Isilon; a + simpler patch has been merged to 6.x to fix this bug without + merging loocking changes.</p> + + <p>TCP debugging is now properly synchronized using a new + tcp_debug_mtx.</p> + + <p>UMA allocation counters are now used for pipes rather than + custom atomic counters, resulting in lowered overhead for pipe + allocation and free.</p> + + <p>Significant code cleanup, commenting, and in some cases + MFC'ing, has taken place with respect to the network stack and + synchronization. Additional DDB debugging commands for sockets of + various sorts have been added, allowing listing of socket state + from DDB without the use of GDB.</p> + + <p>Certain non-MPSAFE subsystems have been removed or will be + removed from FreeBSD 7.0, including IPX over IP tunneling (not + general IPX/SPX support, just the tunneling over IP), KAME IPSEC + (FAST_IPSEC is MPSAFE and now now supports IPv6), i4b, netatm + (two other ATM stacks are still present), and ng_h4. Some of + these features will be reintroduced in FreeBSD 7.1, but by + removing them now, we are able to remove the NET_NEEDS_GIANT + compatibility infrastructure that significant complicates and + obfuscates the socket and network stack code.</p> + + <p>Other measurement and optimization projects continue; however, + the 7.0 locking/synchronization work for the network stack is + essentially complete.</p> + </body> + + <help> + <task>New work to parallelize the netisr thread (netisr2) as well + as distribute UDP and TCP processing over multiple CPUs by + connection, rather than just by input source as in 7.0, was + presented at BSDCan. This work will be targeted at the 8-CURRENT + branch.</task> + + <task>Complete netatm and NET_NEEDS_GIANT removal for 7.0.</task> + + <task>Complete MPSAFE locking of mld6 and nd6 IPv6 subsystems, + which currently run under a global lock.</task> + </help> + </project> + + <project cat='kern'> + <title>TrustedBSD priv(9)</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/">TrustedBSD Project</url> + </links> + + <body> + <p>Further reduction of suser(9) consumers in order to attempt to + remove the suser(9) KPI for 7.0. This includes resource limits, + System V IPC, PPP, netinet port reuse, the NFS server, and + netatalk. Remove unnecessary or redundant privilege checks were + possible. UFS-privileges that apply to other file systems have + been renamed to VFS privileges.</p> + + <p>All suser_cred() flags and priv_check_cred() flags are no + longer required, as SUSER_ALLOWJAIL and SUSER_RUID use are + determined entirely inside kern_jail.c and kern_priv.c and + selected based on the privilege number, not a calling context + flag. All privileges are now consistently allowed or not allowed + in jail, and consistently use the ruid or euid. We will leave the + flags field there as it will likely be used for other things in + the future.</p> + + <p>Documentation in suser(9) and priv(9) has been updated.</p> + </body> + </project> + + <project cat='soc'> + <title>Apple's MacBook on FreeBSD</title> + + <contact> + <person> + <name> + <given>Rui</given> + + <common>Paulo</common> + </name> + + <email>rpaulo@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://repoman.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/rpaulo%2dmacbook/"> + P4 repository</url> + + <url href="http://wiki.freebsd.org/AppleMacbook">wiki page</url> + </links> + + <body> + <p>Apple's MacBook computers are nicely designed and have neat + features that other laptops don't. While Mac OS X is a nice + operating system, UNIX folks (like me) would prefer to run other + operating systems like FreeBSD. This project aims to bring bug + fixes and new drivers to FreeBSD that would help running this OS + on this platform.</p> + </body> + + <help> + <task>Write drivers or fix issues for/with the touchpad, + keyboard, remote control IR receiver, Bluetooth.</task> + + <task>Fix reboot, halt, suspend/resume issues.</task> + </help> + </project> + + <project cat='team'> + <title>Security Officer and Security Team</title> + + <contact> + <person> + <name> + <given>Security</given> + + <common>Officer</common> + </name> + + <email>security-officer@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Security</given> + + <common>Team</common> + </name> + + <email>security-team@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/security/" /> + + <url + href="http://www.freebsd.org/administration.html#t-secteam" /> + + <url href="http://vuxml.freebsd.org/" /> + </links> + + <body> + <p>In the time since the last status report, two security + advisories have been issued concerning problems in the base + system of FreeBSD; both of these problems were in "contributed" + code maintained outside of FreeBSD. The FreeBSD Vulnerabilities + and Exposures Markup Language (VuXML) document has continued to + be updated; since the last status report, 35 new entries have + been added, bringing the total up to 925.</p> + + <p>In order to improve handling of security issues in the FreeBSD + Ports Collection a new "ports-security" team has been created to + include ports committers who periodically help with fixing ports + security issues and documenting them in the FreeBSD VuXML + document. Committers who wish to help with this effort can + contact simon@ for details.</p> + + <p>The following FreeBSD releases are supported by the FreeBSD + Security Team: FreeBSD 5.5, FreeBSD 6.1, and FreeBSD 6.2. The + respective End of Life dates of supported releases are listed on + the web site; it is expected that of the upcoming releases, + FreeBSD 6.3 will be supported for two years after release, while + FreeBSD 7.0 will be supported for one year after release.</p> + </body> + </project> + + <project cat='soc'> + <title>lockmgr rewriting</title> + + <contact> + <person> + <name> + <given>Attilio</given> + + <common>Rao</common> + </name> + + <email>attilio@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Jeff</given> + + <common>Roberson</common> + </name> + + <email>jeff@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/AttilioRao"> + http://wiki.freebsd.org/AttilioRao</url> + </links> + + <body> + <p>The project consists in a rewriting of the lockmgr(9) + interface on a lighter basis, using atomic instructions and + direct usage of the sleepqueue interface. This should lead to a + faster primitive, a saner interface and an higher maintainability + of the code.</p> + + <p>So far, 3 newly files called kern/kern_lockng.c, + sys/_lockmgrng.h and sys/lockmgrng.h have been created for the + new primitive and an initial implementation has been committed + into the perforce branch: + //depot/user/attilio/attilio_lockmgr/...</p> + + <p>The implementation contains a good set of code intended to + replace old lockmgr. Actually it only misses the support for lock + draining that will be committed after an initial phase of testing + and the inclusion of a better wake-up algorithm (which will + simplify draining a lot and will improve performance on + wakeup).</p> + </body> + + <help> + <task>Need some testing</task> + </help> + </project> + + <project cat='soc'> + <title>Gvinum improvements</title> + + <contact> + <person> + <name> + <given>Ulf</given> + + <common>Lilleengen</common> + </name> + + <email>lulf@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://folk.ntnu.no/lulf/patches/freebsd/gvinum/soc2007"> + Patches of my SoC wo</url> + + <url href="http://blogs.freebsdish.org/lulf/">Weblog</url> + + <url href="http://wiki.freebsd.org/UlfLilleengen/SOC"> + Wikipage</url> + </links> + + <body> + <p>My previous status reports contained a lot of code that + updated gvinum with the old vinum features.</p> + + <p>This year gvinum has been significantly rewritten. Lukas Ertl + began rewriting the way gvinum is organized from using a multi + consumer/provider model, to use a single consumer and provider, + and having an event-system that first handles user-requests, and + then runs normal I/O operations (Much like other GEOM classes). + This makes the code easier to read, and perhaps there will be + less bugs :)</p> + + <ol> + <li>setstate on plexes and volumes.</li> + + <li>attach/detach command now works.</li> + + <li>concat/stripe/mirror commands. The previous code conflicted + more than I expected with the new gvinum system, but it should + work now.</li> + + <li>(Mounted) rebuilds possible.</li> + + <li>(Mounted) sync possible.</li> + + <li>Some refactoring of old code (Basically updating old code + to use the new event system, and add some abstractions where + possible)</li> + </ol> + + <p>And of course, some time has gone to work out how things + should be done, and to fix other bugs. I hope some of you are + interested in trying this out (all the work has been in perforce + so far), a patch can be found in the URL section. . This is a bit + experimental, and although I've done much testing to hunt down + bugs, there are most probably bugs left.</p> + + <p>I have other goals this summer as well. However, since some + parts of gvinum was rewritten, I might not be able to do all of + these, but growing is already working for the concatenated + volumes (and also mirrored). I'd also like to implement growing + for Raid5 arrays as well. Logging plexes would also be cool to + have, but this is not really needed, since we have g_journal. + Both these features will be addressed after I've made sure gvinum + does all old vinum does, and also perhaps better. As I might have + some extra time on my hands this summer, so I gladly accept + suggestions on what else I might fix or implement "while I'm at + it".</p> + </body> + + <help> + <task>Stability, stability, stability. I want gvinum to work + really well. To accomplish that I have several test-machines I'm + going to do different tests on. I sort of have a little test-plan + in the working that I'll be using.</task> + + <task>A gvinumadmin tool that would make gvinum easier to use for + unexperienced users. Perhaps integrate this into the installer. + This is now probably something I'll do at the end, when hopefully + everything works :) I might poke Ivan Voras a bit on this.</task> + + <task>Documenting gvinum and it's differences to vinum better. I + take notes on where I need to document, so this is in + progress.</task> + + <task>Implementing growing and shrinking of volumes.</task> + + <task>Implement logging plexes. Log all parity data being + written.</task> + </help> + </project> + + <project cat='misc'> + <title>libarchive/bsdtar</title> + + <contact> + <person> + <name> + <given>Tim</given> + + <common>Kientzle</common> + </name> + + <email>kientzle@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Colin</given> + + <common>Percival</common> + </name> + + <email>cperciva@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~kientzle/libarchive/"> + Project page</url> + </links> + + <body> + <p>Both libarchive 2 and bsdtar 2 are now in -CURRENT and will be + in 7.0. Libarchive 1.9 and bsdtar 1.9 should be in 6-STABLE in + time for 6.3.</p> + + <p>libarchive 2 is much faster writing to disk than libarchive 1. + It also supports new formats, has several minor API/ABI + corrections, is more portable, and has many fewer bugs. Of + special note is "libarchive_test", a new program that exercises + much of the libarchive functionality; anyone interested in + working on libarchive should become familiar with this test + suite. bsdtar 2 is less ambitious, but does have a number of bug + fixes and takes advantage of several new features in libarchive + 2.</p> + + <p>libarchive 1.9 is identical to libarchive 2 except it + maintains the old API/ABI. Similarly, bsdtar 1.9 is nearly + identical to bsdtar 2, lacking only a few features that would + prevent it from being used with existing libarchive 1 + libraries.</p> + </body> + + <help> + <task>Tim Kientzle has started work on a libarchive-based cpio + implementation that should be ready for inclusion with FreeBSD + 8.</task> + + <task>Volunteer needed: We want a libarchive-based pax to replace + our out-of-date pax implementation.</task> + + <task>Volunteer needed: pkg_add should use libarchive instead of + forking an external tar; this could eventually make it much + faster.</task> + + <task>Volunteer(s) needed: libarchive should write more cpio + variants (easy); libarchive should read and write mtree format + (not difficult); libarchive should write GNUtar 1.0 format sparse + tar entries (tricky); bsdtar should support + --metadata=<archive> to read names and properties from one + archive, with data from disk, to create a new archive (mtree + support in libarchive would make this very useful); bsdtar should + preserve sparseness when creating archives.</task> + </help> + </project> + + <project cat='proj'> + <title>USB update</title> + + <contact> + <person> + <name> + <given>Warner</given> + + <common>Losh</common> + </name> + + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>About 18 months ago, I started to remove the compatibility + macros that we had in the USB stack. These macros made it very + hard to read the code and to diagnose problems. They represented + a barrier to entry for people reading and understanding the + stack. In addition, many of them effectively hid bugs from all + but the most intensive investigations of the code.</p> + + <p>I've removed almost all of the macros in the client drivers, + and all instances of the macros in the core FreeBSD USB stack. + This makes the drivers more readable, and a little more robust. + During this process, I fixed a lot of little bugs that people had + been tripping over, and some that people hadn't reported. I've + added a boatload of new vendor and product ids to the drivers + from user PRs as well as from OpenBSD/NetBSD drivers.</p> + + <p>I finished up this work so that the FreeBSD USB stack would be + more maintainable during the RELENG_7 period of time. I plan on + MFCing most of the changes I've made into RELENG_6 after they + have been shaken out in current. There was only one API changes + in this work, so this is doable, and makes sharing drivers + between 6.x and 7.x much easier. At this stage, it is unclear how + long RELENG_6 will be around, so I'm hoping this will make USB + much better in 6.3 if that's the release people choose to + run.</p> + + <p>I've shied away from many of the more complicated changes to + the stack. There's work being done outside of the tree by Hans + Petter Selasky (hps) to make these sorts of changes. There is + much in his stack that's ready to be merged, and I hope to + integrate from that work useful bits that can be merged without + disruption to improve the FreeBSD USB stack.</p> + + <p>I'm also looking for other FreeBSD developers that can jump in + and help. Nearly all of the improvements I've done by spending a + few hours a week sorting through the PRs for extremely low + hanging fruit. There's plenty of room for others to be involved + as well in improving FreeBSD's USB stack, as well as chances for + us to import the now-useful bits from the evolving hps USB stack, + hopefully reducing the diffs between it and the present FreeBSD + USB stack. In addition, I'm looking for someone to do similar + device ID merges from DragonFlyBSD.</p> + + <p>Finally, I've embarked on a mission to try to merge all the + BSD's usbdevs files. There's no reason to have separate ones. + I've started to modify usbdevs(1) to read the + src/sys/dev/usb/usbdevs file and report more verbose information + that way. A merged usbdevs would be larger, and take up more + memory in a USBVERBOSE kernel, so to mitigate that effect, I'm + making changes to usbdevs(1).</p> + </body> + + <help> + <task>The biggest area of concern before the 7.0 release is to + get the updated device lists into the manual pages. This task is + too big for me to take on in addition to the work I'm doing in + cleaning up.</task> + + <task>We need more people that are willing to help out on the + 'trivial' PRs that add IDs to the driver. In addition, we need + people to periodically sync our driver lists with DragonFlyBSD, + NetBSD, and OpenBSD drivers.</task> + + <task>Merging the other BSD's usbdevs tables would be very + helpful.</task> + + <task>Writing a usbdevs parser for usbdevs(1) to use.</task> + </help> + </project> + + <project cat='net'> + <title>Wireless Networking</title> + + <contact> + <person> + <name> + <given>Sam</given> + + <common>Leffler</common> + </name> + + <email>sam@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Andrew</given> + + <common>Thompson</common> + </name> + + <email>thompsa@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>A major update of the 802.11 wireless support was committed. + Changes include advanced station mode facilities such as + background scanning and roaming, and support for 802.11n devices. + In addition parts of the Atheros' SuperG protocol extensions were + added so that wireless clients that communicate with + Atheros-based access points can operate more effectively. The + changes to the infrastructure are also important because they + simplify future distribution of Virtual AP (VAP) support.</p> + + <p>This work represents the effort of many people including Kip + Macy, Andrew Thompson, Sepherosa Ziehau, Max Laier, and Kevin Lo. + Getting these changes into the tree now ensures they will be + present for the lifetime of the 7.x branch.</p> + + <p>The scanning and SuperG work were supported by Atheros. The + 802.11n-related work was supported by Marvell.</p> + </body> + + <help> + <task>Please test your wireless networking, especially during the + 7.0 BETA and RC period.</task> + </help> + </project> + + <project cat='net'> + <title>FreeBSD and Wake On Lan</title> + + <contact> + <person> + <name> + <given>Stefan</given> + + <common>Sperling</common> + </name> + + <email>stsp@stsp.name</email> + </person> + </contact> + + <links> + <url href="http://stsp.name/wol/" /> + + <url href="http://stsp.name/wol/README.txt" /> + + <url + href="http://www.freebsd.org/cgi/query-pr.cgi?pr=83807&cat=kern" /> + </links> + + <body> + <p>I have been working on making wake on lan (WOL) work with + FreeBSD. Contrary to popular believe OS support is required for + WOL to work properly. In particular network card drivers need to + configure network cards for WOL during system shutdown, else the + cards won't wake up. WOL is _not_ just a BIOS issue.</p> + + <p>This is work in progress. Currently the following + cards/chipsets are supported:</p> + + <ul> + <li>NatSemi DP83815 (if_sis)</li> + + <li>Via Rhine (if_vr, only VT6102 and up chips support + WOL)</li> + + <li>Nvidia nForce (if_nve, + <b>needs testing</b> + + )</li> + + <li>3Com Etherlink XL and Fast Etherlink XL (if_xl, + <b>needs testing</b> + + , only 3c905B type adapters support WOL)</li> + </ul> + + <p>I would be glad to get more feedback on my patch. I can add + support for more chipsets but I need testers for hardware I don't + have. I would appreciate access to data sheets for any NIC + chipsets that are supported by FreeBSD and have WOL support.</p> + + <p>I would especially appreciate technical feedback on the patch, + preferably by a committer who is willing to nitpick the patch to + make it ready for inclusion in -CURRENT. I currently maintain the + patch against RELENG_6_2 for my own use but I would port it to + -CURRENT for inclusion.</p> + </body> + </project> + + <project cat='proj'> + <title>FreeBSD/xen</title> + + <contact> + <person> + <name> + <given>Rink</given> + + <common>Springer</common> + </name> + + <email>rink@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Work is well under way to finish Kip Macy's FreeBSD/xen port, + and get it into a shape which is suitable for inclusion in + 7.0.</p> + + <p>Generally, the port is stable and performs quite well. The + major bottleneck is the inability to work with GCC 4.2, this is + the last major TODO before the work can be committed.</p> + </body> + + <help> + <task>Fix the port to correctly work with GCC 4.2.</task> + + <task>Port the Xen drivers to newbus.</task> + + <task>Test/fix PAE support.</task> + + <task>Start on amd64 support.</task> + </help> + </project> + + <project cat='vendor'> + <title>OpenBSD packet filter - pf</title> + + <contact> + <person> + <name> + <given>Max</given> + + <common>Laier</common> + </name> + + <email>mlaier@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>pf in HEAD (soon to be FreeBSD 7.0) has been updated to + OpenBSD 4.1 bringing in a couple of new features:</p> + + <ul> + <li>ftp-proxy has been rewritten, and a tftp version, + tftp-proxy, has been added</li> + + <li>pf(4) now supports Unicast Reverse Path Forwarding (uRPF) + checks for simplified ingress filtering</li> + + <li>The pflog(4) interface is now clonable. pf(4) can log to + multiple pflog interfaces now, each rule can specify which + pflog interface to log to</li> + + <li>pflogd(8) can now be told which pflog interface to work + with</li> + + <li>pfctl(8) can now expire table entries</li> + + <li>keep state is now the default for pf.conf(5) rules, as is + the flags S/SA option on TCP connections. no state and flags + any can be used to disable stateful filtering or TCP flags + checking</li> + + <li>The pfctl(8) ruleset optimiser can be enabled in + pf.conf(5)</li> + + <li>pf(4) anchors can now be loaded inline in the main + pf.conf(5) and can be printed recursively</li> + + <li>Allow pf(4) rules inside anchors to have their counters + reset, and make counter read & reset an atomic + operation</li> + </ul> + + <p>Some patches that went into OpenBSD after 4.1 and improve + performance significantly will be merged later.</p> + + <p>Work to support pf and netgraph interaction is underway and + will be imported after 7.0. As all required ABI changes have been + made during the update, we will be able to MFC this work for 7.1 + later on.</p> + </body> + </project> + + <project cat='vendor'> + <title>FreeBSD and Coverity Prevent</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + + <common>Dawidek</common> + </name> + + <email>pjd@FreeBSD.org</email> + </person> + + <person> + <name> + <given>David</given> + + <common>Maxwell</common> + </name> + + <email>dmaxwell@coverity.com</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>FreeBSD's static analysis scans have been updated with a + recent version of Coverity Prevent. Coverity is providing + additional advice on configuration of the analysis to maximize + the benefit from the tools.</p> + + <p>At BSDCan2007, Coverity provided FreeBSD with a license for an + additional analysis tool called Extend, which allows writing + custom FreeBSD specific code checkers. David Maxwell presented + training material for interested FreeBSD developers. Some + applications of custom checkers have been considered, and more + results will be forthcoming as they are implemented and + tested.</p> + </body> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2007-07-2007-10.xml b/en_US.ISO8859-1/htdocs/news/status/report-2007-07-2007-10.xml new file mode 100644 index 0000000000..014af23bfc --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2007-07-2007-10.xml @@ -0,0 +1,1031 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status +Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2007-07-2007-10.xml,v 1.3 2008/01/27 18:30:01 gabor Exp $ --> +<report> + <date> + <month>July-October</month> + + <year>2007</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report covers FreeBSD related projects between July and + October 2007. The sixth EuroBSDCon was held in Denmark in September. + The Google Summer of Code project came to a close and lots of + participants are working getting their code merged back into + FreeBSD.</p> + + <p>The bugs in the FreeBSD HEAD branch are being shaked out and it is + being prepared for the FreeBSD 7 branching. If your are curious about + what's new in FreeBSD 7.0 we suggest reading Ivan Voras' excellent + summary + <a href="http://ivoras.sharanet.org/freebsd/freebsd7.html">here</a> + + .</p> + + <p>Thanks to all the reporters for the excellent work! We hope you + enjoy reading.</p> + </section> + + <category> + <name>soc</name> + + <description>Google Summer of Code</description> + </category> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>team</name> + + <description>FreeBSD Team Reports</description> + </category> + + <category> + <name>net</name> + + <description>Network Infrastructure</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='soc'> + <title>MTund - Magic Tunnel Daemon</title> + + <contact> + <person> + <name> + <given>Matus</given> + + <common>Harvan</common> + </name> + + <email>mharvan@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/MTund">mtund Wiki Page</url> + + <url + href="http://www.inf.ethz.ch/personal/mharvan/docs/eurobsdcon.pdf"> + MTund Poster</url> + </links> + + <body> + <p>IP can easily be tunneled over a plethora of network protocols + at various layers, such as IP, ICMP, UDP, TCP, DNS, HTTP, SSH. + While a direct connection may not always be possible due to a + firewall, the IP packets could be encapsulated as payload in other + protocols, which would get through. However, each such + encapsulation requires the setup of a different program and the + user has to manually probe different encapsulations to find out + which of them works in a given environment.</p> + + <p>MTund is a tunneling daemon using run-time loadable plugins for + the different encapsulations. It automagically selects the best + encapsulation in each environment and can fail over to another + encapsulation. Several plugins have been implemented and the daemon + supports multiple concurrent clients.</p> + + <p>Note that the project originally started under the name of Super + Tunnel Daemon, but was later renamed to Magic Tunnel Daemon + (MTund).</p> + </body> + + <help> + <task>Config file format and parser.</task> + + <task>More plugins (http, ssh, ...).</task> + </help> + </project> + + <project cat='docs'> + <title>The Spanish Documentation Project</title> + + <contact> + <person> + <name> + <given>J. Vicente</given> + + <common>Carrasco Vayá</common> + </name> + + <email>carvay@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://www.freebsd.org/doc/es_ES.ISO8859-1/articles/fdp-es/"> + Info for volunteers</url> + </links> + + <body> + <p>After a long break in this project, we started reviewing and + refreshing our translations. We have to update the content to + reflect the current state of the English version. There are a few + parts written in a poor style, another task is to improve these a + bit. Any kind of help is highly welcome.</p> + </body> + + <help> + <task>Sync the website with the English version.</task> + + <task>Sync the documentation with the English version.</task> + + <task>Review the quality of poorly translated parts.</task> + + <task>Add more translations.</task> + </help> + </project> + + <project cat='docs'> + <title>The Hungarian Documentation Project</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gábor</given> + + <common>Páli</common> + </name> + + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/hu/docproj/hungarian.html">Info + for volunteers</url> + + <url href="http://www.freebsd.org/hu/">Hungarian website</url> + + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/docproj%5fhu&HIDEDEL=NO"> + Perforce repository</url> + </links> + + <body> + <p>We have a new volunteer, Gábor Páli, who provided us + some high-quality contributions. As a result, we have been able to add 5 + new articles since the last status report.</p> + + <p>There is also an ongoing effort in the Perforce repository to + translate the FreeBSD Handbook to Hungarian. Any kind of support is + highly welcome.</p> + </body> + + <help> + <task>Translate the Handbook.</task> + </help> + </project> + + <project cat='misc'> + <title>EuroBSDcon 2007</title> + + <contact> + <person> + <name> + <common>EuroBSDCon 2007 Organizing Committee</common> + </name> + + <email>info@EuroBSDCon.dk</email> + </person> + </contact> + + <links> + <url href="http://2007.EuroBSDCon.org/" /> + </links> + + <body> + <p>The sixth EuroBSDCon went well. 215 people attended the + conference. Feedback has been very positive.</p> + + <p>At the conference we had a Best Talk contest. Steven Murdoch, + Isaac Levy and Pawel Jakub "zfs-man" Dawidek each received a prize + for their fantastic talks.</p> + + <p>Also over 300 pictures from the conference has been uploaded to + Flickr with the tag + <a href="http://www.flickr.com/photos/tags/eurobsdcon2007/"> + EuroBSDCon2007</a> + </p> + + <p>Videos and slides from the talks are now online at the + conference website.</p> + + <p>We thank our speakers for graciously having permitted recording + and publication of their talks</p> + + <p>EuroBSDCon 2008 will take place in Strassbourg.</p> + </body> + </project> + + <project cat='soc'> + <title>finstall</title> + + <contact> + <person> + <name> + <given>Ivan</given> + + <common>Voras</common> + </name> + + <email>ivoras@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/finstall" /> + </links> + + <body> + <p>The "finstall" project is about the new graphical installer for + FreeBSD. The basic frameworks (both client-side and server-side) + are done during the SoC 2007 and it's ready for major new features + to be implemented. This project should yield an usable installer + for 7.0-RELEASE.</p> + </body> + + <help> + <task>- There are several patches needed for finstall's operation + that are still waiting on re@'s approval (unionfs, pwd, kbdmap). + Finstall will be late or unusable until these patches are + committed.</task> + + <task>- After the patches are committed, there are several exciting + features to be implemented, among others ZFS and GEOM RAID + support.</task> + </help> + </project> + + <project cat='misc'> + <title>GNATS graphs</title> + + <contact> + <person> + <name> + <given>Edwin</given> + + <common>Groothuis</common> + </name> + + <email>edwin@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~edwin/gnats/" /> + </links> + + <body> + <p>With the leaving of bsd@, we lost the GNATS statistics webpages. + On this URL I generate a new set of graphs, right now a subset of + what bsd@ had, hopefully a superset of that in the future.</p> + </body> + </project> + + <project cat='soc' summary='t'> + <title>Summer of Code</title> + + <contact> + <person> + <name> + <given>Murray</given> + + <common>Stokely</common> + </name> + + <email>murray@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/summerofcode-2007.html"> + Official FreeBSD Summer of Code 2007 Final Status Update</url> + + <url + href="http://googlesummerofcode.blogspot.com/2007/09/updates-from-freebsd.html"> + Google Blog Post About FreeBSD</url> + + <url href="http://wiki.freebsd.org/SummerOfCode2007">FreeBSD Summer + of Code Wiki</url> + </links> + + <body> + <p>We're happy to report the successful conclusion of our third + consecutive Google Summer of Code. By all accounts, the FreeBSD + participation in this program was an unqualified success. We + narrowed down the many impressive applications to 25 that were + selected for funding and 92% of these completed successfully and + were awarded the full $4,500 stipend. The FreeBSD Foundation was + also granted $500 per student from Google for a total of + $12,500.</p> + + <p>These student projects included security research, improved + installation tools, new utilities, and more. Many of the students + have continued working on their FreeBSD projects even after the + official close of the program. Three students have already been + granted full src/ commit access to CVS and more are expected. At + least 2 of our FreeBSD mentors will be meeting with Google + organizers in Mountain View this month to discuss the program at + the Mentor Summit.</p> + </body> + + <help> + <task>Integration of student projects into FreeBSD -CURRENT. + Several are currently blocked on the FreeBSD 7.0 code freeze, but + we hope to see these contributions included in a future + release.</task> + + <task>Updating the ideas list. Many of the items listed there have + been completed and we could always use new projects for next year's + students and for others to work on throughout the year. + http://www.FreeBSD.org/projects/ideas</task> + </help> + </project> + + <project cat='soc'> + <title>gvirstor</title> + + <contact> + <person> + <name> + <given>Ivan</given> + + <common>Voras</common> + </name> + + <email>ivoras@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/gvirstor" /> + </links> + + <body> + <p>GEOM_VIRSTOR (virtual disk space / over-commit GEOM class) has + been committed to 7-CURRENT and will ship in 7.0-RELEASE. Thanks to + Pawel Jakub Dawidek and others who have made this possible.</p> + </body> + + <help> + <task>It needs wider exposure and testing.</task> + </help> + </project> + + <project cat='proj'> + <title>USB</title> + + <contact> + <person> + <name> + <given>Hans Petter</given> + + <common>Sirevaag Selasky</common> + </name> + + <email>hselasky@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&HIDEDEL=NO"> + Current USB files</url> + + <url + href="http://perforce.freebsd.org/fileLogView.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb/README"> + Current USB API README file</url> + </links> + + <body> + <p>During the last three months there has been a flush of changes + going into the FreeBSD USB P4 project. The changes mainly concern + the ability to support the USB device side and multi frame USB + transfers. Up to date the FreeBSD USB stack has only supported the + USB Host Side. Before Christmas 2007 the P4 USB project will offer + USB device support and some simple USB device side implementations. + Technically an USB device side driver will look very similar to an + USB host side driver. Infact there will be very few differences. + Support for multi frame USB transfers opens up the possibility to + transfer multiple short-packet terminated USB frames to/from + different memory locations resulting in only one interrupt on the + USB Host Controller. More specific: I have implemented support for + the "alt_next" pointer in the EHCI Transfer Descriptor. This should + give a noticeable increase in the maximum number of short-packet + terminated BULK frames that can be transferred per second.</p> + + <p>I regularly get questions from people asking about when the USB + P4 project will be merged into FreeBSD-current. The answer is not + simple, but probably something like another year. The reason is not + that the current code in the USB P4 project is not usable, but + rather that the quality needs to be raised in means of making + already good solutions more technically excellent, writing more + documentation and styling the code.</p> + + <p>Ideas and comments with regard to the new USB API are welcome at + freebsd-usb@freebsd.org.</p> + </body> + </project> + + <project cat='proj'> + <title>Porting Linux KVM to FreeBSD</title> + + <contact> + <person> + <name> + <given>Fabio</given> + + <common>Checconi</common> + </name> + + <email>fabio@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Luigi</given> + + <common>Rizzo</common> + </name> + + <email>luigi@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://feanor.sssup.it/~fabio/freebsd/lkvm/" /> + </links> + + <body> + <p> + <p>Linux KVM (Kernel-based Virtual Machine) is a software package + that can be used to create virtual machines fully emulating x86 + hardware on top of machines supporting Intel VT-x or AMD-V + virtualization extensions, available on newer AMD and Intel + processors, e.g., recent Athlon64, Core 2 Duo, Xeon and so + on.</p> + + <p>Linux KVM has been ported to FreeBSD as a loadable kernel + module, using the linux-kmod-compat port (in /usr/ports/devel/) + to reuse as much as possible of the original source code, plus an + userspace client consisting in a modified version of qemu, that + uses KVM for the execution of its guests.</p> + + <p>The porting has been completed, many of the limitations + present at the end of the Summer of Code have been removed and + the known bugs have been fixed. Some configurations have been + tested, FreeBSD-CURRENT i386 guests have been booted on Intel and + AMD processors, both in i386 and amd64 (host) installations. Only + one client at a time is supported by now and performance is not + that exciting, but the project seems to be ready to receive wider + testing.</p> + </p> + </body> + </project> + + <project cat='proj'> + <title>Apple's MacBook on FreeBSD</title> + + <contact> + <person> + <name> + <given>Rui</given> + + <common>Paulo</common> + </name> + + <email>rpaulo@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/AppleMacbook" /> + </links> + + <body> + <p>The Summer of Code project went well and we reached interesting + results. At least the Mac Mini should be fully supported by now. + Regarding the other Apple systems, we still need to polish some + edges.</p> + </body> + + <help> + <task>Integrate rpaulo-macbook p4 branch into CVS.</task> + + <task>Continue the work on the remaining issues.</task> + </help> + </project> + + <project cat='proj'> + <title>Multicast DNS</title> + + <contact> + <person> + <name> + <given>Fredrik</given> + + <common>Lindberg</common> + </name> + + <email>fli@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/MulticastDNS" /> + </links> + + <body> + <p>The project (started out as a GSoC 2007 project) aims to provide + a complete Multicast DNS and Service Discovery suite. Much progress + have been made since the last status report and the project is + slowly reaching a usable state. Most features are complete and the + current focus is on fixing outstanding bugs, fine tuning and + testing. However, there are still a few open tasks (see below). + More information and snapshots can be found at the wiki page.</p> + </body> + + <help> + <task>Avahi library wrapper.</task> + + <task>dns_sd (Apple) library wrapper.</task> + + <task>Testing (always welcome).</task> + </help> + </project> + + <project cat='proj'> + <title>Multi-link PPP daemon (MPD) 5.x</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Motin</common> + </name> + + <email>mav@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://sourceforge.net/projects/mpd/">Project home</url> + + <url href="http://mpd.sourceforge.net/doc5/mpd5.html"> + ChangeLog</url> + </links> + + <body> + <p>New mpd-5.x branch has been started and first public release is + planned soon. The main goal of the new branch is to implement new + operation principles based on dynamic on-demand links/bundles + creation. There are several benefits received from new design:</p> + + <ul> + <li>Significantly simplified server configuration - no more tons + of predefined links/bundles,</li> + + <li>New multilink implementation - no more predefined link-bundle + relations,</li> + + <li>Call forwarding (LAC, PAC, TSA) like in Cisco VPDN setups can + now be enabled/configured depending on peer auth + name/domain.</li> + </ul> + </body> + + <help> + <task>L2TP auth proxying support.</task> + </help> + </project> + + <project cat='net'> + <title>Network Stack Virtualization</title> + + <contact> + <person> + <name> + <given>Marko</given> + + <common>Zec</common> + </name> + + <email>zec@fer.hr</email> + </person> + </contact> + + <links> + <url href="http://imunes.tel.fer.hr/virtnet/" /> + </links> + + <body> + <p>The network stack virtualization project aims at extending the + FreeBSD kernel to maintain multiple independent instances of + networking state. This allows for networking independence between + jail-like environmens, each maintaining its private network + interface set, IPv4 and IPv6 network and port address space, + routing tables, IPSec configuration, firewalls, and more.</p> + + <p>The prototype, which is kept in sync with FreeBSD -CURRENT, + should be sufficiently stable for testing and experimental use. The + project's web page includes weekly code snapshots, as well as a + virtualized FreeBSD system installed on a VMWare disk image + available for download.</p> + + <p>The short-term goal is to deliver production-grade kernel + support for virtualized networking for FreeBSD 7.0-RELEASE (as a + snap-in kernel replacement), while continuing to keep the code in + sync with -CURRENT for possible merging at a later date.</p> + </body> + </project> + + <project cat='soc'> + <title>Porting OpenBSD's sysctl Hardware Sensors Framework to + FreeBSD</title> + + <contact> + <person> + <name> + <given>Constantine A.</given> + + <common>Murenin</common> + </name> + + <email>cnst@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Shteryana</given> + + <common>Shopova</common> + </name> + + <email>syrinx@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/GSoC2007/cnst-sensors">Port + OpenBSD's sysctl hw.sensors framework to FreeBSD, a Google Summer + of Code 2007 project</url> + + <url href="http://cnst.livejournal.com/tag/GSoC2007">cnst's + GSoC2007 blog</url> + + <url href="http://cnst.livejournal.com/data/atom?tag=GSoC2007"> + cnst's GSoC2007 atom feed</url> + + <url + href="http://lists.freebsd.org/pipermail/freebsd-hackers/2007-September/021722.html"> + Project completion announcement from 2007-09-13</url> + + <url + href="http://p4web.freebsd.org//depot/projects/soc2007/cnst-sensors/?ac=83" /> + </links> + + <body> + <p>The + <strong>GSoC2007/cnst-sensors</strong> + + project was about porting the + <em>sysctl hw.sensors</em> + + framework from OpenBSD to FreeBSD. The project was + <a + href='http://lists.freebsd.org/pipermail/freebsd-hackers/2007-September/021722.html'> + successfully completed</a>, + + <a + href='http://leaf.dragonflybsd.org/mailarchive/commits/2007-10/msg00015.html'> + committed into DragonFly BSD</a>, and is now pending final review and integration + into the FreeBSD's CVS tree (subject to the tree being unfrozen).</p> + + <p>The <em>sensors framework</em> provides a unified interface for + storing, registering and accessing information about hardware + monitoring sensors. Sensor types include, but are not limited to, + temperature, voltage, fan RPM, time offset and logical drive + status. In the OpenBSD base system, the framework spans + <em>sensor_attach(9)</em>, <em>sysctl(3)</em>, <em>sysctl(8)</em>, + <em>systat(1)</em>, <em>sensorsd(8)</em>, <em>ntpd(8)</em> and + more than 50 drivers, ranging from I2C temperature sensors and + Super I/O hardware monitors to IPMI and RAID controllers. Several + third-party tools are also available, for example, a plug-in for + Nagios and ports/sysutils/symon.</p> + + <p>As a part of this Google Summer of Code project, all core + components of the framework were ported, including sysctl, systat + and sensorsd. Some drivers for the most popular Super I/O Hardware + Monitors were ported, too: <em>it(4)</em>, supporting most + contemporary ITE Tech Super I/O, and <em>lm(4)</em>, supporting + most contemporary Winbond Super I/O. Moreover, some existing + FreeBSD drivers were converted to utilise the framework, for + example, <em>coretemp(4)</em>.</p> + </body> + + <help> + <task>Final Review and Commit</task> + </help> + </project> + + <project cat='docs'> + <title>PC-BSD Handbook</title> + + <contact> + <person> + <name> + <given>Murray</given> + + <common>Stokely</common> + </name> + + <email>murray@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Matt</given> + + <common>Olander</common> + </name> + + <email>matt@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Fukang</given> + + <common>Chen</common> + </name> + + <email>loader@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.pcbsd.org">PC-BSD Web Page</url> + + <url href="http://www.FreeBSD.org/handbook">FreeBSD Handbook</url> + </links> + + <body> + <p>The PC-BSD derivative of FreeBSD is becoming increasingly + popular for new users of BSD. Much of the content in the existing + FreeBSD Handbook is directly applicable to PC-BSD. We are writing + PC-BSD specific installation and port/packages chapters (PBI). + These chapters will be checked into + docs/en_US.ISO8859-1/books/pcbsd-handbook and will include some of + the same chapters as the Handbook does, but with a different + &os entity and possibly with some conditional changes in those + chapter files.</p> + </body> + + <help> + <task>More work is needed on a PC-BSD ports/packages chapter. + Fukang may already have some work in this area so coordinate with + him first.</task> + + <task>More text is needed for the PC-BSD installation chapter to + augment the screenshots that Fukang has collected. Contact him to + coordinate.</task> + </help> + </project> + + <project cat='team'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/ports/">The FreeBSD Ports + Collection</url> + + <url + href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"> + Contributing to the FreeBSD Ports Collection</url> + + <url href="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD + ports unfetchable distfile survey (Bill Fenner's report)</url> + + <url href="http://portsmon.FreeBSD.org/index.html">FreeBSD ports + monitoring system</url> + + <url href="http://www.freebsd.org/portmgr/index.html">The FreeBSD + Ports Management Team</url> + + <url href="http://tinderbox.marcuscom.com">The Marcuscom + Tinderbox</url> + + <url href="http://wiki.freebsd.org/gcc4">GCC4 Status Page</url> + </links> + + <body> + <p>The ports count is over 17,700. The PR count has decreased a bit + to just over 700.</p> + + <p>There have been 6 experimental runs on the build cluster. The + resulting commits include the fixup of last year's DESTDIR changes, + the refactoring of perl bits into bsd.perl.mk, the update of xorg + from 7.2 to 7.3, the upgrade of all of the autoconf dependencies to + the latest version (wherever possible), and the upgrade of Python + to 2.5. This effort has resulted in the fewest number of 'open' + portmgr PRs in quite some time. portmgr appreciates all the people + who worked with us on these patches, and people's patience as we + catch up.</p> + + <p>As well, lofi@ committed the upgrade of QT to 4.3.1.</p> + + <p>We have added 3 new committers since the last report.</p> + </body> + + <help> + <task>GCC4.2 has been imported to the base for 7.0. Unfortunately, + this broke a large number of ports. The ones that have not yet been + fixed have now been flagged as 'broken' for both i386 and amd64, as + appropriate. Please see the GCC4 status page (above) if you are + able to help.</task> + + <task>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.</task> + + <task>Although we have added many maintainers, we still have many + unmaintained ports. The packages on amd64 are lagging behind a bit; + those on sparc64 require even more work.</task> + </help> + </project> + + <project cat='soc'> + <title>FreeBSD-update Front End</title> + + <contact> + <person> + <name> + <given>Andrew</given> + + <common>Turner</common> + </name> + + <email>andrew@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://developer.berlios.de/projects/facund/" /> + </links> + + <body> + <p>The freebsd-update front end is able to wait for freebsd-update + to download a new set of patches to apply. It can then install and + rollback the patches on either the local computer or over a SSH + tunnel.</p> + + <p>Since the end of the Summer of Code work has moved to BerliOS. + The focus has been on writing tests for the front end, back end and + communication library. The library has had tests written for most + of it while the front and back ends have none.</p> + </body> + + <help> + <task>Write more tests.</task> + </help> + </project> + + <project cat='soc'> + <title>Ports Collection infrastructure improvements</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/G%C3%A1borSoC2007">Wiki + page</url> + </links> + + <body> + <p>The two most important parts of this Summer of Code projects + have been accomplished.</p> + + <p>The DESTDIR support for the Ports Collection has been rewritten + to use a chrooted install. Now it is much more lightweight and + easier to understand, but it works well for the most common cases, + where it is supposed to be useful.</p> + + <p>The Perl parts of the Ports Collection infrastructure have been + extracted into an own module. At the same time, a new version + handling has been invented. You can find more info on the Wiki.</p> + </body> + </project> + + <project cat="team"> + <title>FreeBSD.org Admins Report</title> + + <contact> + <person> + <name> + <given>FreeBSD.org</given> + + <common>Admins Team</common> + + <email>admins@FreeBSD.org</email> + </name> + </person> + </contact> + + <body> + <p>Over the last couple of months several FreeBSD.org systems have + been experiencing hardware issues. This included the main + web-server www.FreeBSD.org which had a bad fan. The bad fan has + been replaced so it should hopefully be stable again. In general we + are working on replacing older hardware with newer systems and + consolidating machine functions in the process.</p> + + <p>Since August most FreeBSD.org services have been available via + IPv6 with connectivity provided from ISC using a tunnel.</p> + + <p>To honor the "Eat your own dog-food" principle the first two + FreeBSD.org infrastructure systems have been upgraded to FreeBSD 7 + and more are being upgraded as time permit.</p> + + <p>Due to heavy load on the project's Perforce and CVS server the + two services are being moved to separate systems to improve + performance of both CVS and Perforce.</p> + </body> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2007-10-2007-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2007-10-2007-12.xml new file mode 100644 index 0000000000..1ef5e25fb8 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2007-10-2007-12.xml @@ -0,0 +1,1562 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status +Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2007-10-2007-12.xml,v 1.9 2008/02/18 16:25:45 brd Exp $ --> +<report> + <date> + <month>October - December</month> + + <year>2007</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report covers FreeBSD related projects between October and + December 2007. + <a href="http://2008.asiabsdcon.org/">AsiaBSDCon 2008</a> + + is approaching and will be held at the Tokyo University of Science in + Tokyo, Japan on the 27th - 30th of March 2008. The FreeBSD Foundation + has released a + <a + href="http://www.freebsdfoundation.org/press/2007Dec-newsletter.shtml"> + Newsletter</a> + + detailing their activities over the past few months.</p> + + <p>FreeBSD 7.0 is nearing release and the 2nd Release Candidate is + ready for testing and is available for + <a href="http://www.freebsd.org/where.html#helptest">download now</a>.</p> + + <p>Thanks to all the reporters for the excellent work! We hope you + enjoy reading.</p> + </section> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>team</name> + + <description>FreeBSD Team Reports</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <category> + <name>bin</name> + + <description>Userland Programs</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='misc'> + <title>Bug Busting</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>bugmeister_at_FreeBSD_dot_org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/support.html#gnats">GNATS</url> + + <url href="http://wiki.freebsd.org/BugBusting/Resources">BugBusting + Resources</url> + + <url href="http://wiki.freebsd.org/Bugathons/January2008">January + 2008 Bugathon</url> + </links> + + <body> + <p>As a result of a posting on freebsd-current@ complaining about a + communication gap between users and developers, there has been a + great deal of new interest in working on bugbusting -- in particular, + we brainstormed on ideas on how non-committers can help. The two main + ideas that are being discussed are incoming bug triage (classifying, + rating, and so forth), and working with users (helping users to work + through problems that aren't classical Problem Reports.</p> + + <p>As a result of this, we held our first Bugathon in quite some time + (on #freebsd-bugbusters on EFNet). Over 30 people participated. As a + result of this, over 120 PRs were closed, and dozens more were put + into the 'feedback' state. Most of these PRs were in the kern/ and + bin/ categories, which are the two that need the most work. (The new + arrival rate was over 40/day during this time, including ports, so + there was a significant net decrease.)</p> + + <p>Several new wiki pages were created to support this effort, and + finally capture a lot of the previous discussions from both the + mailing list and the IRC channel. There are even more good ideas + which Mark Linimon has promised to work up and investigate, + including:</p> + <ul> + <li>a web page to show "last N days of PRs"</li> + + <li>some way for committers to only view PRs that have been in some + way 'vetted' or 'confirmed'</li> + + <li>more publicity for what we've already got in place, and for + what we intend to do next</li> + + <li>new categories, classifications, and states for PRs, that will + better match our workflow</li> + </ul> + + <p>Note: at this time we are not yet looking to replace GNATS. The + idea right now is to see what we can learn about how our workflow + does (and ought to) work, and experiment with some low-cost changes + to get various people's reactions. Linimon's feeling is that any of + these kinds of changes would carry over to a new system, if we were + to change over.</p> + + <p>rwatson also created a wiki page to put down some thoughts about + how to work on the various kernel problems that are reported. + Although preliminary, this captures some expertise and puts it into a + place where prospective volunteers can more easily find it.</p> + + <p>The overall PR count is back up to just under 5300. Although this + is net increase from the previous report, there were long periods of + src and ports freeze during this time, which creates a spike in the + overall count. (src and ports both remain in slush during that time). + The peak number was approaching 5500.</p> + + <p>Overall, we seem to have some momentum and new volunteers + interested in working on user-reported problems. bugmeister is + hopeful that we can capitalize on this and make some good progress in + the rest of 2008.</p> + </body> + </project> + + <project cat='kern'> + <title>Coda</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>A large number of bugs have been fixed in the FreeBSD "coda" + kernel module over the past six months, and a man page has been + added to describe the module. Many of these bugs were the result of + the coda module failing to keep up with the many enhancements to + FreeBSD VFS over the last few years. As a result of these fixes, it + is now possible to use Coda with FreeBSD 7.x and 8.x without + immediate panics, and possibly for an extended period. The new man + page does clarify that Coda is an experimental distributed file + system and not yet appropriate for production use on FreeBSD, but + things are looking a lot better than they were.</p> + </body> + + </project> + + <project cat='docs'> + <title>The Spanish Documentation Project</title> + + <contact> + <person> + <name> + <given>José Vicente</given> + + <common>Carrasco Vayá</common> + </name> + + <email>carvay@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://www.freebsd.org/doc/es_ES.ISO8859-1/articles/fdp-es/"> + Info for volunteers</url> + </links> + + <body> + <p>Since the last status report we have made a nice progress about + the website translation. The structure of the translated sites is + polished and we have brought a significant set of pages up-to-date. + New pages with important content have also been translated. Apart + from the good progress, there is a still a lot to do. Some pages + are still seriously outdated and some important parts are + missing.</p> + + <p>At the same time, we have added one new article translation and + one is still awaiting review before being committed.</p> + </body> + + <help> + <task>Continue synchronizing the website with the English one and + translate further important parts</task> + + <task>Synchronize the articles and the Handbook</task> + + <task>Add new translations</task> + </help> + </project> + + <project cat='docs'> + <title>The Hungarian Documentation Project</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gábor</given> + + <common>Páli</common> + </name> + + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/hu/">Hungarian webpage</url> + + <url href="http://www.freebsd.org/doc/hu_HU.ISO8859-2/articles/"> + Hungarian articles</url> + + <url + href="http://perforce.freebsd.org/changeList.cgi?FSPC=//depot/projects/docproj%5fhu/books/handbook/...%2b//depot/projects/docproj%5fhu/share/..."> + Perforce changelist</url> + </links> + + <body> + <p>We have added the translation of the FreeBSD Flyer and + maintained the existing translations. A huge progress is being made + to provide a Hungarian translation of the FreeBSD Handbook. Also, + there is an ongoing effort to provide Hungarian release notes for + the upcoming FreeBSD releases.</p> + </body> + + <help> + <task>Translate Handbook</task> + + <task>Add release notes for HEAD and RELENG_7</task> + + 0</help> + </project> + + <project cat='proj'> + <title>DTrace</title> + + <contact> + <person> + <name> + <given>John</given> + + <common>Birrell</common> + </name> + + <email>jb@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~jb/reasons/reasons.html"> + Change summary</url> + </links> + + <body> + <p>Thanks to support from Cisco Systems, Inc, the port of the + DTrace dynamic tracing framework from OpenSolaris to FreeBSD is + active again. A solution to the integration issues surrounding the + CDDL and BSD licenses has been found. There is an entirely BSD + licensed set of hooks/shims which are optionally compiled into the + kernel. This option can be included in the GENERIC kernel and + shipped without any CDDL patent encumberance. The CTF (Compact C + Type Format) tools now work across all architectures enabled in a + 'make universe'. A BSD licensed DWARF library has been developed. + The kernel DTrace support is limited to amd64 and i386 at the + moment. It currently passes 822 of the tests in the DTrace Test + Suite. It is expected that the initial commit to FreeBSD-CURRENT + will occur within the next month after review. Refer to the change + summary page for details of the proposed changes.</p> + </body> + + </project> + + <project cat='proj'> + <title>FreeBSD Installer</title> + + <contact> + <person> + <name> + <given>Mike</given> + + <common>Makonnen</common> + </name> + + <email>mtm@FreeBSD.Org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~mtm/fin.tar.bz2" /> + </links> + + <body> + <p>The FreeBSD Installer project (FIN) is yet another attempt to + replace the aging sysinstall(8). I am attempting to keep the best + parts of sysinstall(8) and combine them with the framework provided + by the BSDInstaller (bsdinstaller.org) to create an installation + program for FreeBSD that is multi-lingual, supports multiple + installation media, supports remote installation, and is easily + extensible to other installation types (gui, cgi, etc). The current + implementation will slice disks, install your choice of base + distributions, and set hostname and root password.</p> + </body> + + <help> + <task>Setting date, time, and time zone information</task> + + <task>Choosing and installing packages</task> + + <task>Support for installation media other than IDE CD-Rom (HTTP, + FTP, etc)</task> + + <task>Integration with devel/gettext</task> + </help> + </project> + + <project cat='kern'> + <title>LVM geom class</title> + + <contact> + <person> + <name> + <given>Andrew</given> + + <common>Thompson</common> + </name> + + <email>thompsa@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>glvm is a geom class which reads the metadata from a LVM2 (Linux + volume manager) disk and creates a geom provider for each logical + volume. An example is the logs lv on a volume group called vg0 + appearing as /dev/lvm/vg0-logs, this can be mounted as a disk.</p> + + <p>The code is working and will be posted for testing soon.</p> + </body> + </project> + + <project cat='bin'> + <title>malloc(3)</title> + + <contact> + <person> + <name> + <given>Jason</given> + + <common>Evans</common> + </name> + + <email>jasone@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>malloc(3) has been enhanced in several ways to reduce lock + contention when multi-threaded programs concurrently use the + malloc(3) functions. The primary enhancements are lazy deallocation + and dynamic arena load balancing.</p> + + <p>Lazy deallocation is designed to reduce contention for programs + that use the producer-consumer model, where a thread produces + (allocates) objects, and a pool of worker threads consumes + (deallocates) those objects. As a side benefit, lazy deallocation + also substantially reduces lock contention if multiple unrelated + threads are using the same arena.</p> + + <p>Allocation activity patterns can change throughout the lifetime + of a program. Dynamic arena load balancing monitors arena lock + contention and re-assigns threads to other arenas as necessary, + thus smoothing out allocator performance.</p> + + <p>In order to monitor lock contention in support of arena load + balancing, I had to switch to using pthreads mutexes. This all by + itself smoothed out allocator performance under high load, since + the internal libc "spinlocks" aren't really spinlocks, whereas + malloc now spins for a bit before blocking.</p> + + <p>I plan to MFC these changes to RELENG_7, hopefully in time for + the FreeBSD 7.1 release.</p> + </body> + </project> + + <project cat='kern'> + <title>FreeBSD/mips</title> + + <contact> + <person> + <name> + <given>Warner</given> + + <common>Losh</common> + </name> + + <email>imp@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Oleksandr</given> + + <common>Tymoshenko</common> + </name> + + <email>gonzo@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ollivier</given> + + <common>Houchard</common> + </name> + + <email>cognet@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Randall</given> + + <common>Stewart</common> + </name> + + <email>rrs@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>FreeBSD/mips boots to multiuser using gxemul on the MALTA board + with a 4Kc based CPU. The port is targeting MIPS32 and MIPS64 + release 1 and release 2 based systems. Work is underway to support + multicore systems.</p> + + <p>Preliminary ports to adm 5120, the IDT RC32434, the Sentry 5, + and a few other targets have started. These ports are in various + stages of stability.</p> + + <p>Juniper Networks has donated a generic MIPS FreeBSD port. This + port doesn't run on any real hardware, but contains the necessary + parts to run on idealized MIPS hardware. The FreeBSD/mips workers + have been merging the current base and the Juniper code into a + unified base. In addition, Cavium Networks has donated code + supporting their multicore mips64r2 platform. This code is also + being merged into the tree and cleaned up as well. The merged code + base presently is making it to the first (or maybe second) call to + cpu_switch before dying. Active work is underway in this area.</p> + </body> + </project> + + <project cat='misc'> + <title>FreeBSD Mirror Site Status</title> + + <contact> + <person> + <name> + <given>Edwin</given> + + <common>Groothuis</common> + </name> + + <email>edwin@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.mavetju.org/unix/ftp-stats.php" /> + </links> + + <body> + <p>There are several websites already with overview of the FreeBSD + FTP mirrror sites, but they all seem to have one problem: They are + not manually updated with the list of sites. For example, + http://mirrorlist.freebsd.org/FBSDsites.php, despite being hosted + by an Australia, doesn't have the Australian mirrors on it, while + http://people.freebsd.org/~kuriyama/mirrors/ doesn't tell you which + files are available from there. The data on my page shows the + availability of the ISO images on all FTP mirror sites. The list of + FTP mirror sites is obtained from DNS by either doing a + zone-transfer or by just trying the standard names. The first data + block shows a quick overview of the availability of the ISO image + directories per server, architecture and mirror site. The second + data block shows a verbose availability of the contents of the ISO + image directories per server.</p> + </body> + + <help> + <task>The next addition will be the availability of the pre-build + packages.</task> + </help> + </project> + + <project cat='kern'> + <title>Multi-IPv4/v6 jails</title> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + + <common>Zeeb</common> + </name> + + <email>bz@FreeBSD.ORG</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The multi-IPv4/v6 jails project was resumed in early January + after previous work had been abandoned in 2006.</p> + + <p>As an alternate solution to full network stack virtualization, + this work shall provide a lightweight solution for multi-IP + virtualization. The changes are even more important because of the + emerging demand for IPv6.</p> + + <p>The current status includes updated user space utilities. Kernel + side has grown support for multiple IP addresses for both address + families in jails, while the old kernel internal lookup/checking + functions were kept and can be compiled in during the transition + period limiting jails to one IP address. Additionally a show jails + DDB command was added to ease debugging.</p> + + <p>As an auxiliary project the last suser(9) checks were replaced + in netinet6/ to support optional raw IPv6 sockets with jails. The + new priv(9) checks were committed to HEAD.</p> + </body> + + <help> + <task>Check for proper v4-mapped v6 address handling.</task> + + <task>Review/add SCTP jail checks.</task> + + <task>Think of enhanced lookups for jails with lots of IP addresses + (preserving the "primary" IPv4 address).</task> + + <task>Regression tests and review.</task> + </help> + </project> + + <project cat='vendor'> + <title>if_nxge -- Neterion Xframe 10GbE Server/Storage adapter + driver</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The if_nxge driver, contributed by Neterion, has been merged + into FreeBSD 8-CURRENT and FreeBSD 7-STABLE, and will appear in + FreeBSD 7.0.</p> + + <p>The nxge driver provides support for Neterion Xframe-I and + Xframe-II adapters. The driver supports TCP Segmentation Offload + (TSO/LSO), Large Receive Offload (LRO), Jumbo Frames (5 buffer + mode), Header Separation (Rx 2 buffer mode), VLAN, and Promiscuous + mode.</p> + + <p>For general information and support, please visit the Neterion + support page http://www.neterion.com/support/support.html.</p> + + <p>The nxge driver supports Neterion Xframe 10 Gigabit Ethernet + adapters listed in http://www.neterion.com/how/pricing.html.</p> + </body> + </project> + + <project cat='proj'> + <title>Performance Monitoring Project</title> + + <contact> + <person> + <name> + <given>Erik</given> + + <common>Cederstrand</common> + </name> + + <email>erik@cederstrand.dk</email> + </person> + </contact> + + <links> + <url href="http://littlebit.dk:5000/">Temporary website + location</url> + </links> + + <body> + <p>As part of my thesis, I've been working on a framework to + monitor the performance of CURRENT over time. The project is now in + a state where a server and a slave are producing benchmark results + and publishing the results to a web page for testing. Already, the + setup has detected regressions. Lots of improvements can be made, + but it is already quite useful. Over the next month I'll be adding + a few features, fixing bugs and writing documentation.</p> + </body> + + <help> + <task>Decide on a useful set of benchmarks</task> + + <task>Find a more permanent home for the database and + webserver</task> + + <task>Go live</task> + </help> + </project> + + <project cat='ports'> + <title>Ports 2.0</title> + + <contact> + <person> + <name> + <given>Aryeh</given> + + <common>Friedman</common> + </name> + + <email>aryeh.friedman@gmail.com</email> + </person> + + <person> + <name> + <given>Alejandro</given> + + <common>Pulver</common> + </name> + + <email>alepulver@FreeBSD.org</email> + </person> + + <person> + <name> + <given>David</given> + + <common>Southwell</common> + </name> + + <email>david@vizion2000.net</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Completed initial requirements gathering. Selection of + development tools complete. General internal design complete.</p> + + <p>Ports 2.0 goals are:</p> + + <ul> + <li>Re-engineer/modernize the ports build process using graph + theory and more flexible depends calculations.</li> + + <li>Better document ports 1.0 and 2.0</li> + + <li>Maintain 100% user level compatibility with ports 1.0</li> + + <li>After a long trial period replace ports 1.0 in the "base + system"</li> + </ul> + </body> + + <help> + <task>Create engine</task> + + <task>Combine ports 1.0 docs from porters guide and the handbook + into a single guide</task> + + <task>Create a proof of concept by building xorg (including all + dependanicies) under the new system</task> + + <task>Create mailing list and web site</task> + </help> + </project> + + <project cat='ports'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/ports/">The FreeBSD Ports + Collection</url> + + <url + href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"> + Contributing to the FreeBSD Ports Collection</url> + + <url href="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD + ports unfetchable distfile survey (Bill Fenner's report)</url> + + <url href="http://portsmon.FreeBSD.org/index.html">FreeBSD ports + monitoring system</url> + + <url href="http://www.freebsd.org/portmgr/index.html">The FreeBSD + Ports Management Team</url> + + <url href="http://tinderbox.marcuscom.com">marcuscom + Tinderbox</url> + </links> + + <body> + <p>The ports count continues to accelerate and is now over 18,000. + The PR count, which had dipped to around 750 before the 6.3/7.0 + freeze, is now back up to about 1000, due to the fact that we + remain in ports slush.</p> + + <p>Because of the freeze/slush, no experimental ports runs have + been committed since the last report. Although 2 more -exp runs + have been completed, we are waiting for 7.0R to commit them.</p> + + <p>Once 7.0R happens, a lot of chaos is going to happen in the + Ports Collection. This has built up during the long release cycle. + Get ready for the following changes, among others:</p> + + <ul> + <li>upgrade of KDE to 4.0 (being tested)</li> + + <li>upgrade to gettext</li> + + <li>upgrade to libtool</li> + + <li>introduction of perl 5.10</li> + + <li>final removal of XFree86 (deprecated for quite some + time)</li> + + <li>removal of other expired ports</li> + </ul> + + <p>Most of the portmgr activity was related to the QA process for + the releases. In addition, linimon spent quite some time trying to + get the sparc64 ports into better shape, and sent out a request for + more people to help test sparc64 ports. Some people have responded + with offers for letting committers get accounts on their machines.</p> + + <p>Unfortunately during this time period, we became unable to build + packages for ia64-7. As a result, we are not currently building + packages for ia64 any more. If any one wants to step up to work on + this architecture, let portmgr know.</p> + + <p>We are currently building packages for amd64-5, amd64-6, + amd64-7, amd64-8, i386-5, i386-6, i386-7, i386-8, sparc64-6, and + sparc64-7. Note, however, that RELENG_5 will reach the end of its + supported life on May 31, and package builds for those 2 buildenvs will stop + as of that date. (8 buildenvs * 18,000 ports should be enough to + keep us busy.)</p> + + <p>Other than that, the packages are in the best shape that they + have been in for some time. linimon continues to work on package + analysis tools for portsmon.</p> + + <p>We have added 2 new committers since the last report.</p> + </body> + + <help> + <task>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.</task> + + <task>Although we have added many maintainers, we still have over + 4,000 unmaintained ports (see, for instance, the list on portsmon). + We are always looking for dedicated volunteers to adopt at least a + few unmaintained ports. As well, the packages on amd64 and sparc64 + lag behind i386, and we need more testers for those.</task> + </help> + </project> + + <project cat='bin'> + <title>procstat(1)</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>A new command line tool, procstat(1), allows detailed inspection + and printing of process properties, including file descriptors, + threads, kernel thread stacks, credentials, and virtual memory + mappings of processes. Several new sysctls have been added to the + kernel in order to export this information cleanly, and the + stack(9) facility has been enhanced to allow the capture of kernel + stacks from threads other than curthread. None of these features + depends on procfs, continuing the effort to remove a requirement + for procfs in order to print process information, as well as adding + new types of information not available with procfs. Kernel stack + printing is particularly useful as it provides much more detailed + information on why a thread is blocked in kernel beyond the useful + but limited wmesg context provided to date. This is helpful in + debugging both user process problems and kernel problems. procstat + has been merged into FreeBSD 8-CURRENT, and will be merged to + 7-STABLE after FreeBSD 7.0 is released.</p> + </body> + + <help> + <task>Merge to RELENG_7.</task> + + <task>Add a mode to print process signal disposition.</task> + </help> + </project> + + <project cat='doc'> + <title>FreeBSD Greek Documentation Team</title> + + <contact> + <person> + <name> + <given>Giorgos</given> + + <common>Keramidas</common> + </name> + + <email>keramida@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://hg.hellug.gr/freebsd/doc-el/">Online Hg + repository of the translation team's work-in-progress changes</url> + </links> + + <body> + <p>The Greek doc translation team has grown significantly since we + started the translations. Most of the Handbook has already been + translated to Greek (and committed to the CVS tree), as a + collaborative effort of Manolis Kiagias, Nikos Kokkalis, Panagiotis + Kritikakos, Vaggelis Typaldos, Stylianos Sideridis and others. + Manolis has started translating the FAQ too, and we also tagged + most of the Greek documents with their original, English revision + ID. There are also plans for a translation of + <em>www/en</em> + + , but these may have to be deferred until we find the time to + complete the Handbook, which is our primary target right now.</p> + </body> + + <help> + <task>Finish the Handbook translation</task> + + <task>Carefully review the translated text</task> + + <task>Resync the rest of the SRCID tags with English file + revisions</task> + + <task>Keep translating more parts of the FAQ</task> + + <task>Start updating the articles to the latest English versions + too</task> + + <task>As time permits, start a www translation too</task> + </help> + </project> + + <project cat='kern'> + <title>FreeBSD SMP network stack scalability</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Kris</given> + + <common>Kennaway</common> + </name> + + <email>kris@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>There are a variety of on-going projects relating to improving + SMP scalability of the FreeBSD network stack post-7.0. These + include:</p> + + <p> + <em>Detailed profiling of application workloads such as BIND9, + MySQL, PgSQL and Apache have been used to identify performance + bottlenecks and to guide changes to the source code.</em> + </p> + + <p> + <em>rwlock(9) use for pcbinfo and inpcb locking</em> + + , allowing the acquisition of only read locks for pcbinfo and inpcb + during UDP receive and transmit--this is highly desirable in order + to improve BIND9 performance, which sends and receives from many + threads at a time on a single UDP socket.</p> + + <p> + <em>Breaking out pcbinfo into a series of parallel data + structures</em> + + , where the particular pcbinfo instance is selected using a hash of + the connection tuple (and where ambiguous cases are present in all + instances). This would allow greatly reducing pcbinfo contention + for parallel input cases, which are increasingly likely with + multiple input queue network devices, such as the Chelsio cxgb + 10gbps driver.</p> + + <p> + <em>Investigation of use opportunities for rmlock(9)</em> + + -- rmlocks provide very lightweight acquisition for read, but + expensive acquisition for write, and may be an appropriate + replacement for rwlocks where significantly more reads than writes + take place -- such as for firewall rule list protection, pf hook + registration, address lists, etc.</p> + + <p> + <em>Weak connection affinity</em> + + , in which the effective affinity of a connection, determined by + its hash/rss work assignment to a particular input queue by the + network stack or network card, is tracked and exposed to user space + so that work associated with that connection can be performed on or + close to the CPU where the kernel will be processing input for the + connection. Software work placement has been done using the + <em>netisr2</em> + + implementation, which creates per-CPU netisr threads and assigns + work based on connection properties.</p> + + <p>There are also many other pieces of related work going on, + especially relating to 10gbps network drivers, and workloads of + particular interest include BIND9, MySQL, pgsql, Apache, and + general TCP parallelism.</p> + </body> + </project> + + <project cat='team'> + <title>Security Officer and Security Team</title> + + <contact> + <person> + <name> + <given>Security</given> + + <common>Officer</common> + </name> + + <email>security-officer@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Security</given> + + <common>Team</common> + </name> + + <email>security-team@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/security/" /> + + <url href="http://www.freebsd.org/administration.html#t-secteam" /> + + <url href="http://vuxml.freebsd.org/" /> + </links> + + <body> + <p>In the time since the last status report, four security + advisories have been issued concerning problems in the base system + of FreeBSD; one of these problems was in "contributed" code + maintained outside of FreeBSD. The FreeBSD Vulnerabilities and + Exposures Markup Language (VuXML) document has continued to be + updated; since the last status report, 61 new entries have been + added, bringing the total up to 1023. Many of these new VuXML + entries were made by members of the "ports-security" team.</p> + + <p>The "ports-security" team is still looking for more committers + who can periodically help with fixing ports security issues and + documenting them in the FreeBSD VuXML document. Committers who wish + to help with this effort can contact simon@ for details.</p> + + <p>The following FreeBSD releases are supported by the FreeBSD + Security Team: FreeBSD 5.5, FreeBSD 6.1, FreeBSD 6.2, and FreeBSD + 6.3. The respective End of Life dates of supported releases are + listed on the web site; it is expected that the upcoming FreeBSD + 7.0 release will be supported for one year after its release.</p> + </body> + </project> + + <project cat='misc'> + <title>Opensource Solutions '08</title> + + <contact> + <person> + <name> + <given>Mathieu</given> + + <common>Arnold</common> + </name> + + <email>mat@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ollivier</given> + + <common>Robert</common> + </name> + + <email>roberto@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Thierry</given> + + <common>Thomas</common> + </name> + + <email>thierry@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Rodrigo</given> + + <common>Osorio</common> + </name> + + <email>rodrigo@bebik.net</email> + </person> + </contact> + + <links> + <url href="http://www.solutionslinux.fr/en/" /> + </links> + + <body> + <p>Like every year for the past few years is held what in France is + mostly called "Solutions Linux" in Paris La Défense. The exhibition + will take place the 29, 30 and 31st of January in the CNIT.</p> + + <p>The interesting thing about this event is that 80% of the floor + is taken by companies (IBM, Novell, Oracle), and the remaining 20% + is given freely to associations and non-profit organizations, where + you'll find many (if not most) french LUGs, *BSDs, most Linux + distributions, Mozilla, OOo...</p> + + <p>This year, FreeBSD will once again have a booth, and we'll be + showing what FreeBSD is, why it's the damn best OS out there. We'll + also be distributing flyers and CD's for the whole three days</p> + + <p>Admission to the exhibitions is free, so if you ever happen to + pass by, come and see us, we'll be at booth A39.</p> + </body> + </project> + + <project cat='proj'> + <title>TCP ECN</title> + + <contact> + <person> + <name> + <given>Rui</given> + + <common>Paulo</common> + </name> + + <email>rpaulo@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://p4web.freebsd.org/@md=d&cd=//depot/projects/&c=DN2@//depot/projects/tcpecn/?ac=83"> + Perforce repository</url> + + <url + href="http://lists.freebsd.org/pipermail/freebsd-net/2007-November/016007.html"> + Mail discussion</url> + + <url href="http://people.freebsd.org/~rpaulo/tcp_ecn.diff"> + Patch</url> + </links> + + <body> + <p>Completed and tested. Awaiting review from other committers.</p> + </body> + </project> + + <project cat='kern'> + <title>TCP Reassembly Queue Optimization</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/changeList.cgi?CMD=changes&FSPC=//depot/projects/tcp_reass/..."> + Change log</url> + + <url + href="http://perforce.freebsd.org/fileViewer.cgi?FSPC=//depot/projects/tcp_reass/netinet/tcp_reass.c"> + TCP reassembly queue source file</url> + </links> + + <body> + <p>The FreeBSD TCP reassembly queue system has reached its limits + with today's high speed links over long distances and large socket + buffers. The old code is almost unchanged compared to 4.4BSD + and gets quite inefficient with large mbuf chains.</p> + + <p>The new code aggregates consecutive segments into blocks and + inserts the blocks into a tail queue. The insertion points for a + newly arrived segment are checked in order of their probability. + This prevents full chain traversals and is very efficient.</p> + + <p>To prevent easy resource exhaustion attacks the effective mbuf + usage is accounted for and limited by the size of socket buffer. + This way the reassembly queue can't be abused with many holes among + small segments.</p> + + <p>A further addition is the combination of received SACK block + tracking with the reassembly queue. The reassembly queue now tracks + all blocks of segments. This makes tracking it again for SACK + unnecessary. Additionally the limitation to six SACK blocks is + lifted and the size of the inpcb structure is reduced quite a + bit.</p> + + <p>The new code is stable and in testing correctly handles the + download of a full set of FreeBSD CDROM images and 180 ports + distfiles from widely distributed sites around the world at 2% + packet loss.</p> + </body> + + <help> + <task>Additional small performance and space optimizations.</task> + + <task>Extended testing with new ipfw tcptruncate option to chop up + TCP segments and feed them with full and partial loss into + reassembly.</task> + + <task>Full code review by other TCP developers.</task> + </help> + </project> + + <project cat='kern'> + <title>Major TCP Code Cleanup and Rewrite</title> + + <contact> + <person> + <name> + <given>Andre</given> + + <common>Oppermann</common> + </name> + + <email>andre@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/changeList.cgi?CMD=changes&FSPC=//depot/projects/tcp_new/..."> + Change log</url> + + <url + href="http://perforce.freebsd.org/fileViewer.cgi?FSPC=//depot/projects/tcp_new/netinet/tcp_input.c"> + TCP input source code</url> + </links> + + <body> + <p>The FreeBSD TCP code has evolved a lot over time and many new + features were added. However over time it got crufty, complex and + hard to read and track. In some places functionality was moved away + but the corresponding code in the main TCP functions was not or not + fully removed.</p> + + <p>The main purpose of of the TCP code cleanup and rewrite is to + make the code:</p> + + <ul> + <li>Easily readable again;</li> + + <li>Easily trackable again;</li> + + <li>A lot simpler to maintain;</li> + + <li>Verifiably correct and RFC conforming;</li> + + <li>Easily extendable for new congestion control algorithms;</li> + + <li>Increase in performance.</li> + </ul> + + <p>Quite a bit of code is already (re)written but a lot still + remains to be done.</p> + </body> + + <help> + <task>Integration of code from private branch into public perforce + repository.</task> + + <task>Completion of code and rewrite. Integration with pluggable + congestion control algorithms.</task> + + <task>Full code behavior check against all TCP RFCs and drafts of + upcoming RFCs.</task> + + <task>Extended testing and full code review by other TCP + developers.</task> + </help> + </project> + + <project cat='kern'> + <title>DDB scripting, output capture, and textdumps</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The kernel DDB facility has been enhanced to add several new + features:</p> + + <p> + <em>DDB scripting</em> + allows the user to define a set of simple scripts from within the + debugger or userspace using the new ddb(8) tool to automate + debugging steps. Scripts can be automatically executed when the + debugger is entered ("kdb.enter.panic", "kdb.enter.break", ...) + or manually using the DDB "run" command.</p> + + <p> + <em>DDB output capture</em> + allows the user to request that the output of DDB be captured + into a buffer for access from user space or to be written out in + a textdump.</p> + + <p> + <em>DDB textdumps</em>, + a new dump format that writes out a tarball of text-based + debugging information, such as the kernel message buffer, panic + message, kernel configuration, kernel version, and DDB capture + buffer to the swap partition, to be extracted via savecore(8). + This provides a compact, portable, and kernel compile independent + debugging package.</p> + + <p>Various interesting formulas for use are described in ddb(4) + and textdump(4); the facilities are separable, so you can, for + example, run a few DDB commands and capture their output, then + write a regular dump and extract that output using kgdb, or you + can do the same and write it out as a textdump. Likewise, scripts + can be used to automate manual debugging, or implement textdumps + by enabling output capture, running a series of commands, and + forcing a textdump to be written before rebooting.</p> + + <p>Support for these facilities has been merged into 8-CURRENT, + and will be merged to 7-STABLE after the release of FreeBSD + 7.0.</p> + </body> + + <help> + <task>Improve semantics of combining textdumps with + KDB_UNATTENDED.</task> + + <task>Allow scripts to use the DDB "continue" command when the + script has been started automatically as a result of a KDB enter + event, such as "kdb.enter.sysctl" or "kdb.enter.break".</task> + </help> + </project> + + <project cat='proj'> + <title>TrustedBSD Audit</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Christian</given> + + <common>Peron</common> + </name> + + <email>csjp@FreeBSD.org</email> + </person> + + <person> + <name> + <given>TrustedBSD Audit Mailing List</given> + </name> + + <email>trustedbsd-audit@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.TrustedBSD.org/audit.html">TrustedBSD Audit + home page</url> + + <url href="http://www.TrustedBSD.org/openbsm.html">TrustedBSD + OpenBSM home page</url> + + <url href="http://www.TrustedBSD.org/bsmtrace.html">BSMtrace home + page</url> + </links> + + <body> + <p>The TrustedBSD Project was proud to release OpenBSM 1.0, the + first production release of OpenBSM, which is shipped with FreeBSD + 6.3 and will ship with FreeBSD 7.0. This release represents largely + polishing, bug fixing, and cleanup over the previous alpha release, + but for FreeBSD 6.x introduced features such as XML audit trail + printing, new token types, and new event identifiers.</p> + + <p>A variety of development work continues on audit, including + initial work on OpenBSM 1.1 alpha, work on improving the + performance and semantics of audit pipes, and the experimental + bsmtrace host intrusion detection package.</p> + </body> + + <help> + <task>Improve performance for live intrusion detection by + introducing additional buffering and multi-record copying for audit + pipes.</task> + + <task>Improve flexibility for live intrusion detection and + monitoring by adding finer-grained record matching support for + audit pipes, such as by-pid and by-pid-tree.</task> + + <task>Introduce multi-host network support for experimental + bsmtrace intrusion detection package, allowing central monitoring + and alarms on live bsm traces from many hosts.</task> + + <task>Continue analysis of CC audit requirements to flesh out + missing event sources, such as user admin tools that don't + currently generate audit records.</task> + </help> + </project> + + <project cat='kern'> + <title>VM Overcommit</title> + + <contact> + <person> + <name> + <given>Konstantin</given> + + <common>Belousov</common> + </name> + + <email>kostikbel@gmail.com</email> + </person> + + <person> + <name> + <given>Peter</given> + + <common>Holm</common> + </name> + + <email>peter@holm.cc</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~kib/overcommit">The project + page</url> + </links> + + <body> + <p>The patch to account the possibly required swap space and limit + it by total amount of configured swap or per-uid limit is revived, + ported to the 8-CURRENT. Now it is intensively tested by Peter + Holm. Please, give it a run in the diverse workloads. Your comments + are welcome!</p> + </body> + </project> + + <project cat='proj'> + <title>Xen</title> + + <contact> + <person> + <name> + <given>Kip</given> + + <common>Macy</common> + </name> + + <email>kmacy@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.fsmware.com/xenofreebsd/7.0/download/">A + small file-backed disk and some sample configuration files can be + found</url> + </links> + + <body> + <p>The port will only run as a guest (i.e. domU) right now, on + i386/PAE platforms. Status:</p> + <ul> + <li>domU is self-hosting on 8-CURRENT (can compile world + kernel + in a VM).</li> + <li>Xen 3.0.3 and earlier are not supported.</li> + <li>Device structure needs to be cleaned up, it's not conformant + to newbus.</li> + <li>SMP and amd64 are targeted for support by May for RELENG_6 + and RELENG_7.</li> + <li>dom0 support is not currently on the roadmap.</li> + </ul> + </body> + + <help> + <task>Substantial cleanup needed, talk with Kip Macy or Scott Long + if you are interested in helping</task> + </help> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2008-01-2008-03.xml b/en_US.ISO8859-1/htdocs/news/status/report-2008-01-2008-03.xml new file mode 100644 index 0000000000..6234aa0e00 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2008-01-2008-03.xml @@ -0,0 +1,867 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status +Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2008-01-2008-03.xml,v 1.2 2008/05/16 17:54:32 brd Exp $ --> +<report> + <date> + <month>January - March</month> + + <year>2008</year> + </date> + + <section> + <title>Introduction</title> + + <p>This Status Report covers FreeBSD related projects between January + and March 2008. During this time FreeBSD 7.0 was released. + <a href="http://www.bsdcan.org/">BSDCan</a> + + is upon us with the Developer Summit starting the 14th and the + Conference starting the 16th.</p> + + <p>Thanks to all the reporters for the excellent work! We hope you + enjoy reading.</p> + </section> + + <category> + <name>soc</name> + + <description>Google Summer of Code</description> + </category> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>team</name> + + <description>FreeBSD Team Reports</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <project cat='team'> + <title>FreeBSD Bugbusting Team</title> + + <contact> + <person> + <name> + <given>Ceri</given> + + <common>Davies</common> + </name> + + <email>bugmeister_at_freebsd_dot_org</email> + </person> + + <person> + <name> + <given>Remko</given> + + <common>Lodder</common> + </name> + + <email>bugmeister_at_freebsd_dot_org</email> + </person> + + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>bugmeister_at_freebsd_dot_org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/support.html#gnats">GNATS</url> + + <url href="http://wiki.freebsd.org/BugBusting/Resources">BugBusting + Resources</url> + + <url href="http://wiki.freebsd.org/Bugathons/February2008">February + 2008 Bugathon</url> + + <url + href="http://people.freebsd.org/~linimon/studies/prs/recentprs.txt"> + new PRs in the last 7 days</url> + + <url + href="http://people.freebsd.org/~linimon/studies/prs/recommended_prs.txt"> + PRs recommended for committer evaluation</url> + + <url + href="http://people.freebsd.org/~linimon/studies/prs/stalefeedback.txt"> + feedback PRs with no change in 2 months</url> + </links> + + <body> + <p>As one of the results of our January and February bugathons, we + have granted Volker Werth (vwe@) direct access to GNATS. During the + past few months he has been instrumental in working on several + hundred PRs (mainly src-related), and either closing them or + helping users work through issues they are having. There have been + several commits to the src tree that directly resulted from this. + Welcome Volker!</p> + + <p>As well, several new people are assisting us in classifying + incoming PRs, working with users, and reviewing patches. Among the + most active are Bruce Cran, Dylan Cochran, and Harrison Grundy. We + appreciate everyone's efforts.</p> + + <p>As a direct result of the above, we have been able to hold the + overall PR count down to around 5300 (the peak was around 5500). + despite the facts that PR submissions have jumped recently, and the + ports PR backlog is a little higher than recent trends (due to the + long freeze/slush cycle). What is most encouraging, however, is not + the absolute number, as much as that we are handling incoming PRs + much more quickly and completely. While we are still not where we + need to be, this trend is very encouraging.</p> + + <p>As well, The Bugbusting Team has learned some lessons about how + we can best involve new people in bugbusting, e.g., how to best + leverage people who have varying levels of experience and areas of + interest. Our old response of "just look through the bug reports + and let us know if you see anything that needs doing" tends to + discourage all but the most highly-motivated. Some of these ideas + are being studied to figure how to change our process flow.</p> + + <p>There are still a number of good technical suggestions from the + two Bugathons that need to be written up and discussed. The first + few have resulted in the following: there are a few new web pages + that include: new PRs in the last 7 days; the web representation of + the "recommended by bugbusting team" list; and "PRs in feedback + with no change for 2 months". (See above). Many more need to be + added.</p> + + <p>Much of the work of the second Bugathon was in identifying and + closing PRs for which fixes had already been committed. Others were + identified and relabled as 'patched' to move them along.</p> + </body> + + <help> + <task>Think of some way for committers to only view PRs that have + been in some way 'vetted' or 'confirmed.'</task> + + <task>Generate more publicity for what we've already got in place, + and for what we intend to do next.</task> + + <task>Define new categories, classifications, and states for PRs, + that will better match our workflow.</task> + </help> + </project> + + <project cat='proj'> + <title>ProPolice support for FreeBSD</title> + + <contact> + <person> + <name> + <given>Jérémie</given> + + <common>Le Hen</common> + </name> + + <email>jeremie@le-hen.org</email> + </person> + </contact> + + <links> + <url href="http://tataz.chchile.org/~tataz/FreeBSD/SSP/"> + FreeBSD/SSP</url> + </links> + + <body> + <p>This patch modifies the build infrastructure in order to use + GCC's stack-smashing protection (SSP, aka ProPolice) when building + world, kernel and ports. Don't forget to see the website and + especially the FAQ for a list of ports that fail to build with + ProPolice. The patch extends the meaning of src.conf(5) WITHOUT_SSP + so as to prevent both building libssp and using ProPolice when + compiling. An interesting thing to note is that libssp is GNU + licensed (it is provided with GCC 4.2.1) but since libc includes + the mandatory symbols, programs won't be linked against GNU libssp. + A new knob USE_SSP has been also added for the ports + infrastructure, you can set it to "yes" in make.conf(5) and use + <tt>USE_SSP=</tt> + + on command-line to disable ProPolice for some ports. The patch has + been reviewed and should hopefully be committed soon. The port part + hasn't been reviewed yet, though.</p> + </body> + </project> + + <project cat='soc'> + <title>finstall - Graphical installer for FreeBSD</title> + + <contact> + <person> + <name> + <given>Ivan</given> + + <common>Voras</common> + </name> + + <email>ivoras@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/finstall" /> + + <url href="http://sourceforge.net/projects/finstall" /> + </links> + + <body> + <p>"finstall" is a graphical installer project for FreeBSD, + sponsored by Google during the 2007 Summer of Code. Its goal is to + create a modern installer, usable by both novice users and experts. + Because it is divided into front end and back end, it can + potentially be used for advanced purposes as system configuration, + remote and custom installs, etc. The project has resulted in a + simple installer ISO image for i386 that can be used for new + installations on empty hard drives. Development has continued + post-SoC but somewhat slowly; recently implemented features include + ZFS support and BSDStats support. To attract more potential + developers (especially those without an account on FreeBSD's + official development systems), the project has moved to + SourceForge. Future development plans include support for headless + / remote installs, partitioning, etc. Talks about finstall will be + given at BSDCan 2008.</p> + </body> + + <help> + <task>Remote / headless install support.</task> + + <task>Better partitioning support in the front end.</task> + + <task>GPT boot support.</task> + + <task>Fine grained package selection support.</task> + </help> + </project> + + <project cat='team'> + <title>The FreeBSD Foundation</title> + + <contact> + <person> + <name> + <given>Deb</given> + + <common>Goodkin</common> + </name> + + <email>deb@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsdfoundation.org">The FreeBSD Foundation + Website</url> + + <url href="http://www.freebsdfoundation.org/subscribe.shtml"> + FreeBSD Foundation Mailing List</url> + </links> + + <body> + <p>The foundation provided legal counsel for the project to + understand the impact of GPLv3 on the project and to create a + policy on software licenses. We approved a budget of $250,000 for + 2008. We were a sponsor for AsiaBSDCon and provided travel grants + to three people to attend the conference. We are a sponsor for + BSDCan and the BSDCan Developer Summit. We have approved travel + grants for 10 people to attend BSDCan. We are supporting projects + that will provide Java 1.6 binaries for FreeBSD 6.3 and 7.0. Join + our mailing list to receive monthly updates. See you at BSDCan!</p> + </body> + </project> + + <project cat='docs'> + <title>Ideas Web Application</title> + + <contact> + <person> + <name> + <given>Murray</given> + + <common>Stokely</common> + </name> + + <email>murray@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://apps.stokely.org/ideas/">Idea Database</url> + + <url href="http://wiki.freebsd.org/IdeasWebApp">Design + Document</url> + </links> + + <body> + <p>A prototype web application has been written for the + http://www.FreeBSD.org website which allows authenticated users to + add new development ideas or comment and vote on ideas added by + others. This application is a proposed replacement for the static + webpage that is currently maintained with project ideas for summer + of code students and others looking to get involved with + FreeBSD.</p> + + <p>Some of the features currently available include:</p> + + <ul> + <li>Allows anyone to propose a new idea.</li> + + <li>Allows anyone to comment and vote on previously proposed + ideas.</li> + + <li>Provides an RSS feed of the newest ideas.</li> + + <li>Provides an RSS feed of the comments/votes for any specific + idea.</li> + + <li>Allows one to sort and search the ideas list by category, + proposer, votes, summary title, or full text, and subscribe to + RSS feed of search results.</li> + + <li>Anonymous ideas/comments are hidden by default until cleared + by a moderator.</li> + + <li>Moderator bits to be set for certain users so that they can + moderate the above (can subscribe to an rss file for unmoderated + ideas and comments needing their attention).</li> + + <li>Import functionality to import the current ideas.xml + file.</li> + + <li>Graphs and statistics about the ideas in the database are + provided.</li> + </ul> + + <p>The code is checked into perforce under + <strong>//depot/user/murray/www/apps/django/ideas/...</strong> + + and I would eventually like to see this hosted on FreeBSD.org + hardware, linked from the main website, and checked into + <strong>www/apps/django/ideas</strong>.</p> + </body> + + <help> + <task>A thorough security review of the code is needed. If you have + experience with reviewing web applications for sql injection, + cross-site scripting, and other vulnerabilities please contact me. + The application uses the Django framework.</task> + + <task>Better import/export tools to get the data from our current + ideas.xml web app into the database and back out again.</task> + + <task>More usability review and suggestions needed to make this a + compelling replacement to the current static XML system.</task> + </help> + </project> + + <project cat='kern'> + <title>Multi-IPv4/v6/no-IP jails</title> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + + <common>Zeeb</common> + </name> + + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://sources.zabbadoz.net/freebsd/jail.html">Webpage + for regularly updates and patches</url> + + <url + href="http://p4web.freebsd.org/@md=d&cd=//depot/user/bz/jail/&rc=s&c=kmz@//depot/user/bz/jail/?ac=43&mx=50"> + Perforce tree</url> + </links> + + <body> + <p>The multi-IPv4/v6 jails project was resumed in early January + after previous work had been abandoned in 2006.</p> + + <p>As an alternate solution to full network stack virtualization, + this work shall provide a lightweight solution for multi-IP + virtualization. The changes are even more important because of the + emerging demand for IPv6.</p> + + <p>The current status includes updated user space utilities. Kernel + side has grown support for multiple IP addresses for both address + families in jails, as well as no IP addresses at all. 32bit and + jail version 1 backward compatibility support were implemented.</p> + + <p>The development was moved to perforce and patches for early + adopters are available.</p> + </body> + + <help> + <task>The TODO list can be found in the TODO file in + perforce.</task> + + <task>Regression tests and review.</task> + </help> + </project> + + <project cat='team'> + <title>The Ports Collection</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/ports/">The FreeBSD Ports + Collection</url> + + <url + href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"> + Contributing to the FreeBSD Ports Collection</url> + + <url href="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD + ports unfetchable distfile survey (Bill Fenner's report)</url> + + <url href="http://portsmon.FreeBSD.org/index.html">FreeBSD ports + monitoring system</url> + + <url href="http://www.freebsd.org/portmgr/index.html">The FreeBSD + Ports Management Team</url> + + <url href="http://tinderbox.marcuscom.com">marcuscom + Tinderbox</url> + </links> + + <body> + <p>portmgr is pleased to announce that Florent Thoumie (flz) has + joined us. We immediately put him to work on cleaning up the pkg_* + tools.</p> + + <p>After the extended freeze and then slush for 7.0R, we have + finally been able to start catching up on the backlog that built up + during that time.</p> + + <p>The ports count is now over 18,200. The PR count has only + dropped to around 1000. We are still turning around PRs fairly + quickly, but are not making progress on the backlog.</p> + + <p>We have only been able to do 2 -exp runs recently. Although a + number of PRs have been closed, we are still at 57 portmgr PRs.</p> + + <p>During this period, GNOME has been updated to 2.22.0. Also, a + new port for linux emulation (emulators/linux_base-f8) has been + introduced for general testing.</p> + + <p>XFree86 has been removed. (It had been deprecated for quite some + time; modern development seems to be happening in X.Org.) This + simplifies the infrastructure. A few other stale ports have been + reaped.</p> + + <p>The following large changes are in the pipeline:</p> + + <ul> + <li>Upgrade of KDE to 4.0 (being tested)</li> + + <li>Upgrade of automake to 1.10.1</li> + + <li>Upgrade of gettext to 0.17</li> + + <li>Upgrade of libtool to 1.5.26 (not 2.x at this time)</li> + + <li>Upgrade of m4 to 1.14.11</li> + + <li>Introduction of Perl 5.10</li> + </ul> + + <p>We are currently building packages for amd64-5, amd64-6, + amd64-7, amd64-8, i386-5, i386-6, i386-7, i386-8, sparc64-6, and + sparc64-7. Note, however, that RELENG_5 will reach end of its + supported life May 31, 2008, and package builds for those 2 + buildenvs will stop as of that date.</p> + + <p>We have been able to use some new machines to speed up the + package builds (in particular, amd64) -- in fact, to the point that + we are now outrunning the capacity of some of the mirrors to stay + current. A solution for the problem is being investigated.</p> + + <p>We have added 4 new committers since the last report.</p> + </body> + + <help> + <task>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.</task> + + <task>Although we have added many maintainers, we still have over + 4,000 unmaintained ports (see, for instance, the list on portsmon). + We are always looking for dedicated volunteers to adopt at least a + few unmaintained ports. As well, the packages on amd64 and sparc64 + lag behind i386, and we need more testers for those.</task> + </help> + </project> + + <project cat='proj'> + <title>Rewriting the TTY layer</title> + + <contact> + <person> + <name> + <given>Ed</given> + + <common>Schouten</common> + </name> + + <email>ed@80386.nl</email> + </person> + </contact> + + <links> + <url + href="http://p4web.freebsd.org/@md=d&cd=//&c=7ru@//depot/user/ed/mpsafetty/?ac=83"> + Perforce branch</url> + </links> + + <body> + <p>About 10 weeks ago I started rewriting the TTY layer. The + existing TTY code is about 20-25 years old and has been extended + over and over, without really improving its design.</p> + + <p>The new TTY layer will allow us to remove usage of the Giant + from drivers. It also includes an improved buffering mechanism, + which has more constant-time operations and prevents copying data + multiple times when moving data to userspace.</p> + + <p>Right now the code should work quite well for most users. The + code in Perforce includes a new pseudo-TTY driver, which is finally + capable of destroying TTY's and their associated buffers when + needed. The syscons, uart and ucom drivers have also been ported to + the new TTY layer.</p> + + <p>The code is quite complete, but it still misses driver + interaction for carrier/connection detection and sending breaks. + Many drivers still need to be ported.</p> + </body> + + <help> + <task>People who are willing to test. Contact me if you cannot + perform Perforce checkouts.</task> + + <task>Not all drivers have been ported. Patches or hardware are + welcome.</task> + + <task>Some changes could already be backported.</task> + </help> + </project> + + <project cat='soc'> + <title>Summer of Code</title> + + <contact> + <person> + <name> + <given>Murray</given> + + <common>Stokely</common> + </name> + + <email>murray@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/summerofcode.html" /> + + <url href="http://wiki.freebsd.org/SummerOfCode" /> + </links> + + <body> + <p>The student application period for the Summer of Code is over + and the mentors and administrators are carefully reviewing the + applications, clarifying the project parameters, and deciding which + students to recommend for funding from Google.</p> + + <p>This year we received over 100 student applications from + students in 26 different countries. We also have over 60 potential + mentors that we are currently matching up with students. We will + soon announce the winning students on the summer of code website + and the process of bringing these students into our development + community will begin.</p> + + <p>Each student will again be given Perforce and wiki access and + all developers are encouraged to contact any students working in + related areas, as we don't want the students to have access to our + community only through their formal assigned mentor.</p> + </body> + + <help> + <task>Help introduce our new summer of code students to FreeBSD + development. Some students are very experienced at developing on + FreeBSD and others are new to our environment and could use more + assistance.</task> + + <task>Update the ideas database with new project ideas that you'd + like to see for next year's Summer of Code.</task> + </help> + </project> + + <project cat='kern'> + <title>UnionFS Improvements</title> + + <contact> + <person> + <name> + <given>Daichi</given> + + <common>GOTO</common> + </name> + + <email>daichi@freebsd.org</email> + </person> + + <person> + <name> + <given>Masanori</given> + + <common>OZAWA</common> + </name> + + <email>ozawa@ongs.co.jp</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~daichi/unionfs/" /> + </links> + + <body> + <p>Our implementation of UnionFS has been merged into HEAD, + 7-stable and 6-stable already. Now we are working on UnionFS + stability improvement. We have developed the following 5 patches. + If you are interested, please try them and report your results.</p> + <ul> + <li> + <a + href="http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-1.diff"> + unionfs-p20-1.diff</a> + </li> + + <li> + <a + href="http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-2.diff"> + unionfs-p20-2.diff</a> + </li> + + <li> + <a + href="http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-3.diff"> + unionfs-p20-3.diff</a> + </li> + + <li> + <a + href="http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-4.diff"> + unionfs-p20-4.diff</a> + </li> + + <li> + <a + href="http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-5.diff"> + unionfs-p20-5.diff</a> + </li> + </ul> + </body> + + <help> + <task>Robert Watson has pointed out that unionfs-p20-5.diff has + some problems around how it treats sockets. We are researching + those.</task> + </help> + </project> + + <project cat='proj'> + <title>USB</title> + + <contact> + <person> + <name> + <given>Hans Petter</given> + + <common>Sirevaag Selasky</common> + </name> + + <email>hselasky@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://p4web.freebsd.org/@md=d&cd=//depot/projects/usb/src/sys/dev/usb/&c=A2y@//depot/projects/usb/src/sys/dev/usb/?ac=83"> + Current USB files</url> + + <url + href="http://p4web.freebsd.org/@md=d&cd=//depot/projects/usb/src/sys/dev/usb/&cdf=//depot/projects/usb/src/sys/dev/usb/README&sr=136513&c=2Ro@//depot/projects/usb/src/sys/dev/usb/README"> + Current USB API README file</url> + + <url href="http://www.selasky.org/hans_petter/usb4bsd">Install + instructions</url> + </links> + + <body> + <p>During the last three months there has mostly been bugfix and + documentation commits. The code is currently in a stable and full + featured state. The FreeBSD P4 USB project now has a fully + symmetric USB stack at API level and has been tested to work with + AT91RM9200 ARM based boards and USS820 based devices. There are + currently two USB device side drivers implemented, namely CDC + Ethernet and Mass Storage (SCSI+BBB) so that you can now make your + custom USB Flash Disk using FreeBSD. Don't confuse USB device side + drivers with USB host side drivers.</p> + + <p>Currently the USB P4 project is under review.</p> + + <p>Ideas and comments with regard to the new USB API are welcome on + the FreeBSD + <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-usb">USB + Mailing List</a> + + .</p> + </body> + </project> + + <project cat='docs'> + <title>The Spanish Documentation Project</title> + + <contact> + <person> + <name> + <given>José Vicente</given> + + <common>Carrasco Vayá</common> + </name> + + <email>carvay@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://FreeBSD.org/es">FreeBSD Spanish Website</url> + + <url href="http://www.freebsd.org/doc/es_ES.ISO8859-1/">Spanish + Translations</url> + </links> + + <body> + <p>We are progressing better these days again. We have made some + updates to the website and to the Handbook, including the complete + translation of the jails chapter. We have also added a new + translation of an article and an another one is under review.</p> + </body> + + <help> + <task>Complete updating of the website.</task> + + <task>Update the Handbook and translate new chapters.</task> + </help> + </project> + + <project cat='docs'> + <title>The Hungarian Documentation Project</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gábor</given> + + <common>Páli</common> + </name> + + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://FreeBSD.org/hu">Hungarian website</url> + + <url href="http://www.freebsd.org/doc/hu_HU.ISO8859-2/articles/"> + Hungarian articles</url> + </links> + + <body> + <p>We are pleased to welcome Gábor Páli as a doc committer. He has + successfully completed the translation of the + FreeBSD Handbook. The final review of his work is pending now + and we will import it soon to the repository. We consider the + translation of the release notes the next important milestone of + this translation project.</p> + </body> + + <help> + <task>Review the translated Handbook.</task> + + <task>Translate release notes for -CURRENT and 7.X.</task> + </help> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2008-04-2008-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2008-04-2008-06.xml new file mode 100644 index 0000000000..df8522dd67 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2008-04-2008-06.xml @@ -0,0 +1,929 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status +Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2008-04-2008-06.xml,v 1.1 2008/08/19 23:04:12 brd Exp $ --> +<report> + <date> + <month>April - June</month> + + <year>2008</year> + </date> + + <section> + <title>Introduction</title> + + <p>This Status Report covers FreeBSD related projects between April + and June 2008. During this period The FreeBSD Foundation has + released their <a + href="http://www.freebsdfoundation.org/press/2008Jul-newsletter.shtml">July + Newsletter</a>.</p> + + <p>Thanks to all the reporters for the excellent work! We hope you + enjoy reading.</p> + </section> + + <category> + <name>soc</name> + + <description>Google Summer of Code</description> + </category> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>arch</name> + + <description>FreeBSD Architecture</description> + </category> + + <category> + <name>ports</name> + + <description>The Ports Collection</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <project cat='arch'> + <title>ARM/Marvell port</title> + + <contact> + <person> + <name> + <given>Rafal</given> + + <common>Jaworowski</common> + </name> + + <email>raj@semihalf.com</email> + </person> + + <person> + <name> + <given>Bartlomiej</given> + + <common>Sieka</common> + </name> + + <email>tur@semihalf.com</email> + </person> + </contact> + + <links> + <url href="http://p4web.freebsd.org/@md=d&cd=//depot/projects/arm/src/sys/arm/orion/&c=0h4@//depot/projects/arm/src/sys/arm/orion/?ac=83">Orion in Perforce</url> + </links> + + <body> + <p>After the last couple of months of intensive development going + on towards FreeBSD support for Marvell System-on-Chip devices, we + have FreeBSD 8.0-CURRENT running on the following systems:</p> + <ul> + <li>Orion (already available in Perforce):</li> + <ul> + <li>88F5281</li> + <li>88F5181</li> + <li>88F5182</li> + </ul> + <li>Kirkwood - 88F6281</li> + <li>Discovery - MV78100</li> + </ul> + <p>The above families of SOCs are built around CPU + cores compliant with ARMv5TE instruction set architecture + definition. They share a number of integrated peripherals, for most + of which we already have operational and stable drivers:</p> + <ul> + <li>UART</li> + <li>EHCI USB 2.0</li> + <li>Ethernet</li> + <li>IDMA (general purpose DMA engine)</li> + <li>XOR</li> + <li>TWSI (I2C)</li> + <li>Timers, watchdog, RTC</li> + <li>GPIO</li> + <li>Interrupt controller</li> + <li>L1, L2 cache</li> + </ul> + <p>High level functional summary:</p> + <ul> + <li>Production Quality</li> + <li>Error-free Operation</li> + <li>Multiuser</li> + <li>Self-hosted kernel/world builds</li> + <li>NFS- or USB-mounted root filesystem</li> + </ul> + <p>The code is partially available (Orion in Perforce), other + variants will also be integrated with Perforce/SVN soon.</p> + </body> + + <help> + <task>Drivers that are In-progress: PCI and PCIE.</task> + </help> + </project> + + <project cat='proj'> + <title>Graphics support for the boot loader</title> + + <contact> + <person> + <name> + <given>Oliver</given> + + <common>Fromme</common> + </name> + + <email>olli@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/OliverFromme/BootLoader" /> + </links> + + <body> + <p>This project aims to implement graphics support for FreeBSD's + boot loader. It will replace the existing ASCII menu. (Note that + the ASCII menu will still be available when graphics mode cannot be + used, such as on serial console or on unsupported hardware.)</p> + + <p>For a more detailed description and screen shots please refer to + the project's Wiki URL above.</p> + + <p>Progress is slow (due to lack of time) but steady. The code + currently lives in the Perforce repository. I'll try to prepare a + first public CFT as soon as possible.</p> + </body> + + <help> + <task>Implement a platform switch.</task> + + <task>Implement "themes" support (in FORTH).</task> + + <task>Documentation.</task> + </help> + </project> + + <project cat='proj'> + <title>FreeBSD Bugbusting Team</title> + + <contact> + <person> + <name> + <given>Ceri</given> + + <common>Davies</common> + </name> + + <email>bugmeister@</email> + </person> + + <person> + <name> + <given>Remko</given> + + <common>Lodder</common> + </name> + + <email>bugmeister@</email> + </person> + + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>bugmeister@</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/support.html#gnats">GNATS</url> + <url href="http://wiki.freebsd.org/BugBusting">BugBusting</url> + <url + href="http://people.freebsd.org/~linimon/studies/prs/pr_manpage_index.html"> + PRs indexed by manpage</url> + <url + href="http://people.freebsd.org/~linimon/studies/prs/pr_tag_index.html"> + PRs indexed by tag</url> + <url + href="http://people.freebsd.org/~linimon/studies/prs/prs_possibly_committed.html"> + PRs which may have already been committed</url> + <url + href="http://people.freebsd.org/~linimon/studies/prs/well_known_prs.html"> + Well-Known PRs as determined by the bugbusting team</url> + <url + href="http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues"> + Commonly Reported Issues</url> + maintained by Jeremy Chadwick (includes commentary and + analysis)</links> + + <body> + <p>We have granted Bruce Cran (bruce@) direct access to GNATS and + Volker Werth (vwe@) has been released from mentorship. We + appreciate their help!</p> + + <p>We had a third bugathon in June, which resulted in the closing + of a number of bugs and the investigation/classification of several + others. We are still trying to find ways to get more committers + helping us with closing PRs that the team has already analyzed.</p> + + <p>We continue to make good progress in categorizing PRs as they + arrive with 'tags' that correspond to manpages. (Special thanks go + to Dylan Cochran for the help.) As a result, we now have created + some prototype reports that allow browsing the database + <url + href="http://people.freebsd.org/~linimon/studies/prs/pr_manpage_index.html"> + by manpage</url>.</p> + + <p>In addition, another new report, oriented towards PR submitters, + summarizes the + <url + href="http://people.freebsd.org/~linimon/studies/prs/well_known_prs.html"> + most commonly reported issues</url>. + Many of these issues persist because they are difficult to fix. + Before filing a PR, you may want to check through this list.</p> + + <p>Mark Linimon summarized the good technical suggestions from the + bugathons so far this year to the wiki. As a part of this, he + rearranged the wiki pages, so if you have not seen them for a + while, please see + <url href="http://wiki.freebsd.org/BugBusting">BugBusting</url>. + In particular, the Resources page is much more complete.</p> + + <p>Jeremy Chadwick (koitsu@) is now maintaining a + <url + href="http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues"> + page</url> + + that summarizes some of the commonly reported issues. This + complements some of the reports, above, but includes a great deal + more information, including how-tos.</p> + + <p>The overall PR count has been holding at around 5300 since the + last release.</p> + </body> + + <help> + <task>Think of some way for committers to only view PRs that have + been in some way 'vetted' or 'confirmed'.</task> + + <task>Generate more publicity for what we've already got in place, + and for what we intend to do next.</task> + + <task>Define new categories, classifications, and states for PRs, + that will better match our workflow.</task> + </help> + </project> + + <project cat='proj'> + <title>Build cluster</title> + + <contact> + <person> + <name> + <given>Kris</given> + + <common>Kennaway</common> + </name> + + <email>kris@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>For the past couple of months I have been working on + generalizing the package build cluster to allow it to host other + batch and interactive jobs. Currently we make an inefficient use of + build machines because various projects have dedicated machines + that are either underloaded or overloaded for their particular + tasks. The goal is to provide a framework for combining all of + these machine resources into a single cluster that can be shared by + many users, reducing dead time and allowing distributed build tasks + to take advantage of extra build resources when available. + Developers will be able to obtain on-demand interactive access to a + jail running on any of the available architectures, with root + access. Similarly, batch jobs will specify their resource + requirements and be dispatched to run on a suitable machine in the + cluster. Current status: The job queue manager is working and is + now being used to map package builds to machines. Various package + build scripts have been rewritten to use it instead of the previous + build scheduler. The generic job dispatcher is being prototyped and + will be validated with several existing services such as INDEX + builds. Various support services like ZFS snapshot replication have + been written.</p> + </body> + </project> + + <project cat='docs'> + <title>The FreeBSD Dutch Documentation Project</title> + + <contact> + <person> + <name> + <given>Remko</given> + + <common>Lodder</common> + </name> + + <email>remko@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Rene</given> + + <common>Ladan</common> + </name> + + <email>r.c.ladan@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd-nl.org">Main documentation site</url> + + <url href="http://www.evilcoder.org/freebsd_nl/">Project site</url> + </links> + + <body> + <p> + <p>The FreeBSD Dutch Documentation Project is an ongoing project + to translate the FreeBSD Documentation resources to the Dutch + language.</p> + + <p>The project is currently progressing very well in translating + the FreeBSD Handbook to the Dutch language, the last chapter is + being translated by the project members.</p> + + <p>Recent achievements include the translation of the Jails + chapter, and the Virtualization chapter, as well as progression + on the Advanced Networking chapter. Rene Ladan is a keyplayer in + that region.</p> + + <p>We also started with the FAQ translation, which is another + major target which we should be reaching at some point.</p> + + <p>If you care to helpout with the translation(s) and/or want to + know something about it, please do not hesitate to contact us, we + are glad to help where possible.</p> + </p> + </body> + + <help> + <task>Finish the Handbook translation.</task> + + <task>Finish the FAQ translation.</task> + + <task>Finish the Website translation.</task> + + <task>Keep the projects in sync with the English version(s).</task> + </help> + </project> + + <project cat='docs'> + <title>FreeBSD FAQ Renovation</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Páli</common> + </name> + + <email>pgj@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Manolis</given> + + <common>Kiagias</common> + </name> + + <email>manolis@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/doc/en/books/faq/"> + </url> + + <url href="http://wiki.freebsd.org/faq-renewal">FreeBSD FAQ Renewal + Proposal</url> + </links> + + <body> + <p>An extensive work on renovating the FreeBSD FAQ has been started + to support its Greek and Hungarian translations. Further + improvements and content changes are still possible, we hope other + committers will help us to keep the FAQ updated and tuned + further.</p> + + <p>We have launched a renewal proposal to collect and organize the + ideas around a more interactive, accurate, open for comments, + consistent across several views etc. FAQ document. We would like to + experiment with methods to implement the goals mentioned before, + and help is more than welcome.</p> + </body> + + <help> + <task>Review the renovated FAQ.</task> + + <task>Add more question and answers to the FAQ.</task> + + <task>Refine the FAQ renewal proposal.</task> + </help> + </project> + + <project cat='proj'> + <title>finstall</title> + + <contact> + <person> + <name> + <given>Ivan</given> + + <common>Voras</common> + </name> + + <email>ivoras@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/finstall" /> + + <url href="http://www.sf.net/projects/finstall" /> + </links> + + <body> + <p>Between the last report and this one, the project has yielded a + LiveCD installer for i386 containing FreeBSD 7.0-RELEASE. The + project was presented at BSDCan 2008. The development is + progressing slowly due to the lack of free time. I'm looking for + funding that will allow me more involvement in the project. The big + item currently in development is documentation and description of + the protocol used between the front-end and the back-end, which + will result in more robustness in the implementation and could + support third-party clients. This sub-project is near completion. + The project is currently hosted at SourceForge to allow + contribution from non-FreeBSD developers.</p> + </body> + + <help> + <task>Partition editor.</task> + + <task>Package selection.</task> + </help> + </project> + + <project cat='docs'> + <title>The FreeBSD Hungarian Documentation Project</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gábor</given> + + <common>Páli</common> + </name> + + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://FreeBSD.org/hu">Hungarian Web Site for + FreeBSD</url> + + <url href="http://www.FreeBSD.org/doc/hu_HU.ISO8859-2/">Hungarian + Documentation for FreeBSD</url> + + <url href="http://wiki.FreeBSD.org/HungarianDocumentationProject"> + The FreeBSD Hungarian Documentation Project's Wiki Page</url> + + <url + href="http://p4web.freebsd.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83"> + Perforce Depot for The FreeBSD Hungarian Documentation + Project</url> + </links> + + <body> + <p>Hungarian translation of the + <a href="http://www.freebsd.org/doc/hu/books/handbook"> + FreeBSD Handbook</a> + + has been finally committed to the doc repository. The translation + of the + <em>FreeBSD FAQ</em> + + has also been started, however, the original document needed to be + brought up to date first. Two other article translations has been + added, + <a href="http://www.freebsd.org/doc/hu/articles/compiz-fusion"> + compiz-fusion</a> + + and + <a href="http://www.freebsd.org/doc/hu/articles/linux-users"> + linux-users</a>.</p> + + <p>Our Perforce depot was reorganized for the better layout, giving + newcomers more space to play. The + <a + href="http://www.freebsd.org/cgi/cvsweb.cgi/doc/el_GR.ISO8859-7/share/tools/checkupdate/checkupdate.py"> + checkupdate</a> + + script written by Giorgos Keramidas, a new tool for checking + translations has been adopted to help the project's work.</p> + </body> + + <help> + <task>Translate release notes for -CURRENT and 7.X.</task> + + <task>Translate more articles.</task> + + <task>Translate books/fdp-primer.</task> + </help> + </project> + + <project cat='ports'> + <title>Qt/KDE4 Status Report</title> + + <contact> + <person> + <name> + <given>Martin</given> + + <common>Wilke</common> + </name> + + <email>miwi@FreeBSD.org</email> + </person> + + <person> + <name> + <given>FreeBSD KDE Team</given> + </name> + + <email>kde@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://freebsd.kde.org" /> + </links> + + <body> + <p>Qt4 has been updated to 4.4.1 in our test repository. We ran + into some runtime problems with Qt 4.4.0, so it was never committed + it to the ports tree. Most of the problems have been fixed in 4.4.1 + and we plan to commit it in a few days.</p> + + <p>At the moment, the KDE 4.1 ports are ready for testing before + they are committed to the FreeBSD ports tree. We have already had + the first Call for Public Testing on July 17th, 2008 with KDE 4.1 + beta2. The feedback has been positive so far. If you want to help + to test them to speed up the process, please visit the + <a href="http://wiki.freebsd.org/KDE4/install">Wiki page</a> + + and provide feedback.</p> + + <p>We plan to have it all committed by the middle of August.</p> + </body> + </project> + + <project cat='soc'> + <title>Layer2 filtering</title> + + <contact> + <person> + <name> + <given>Gleb</given> + + <common>Kurtsou</common> + </name> + + <email>gk@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Andrew</given> + + <common>Thompson</common> + </name> + + <email>thompsa@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://wiki.freebsd.org/GlebKurtsov/Improving_layer2_filtering" /> + + <url href="http://blogs.freebsdish.org/gleb/" /> + </links> + + <body> + <p>Project aims to improve layer2 filtering in ipfw and pf. So far + following project goals are achieved: pfil framework is extended to + handle ethernet packets, ipfw layer2 filtering is greatly + simplified, added l2filter and l2tag per interface flags. Both ipfw + and pf firewalls support filtering by ethernet addresses, support + stateful filtering with ethernet addresses and firewall's lookup + tables are extended to contain ethernet addresses.</p> + </body> + + <help> + <task>Implement ARP filtering options in IPFW.</task> + </help> + </project> + + <project cat='ports'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/ports/">The FreeBSD Ports + Collection</url> + + <url + href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"> + Contributing to the FreeBSD Ports Collection</url> + + <url href="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD + ports unfetchable distfile survey (Bill Fenner's report)</url> + + <url href="http://portsmon.FreeBSD.org/index.html">FreeBSD ports + monitoring system</url> + + <url href="http://www.freebsd.org/portmgr/index.html">The FreeBSD + Ports Management Team</url> + + <url href="http://tinderbox.marcuscom.com">marcuscom + Tinderbox</url> + </links> + + <body> + <p>The ports count has jumped to over 19,000. The PR count has been + holding steady at around 900.</p> + + <p>KDE has been updated to 4.1. Special thanks go to Martin Wilke + for a great deal of pre-testing.</p> + + <p>GNOME has been updated three times, first to 2.22.1 and then to + 2.22.2 and 2.22.3.</p> + + <p>Other notable updates are automake, gettext, libtool, and + m4.</p> + + <p>Florent Thoumie has been working on some updates to the pkg_* + tools.</p> + + <p>Ion-Mihai Tetcu has set up a tinderbox with several purposes: + first, to quickly try to build packages as changes are committed; + secondly, to build them with a non-standard set of environment + variables; and thirdly, to build older packages with the non- + standard set of environment variables. As a result of all this + work, and work by various committers, we are much closer to + building packages corrected in the NOPORTDOCS case.</p> + + <p>Kris Kennaway has done a substantial rewrite of the package + building tools, including moving as a default to ZFS, which allows + quick cloning of src and ports directories. It is now much easier + to manage and monitor the builds. Work on this is continuing. See + the commits to + <url + href="http://www.freebsd.org/cgi/cvsweb.cgi/ports/Tools/portbuild/scripts/"> + Tools/portbuild/scripts</url> + + for more information. (Work is ongoing to update the Package + Building article.) Related work has involved cleaning up some of + the ports infrastructure; in particular, the INDEX builds are now + much faster.</p> + + <p>We have been able to do many -exp runs since the last report, + including those for bsd.cmake.mk, autotools update, CC environment + passing, the KDE 4.1 pre-integration and post-integration checks, + lockmgr changes, tty changes, and others.</p> + + <p>Although a number of PRs have been closed, we are still at 57 + portmgr PRs, the same as the last report.</p> + + <p>The following large changes are in the pipeline: + <ul> + <li>Introduction of Perl 5.10</li> + </ul> + </p> + + <p>We are currently building packages for amd64-6, amd64-7, + amd64-8, i386-6, i386-7, i386-8, sparc64-6, and sparc64-7. RELENG_5 + has reached the end of its supported life.</p> + + <p>We have added 4 new committers since the last report.</p> + </body> + + <help> + <task>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.</task> + + <task>Although we have added many maintainers, we still have over + 4,000 unmaintained ports (see, for instance, the list on portsmon). + We are always looking for dedicated volunteers to adopt at least a + few unmaintained ports. As well, the packages on amd64 and sparc64 + lag behind i386, and we need more testers for those.</task> + </help> + </project> + + <project cat='soc'> + <title>Porting BSD-licensed text-processing tools from + OpenBSD</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/G%C3%A1borSoC2008">Wiki + page</url> + + <url + href="http://p4web.freebsd.org/@md=d&cd=//&c=Kqj@//depot/projects/soc2008/gabor_textproc/?ac=83"> + Perforce depot</url> + </links> + + <body> + <p>The grep utility is ready for a thorough test on the portbuild + cluster. It is almost compatible with GNU grep, but there are + differences in the regex handling at the level of the regex + libraries of GNU and the base system one, thus a better + compatibility is very hard to implement.</p> + + <p>Some progress has been made on diff, but some important options + are still missing. The sort utility seems to be very problematic in + the aspect of the wide character support by design, thus it was + given a lower priority.</p> + </body> + + <help> + <task>Finish the incomplete options of diff and optimize it.</task> + + <task>Investigate about the opportunities to fix sort.</task> + </help> + </project> + + <project cat='docs'> + <title>The FreeBSD Spanish Documentation Project</title> + + <contact> + <person> + <name> + <given>José Vicente</given> + + <common>Carrasco Vayá</common> + </name> + + <email>carvay@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://FreeBSD.org/es">Spanish Web Site for + FreeBSD</url> + + <url href="http://www.FreeBSD.org/doc/es_ES.ISO8859-1/">Spanish + Documentation for FreeBSD</url> + + <url href="http://wiki.FreeBSD.org/SpanishDocumentationProject">The + FreeBSD Spanish Documentation Project's Wiki Page</url> + + <url + href="http://p4web.freebsd.org/@md=d&cd=//depot/projects/docproj_es/&c=S1s@//depot/projects/docproj_es/?ac=83"> + Perforce Depot for The FreeBSD Spanish Documentation Project</url> + </links> + + <body> + <p>We have not made any significant progress in this period. We + definitely need more active translators to progress with the + translation project.</p> + </body> + + <help> + <task>Complete renovation of the Spanish web site.</task> + + <task>Update Handbook translation.</task> + + <task>Translate release notes for -CURRENT and 7.X.</task> + </help> + </project> + + <project cat='proj'> + <title>USB</title> + + <contact> + <person> + <name> + <given>Hans Petter</given> + + <common>Sirevaag Selasky</common> + </name> + + <email>hselasky@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://p4web.freebsd.org/@md=d&cd=//depot/projects/usb/src/sys/dev/usb2/&c=oDu@//depot/projects/usb/src/sys/dev/usb2/?ac=83"> + Current USB files</url> + + <url + href="http://p4web.freebsd.org/@md=d&cd=//&cdf=//depot/projects/usb/src/sys/dev/usb2/core/README.TXT&c=Vfw@//depot/projects/usb/src/sys/dev/usb2/core/README.TXT?ac=64&rev1=2"> + Current USB API README file</url> + </links> + + <body> + <p>During the last three months there has been a number of changes. + Most notably all global USB symbols have been renamed to "usb2_" to + allow for co-existence with the old USB stack. Also there is now a + completely new and reworked UGEN driver which allows multiple + drivers to hook onto the same USB device. No more need to unload + any kernel drivers. For example it is now possible to have a + userland Mouse driver stealing half of the mouse events at the same + time "ums" is loaded. The only disadvantage is that your mouse + cursor will move slower on the screen. This is maybe not the most + common use-case, but it illustrates that kernel USB drivers are no + longer locking out other USB userland drivers. A new userland + libusb is in the works for FreeBSD. The USB stack now also has + support for independent USB BUS, USB Device, and USB Interface + permissions. That means you can more easily give USB permissions to + USB device drivers at either USB BUS, USB Device or USB Interface + level. All USB modules have now been grouped into functional + categories: usb2_bluetooth, usb2_ndis, usb2_controller, usb2_quirk, + usb2_core, usb2_serial, usb2_ethernet, usb2_sound, usb2_image, + usb2_storage, usb2_input, usb2_template, usb2_misc, and + usb2_wlan.</p> + + <p>Ideas and comments with regard to the new USB API are welcome + on the <a + href="http://lists.freebsd.org/mailman/listinfo/freebsd-usb"> + FreeBSD-USB Mailing List</a>.</p> + </body> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2008-07-2008-09.xml b/en_US.ISO8859-1/htdocs/news/status/report-2008-07-2008-09.xml new file mode 100644 index 0000000000..d175a9bcb8 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2008-07-2008-09.xml @@ -0,0 +1,787 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status +Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2008-07-2008-09.xml,v 1.3 2008/11/11 08:18:58 maxim Exp $ --> +<report> + <date> + <month>July-September</month> + + <year>2008</year> + </date> + + <section> + <title>Introduction</title> + + <p>In this Quarter work has been progressing in quite a few areas of + FreeBSD. FreeBSD 7.1-BETA2 and 6.4-RC2 have been released for + pre-release testing. EuroBSDCon 2008 took place in Strasbourg, France + and quite a few developers got together for the Developer Summit + before the Conference. The USB2 stack has been imported into the + -HEAD branch.</p> + + <p>Thanks to all the reporters for the excellent work! We hope you + enjoy reading.</p> + </section> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>team</name> + + <description>FreeBSD Team Reports</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='proj'> + <title>FreeBSD for ASUS EeePC</title> + + <contact> + <person> + <name> + <given>Stanislav</given> + + <common>Sedov</common> + </name> + + <email>stas@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Rui</given> + + <common>Paulo</common> + </name> + + <email>rpaulo@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Lars</given> + + <common>Engels</common> + </name> + + <email>lme@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/AsusEee">ASUS Eee Wiki</url> + </links> + + <body> + <p> + <em>ASUS Eee</em> + + is a line of cheap subnotebooks. These come with Linux or Windows + preinstalled. The hardware is a bit inconventional, so it required + some efforts to make FreeBSD run properly on this hardware. Also, + these machines contain some hardware that was not supported by + FreeBSD.</p> + + <p>Currently FreeBSD should run on all Eee models out of the box, + and most hardware should just work. At least, 700, 701, 901 and + 1000 was tested successfully. The hardware supported includes + Atheros wireless backed by ath(4) in HEAD (you still need a patch + for RELENG_7), Attansic L2 FastEthernet controller (ae(4)), + High Definition audio controller (snd_hda), Synaptics touchpad and + so on. Suspend/resume also works fine with some exceptions.</p> + + <p>There is also a hardware monitoring module, that allows user to + control FAN speed and voltage, as well as monitor current CPU + temperature. Wiki page contains information on how to obtain this + module and use it. There are also a lot of useful tips and tricks + for using FreeBSD on ASUS EeePC on that page.</p> + </body> + + <help> + <task>Attansic L1 Gigabit Ethernet support (for ASUS Eee + 901)</task> + + <task>Wireless driver for ASUS Eee 901 (ral(4))</task> + + <task>Fix Synaptics resume path.</task> + </help> + </project> + + <project cat='proj'> + <title>CVSMode for csup</title> + + <contact> + <person> + <name> + <given>Ulf</given> + + <common>Lilleengen</common> + </name> + + <email>lulf@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://p4web.freebsd.org/@md=d&cd=//&po=h&c=gCY@//depot/user/lulf/csup/?ac=83"> + Perforce repository</url> + </links> + + <body> + <p>The implementation of cvsmode for csup has become more mature, + and has been tested by a few people so far. All parts directly + related to CVSMode have been implemented, and it seems to work + quite well. Testers are still needed, so any users of cvsup + using it to mirror or fetch the CVS repository (cvsmode/mirror + mode) are encouraged to try it.</p> + </body> + + <help> + <task>Implement support for the rsync protocol (not needed for proper + working, but it will probably speed up csup in some cases)</task> + + <task>Implement complete support for using the status file in + cvsmode</task> + </help> + </project> + + <project cat='docs'> + <title>The FreeBSD Hungarian Documentation Project</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gábor</given> + + <common>Páli</common> + </name> + + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/hu">Hungarian Web Page for + FreeBSD</url> + + <url href="http://www.FreeBSD.org/doc/hu">Hungarian Documentation + for FreeBSD</url> + + <url href="http://wiki.FreeBSD.org/HungarianDocumentationProject"> + The FreeBSD Hungarian Documentation Project's Wiki Page</url> + + <url + href="http://p4web.freebsd.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83"> + Perforce Depot for the FreeBSD Hungarian Documentation + Project</url> + </links> + + <body> + <p>In July, + <em>pgj</em> + + gave a + <a + href="http://people.freebsd.org/~pgj/fhdp/fhdp-slides.20080704.pdf.gz"> + presentation</a> + + (in Hungarian) about the FreeBSD Hungarian Documentation Project in + Debrecen, Hungary.</p> + + <p>Based on the checkupdate script mentioned in our previous status + report, we launched our + <a + href="http://lists.freebsd.org/pipermail/cvs-doc/2008-July/018608.html"> + Translation Checking Service</a> + + to help to schedule periodic updates for Hungarian doc/www + translations. Moreover, a small bug in EPS images blocking + automatic generation of the Handbook PDF version + <a + href="http://lists.freebsd.org/pipermail/cvs-doc/2008-August/018785.html"> + was corrected</a> + + , therefore it is now available for + <a href="ftp://ftp.freebsd.org/pub/FreeBSD/doc/hu/books/handbook"> + download</a> + + .</p> + + <p>Shortly after the renovation of its source, translation of the + FAQ has also become part of Hungarian documentations. Both + <a href="http://www.freebsd.org/doc/hu/books/faq">online</a> + + and + <a href="ftp://ftp.freebsd.org/pub/FreeBSD/doc/hu/books/faq"> + offline</a> + + versions are available. A recently translated article + (<a href="http://www.freebsd.org/doc/hu/articles/gjournal-desktop"> + gjournal-desktop</a>) has also been added.</p> + + <p>Hungarian translation of the + <em>FreeBSD Documentation Project Primer for New Contributors</em> + + has been + <a href="http://wiki.freebsd.org/TheHungarianFDPPrimer">started</a> + + . We hope this will encourage others to help our work. There is + always place in our team, every submitted translation or feedback + is appreciated and very welcome.</p> + </body> + + <help> + <task>Translate release notes for -CURRENT and 7.X</task> + + <task>Translate articles</task> + + <task>Translate the FDP Primer</task> + + <task>Read the translations, send feedback</task> + </help> + </project> + + <project cat="proj"> + <title>The FreeBSD Foundation</title> + + <contact> + <person> + <name> + <given>Deb</given> + + <common>Goodkin</common> + </name> + + <email>deb@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsdfoundation.org" /> + </links> + + <body> + <p>For the first time we sent out a request for project proposals. + We were very excited about the proposals we received. We accepted + four projects and will be announcing them soon. We were proud to + sponsor NYCBSDCon and EuroBSDCon. We are also a sponsor of + MeetBSDCon. We provided travel grants for the Cambridge FreeBSD + Developer Summit in August. We are continuing to provide updated + Java binaries for FreeBSD 7.0. We continued to provide legal + support for the project.</p> + </body> + </project> + + <project cat='misc'> + <title>FreeBSD mirror statistics</title> + + <contact> + <person> + <name> + <given>Edwin</given> + + <common>Groothuis</common> + </name> + + <email>edwin@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.mavetju.org/unix/freebsd-mirrors/"> + Website</url> + + <url href="http://www.mavetju.org/unix/freebsd-mirrors/score.php"> + 10 Day Score overview</url> + </links> + + <body> + <p>There are many FreeBSD mirrors, either FTP or WWW or CVSup or + RSync, but are they really all up-to-date? Some are, some aren't. + The ones who aren't, how out to date are they? Or do they only + carry a subset of the data? And how does it go over time?</p> + + <p>This project checks once per day the contents of the sites which + are advertised in DNS, with the rsync*, www*, cvsup* and ftp* + prefixes. The lists of hosts are based on the contents of the DNS + zonefile for the country domains, so it will be automatically + adjusted whenever a mirror is added.</p> + + <p>The statuses can be compared on country base and between two + dates and the 10 day score overview shows the general health of the + FreeBSD Mirroring network.</p> + </body> + + <help> + <task>Create a list of contact details per mirror.</task> + + <task>Chase mirror maintainers with regarding to the status of + their servers.</task> + </help> + </project> + + <project cat='proj'> + <title>USB2</title> + + <contact> + <person> + <name> + <given>Hans Petter</given> + + <common>Sirevaag Selasky</common> + </name> + + <email>hselasky@freebsd.org</email> + </person> + </contact> + + <links> + <url + href="http://p4web.freebsd.org/@md=d&cd=//depot/projects/usb/src/sys/dev/usb2/&c=OPj@//depot/projects/usb/src/sys/dev/usb2/?ac=83"> + Current USB files</url> + </links> + + <body> + <p>The new USB stack has been imported to FreeBSD-CURRENT. There is + an ongoing review process at the freebsd-usb mailing list and the + freebsd-current mailing list. A couple of minor issues remain.</p> + + <p>Ideas and comments with regard to the new USB stack are welcome + at freebsd-usb@freebsd.org .</p> + </body> + + <help> + </help> + </project> + + <project cat='kern'> + <title>Multi-IPv4/v6/no-IP jails</title> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + + <common>Zeeb</common> + </name> + + <email>bz@FreeBSD.ORG</email> + </person> + </contact> + + <links> + <url href="http://sources.zabbadoz.net/freebsd/jail.html">Web page + for regularly updates and patches</url> + + <url + href="http://p4web.freebsd.org/@md=d&cd=//depot/user/bz/jail/&rc=s&c=kmz@//depot/user/bz/jail/?ac=43&mx=50"> + Perforce tree</url> + </links> + + <body> + <p>The multi-IPv4/v6/no-IP jails project was resumed beginning of + this year and is in the final stage now. A commit is imminent + waiting for final review to be finished.</p> + + <p>As an alternative solution to full network stack virtualization, + this work shall provide a lightweight solution for multi-IP + virtualization. The changes are even more important because of the + emerging demand for IPv6.</p> + + <p>Ideally this will be merged to FreeBSD 7 before 7.2-RELEASE and + stay in FreeBSD 8 for the transitional period to full network stack + virtualization.</p> + </body> + + <help> + <task>Finish review.</task> + + <task>Management (rc framework, ..) for 7-STABLE.</task> + + <task>Identify ports that need to be updated.</task> + </help> + </project> + + <project cat='misc'> + <title>MavEtJu's FreeBSD Mailing List Browser</title> + + <contact> + <person> + <name> + <given>Edwin</given> + + <common>Groothuis</common> + </name> + + <email>edwin@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.mavetju.org/mail/">Website</url> + </links> + + <body> + <p>Earlier this year I put efforts into the creation of a new layout + for the FreeBSD mailinglists. The following issues were tackled: + <ul> + <li>Display which mailinglists are active and are visited + often.</li> + + <li>A clean weekly/monthly overview per list.</li> + + <li>In the weekly/monthly overview, be able to go forward and + backward in time.</li> + + <li>Browsing through threads goes by the Replies/Replies + To/Referenced By/References To fields of the emails, but visible + who the email is from.</li> + + <li>An overview of the thread with quick links to the + articles.</li> + + <li>Text attachments are normally shown, other attachment are + normally not shown.</li> + + <li>Tag messages, see your browsing history, reply to emails and + an "wrap long lines" feature.</li> + + <li>Filtering out of svn-, cvs-, freebsd-, and p4- groups.</li> + + <li>Show date and time in the format you want.</li> + + <li>Storing of preferences managed via OpenID + identification.</li> + </ul> + + The mailinglist website is updated once per hour with the + mailinglists via cvsup.</p> + </body> + + <help> + <task>Addition of RSS feeds per mailinglist and for the "last day" + feature.</task> + </help> + </project> + + <project cat='misc'> + <title>FreeBSD Multimedia Resources List</title> + + <contact> + <person> + <name> + <given>Edwin</given> + + <common>Groothuis</common> + </name> + + <email>edwin@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://www.mavetju.org/unix/multimedia/freebsd/multimedia.html"> + Website</url> + + <url + href="http://www.mavetju.org/unix/multimedia/freebsd/multimedia.xml"> + RSS feed</url> + </links> + + <body> + <p>Please note that the FreeBSD Multimedia Resources List is still + alive and kicking. It is a one-stop-shop for FreeBSD related + podcasts, vodcasts and audio/video resources. It has talks, videos + and papers of the New York City BSD Con 2008, FreeBSD Developer + Summit, BSDCan 2008, AsiaBSDCon 2008, OpenFest and has recordings + with regular talks like the NYCBUG user group and regular podcast + of BSDTalk.</p> + </body> + + <help> + </help> + </project> + + <project cat='proj'> + <title>pkg_trans</title> + + <contact> + <person> + <name> + <given>Ivan</given> + + <common>Voras</common> + </name> + + <email>ivoras@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/IvanVoras/PkgTransProposal" /> + </links> + + <body> + <p>The "pkg_trans" project is a work in progress aiming to add + package transactions / grouping to common package manipulation + utilities (pkg_add, pkg_delete). The intention is to have all + packages pulled in by a particular command like "pkg_add" or "make + install" grouped in a single transaction, which can be later rolled + back. This will allow users to, for example, install a big tree of + dependent packages (like kde4), try it, and later delete it.</p> + + <p>Currently the pkg_trans and the patched utilities are available + for testing. There are some open issues but it's generally + stable.</p> + </body> + + <help> + <task>I cannot modify the "make install" infrastructure for ports + and 3rd party utilities such as portupgrade. People who know these + utilities are very welcome to help.</task> + + <task>More testing is needed.</task> + </help> + </project> + + <project cat='arch'> + <title>FreeBSD/powerpc for Freescale MPC8572</title> + + <contact> + <person> + <name> + <given>Rafal</given> + + <common>Jaworowski</common> + </name> + + <email>raj@semihalf.com</email> + </person> + + <person> + <name> + <given>Bartlomiej</given> + + <common>Sieka</common> + </name> + + <email>tur@semihalf.com</email> + </person> + </contact> + + <body> + <p>The MPC8572 system-on-chip device is a high-end member of + Freescale PowerQUICC III family, which features a rich set of + integrated peripherals. It is a dual e500v2 core system, compliant + with Book-E definition of the Power Architecture. For detailed + specification see: + http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MPC8572E + This work is extending our (single core) MPC85XX port already + available in the SVN tree. Currently the MPC8572 support covers: + <ul> + <li>all existing functionality of FreeBSD/MPC85XX (console, e500 + interrupts/exceptions, networking, etc.)</li> + + <li>SMP</li> + + <ul> + <li>dual-e500 cores running at 1.5GHz each</li> + + <li>ULE</li> + </ul> + + <li>Security engine (SEC)</li> + + <li>General purpose DMA controller</li> + + <li>Pattern matching engine (PME)</li> + + <li>Ethernet controller (eTSEC) advanced features</li> + + <ul> + <li>multicast</li> + + <li>jumbo frames</li> + + <li>TCP/IP h/w checksumming</li> + + <li>VLAN tagging</li> + + <li>polling</li> + + <li>interrupt coalescing</li> + </ul> + + <li>PCI-Express bridge</li> + + <li>I2C controller</li> + </ul> + + High level functional summary: + <ul> + <li>stable multiuser SMP operation</li> + + <li>NFS-mounted root filesystem</li> + </ul> + </p> + </body> + + <help> + <task>Remaining built-in peripherals drivers</task> + </help> + </project> + + <project cat='team'> + <title>Release Engineering Team</title> + + <contact> + <person> + <name> + <given>Ken</given> + + <common>Smith</common> + </name> + + <email>re@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The Release Engineering Team continues to work on getting + 6.4-RELEASE and 7.1-RELEASE ready. 6.4-RC2 builds are coming up + shortly, with 6.4-RELEASE expected about two weeks later. There are + still a few issues being worked on for 7.1-RELEASE though hopefully + we will be ready to proceed with 7.1-RC1 within the next week. Both + 6.4-RELEASE and 7.1-RELEASE will include DVD image ISOs for the + amd64 and i386 architectures which has been requested by quite a + few end-users.</p> + </body> + </project> + + <project cat='team'> + <title>FreeBSD Security Officer and Security Team</title> + + <contact> + <person> + <name> + <given>Security</given> + + <common>Officer</common> + </name> + + <email>security-officer@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Security</given> + + <common>Team</common> + </name> + + <email>security-team@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/security/" /> + + <url href="http://www.freebsd.org/administration.html#t-secteam" /> + + <url href="http://vuxml.freebsd.org/" /> + </links> + + <body> + <p>The FreeBSD Security Team has recently had some membership + changes. George V. Neville-Neil, Dag-Erling Smorgrav, and Marcus + Alves Grando have retired from the team. We thank them for their + work while they were on the security team. Xin Li, Martin Wilke, + Qing Li, and Stanislav Sedov have joined the team.</p> + </body> + </project> + + <project cat='kern'> + <title>Synaptics touchpads support improvements in psm(4)</title> + + <contact> + <person> + <name> + <given>Jean-Sébastien</given> + + <common>Pédron</common> + </name> + + <email>dumbbell@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/SynapticsTouchpad" /> + </links> + + <body> + <p>psm(4) provides basic support for Synaptics Touchpad but doesn't + allow one to take advantage of many features like multi-finger tap + and tap-hold, or virtual scrolling. A driver for X.Org is available + but the movements are not very precise and the setup is not easy if + you want to use your touchpad in the console.</p> + + <p>The goal of this project is to first provide a better movement + filtering and smoothing, then bring the more advanced features.</p> + + <p>Right now, movement filtering, multi-finger tap, tap-hold and + virtual scrolling (using a dedicated area) is implemented.</p> + + <p>Virtual scrolling with two fingers (as seen on Apple MacBook) + will be brought back soon.</p> + + <p>But before that, the new driver needs testing! It's currently + tested on an ASUS V6V only and feedback on other laptops would be + greatly appreciated.</p> + </body> + + <help> + <task>Test and send feedback.</task> + </help> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2008-10-2008-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2008-10-2008-12.xml new file mode 100644 index 0000000000..4430778d8e --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2008-10-2008-12.xml @@ -0,0 +1,1164 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status +Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2008-10-2008-12.xml,v 1.3 2009/01/30 06:38:07 blackend Exp $ --> +<report> + <date> + <month>October-December</month> + + <year>2008</year> + </date> + + <section> + <title>Introduction</title> + + <p>This quarter included some very exciting work including the + release of FreeBSD 6.4 and the much anticipated release of + FreeBSD 7.1. We also launched our own official <a + href="http://forums.FreeBSD.org">FreeBSD Forums</a>. + The first Bugathon of the year will be held this weekend, see + below for more information and how to participate.</p> + + <p>Thanks to all the reporters for the excellent work! We hope you + enjoy reading.</p> + </section> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>team</name> + + <description>FreeBSD Team Reports</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='misc'> + <title>YouTube Channel for BSD</title> + + <contact> + <person> + <name> + <given>Murray</given> + + <common>Stokely</common> + </name> + + <email>murray@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.youtube.com/bsdconferences">BSD Conferences + YouTube Channel</url> + + <url + href="http://murrayFreeBSD.blogspot.com/2008/12/new-channel-on-youtube-for-bsd.html"> + Channel Announcement</url> + + <url href="http://wiki.FreeBSD.org/VideoProductionAndPublishing"> + Video Production and Publishing Wiki</url> + </links> + + <body> + <p>A new <a href="http://www.youtube.com/bsdconferences">channel</a> + has been setup on <a href="http://www.youtube.com">YouTube</a> + explicitly for BSD conference recordings. This channel does not + have the normal 10 minute limit so full high quality presentations + from 30 minutes to nearly 2 hours have been uploaded. So far over + 23 videos are available from MeetBSD and NYCBSDCon, with more from + BSDCan and AsiaBSDCon coming soon.</p> + + <p>We are currently looking for more videos from + <a href="http://www.bsdcan.org">BSDCan</a>, + <a href="http://www.eurobsdcon.org">EuroBSDCon</a>, + <a href="http://www.asiabsdcon.org">AsiaBSDCon</a>, + etc to upload to the channel. We also need help in creating + subtitles for each video in various languages. If you would like to + help out in generating subtitles for your language or if you have + old video content from one of the above BSD conferences please let + us know.</p> + </body> + + <help> + <task>Adding subtitles in various languages to all of the technical + talks.</task> + + <task>Finding more videos from previous conferences to + upload.</task> + + <task>Audio post-processing. If anyone has experience removing + audio artifacts from a video recording we would love to talk to you + about working some magic on raw footage we have before uploading it + to YouTube.</task> + + <task>We could use additional tips for improved video recording and + post-processing added to our video production and publishing + wiki.</task> + </help> + </project> + + <project cat='misc'> + <title>BSD-licensed grep</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/soc2008/gabor_textproc/&c=vqZ@//depot/projects/soc2008/gabor_textproc/grep/?ac=83"> + Project repository</url> + </links> + + <body> + <p>Some bugs have been fixed in the buffering and binary file + detection parts of grep. Due to the differences between the GNU + regexp library and our libc regexp implementation, I switched to the + GNU library so that we can maintain an acceptable level of + compatibility. The desired option would be to drop both GNU grep + and the GNU regexp library, but unfortunately we cannot just do that + because of these incompatibilities. Accordingly, the first step + should be replacing grep and then we should review and optimize our + regexp library. With this decision, BSD grep has acquired a higher + level of compatibility and now seems to be much more useful.</p> + </body> + + <help> + <task>Make a portbuild run with BSD grep and fix possible + bugs.</task> + </help> + </project> + + <project cat='proj'> + <title>FreeBSD Bugathons</title> + + <contact> + <person> + <email>bugbusters@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/BugBusting" /> + + <url href="http://wiki.FreeBSD.org/BugBusting/Resources" /> + + <url href="http://bugs.FreeBSD.org" /> + + <url + href="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?responsible=freebsd-net" /> + </links> + + <body> + <p>Last year, we didn't have many Bugathons - this year is planned + to be different!</p> + + <p>The BugBusting team is trying to improve bug handling and thus + we'll start a new experiment. In the past our Bugathons were + general Bugathons with no special topic set. Instead, starting in + 2009 we'll try to hold a series of Bugathons that concentrate on + special interest areas.</p> + + <p>Our next Bugathon will be held from 2009-01-30 to 2009-02-01 + (Fri-Sun). We'll try to handle as many network related bugs as we + can. Our plan is to try to work through all network related PRs + still open in GNATS.</p> + + <p>We need a number of maintainers in the area of networking + (drivers, chipsets, protocols, userland processes) to attend and + committers willing to commit fixes and improvements. Of course, we + also need users and administrators with special interest in network + related items to be with us to sort out things. Every helping hand, + everyone able to debug and analyze things is welcome.</p> + + <p>If you're interested in getting networking stuff improved, join + us to make the upcoming releases of 7.2 and 8.0 the best ever + FreeBSD releases.</p> + + <p>Join us on IRC: EFnet #FreeBSD-bugbusters from Friday 2009-01-30 + to Sunday 2009-02-01. Don't miss this event!</p> + + <p>The next Bugathon (TBA) will have topics in different special + interest areas.</p> + </body> + + <help> + <task>Feel free to ask questions! You can reach the BugBusting team + at bugbusters@FreeBSD.org. Be there! Work with us! Join the team - + be a part!</task> + </help> + </project> + + <project cat='proj'> + <title>FreeBSD BugBusting Team</title> + + <contact> + <person> + <name> + <given>Remko</given> + + <common>Lodder</common> + </name> + + <email>bugmeister@</email> + </person> + + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>bugmeister@</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/support.html#gnats">GNATS</url> + + <url href="http://wiki.FreeBSD.org/BugBusting">BugBusting</url> + + <url href="http://people.FreeBSD.org/~linimon/studies/prs/"> + experimental report pages</url> + </links> + + <body> + <p>We will be having our next Bugathon on 2009-01-30 to 2009-02-01 + (see <a href="#FreeBSD-Bugathons">this</a> entry).</p> + + <p>At the recent DevSummit in Strasbourg, the participants spent + half a day working through the current "recommended PRs" list. The + list was divided up into sections by date, and each table was + assigned one section to work through. Not only were a good number + of fixes committed and their PRs closed, but the src developers + were brought up to speed on the triage work that the BugBusting + team has been doing (see below). We hope to build on this momentum + in the future. In addition, many new ideas for improved report + pages were discussed.</p> + + <p>We continue to make good progress in categorizing PRs as they + arrive with 'tags' that correspond to manpages. As a result, we now + have created some prototype reports that allow browsing the + database + <a + href="http://people.FreeBSD.org/~linimon/studies/prs/pr_manpage_index.html"> + by manpage</a>.</p> + + <p>In addition, another new report, oriented towards PR submitters, + summarizes the + <a + href="http://people.FreeBSD.org/~linimon/studies/prs/well_known_prs.html"> + most commonly reported issues</a>. Many of these issues persist + because they are difficult to fix. Before filing a PR, you may + want to check through this list.</p> + + <p>As well, we now have a more active set of volunteers who are + willing to help users with reported problems of the form "xyz does + not seem to work". These types of reports are now being handled + much better than in the past.</p> + + <p>One of those volunteers, Bruce Cran (brucec@), has now been + released from mentorship.</p> + + <p>Mark Linimon (linimon@) continues to work on more new prototype + reports, including:</p> + + <ul> + <li><a + href="http://people.FreeBSD.org/~linimon/studies/prs/recentprs_day.html"> + New PRs in the past day</a>, <a + href="http://people.FreeBSD.org/~linimon/studies/prs/recentprs_week.html"> + week</a>, <a + href="http://people.FreeBSD.org/~linimon/studies/prs/recentprs_month.html"> + month</a>.</li> + + <li><a + href="http://people.FreeBSD.org/~linimon/studies/prs/prs_for_tag_regression.html"> + PRs with regressions</a>.</li> + + <li>A way for developers to <a + href="http://people.FreeBSD.org/~linimon/annotated_prs.sample.html"> + create their own customized reports</a>.</li> + </ul> + + <p>The <a + href="http://wiki.FreeBSD.org/BugBusting/Commonly_reported_issues"> + commonly reported issues</a> summary page, previously maintained + by Jeremy Chadwick, has been moved to a new location.</p> + + <p>The overall PR count jumped to over 5600 during the 6.4/7.1 + release cycle, but has come down a bit.</p> + </body> + + <help> + <task>Try to find ways to get more committers helping us with + closing PRs that the team has already analyzed.</task> + + <task>Think of some way for committers to only view PRs that have + been in some way 'vetted' or 'confirmed'.</task> + + <task>Generate more publicity for what we've already got in place, + and for what we intend to do next.</task> + + <task>Define new categories, classifications, and states for PRs, + that will better match our workflow.</task> + </help> + </project> + + <project cat='docs'> + <title>The FreeBSD Hungarian Documentation Project</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gábor</given> + + <common>Páli</common> + </name> + + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/hu">Hungarian Web Page for + FreeBSD</url> + + <url href="http://www.FreeBSD.org/doc/hu">Hungarian Documentation + for FreeBSD</url> + + <url href="http://wiki.FreeBSD.org/HungarianDocumentationProject"> + The FreeBSD Hungarian Documentation Project's Wiki Page</url> + + <url + href="http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83"> + Perforce Depot for the FreeBSD Hungarian Documentation + Project</url> + </links> + + <body> + <p>Hungarian translation of the + <em>FreeBSD Documentation Project Primer for New Contributors</em> + + has been finished and now it is available both + <a href="http://www.FreeBSD.org/doc/hu/books/fdp-primer">online</a> + + and + <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/hu/books/fdp-primer"> + for download</a>.</p> + + <p>We hope that having the FDP Primer translated will encourage + people to help our work. There is always place in our team, every + submitted translation or feedback is appreciated and very + welcome.</p> + + <p>Beside the continuous maintenance of the Hungarian documentation + and web pages, a new article translation has been added to the + Hungarian Documentation Set, + <a href="http://www.FreeBSD.org/doc/hu/articles/cups">CUPS</a>.</p> + </body> + + <help> + <task>Read the translations, send feedback</task> + + <task>Translate web pages</task> + + <task>Translate articles</task> + + <task>Translate release notes for -CURRENT and 7.X</task> + </help> + </project> + + <project cat='misc'> + <title>The FreeBSD Forums</title> + + <contact> + <person> + <name> + <given>FreeBSD Forums</given> + + <common>Admins</common> + </name> + + <email>forum-admins@</email> + </person> + + <person> + <name> + <given>FreeBSD Forums</given> + + <common>Moderators</common> + </name> + + <email>forum-moderators@</email> + </person> + </contact> + + <links> + <url href="http://forums.FreeBSD.org/" /> + </links> + + <body> + <p>The FreeBSD forums were publicly launched on November 16th, 2008 + as a complementary support channel to our great mailing lists.</p> + + <p>There were almost 2000 new users registered in the first three + days and each day we receive about 20 new user registrations. After + less than three months after going public, we are now serving + around 10,000 posts in 1,500 threads. We have received very + positive feedback from our users, which we take as a good + compensation for our efforts put into this project.</p> + </body> + </project> + + <project cat='proj'> + <title>The FreeBSD Foundation Status Report</title> + + <contact> + <person> + <name> + <given>Deb</given> + + <common>Goodkin</common> + </name> + + <email>deb@FreeBSDFoundation.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSDfoundation.org" /> + </links> + + <body> + <p>We ended the year raising over $282,000! We received 173 + donations just in December. We are very grateful to all the people + who helped us come very close to our 2008 goal.</p> + + <p>Three projects were started that are being funded by the + foundation. They are Safe Removal of Active Disk Devices, + Improvements to the FreeBSD TCP Stack, and Network Stack + Virtualization Projects. + <a + href="http://www.FreeBSDfoundation.org/project%20announcements.shtml"> + Click here</a> + + to find out more about the projects.</p> + + <p>We were a sponsor for meetBSD. We provided a travel grant for a + developer to attend this conference. We also handed out a few + limited edition foundation vests for developer recognition.</p> + + <p>Read our + <a + href="http://www.FreeBSDfoundation.org/press/2008Dec-newsletter.shtml"> + end-of-year newsletter</a>, to find out what else we've done to + help The FreeBSD Project and community.</p> + </body> + </project> + + <project cat='docs'> + <title>The FreeBSD Greek Documentation Project</title> + + <contact> + <person> + <name> + <given>Giorgos</given> + + <common>Keramidas</common> + </name> + + <email>keramida@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Manolis</given> + + <common>Kiagias</common> + </name> + + <email>manolis@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSDgr.org">Greek Documentation Project + Wiki and test builds</url> + </links> + + <body> + <p>The FreeBSD Greek Documentation Project managed to complete a + significant amount of work during 2008. The first ten chapters of + the Handbook are now completely translated and kept in sync with + the English text. Work is also progressing nicely in the second + part of The Handbook, with many new translated chapters. At this + pace, we hope to have a complete Greek Handbook by 8.0-RELEASE.</p> + + <p>More volunteers are always welcome of course, as there is still + plenty of work to be done.</p> + </body> + + <help> + <task>Complete the Greek translation of the Handbook (about ten + chapters remaining)</task> + + <task>Complete the Greek translation of the FAQ (currently at + around 40%)</task> + + <task>Translate more documentation (articles) to Greek</task> + + <task>Begin a Greek website on FreeBSD.org (volunteers + needed)</task> + </help> + </project> + + <project cat='kern'> + <title>Multi-IPv4/v6/no-IP jails</title> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + + <common>Zeeb</common> + </name> + + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://sources.zabbadoz.net/FreeBSD/jail.html">Web page + for regularly updates and patches</url> + + <url + href="http://p4web.FreeBSD.org/@md=d&cd=//depot/user/bz/jail/&rc=s&c=kmz@//depot/user/bz/jail/?ac=43&mx=50"> + Perforce tree</url> + </links> + + <body> + <p>The multi-IPv4/v6/no-IP jails project patch has finally been + committed to FreeBSD-CURRENT at the end of November.</p> + + <p>As an alternate solution to full network stack virtualization, + this work shall provide a lightweight solution for multi-IP + virtualization. The changes are even more important because of the + emerging demand for IPv6. Ideally this will be merged to FreeBSD 7 + before 7.2-RELEASE and stay in FreeBSD 8 for the transitional + period to full network stack virtualization.</p> + + <p>Since the commit a few minor things have been fixed and work to + address most of the remaining old jails PRs has almost been + finished. The fallout from ports breakage has been handled with + help from Erwin Lansing from the PortMgr Team.</p> + </body> + </project> + + <project cat='proj'> + <title>BSD# Project</title> + + <contact> + <person> + <name> + <given>Phillip</given> + + <common>Neumann</common> + </name> + + <email>pneumann@gmail.com</email> + </person> + + <person> + <name> + <given>Romain</given> + + <common>Tartière</common> + </name> + + <email>romain@blogreen.org</email> + </person> + </contact> + + <links> + <url href="http://code.google.com/p/bsd-sharp/">The BSD# project on + Google-code</url> + + <url href="http://www.mono-project.org/">Mono (Open source .Net + Development Framework)</url> + </links> + + <body> + <p>The BSD# Project is devoted to porting the Mono .NET framework + and applications to the FreeBSD operating system.</p> + + <p>Because of a lack of time, Mono stalled at version 1.2.5 for + more than one year in the FreeBSD ports tree. However, things have + moved and the BSD# Team is proud to announce that the Mono ports are + about to be updated to 2.0.1. Ports depending on Mono will also be + updated to the latest available version at the same occasion.</p> + + <p>While the ports will be updated really soon now that FreeBSD 7.1 + has been released, impatient people can download and merge the BSD# ports + in their FreeBSD tree right now following the instructions provided + on the BSD# Project's page.</p> + </body> + + <help> + <task>Test and send feedback.</task> + + <task>Port Mono applications to FreeBSD.</task> + + <task>Build a debug live-image of FreeBSD so that Mono hackers + without a FreeBSD box can help us fixing bugs more + efficiency.</task> + </help> + </project> + + <project cat='kern'> + <title>PmcTools</title> + + <contact> + <person> + <name> + <given>Joseph</given> + + <common>Koshy</common> + </name> + + <email>jkoshy@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/PmcTools">Wiki Page</url> + + <url href="http://code.google.com/p/pmctools/issues">Bug List</url> + </links> + + <body> + <p>Support for Intel (TM) Atom/Core/Core2 family PMCs was added to + PmcTools. Bugs in the toolset were tracked down and fixed, and the + ABI between libpmc(3) and hwpmc(4) was reworked to hopefully be + more future proof.</p> + </body> + </project> + + <project cat='team'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ports/">The FreeBSD Ports + Collection</url> + + <url + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/"> + Contributing to the FreeBSD Ports Collection</url> + + <url href="http://portsmon.FreeBSD.org/index.html">FreeBSD ports + monitoring system</url> + + <url href="http://www.FreeBSD.org/portmgr/index.html">The FreeBSD + Ports Management Team</url> + + <url href="http://tinderbox.marcuscom.com">marcuscom + Tinderbox</url> + </links> + + <body> + <p>Most of the effort in the last quarter has been QA effort for + 6.4-RELEASE and 7.1-RELEASE. Since that time, we have once again + begun work on experimental package runs.</p> + + <p>The ports count has jumped to over 19,600. The PR count had + jumped during the freeze/slush cycle for release, but has now + dropped back to its usual count of around 900.</p> + + <p>GNOME has been updated to 2.24.3.</p> + + <p>KDE has been updated to 4.1.4.</p> + + <p>X.Org has been updated to 7.4.</p> + + <p>The following large changes are in the pipeline:</p> + + <ul> + <li>Introduction of Perl 5.10.</li> + </ul> + + <p>We are currently building packages for amd64-6, amd64-7, + amd64-8, i386-6, i386-7, i386-8, sparc64-6, and sparc64-7. Several + new i386 and sparc64 machines have been added, which has helped + speed up the builds. We especially appreciate the loan of a number + of sparc64 machines by Gavin Atkinson.</p> + + <p>We have added 5 new committers since the last report, and 2 + older ones have rejoined.</p> + </body> + + <help> + <task>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.</task> + + <task>Although we have added many maintainers, we still have over + 4,700 unmaintained ports (see, for instance, the list on portsmon). + (The percentage hovers around 24%.) We are always looking for + dedicated volunteers to adopt at least a few unmaintained ports. As + well, the packages on amd64 and sparc64 lag behind i386, and we + need more testers for those.</task> + </help> + </project> + + <project cat='arch'> + <title>FreeBSD/powerpc for AMCC/IBM PPC440/460</title> + + <contact> + <person> + <name> + <given>Rafal</given> + + <common>Jaworowski</common> + </name> + + <email>raj@semihalf.com</email> + </person> + </contact> + + <body> + <p>This work is bringing support for another Book-E style PowerPC + implementation (PPC440/460 core) embedded in a wide range of + system-on-chip devices. Current state highlights:</p> + + <ul> + <li>Locore kernel initialisation</li> + + <li>TLB handling</li> + + <li>Console (UART)</li> + + <li>Interrupts controller (UIC)</li> + + <li>USB controller (OHCI, EHCI)</li> + + <li>Multi user operation</li> + </ul> + + <p>The CPU layer (kernel start-up, TLB handling) is derived from + existing E500 support. Eventually the code will be re-factored so + that the common logic is shared between processor variations and + only the lowest-level routines are provided separately. A number of + drivers for peripherals integrated on the chip needs to be written + (Ethernet, PCI/PCI-Express, crypto engines, SATA, I2C, SPI, GPIO + and others).</p> + </body> + </project> + + <project cat='team'> + <title>Release Engineering</title> + + <contact> + <person> + <name> + <given>Release Engineering</given> + </name> + + <email>re@</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>Since the last status report both 7.1-RELEASE (5 January 2009) + and 6.4-RELEASE (28 November 2008) have been released. Starting + with 6.4-RELEASE, a new DVD ISO image called "dvd1" is provided + for amd64/i386. This image contains everything that is on the + CDROM discs. So "dvd1" can be used to do a full installation that + includes a basic set of packages, it has all of the documentation + for all supported languages, and it can be used for booting into + a "live CD-based filesystem" and system rescue mode. 6.4-RELEASE + was the last release of the 6.X branch, we have currently no plan + for any other 6.X release since most of the developers are + focused on 8-CURRENT and 7.X.</p> + + <p>The long awaited 7.1-RELEASE is out since 5th of January. This + release process was far too long from everyone's point of view. + Working on another release (6.4-RELEASE) at the same time was not + helping the things, but we are aware of many problems that need + to be worked on to ease the whole release process. As a + consequence, we are currently working on a new plan for future + 7.X (or 8.0) release. We plan to:</p> + + <ul> + <li>Reduce the freeze period of ports tree, the freeze should + occur near the end of the release process during RC cycle</li> + + <li>Change the way showstoppers are handled and do not stop a + release process for non-important issues or lack of + features.</li> + </ul> + + <p>Some work has also been done on the documentation build, we + want to provide a more flexible way to install docs (Handbook, + FAQ, etc.) and detach the documentation build from the release build to use + instead ports (packages). This should make release building + easier on slow architectures. Hopefully this switch will be done + for 7.2-RELEASE or 8.0-RELEASE.</p> + + <p>Regarding the time line, we still plan to release 8.0-RELEASE + in mid-June 2009. A time for the 7.2-RELEASE has not been set + yet.</p> + </body> + </project> + + <project cat='kern'> + <title>SD/MMC subsystem</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Motin</common> + </name> + + <email>mav@FreeBSD.org</email> + </person> + + <person> + <name> + <given>M. Warner</given> + + <common>Losh</common> + </name> + + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>FreeBSD mmc(4)/mmcsd(4) stack was improved to support all + MMC/SD card types existing now. Support was added for SD High + Capacity (SDHC) cards and MultiMediaCards (MMC) memory cards of + normal (up to 2GB) and high capacity. Support was also added + for 4/8bits wide buses, High Speed timings and multi-block + transfers allows to reach speeds up to 25MB/s (SD) and 52MB/s + (MMC) depending on which card and controller was used.</p> + + <p>Added SD Host Controller driver, sdhci(4), that implements + support for SD specification compatible PCI SD/MMC card readers + to be used with mmc(4)/mmcsd(4) stack. Driver supports PIO and + DMA transfers, 1/4bits buses, high speed timings, card + insert/remove detection and write protection.</p> + </body> + + <help> + <task>Many of the existing SD Host Controllers have undocumented + registers beyond SD specification. Some of them are unable to + detect the card without some additional initialization + implemented.</task> + </help> + </project> + + <project cat='kern'> + <title>HDA sound driver (snd_hda)</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Motin</common> + </name> + + <email>mav@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>snd_hda(4) audio driver was significantly improved to provide + better functionality according to High Definition Audio (HDA) and + Universal Audio Architecture (UAA) specifications.</p> + + <p>According to HDA specification, driver now supports multiple + codecs per HDA bus and multiple audio functional groups per + codec.</p> + + <p>According to UAA specification, driver now implements idea of + multiple logical audio devices per audio functional group. It + means, that depending on specific system needs, single audio + codec may provide several independent functions. For example, + main multichannel output, headset input/output and digital + SPDIF/HDMI audio input/output. Each of these functions are + provided as separate pcm devices and can be used independently.</p> + + <p>Comparing to ALSA and OSS HDA drivers which are heavily tuned + to support each specific codec in every specific system, this + driver uses advanced codec tracing logic which allows it to + support most of existing HDA codecs and systems without any + special tuning, using only information provided by system and + codec itself. This also allows user to widely reconfigure logical + audio devices in his system for his own needs, just by specifying + wanted audio connectors usage in device.hints.</p> + + <p>Also new driver implements SPDIF/HDMI digital audio, + suspend/resume and initial parts of multichannel support.</p> + </body> + + <help> + <task>Implement input-to-output audio bypass tracing for codecs + where bypass signal is not taken from main input mixer.</task> + + <task>Improve amplifiers control logic for cases where one signal + can be controlled in several points.</task> + + <task>Implement multichannel playback, that required significant + sound(4) modifications.</task> + </help> + </project> + + <project cat='arch'> + <title>FreeBSD/sparc64 UltraSPARC III support</title> + + <contact> + <person> + <name> + <given>Marius</given> + + <common>Strobl</common> + </name> + + <email>marius@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://people.FreeBSD.org/~marius/8.0-20090111-SNAP-sparc64-disc1.iso.gz" /> + </links> + + <body> + <p>FreeBSD 8.0-CURRENT now has basic support for sun4u-machines + based on UltraSPARC III and beyond. This is still a work in + progress though due to the diversity of these machines, hardware + errata and bugs in machine independent parts of FreeBSD showing up. + A install image with the latest code which in comparison to the + official snapshot 200812 contains more dcons(4) fixes, an isp(4) + working with 10160 and 12160 on sparc64, an endian-clean mpt(4) as + needed for the on-board controller found in Fire V440, workarounds + needed for Fire V880 and a fix for machines with more than 8GB of + RAM (tested with 16GB) are available at the above URL. Known working + machines so far are:</p> + + <ul> + <li>Blade 1000</li> + <li>Blade 1500</li> + <li>Blade 2000</li> + <li>Fire 280R</li> + <li>Fire V210</li> + <li>Fire V440 (except for the on-board NICs)</li> + <li>Fire V880</li> + <li>Netra 20/Netra T4</li> + </ul> + + <p>The stability of FreeBSD on these machines is en par with that + on pre-USIII-based sun4u-machines. Machines similar to the ones + above like for example Fire V240 should also just work with all + essential on-board devices, i.e. serial console, ATA/SCSI + controller and NIC, being supported. So far the intention is to MFC + this code in time for FreeBSD 7.2.</p> + </body> + + <help> + <task>Apart from serial devices, only cards supported by creator(4) + are currently usable as console, i.e. not even machfb(4) works in + sun4u-machines based on UltraSPARC III or beyond at this point (it + will trigger a RED state exception, which should not be that hard + to fix though), let alone XVR graphics cards.</task> + + <task>A driver for the Sun Cassini/Cassini+ as well as National + Semiconductor DP83065 Saturn Gigabit NICs found on-board for + example in Fire V440 and as add-on cards is under development but + still needs some work.</task> + + <task>There is no driver for controlling the fans in machines based + on the Excalibur board, yet. This means that Blade 1000/2000 are + not very usable as workstations so far due to the noise caused by + the fans permanently running at full speed.</task> + + <task>There is no support for host-to-PCI-Express or host-to-PCI-X + bridges so far, at least for the latter due to lack of access to + such machines. Adding support for the XMITS PCI-X bridges to the + existing schizo(4) should be rather straightforward, PCI-Express + will require a new driver and probably some additional tweaking + though.</task> + </help> + </project> + + <project cat='kern'> + <title>Network Stack Virtualization</title> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + + <common>Zeeb</common> + </name> + + <email>bz@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Marko</given> + + <common>Zec</common> + </name> + + <email>zec@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/Image">Wiki VImage overview + page.</url> + + <url + href="http://www.FreeBSDfoundation.org/project%20announcements.shtml#Bjoern"> + FreeBSD Foundation funding.</url> + </links> + + <body> + <p>The network stack virtualization project aims at extending the + FreeBSD kernel to maintain multiple independent instances of + networking state. This allows for networking independence between + jail-like environments, each maintaining its own private network + interfaces, IPv4 and IPv6 network and port address space, routing + tables, IPSec configuration, firewalls, and more.</p> + + <p>During BSDCan 2007 an initial commit plan had been worked out. + The Developer Summit at Cambridge in August brought the first parts + of VImage into the kernel. Marko gave a summary and outlook at + EuroBSDCon in Strasbourg. From autumn until December all but the + last step had been committed by Marko.</p> + + <p>Druing December Bjoern was able to work full time on VImage + because of FreeBSD Foundation funding. In addition to helping with + reviews, summarizing things on the Wiki, a virtual cross-over + Ethernet-like interface pair was developed to be able to bring + networking to an instances without the mandatory need of + netgraph.</p> + + <p>The next steps will be to bring in the most important last step + giving us multiple network stacks. After that all developers will + be able to help to find (and fix) bugs. Further subsystems not yet + addressed will need to be virtualized then. In addition to this + Jamie Gritton's management interface will be imported.</p> + </body> + </project> + + <project cat='proj'> + <title>VuXML generator</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Foster</common> + </name> + + <email>mark@foster.cc</email> + </person> + </contact> + + <links> + <url href="http://www.credentia.cc/services/vuxml/" /> + </links> + + <body> + <p>VuXML generator ("wizard") is intended for end-users who want to + generate VuXML (XML) definitions. Users can just fill out an HTML + form & this removes some of the guesswork and the learning + curve. The resulting VuXML can be submitted via send-pr as-is for + inclusion into the portaudit database.</p> + </body> + + <help> + <task>Option to submit generated XML into a "review" queue + somewhere (thus eliminate the need for users to run send-pr at + all)</task> + + <task>Option to generate OVAL definition in addition to + VuXML</task> + + <task>Option to generate ready-to-run pr (e.g send-pr -f + <outputfile>)</task> + </help> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2009-01-2009-03.xml b/en_US.ISO8859-1/htdocs/news/status/report-2009-01-2009-03.xml new file mode 100644 index 0000000000..18a832d949 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2009-01-2009-03.xml @@ -0,0 +1,982 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status +Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2009-01-2009-03.xml,v 1.7 2009/05/09 15:44:40 brd Exp $ --> +<report> + <date> + <month>January-March</month> + + <year>2009</year> + </date> + + <section> + <title>Introduction</title> + + <p>Since the last Status Reports there has been interesting progress + in FreeBSD Development. FreeBSD 7.2 was released just a few days ago. + Some of the highlights include: Support for superpages in the FreeBSD + Virtual Memory subsystem. The FreeBSD Kernel Virtual Address space + has been increased to 6GB on amd64. An updated jail(8) subsystem that + supports multi-IPv4/IPv6/noIP and much more. Lots of FreeBSD + Developers are in Ottawa, Canada attending the FreeBSD Developer + Summit that is before BSDCan. BSDCan officially starts tomorrow and + should cover lots of interesting topics, see the + <a href="http://www.bsdcan.org/2009/">BSDCan Website</a> + + for more information.</p> + + <p>Thanks to all the reporters for the excellent work! We hope you + enjoy reading.</p> + </section> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>team</name> + + <description>FreeBSD Team Reports</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <category> + <name>soc</name> + + <description>Google Summer of Code</description> + </category> + + <project cat='team'> + <title>FreeBSD BugBusting Team</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>bugmeister@</email> + </person> + + <person> + <name> + <given>Remko</given> + + <common>Lodder</common> + </name> + + <email>bugmeister@</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/support.html#gnats" /> + + <url href="http://wiki.FreeBSD.org/BugBusting" /> + + <url href="http://people.FreeBSD.org/~linimon/studies/prs/" /> + + <url + href="http://people.freebsd.org/~linimon/studies/prs/recommended_prs.html" /> + </links> + + <body> + <p>We continue to classify PRs as they arrive, with 'tags' + corresponding to the kernel subsystem, or man page references for + userland PRs. These tags, in turn, produce lists of PRs sorted both + + <a + href="http://people.freebsd.org/~linimon/studies/prs/pr_tag_index.html"> + by tag</a> + + and + <a + href="http://people.freebsd.org/~linimon/studies/prs/pr_manpage_index.html"> + by manpage</a> + </p> + + <p>Mark Linimon (linimon@) has created + <a href="http://people.freebsd.org/~linimon/annotated_prs.re.html"> + special reports for the Release Engineering Team</a> + + to help focus on regressions and other areas of interest relating + to the release of FreeBSD 7.2 in the coming weeks. This is a + refinement of the + <a + href="http://people.freebsd.org/~linimon/annotated_prs.sample.html"> + 'customized reports for developers'</a> + + announced in the last status report.</p> + + <p>A full list of all the + <a href="http://people.freebsd.org/~linimon/studies/prs/"> + automatically generated reports</a> + + is also available. Any recommendations for reports which do not + currently exist but which would be beneficial are welcomed.</p> + + <p>Mark Linimon also continues attempting to define the general + problem and investigating possible new work flow models, and will be + presenting on the subject at BSDCan.</p> + + <p>The list of + <a + href="http://people.freebsd.org/~linimon/studies/prs/recommended_prs.html"> + PRs recommended for committer evaluation</a> + + by the BugBusting team continues to receive new additions. This + list contains PRs, mostly with patches, that the BugBusting team + feel are probably ready to be committed as-is, or are probably + trivially resolved in the hands of a committer with knowledge of + the particular subsystem. All committers are invited to take a look + at this list whenever they have a spare 5 minutes and wish to close + a PR.</p> + + <p>Since the last status report, the number of open bugs + continued to hover around the 5600 mark, although has began to rise + with the 7.2 ports freeze.</p> + + <p>As always, more help is appreciated, and committers and + non-committers alike are invited to join us on #freebsd-bugbusters + on EFnet and help close stale PRs or commit patches from valid + PRs.</p> + </body> + + <help> + <task>Try to find ways to get more committers helping us with + closing PRs that the team has already analyzed.</task> + + <task>Think of some way for committers to only view PRs that have + been in some way 'vetted' or 'confirmed'.</task> + + <task>Generate more publicity for what we've already got in place, + and for what we intend to do next.</task> + + <task>Define new categories, classifications, and states for PRs, + that will better match our work flow (in progress).</task> + </help> + </project> + + <project cat='proj'> + <title>Clang replacing GCC in the base system</title> + + <contact> + <person> + <name> + <given>Ed</given> + + <common>Schouten</common> + </name> + + <email>ed@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Roman</given> + + <common>Divacky</common> + </name> + + <email>rdivacky@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Pawel</given> + + <common>Worach</common> + </name> + + <email>pawel.worach@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/BuildingFreeBSDWithClang"> + Building FreeBSD with Clang</url> + + <url href="http://git.hoeg.nl/?p=llvm-bmake">Clang patchset</url> + + <url href="http://clang.llvm.org/">Clang website</url> + </links> + + <body> + <p>The last 3-4 months we've been working together with the LLVM + developers to discuss any bugs and issues we are experiencing with + their Clang compiler frontend. The FreeBSD project is looking at + the possibility to replace GCC with Clang as a system compiler. It + can compile 99% of the FreeBSD world and can compile booting kernel + on i386/amd64 but it still contains bugs and its C++ support is + still immature.</p> + + <p>Ed is maintaining a patchset for the FreeBSD sources to replace + cc(1) by a Clang binary and bootstrap almost all sources with the + Clang compiler.</p> + + <p>The LLVM developers are very helpful fixing most of the bugs + we've reported (over 100). Unfortunately we are currently blocked + on some bug reports that prevent us from building libc, libm, + libcrypto and various CDDL libraries with Clang but the FreeBSD + kernel itself compiles and boots.</p> + </body> + + <help> + <task>Testing Clang with compilation of various applications and + reporting bugs.</task> + + <task>Testing the llvm-bmake branch to find more bugs.</task> + + <task>Arranging an experimental ports build.</task> + </help> + </project> + + <project cat='docs'> + <title>Hungarian Documentation Project</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gábor</given> + + <common>Páli</common> + </name> + + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/hu">Hungarian Web Page for + FreeBSD</url> + + <url href="http://www.FreeBSD.org/doc/hu">Hungarian Documentation + for FreeBSD</url> + + <url href="http://wiki.FreeBSD.org/HungarianDocumentationProject"> + The FreeBSD Hungarian Documentation Project's Wiki Page</url> + + <url + href="http://p4web.freebsd.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83"> + Perforce Depot for the FreeBSD Hungarian Documentation + Project</url> + </links> + + <body> + <p>We are proud to announce that the FreeBSD Hungarian web pages + have been extended by the following items:</p> + + <ul> + <li>Project news entries, staring from 2009 (HTML, RSS, RDF)</li> + + <li>Press releases, starting from 2008 (HTML, RSS)</li> + + <li>Events, starting from 2009 (HTML, RSS)</li> + + <li>Security advisories (HTML, RSS)</li> + </ul> + + <p>We are still hoping that having the + <a href="http://www.freebsd.org/doc/hu/books/fdp-primer/">FDP + Primer</a> + + translated will encourage others to help our work. Feel free to + contribute, every submitted line of translation or feedback is + appreciated and is highly welcome. For more information on how to + contribute, please read the project's + <a href="http://www.freebsd.org/hu/docproj/hungarian.html"> + introduction</a> + + (in Hungarian).</p> + </body> + + <help> + <task>Translate news entries, press releases.</task> + + <task>Translate Release Notes for -CURRENT and 8.X.</task> + + <task>Translate articles.</task> + + <task>Translate web pages.</task> + + <task>Read the translations, send feedback.</task> + </help> + </project> + + <project cat='docs'> + <title>German Documentation Project</title> + + <contact> + <person> + <name> + <given>Johann</given> + + <common>Kois</common> + </name> + + <email>jkois@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Martin</given> + + <common>Wilke</common> + </name> + + <email>miwi@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="https://doc.bsdgroup.de" /> + </links> + + <body> + <p> + <p>In February 2009 the German version of the FreeBSD Developer's + handbook went online. Additionally we managed to update large + areas of the FAQ thanks to the contributions of Benedict + Reuschling.</p> + + <p>The website (at least the areas we see as relevant for a + translation) is translated and updated constantly.</p> + + <p>More volunteers are always welcome of course, as there is + still plenty of work to be done.</p> + </p> + </body> + + <help> + <task>Update the existing documentation set (especially the + handbook).</task> + + <task>Read the translations. Check for problems/mistakes. Send + feedback.</task> + </help> + </project> + + <project cat='soc'> + <title>BSD-licensed text-processing tools</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc"> + Perforce repository</url> + </links> + + <body> + <p>Currently, grep is finished and is only waiting for a portbuild + test. It is known to be more or less feature complete, while it is + much smaller than the GNU version.</p> + + <p>As for sort, there has been some progress with the complete + rewrite and it is lacking few options. Performance is to be + measured, as well.</p> + </body> + + <help> + <task>Test grep on pointyhat.</task> + + <task>Complete sort with the missing features.</task> + + <task>Do performance measurements for sort and look for possible + optimization opportunities.</task> + + <task>Test sort on pointyhat.</task> + </help> + </project> + + <project cat='proj'> + <title>OpenBSM</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <given>TrustedBSD audit mailing list</given> + </name> + + <email>trustedbsd-audit@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.openbsm.org/">OpenBSM web page</url> + </links> + + <body> + <p>The TrustedBSD Project has now released OpenBSM 1.1, the second + production release of the OpenBSM code base. OpenBSM 1.1 has been + merged to FreeBSD 8-CURRENT, and will be merged to 7-STABLE before + FreeBSD 7.3. Major changes since OpenBSM 1.0 include: + <ul> + <li>Trail files now include the host where the trail is + generated. Crash recovery has been improved. Trail expiration + based on size and date is now supported; by default trail files + will be expired after 10MB of trails. The default individual + trail limit is now 2MB.</li> + + <li>Mac OS X Snow Leopard is now a fully supported platform; + launchd(8) can now be used to launchd auditd(8). Command line + tools and libraries are now supported on Mac OS X Leopard.</li> + + <li>Extended header tokens are now supported, allowing audit + trails to be tagged with a host identifier. IPv6 addresses are + now supported in subject tokens. BSM token and record types have + been further synchronized to OpenSolaris; support for many new + system calls has been added. Local errors and socket types are + mapped to and from BSM values.</li> + </ul> + + Since the last test release, OpenBSM 1.1 beta 1, 32/64-bit + compatibility has been fixed for the auditon(2) system call. A + default "expire-after" of 10MB is now set in audit_control(5). + Local fcntl(2) arguments are now mapped to wire BSM versions using + new APIs. The audit_submit(3) man page has been fixed. A new audit + event class has been added for post-login authentication and access + control events.</p> + </body> + + <help> + <task>Migrate to sbufs in token-encoding.</task> + + <task>Support for auditing NFS RPCs.</task> + </help> + </project> + + <project cat='arch'> + <title>FreeBSD/powerpc G5 Support</title> + + <contact> + <person> + <name> + <given>Nathan</given> + + <common>Whitehorn</common> + </name> + + <email>nwhitehorn@freebsd.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>FreeBSD 8.0-CURRENT now has support for PowerPC CPUs operating + in the 64-bit bridge mode. This includes the PowerPC 970 (G5) as + well as the POWER3 and POWER4. Currently only Apple systems are + known to work.</p> + </body> + + <help> + <task>IBM systems currently are not supported due to missing + northbridge support.</task> + + <task>Software fan control on SMU-based Apple G5 systems (G5 iMac, + later Powermac G5) is not available.</task> + </help> + </project> + + <project cat='proj'> + <title>Release Engineering</title> + + <contact> + <person> + <name> + <given>Release Engineering Team</given> + </name> + + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/" /> + </links> + + <body> + <p>The Release Engineering Team (with lots of help from lots of + other people) released FreeBSD 7.2 on May 4th, 2009. During this + period we have also begun reminding developers of the upcoming + FreeBSD 8.0 release cycle which is scheduled to begin in early June + 2009 with release targeted at early September 2009.</p> + </body> + </project> + + <project cat='docs'> + <title>Dutch Documentation Project</title> + + <contact> + <person> + <name> + <given>Remko</given> + + <common>Lodder</common> + </name> + + <email>remko@FreeBSD.org</email> + </person> + + <person> + <name> + <given>René</given> + + <common>Ladan</common> + </name> + + <email>rene@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/DutchDocumentationProject"> + Overview of the project and current status</url> + + <url href="http://www.freebsd.org/doc/nl/">Released + documentation</url> + + <url + href="http://p4web.freebsd.org/@md=d&cd=//&c=pFl@//depot/projects/docproj_nl/?ac=83"> + Perforce repository</url> + </links> + + <body> + <p>The FreeBSD Dutch Documentation Project is an ongoing project + to translate FreeBSD Documentation into the Dutch language.</p> + + <p>The translation of the Handbook was completed last January. It + is kept up-to-date with the English version. Furthermore five + articles and the + <url href="http://www.evilcoder.org/freebsd-flyer.pdf">flyer</url> + + have been translated.</p> + + <p>Some initial work has been done to translate the website, but + most likely more translators are needed to fully realize it.</p> + </body> + + <help> + <task>Recruit more translators.</task> + + <task>Keep the translations up-to-date with the English + versions.</task> + + <task>Finish the translation of the FAQ.</task> + + <task>Translate more articles and maybe some books.</task> + </help> + </project> + + <project cat='proj'> + <title>Sysinfo - a set of scripts which document your system</title> + + <contact> + <person> + <name> + <given>Daniel</given> + + <common>Gerzo</common> + </name> + + <email>danger@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://danger.rulez.sk/index.php/2009/04/14/sysinfo-a-set-of-scripts-which-document-your-freebsd-system/"> + Public release announcement</url> + + <url href="https://forums.freebsd.org/showthread.php?p=19321">The + FreeBSD Forums thread</url> + </links> + + <body> + <p> + <em>Sysinfo</em> + + is a shell script, the purpose of which is to automatically gather system + information and document the hardware and software configuration of the + given host system. The goal is to provide a system operator with + descriptive information about an unknown FreeBSD installation.</p> + + <p>It consists of several modules (also shell scripts), thus is + easily extensible and provides an easy way to inspect overall + system configuration.</p> + + <p>It has been written as part of my Bachelor thesis and its + development is a work in progress. Therefore, I would appreciate if + you could provide me with some feedback as I will defend my thesis + soon. Your feedback is welcome at the + <a href="https://forums.freebsd.org/showthread.php?p=19321"> + forums</a> + + , or alternatively you can send me a private email.</p> + + <p>The tool itself can now be installed using the Ports tree from + the + <a href="http://www.freshports.org/sysutils/sysinfo"> + sysutils/sysinfo</a> + + port.</p> + </body> + + <help> + <task>Receive additional feedback.</task> + + <task>Perform more testing.</task> + + <task>Extend and improve the tool.</task> + </help> + </project> + + <project cat='proj'> + <title>TrustedBSD MAC Framework in GENERIC</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <given>TrustedBSD discussion mailing list</given> + </name> + + <email>trustedbsd-discuss@TrustedBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.trustedBSD.org/mac.html">TrustedBSD MAC home + page</url> + </links> + + <body> + <p>There is on-going work to allow "options MAC" to be included in + the GENERIC kernel for 8.0. This primarily consists of performance + work to reduce overhead when policies are used, and eliminate when + none are configured. Work to date includes: + <ul> + <li>The MAC Framework now detects which object types are labeled + by policies, and MAC label storage is not allocated when it won't + be used.</li> + + <li>Add MAC Framework DTrace probes so allow more easy analysis + of MAC Framework and policy interactions.</li> + + <li>Eliminate mutex-protected reference count used to prevent + module unload during entry point invocation, and replace with an + sx lock and an rwlock, respectively for long-sleepable and + short-sleepable entry points, significantly lowering the overhead + of entering the MAC Framework. If no dynamic policies are loaded, + no locking overhead is taken.</li> + </ul> + </p> + </body> + + <help> + <task>Move to rmlocks for non-sleepable entry points to reduce + cache line thrashing under load.</task> + + <task>Macroize invocation of MAC Framework entry points from the + kernel, and perform caller-side determination of whether MAC is + enabled in order to avoid additional function call overhead in the + caller path if MAC is disabled.</task> + </help> + </project> + + <project cat='arch'> + <title>FreeBSD/sparc64 UltraSPARC III support</title> + + <contact> + <person> + <name> + <given>Marius</given> + + <common>Strobl</common> + </name> + + <email>marius@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Like announced in the previous status report, support for + sun4u-machines based on UltraSPARC III and beyond has been MFC'ed + to stable/7 (the last missing piece was r190297) and thus will be + present in the upcoming 7.2-RELEASE and can be already tested with + 7.2-RC1. Additionally, as of r191076 machfb(4) has been fixed to + work with UltraSPARC III and beyond, that fix unfortunately did not + make it into 7.2-RC1 but will be in the final version. The X.Org + 7.4 and Firefox ports as well as some other gecko-based ones like + Seamonkey once again have been fixed to also work and package on + sparc64, including on UltraSPARC III and UltraSPARC IIIi based + machines equipped with cards driven by creator(4) or machfb(4). The + driver for the Sun Cassini/Cassini+ as well as National + Semiconductor DP83065 Saturn Gigabit NICs found on-board for + example in Fire V440 and as add-on cards is coming along nicely, + the last thing which needs to be implemented before it can hit + CURRENT is support for jumbo frames.</p> + </body> + </project> + + <project cat='proj'> + <title>VFS/NFS DTrace Probes</title> + + <contact> + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>A new DTrace provider, dtnfsclient, has been added to the + FreeBSD 8.x kernel, and will be merged to 7.x before 7.3. The + following probes are available: + <ul> + <li>nfsclient:{nfs2,nfs3}:{procname}:start - NFSv2 and NFSv3 RPC + start probes</li> + + <li>nfsclient:{nfs2,nfs3}:{procname}:done - NFSv2 and NFSv3 RPC + done probes</li> + + <li>nfsclient:accesscache:: - NFS access cache + flush/hit/miss/load probes</li> + + <li>nfsclient:attrcache:: - NFS attribute cache + flush/hit/miss/done</li> + </ul> + + In addition, a number of VFS probes have been added: + <ul> + <li>vfs:vop:{vopname}:entry - VOP entry probe</li> + + <li>vfs:vop:{vopname}:return - VOP return probe</li> + + <li>vfs:namei:lookup:entry - VFS name lookup entry probe</li> + + <li>vfs:namei:lookup:return - VFS name lookup return probe</li> + + <li>vfs:namecache:*:* - VFS namecache + enter/enter_negative/fullpath_enter/fullpath_hit/fullpath_miss/fullpath_return/lookup_hit/lookup_hit_negative/lookup_miss/purge/purge_negative/purgevfs/zap/zap_negative + probes</li> + </ul> + + These probes make it much easier to trace NFS and VFS events.</p> + </body> + + <help> + <task>Add VFSOP tracing.</task> + + <task>Add RPC-layer tracing, such as RPC retransmits.</task> + + <task>Provide decoded NFS RPCs in order to expose transaction IDs + and file handles.</task> + </help> + </project> + + <project cat='proj'> + <title>VirtualBox on FreeBSD</title> + + <contact> + <person> + <name> + <given>Beat</given> + + <common>Gaetzi</common> + </name> + + <email>beat@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Bernhard</given> + + <common>Froehlich</common> + </name> + + <email>decke@bluelife.at</email> + </person> + + <person> + <name> + <given>Dennis</given> + + <common>Herrmann</common> + </name> + + <email>dhn@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Martin</given> + + <common>Wilke</common> + </name> + + <email>miwi@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://miwi.bsdcrew.de/2009/05/virtualbox-on-freebsd/"> + Virtualbox on FreeBSD Announcement</url> + + <url + href="http://miwi.bsdcrew.de/2009/05/virtualbox-on-freebsd-first-screenshots/"> + VirtualBox first Screenshots</url> + + <url + href="http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001369.html"> + SUCCESS from Bernhard Froehlich</url> + </links> + + <body> + <p>After the first mail from Alexander Eichner on the vbox-dev + mailinglist, we started the work on a VirtualBox port. 6 Days was + needed to get VirtualBox to start with over 20 patches. We'd like + to say thanks to Alexander Eichner, all the VirtualBox Developers, + Gustau Perez and Ulf Lilleengen. If you like to play with the + current port you can checkout the port <a + href="http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox/"> + here</a>. + + Please do not ping us about any problems, we know about a lot and + are still working to get them all solved before we do an official + call for testing.</p> + </body> + + <help> + <task>Fix kernel crashes on 7.2-RELEASE.</task> + + <task>Code cleanup.</task> + + <task>Fix errors on AMD64.</task> + + <task>Fix user/permission problems.</task> + </help> + </project> + + <project cat='proj'> + <title>Device mmap() Extensions</title> + + <contact> + <person> + <name> + <given>John</given> + + <common>Baldwin</common> + </name> + + <email>jhb@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/~jhb/pat/" /> + </links> + + <body> + <p>GPU device drivers are increasingly requiring more sophisticated + support for mapping objects into both userland and the kernel. For + example, memory used for textures often needs to be mapped + Write-Combining rather than Write-Back. I have recently created + three patches to provide several extensions.</p> + + <p>The first patch allows device drivers to use a different VM + object to back specific mmap() calls instead of always using the + device pager. The second patch introduces a new VM object type that + can map an arbitrary set of physical address ranges. This can be + used to let userland mmap PCI BARs, etc. The third patch allows + memory mappings to use different caching modes (e.g. + Write-Combining or Uncacheable).</p> + + <p>Together I believe these patches provide the remaining pieces + needed for an Nvidia amd64 driver. They will also be useful for + future Xorg DRM support as well. The current set of patches can be + safely merged back to 7.x as well.</p> + + <p>Currently I am waiting for review and feedback from several + folks. I am hopeful that these patches will be in HEAD soon, prior + to the 8.0 freeze.</p> + </body> + </project> +</report> + diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2009-04-2009-09.xml b/en_US.ISO8859-1/htdocs/news/status/report-2009-04-2009-09.xml new file mode 100644 index 0000000000..44020164e0 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2009-04-2009-09.xml @@ -0,0 +1,2199 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status +Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2009-04-2009-09.xml,v 1.15 2009/10/12 18:06:33 gabor Exp $ --> +<report> + <date> + <month>April-September</month> + + <year>2009</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report covers FreeBSD related projects between April and + September 2009. During that time a lot of work has been done on + wide variety of projects, including the Google Summer of Code + projects. The BSDCan conference was held in Ottawa, CA, in May. + The EuroBSDCon conference was held in Cambridge, UK, in September. + Both events were very successful. + A new major version of FreeBSD, 8.0 is to be released soon. + If you are wondering what's new in this long-awaited release, read + Ivan Voras' excellent <a + href="http://ivoras.sharanet.org/freebsd/freebsd8.html">summary</a>.</p> + + <p>Thanks to all the reporters for the excellent work! We hope you + enjoy the reading.</p> + + <p>Please note that the next deadline for submissions covering + reports between October and December 2009 is January 15th, + 2010.</p> + </section> + + <category> + <name>soc</name> + + <description>Google Summer of Code</description> + </category> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>team</name> + + <description>FreeBSD Team Reports</description> + </category> + + <category> + <name>net</name> + + <description>Network Infrastructure</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='soc'> + <title>libnetstat(3) - networking statistics (Summer of Code 2009)</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Páli</common> + </name> + + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/PGJSoc2009">Wiki page</url> + <url href="http://p4web.freebsd.org/@md=d&cd=//&c=McZ@//depot/projects/soc2009/pgj_libstat/?ac=83">Perforce depot</url> + </links> + + <body> + <p>The libnetstat(3) project provides a user-space library API to monitor + networking functions with the following benefits:</p> + + <ul> + <li>ABI-robust interface making use of accessor functions in + order to divorce monitoring applications from kernel or user ABI + changes.</li> + + <li>Supports running 32-bit monitoring tools on top of a 64-bit + kernel.</li> + + <li>Improved consistency for both kvm(3) and sysctl(3) when + retrieving information.</li> + </ul> + + <p>The supported abstractions are as follows:</p> + + <ul> + <li>Active sockets and socket buffers</li> + <li>Network interfaces and multicast interfaces</li> + <li>mbuf(9) statistics</li> + <li>bpf(4) statistics</li> + <li>Routing statistics, routing tables, multicast routing</li> + <li>Protocol-dependent statistics</li> + </ul> + + <p>There is a sample application, called nettop(8), which provides a + simple ncurses-based top(1)-like interface for monitoring active + connections and network buffer allocations via the library. A + modified version of netstat(1) has also been created to use + libnetstat(3) as much as possible.</p> + </body> + </project> + + <project cat='soc'> + <title>pefs - stacked cryptographic filesystem (Summer of Code 2009)</title> + + <contact> + <person> + <name> + <given>Gleb</given> + + <common>Kurtsou</common> + </name> + + <email>gk@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Stanislav</given> + + <common>Sedov</common> + </name> + + <email>stas@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://blogs.freebsdish.org/gleb/">Gleb's Blog</url> + + <url href="http://wiki.freebsd.org/SOC2009GlebKurtsov">Project page in FreeBSD wiki</url> + </links> + + <body> + <p>Pefs is a kernel level filesystem for transparently encrypting + files on top of other filesystems (like zfs or ufs). It adds no + extra information into files (unlike others), doesn't require + cipher block sized io operations, supports per directory/file keys + and key chaining, uses unique per file tweak for encryption. + Supported algorithms: AES, Camellia, Salsa20. The code is ready for + testing.</p> + </body> + + <help> + <task>Implement encrypted name lookup/readir cache</task> + + <task>Optimize sparse files handling and file resizing</task> + </help> + </project> + + <project cat='proj'> + <title>BSD# Project</title> + + <contact> + <person> + <name> + <given>Romain</given> + + <common>Tartière</common> + </name> + + <email>romain@blogreen.org</email> + </person> + </contact> + + <links> + <url href="http://code.google.com/p/bsd-sharp/">The BSD# project on + Google code</url> + + <url href="http://www.mono-project.org/">Mono (Open source .NET + Development Framework)</url> + </links> + + <body> + <p>The BSD# Project is devoted to porting the Mono .NET framework + and applications to the FreeBSD operating system.</p> + + <p>During the past year, the BSD# Team continued to track the Mono + development and the lang/mono port have almost always been + up-to-date (we however had to skip mono-2.2 because of some + regression issues in this release). Most of our patches have been + merged in the mono trunk upstream, and should be included in the + upcoming mono-2.6 release.</p> + + <p>In the meantime, a few more .NET related ports have been updated + or added to the FreeBSD ports tree. These ports include:</p> + + <ul> + <li>www/xsp and www/mod_mono that make it possible to use FreeBSD + for hosting ASP.NET application;</li> + + <li>lang/boo, a CLI-targeted programming language similar to + Python;</li> + + <li>lang/mono-basic, the Visual Basic .NET Framework for + Mono;</li> + + <li>devel/monodevelop, an Integrated Development Environment for + .NET;</li> + +<!--li>deskuils/gnome-do, an all-in-one launch-box to perform actions quickly with your computer;</li--> + <li>and much more...</li> + </ul> + </body> + + <help> + <task>Test mono ports and send feedback (we are especially + interested in tests where NOPORTDOCS / WITH_DEBUG is + enabled).</task> + + <task>Port the mono-debugger to FreeBSD.</task> + + <task>Build a debug live-image of FreeBSD so that Mono hackers + without a FreeBSD box can help us fixing bugs more + efficiently.</task> + </help> + </project> + + <project cat='proj'> + <title>The Newcons project</title> + + <contact> + <person> + <name> + <given>Ed</given> + + <common>Schouten</common> + </name> + + <email>ed@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/Newcons">Wiki page</url> + + <url href="http://people.freebsd.org/~ed/newcons/patches/"> + Patchset</url> + </links> + + <body> + <p>Some time ago I started writing a new driver for the FreeBSD + kernel called vt(4), which is basically a replacement of syscons. + There is still a lot of work that needs to be done but it is + probably useful to mention what it does (and what does not).</p> + + <p>Right now there are just two graphics drivers for vt(4), namely + a VGA driver for i386 and amd64 and a Microsoft Xbox graphics + driver (because it was so easy to implement). I still have to figure + out what I am going to do with VESA, because maybe it is better to + just ignore VESA and figure out how hard it is to extend DRM to + interact with vt(4).</p> + + <p>Some random features: it already supports both Unicode (UTF-8) + input and output, it is MPSAFE and supports per-window graphical + fonts of variable dimensions, containing an almost infinite amount + of glyphs (both bold and regular).</p> + </body> + + <help> + <task>Research needs to be done on DRM's codebase.</task> + + <task>Syscons should already be migrated to TERM=xterm to make + switching between drivers a bit easier.</task> + </help> + </project> + + <project cat='proj'> + <title>libprocstat(3) - process statistics</title> + + <contact> + <person> + <name> + <given>Stanislav</given> + <common>Sedov</common> + </name> + <email>stas@FreeBSD.org</email> + </person> + <person> + <name> + <given>Ulf</given> + <common>Lilleengen</common> + </name> + <email>lulf@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://svn.freebsd.org/viewvc/base/projects/libprocstat/">libprocstat repository</url> + </links> + + <body> + <p>The libprocstat project is an ongoing effort to develop a library that can + be used to retrieve information about running processes and + open files in the uniform and platform-independent way both from + a running system or from core files. This will facilitate the + implementation of file- or process-monitoring applications like + lsof(1), fstat(1), fuser, etc. The libprocstat repository contains a + preliminary version of the library. It also includes rewrites + of the fstat and the fuser + utilities ported to use this library instead of retrieving all + the required information via the kvm(3) interface; one of the + important advantages of the versions that use libprocstat is + that these utilities are ABI independent.</p> + </body> + + <help> + <task> + Implement KVM-based namecache lookup to retrieve filesystem paths + associated with file descriptors and VM objects. + </task> + <task> + Analyze possible ways of exporting file and process information + from the kernel in an extensible and ABI-independent way. + </task> + </help> + </project> + + <project cat='proj'> + <title>New BSD licensed debugger</title> + + <contact> + <person> + <name> + <given>Doug</given> + <common>Rabson</common> + </name> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/TheBsdDebugger">Wiki page</url> + <url href="http://people.freebsd.org/~dfr/ngdb.git">Repository</url> + <url href="http://wiki.freebsd.org/200909DevSummit?action=AttachFile&do=view&target=NGDB-200909.pdf">Slides</url> + </links> + + <body> + <p>I have been working recently on writing a new debugger, + primarily for the FreeBSD platform. For various reasons, I have + been writing it in a relatively obscure C-like language called + D.</p> + + <p>So far, I have a pretty useful (if a little raw at the edges) + command line debugger which supports ELF, Dwarf debugging + information and (currently) 32 bit FreeBSD and Linux. The + engine includes parsing and evaluation of arbitrary C expressions + along with the usual debugging tools such as breakpoints, source + code listing, single-step etc. All the code is new and BSD + licensed. Currently, the thing supports userland debugging of + i386 targets via ptrace and post-mortem core file debugging of + the same. I will be adding amd64 support real soon (TM) and + maybe support for GDB's remote debugging protocol later.</p> + </body> + </project> + + <project cat='proj'> + <title>Clang replacing GCC in the base system</title> + + <contact> + <person> + <name> + <given>Ed</given> + + <common>Schouten</common> + </name> + + <email>ed@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Roman</given> + + <common>Divacky</common> + </name> + + <email>rdivacky@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Pawel</given> + + <common>Worach</common> + </name> + + <email>pawel.worach@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/BuildingFreeBSDWithClang" /> + </links> + + <body> + <p>The clang@FreeBSD team presents the status of clang/LLVM being + able to compile FreeBSD system. The current status is:</p> + + <ul> + <li>i386 - kernel boots, world needs little hacks but works</li> + + <li>amd64 - kernel boots, world needs little hacks but works</li> + + <li>ppc - broken because of unknown RTLD bug</li> + + <li>other - unknown</li> + </ul> + + <p>All other platforms are untested.</p> + + <p>A lot has happened over the spring/summer: amd64 got proper + mcmodel=kernel support, compiler-rt has been introduced (paving the way + for libgcc replacement), we have run two experimental port builds to see + how clang does there. The C++ support is able to parse devd.cc without + warnings. We have got the kernel working with -O2. FreeBSD has been promoted + to be an officially supported plaform in LLVM. As a result of all this + work, many parts of FreeBSD that did not compile before now build + without problems.</p> + </body> + + <help> + <task>The "ClangBSD" branch of FreeBSD got a little stale and has not + been updated for a while.</task> + + <task>We also need to get some important fixes + into LLVM to get libc compiling and some other smaller issues.</task> + + <task>We can still appreciate more testers on minor platforms (mostly on + ARM, PPC and MIPS, but testing on other platforms is also welcome).</task> + </help> + </project> + + <project cat='proj'> + <title>Grand Central Dispatch - FreeBSD port</title> + + <contact> + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + <person> + <name> + <given>Stacey</given> + <common>Son</common> + </name> + <email>sson@FreeBSD.org</email> + </person> + <person> + <name> + <given>libdispatch mailing list</given> + </name> + <email>libdispatch-dev@lists.macosforge.org</email> + </person> + </contact> + + <links> + <url href="http://libdispatch.macosforge.org/">GCD / libdispatch web page</url> + </links> + + <body> + <p>We have ported libdispatch, Apple's Grand Central Dispatch event + and concurrency framework to FreeBSD:</p> + + <ul> + <li>Added new kqueue primitives required to support GCD, such + as EVFILT_USER and EV_TRIGGER</li> + <li>Created autoconf and automake build framework for libdispatch</li> + <li>Modified libdispatch to use POSIX semaphores instead of + Mach semaphores</li> + <li>Adapted libdispatch to use portable POSIX time routines</li> + </ul> + + <p>Jordan Hubbard has also prepared a blocks-aware clang compiler + package for FreeBSD. When compiled with clang, libdispatch + provides blocks-based, as well as function-based callbacks.</p> + + <p>The port was presented at the FreeBSD Developer Summit in + Cambridge, UK in September, and slides are online on the devsummit + wiki page. A FreeBSD port is now available in the Ports Collection. + After FreeBSD 8.0-RELEASE has shipped, the new kqueue primitives will be + MFC'd so that libdispatch works out of the box on FreeBSD 8.1-RELEASE.</p> + </body> + + <help> + <task> + Complete porting of libdispatch test suite to FreeBSD. + </task> + <task> + Investigate pthread work queue implementation for FreeBSD. + </task> + <task> + Evaluate performance impact of some machine-dependent and + OS-dependent optimizations present in the Mac OS X version of + libdispatch to decide if they should be done for other + platforms and OS's. + </task> + <task> + Explore whether FreeBSD base operating system tools would benefit + from being modified to use libdispatch. + </task> + </help> + </project> + + <project cat='proj'> + <title>VirtualBox on FreeBSD</title> + + <contact> + <person> + <name> + <given>Beat</given> + <common>Gaetzi</common> + </name> + <email>beat@FreeBSD.org</email> + </person> + <person> + <name> + <given>Bernhard</given> + <common>Froehlich</common> + </name> + <email>decke@bluelife.at</email> + </person> + <person> + <name> + <given>Dennis</given> + <common>Herrmann</common> + </name> + <email>dhn@FreeBSD.org</email> + </person> + <person> + <name> + <given>Juergen</given> + <common>Lock</common> + </name> + <email>nox@FreeBSD.org</email> + </person> + <person> + <name> + <given>Martin</given> + <common>Wilke</common> + </name> + <email>miwi@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/VirtualBox" /> + </links> + + <body> + <p>VirtualBox has been committed to the Ports tree and synchronized + with the latest trunk version from Sun. Several known + problems are already fixed and some new features have been + added:</p> + + <ul> + <li>VT-x support</li> + <li>Bridging support (Big Thanks to Fredrik Lindberg)</li> + <li>Host Serial Support</li> + <li>ACPI Support</li> + <li>Host DVD/CD access</li> + <li>SMP Support</li> + </ul> + + <p>We would like to say thanks to all the people who helped us by + reporting bugs and submitting fixes. We also thank the VirtualBox + developers for their help with the ongoing effort to port + VirtualBox on FreeBSD.</p> + </body> + </project> + + <project cat='docs'> + <title>The FreeBSD Dutch Documentation Project</title> + + <contact> + <person> + <name> + <given>René</given> + + <common>Ladan</common> + </name> + + <email>rene@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Remko</given> + + <common>Lodder</common> + </name> + + <email>remko@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/docproj/translations.html#dutch"> + Current status of the Dutch translation</url> + </links> + + <body> + <p>The current translations (Handbook and some articles) are kept + up to date with the English versions. Some parts of the website + have been + <url href="http://www.freebsd.org/nl">translated</url>, more work + is in progress.</p> + </body> + + <help> + <task>Find more volunteers for translating the remaining parts of + the website and the FAQ.</task> + </help> + </project> + + <project cat='docs'> + <title>The FreeBSD German Documentation Project</title> + + <contact> + <person> + <name> + <given>Johann</given> + + <common>Kois</common> + </name> + + <email>jkois@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Benedict</given> + + <common>Reuschling</common> + </name> + + <email>bcr@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Martin</given> + + <common>Wilke</common> + </name> + + <email>miwi@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="https://doc.bsdgroup.de" /> + + <url + href="http://code.google.com/p/bsdcg-trans/wiki/BSDPJTAdede" /> + </links> + + <body> + <p>In May 2009, Benedict Reuschling received his commit bit to the + www/de and doc/de_DE.ISO8859-1 trees under the mentorship of Johann + Kois. Since then, he has been working primarily on the Handbook, updating + existing chapters and translating new ones. Most notably, the + filesystems and DTrace chapters have been recently translated. Bugs found + in the original documents along the way were reported back so that + the other translation teams could incorporate them, as well.</p> + + <p>Christoph Sold has put his time in translating the wiki pages of + the BSD Certification Group into the German language. This is very + helpful for all German people who want to take the exam and like to read + the information about it in their native language. Daniel Seuffert + has sent valuable corrections and bugfixes. Thanks to both of them for + their time and efforts!</p> + + <p>The website is translated and updated constantly. Missing parts + will be translated as time permits.</p> + + <p>We appreciate any help from volunteers in proofreading + documents, translating new ones and keeping them up to date. Even + small error reports are of great help for us. You can find + contact information at the above URL.</p> + </body> + + <help> + <task>Update the existing documentation set (especially the + Handbook).</task> + + <task>Translate more articles to German.</task> + + <task>Read the translations. Check for problems and mistakes. Send + feedback.</task> + </help> + </project> + + <project cat="team"> + <title>The FreeBSD Foundation Status Report</title> + + <contact> + <person> + <name> + <given>Deb</given> + <common>Goodkin</common> + </name> + <email>deb@FreeBSDFoundation.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsdfoundation.org" /> + </links> + + <body> + <p>Kicking off our fall fund-raising campaign! Find out more at + <a href="http://www.freebsdfoundation.org/donate/">http://www.freebsdfoundation.org/donate/</a>.</p> + + <p>We were a sponsor for EuroBSDCon 2009, and provided travel + grants to 8 FreeBSD developers and users. We sponsored Kyiv BSD + 2009, in Kiev Ukraine. We were also a sponsor of BSDCan, and + sponsored 7 developers. We funded three new projects, New Console + Driver by Ed Schouten, AVR32 Support by Arnar Mar Sig, and + Wireless Mesh Support by Rui Paulo, which has completed. + We continued funding a project that is making improvements to the + FreeBSD TCP Stack by Lawrence Stewart. The project that made + removing disk devices with mounted filesystems on them safe, by + Edward Napierala, is now complete.</p> + + <p>We recognized the following FreeBSD developers at EuroBSDCon + 2009: Poul-Henning Kamp, Bjoern Zeeb, and Simon Nielsen. These + developers received limited edition FreeBSD Foundation vests.</p> + + <p>Follow us on <a + href="https://twitter.com/freebsdfndation">Twitter</a> now!</p> + </body> + </project> + + <project cat='team'> + <title>FreeBSD Bugbusting Team</title> + + <contact> + <person> + <name> + <given>Gavin</given> + <common>Atkinson</common> + </name> + <email>gavin@FreeBSD.org</email> + </person> + <person> + <name> + <given>Mark</given> + <common>Linimon</common> + </name> + <email>linimon@FreeBSD.org</email> + </person> + <person> + <name> + <given>Remko</given> + <common>Lodder</common> + </name> + <email>remko@FreeBSD.org</email> + </person> + <person> + <name> + <given>Volker</given> + <common>Werth</common> + </name> + <email>vwe@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/support.html#gnats" /> + <url href="http://wiki.FreeBSD.org/BugBusting" /> + <url href="http://people.FreeBSD.org/~linimon/studies/prs/" /> + <url href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html" /> + </links> + + <body> + <p>We continue to classify PRs as they arrive, adding 'tags' to + the subject lines corresponding to the kernel subsystem + involved, or man page references for userland PRs. These tags, + in turn, produce lists of PRs sorted both by tag and by + manpage.</p> + + <p>The list of PRs recommended for committer evaluation by the + Bugbusting Team continues to receive new additions. This list + contains PRs, mostly with patches, that the Bugbusting Team + feel are probably ready to be committed as-is, or are probably + trivially resolved in the hands of a committer with knowledge + of the particular subsystem. All committers are invited to take + a look at this list whenever they have a spare 5 minutes and + wish to close a PR.</p> + + <p>A full list of all the automatically generated reports is also + available at one of the cited URLs. Any recommendations for + reports which not currently exist but which would be + beneficial are welcomed.</p> + + <p>Gavin Atkinson gave a presentation on "The PR Collection + Status" at the EuroBSDCon 2009 DevSummit, and discussed with + other participants several other ideas to make the PR database + more useful and usable. Several good ideas came from this, and + will hopefully lead to more useful tools in the near future. + Discussions also took place on how it may be possible to + automatically classify non-ports PRs with a view towards + notifying interested parties, although investigations into this + have not yet begun.</p> + + <p>Mark Linimon also continues attempting to define the general + problem and investigating possible new workflow models, and + presented work on this at BSDCan 2009.</p> + + <p>Since the last status report, the number of open bugs has + increased to around the 5900 mark, partially because of an + increased focus on getting more information into the existing + PRs, in an attempt to make sure all the information required is + now available. As a result, although the number of open PRs has + increased, they are hopefully of better quality.</p> + + <p>As always, more help is appreciated, and committers and + non-committers alike are always invited to join us on + #freebsd-bugbusters on EFnet and help close stale PRs or commit + patches from valid PRs.</p> + </body> + + <help> + <task> + Work on suggestions from developers who were at the EuroBSDCon + DevSummit. + </task> + <task> + Try to find ways to get more committers helping us with closing + the PRs that the team has already analyzed. + </task> + </help> + </project> + + <project cat='team'> + <title>FreeBSD Ports Management Team</title> + + <contact> + <person> + <name> + <given>Mark</given> + <common>Linimon</common> + </name> + <email>linimon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.freebsd.org/ports/">The FreeBSD Ports + Collection</url> + <url href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"> + Contributing to the FreeBSD Ports Collection</url> + <url href="http://portsmon.FreeBSD.org/index.html">The FreeBSD + ports monitoring system</url> + <url href="http://www.freebsd.org/portmgr/index.html">The + FreeBSD Ports Management Team</url> + <url href="http://tinderbox.marcuscom.com">marcuscom Tinderbox</url> + </links> + + <body> + <p>The ports count has soared to over 20,700. The PR count had + been driven below 800 by some extraordinary effort, but once + again is back to its usual count of around 900.</p> + + <p>We are currently building packages for amd64-6, amd64-7, + amd64-8, i386-6, i386-7, i386-8, sparc64-7, and sparc64-8. + There have been preliminary runs of i386-9; however, to be able + to continue builds on -9, we will either need to find places to + host a number of new machines, or drop package building for -6. + The mailing list discussion of the latter proved quite + controversial.</p> + + <p>We have added some new i386 machines to help speed up the + builds, but this only makes up for the disk failures on some + of our older, slower, i386 nodes.</p> + + <p>We also appreciate the loan of more package build machines from + several committers, including pgollucci@, gahr@, erwin@, Boris + Kochergin, and Craig Butler.</p> + + <p>The portmgr@ team has also welcomed new members Ion-Mihai Tetcu + (itetcu@) and Martin Wilke (miwi@). We also thank departing + member Kirill Ponomarew (krion@) for his long service.</p> + + <p>Ion-Mihai has spent much time working on a system that does + automatic Quality Assurance on new commits, called QAT. A + second tinderbox called QATty has helped us to fix many problems, + especially those involving custom PREFIX and LOCALBASE settings, + and documentation inclusion options. Ports conformance to + documented features / non-default configuration will follow.</p> + + <p>Between pav and miwi, over 2 dozen experimental ports runs have + been completed and committed.</p> + + <p>We have added 5 new committers since the last report, and 2 + older ones have rejoined.</p> + </body> + + <help> + <task>We are currently trying to set up ports tinderboxes that + can be made available to committers for pre-testing; those + who can loan machines for this should contact Ion-Mihai + (itetcu@) with details regarding the hardware and + bandwidth.</task> + <task>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.</task> + <task>Although we have added many maintainers, we still have + almost 4,700 unmaintained ports (see, for instance, the list on + portsmon). (The percentage is down to 22%.) We are always + looking for dedicated volunteers to adopt at least a few + unmaintained ports. As well, the packages on amd64 and sparc64 + lag behind i386, and we need more testers for those.</task> + </help> + </project> + + <project cat='team'> + <title>FreeBSD KDE Team</title> + + <contact> + <person> + <name> + <given>Thomas</given> + + <common>Abthorpe</common> + </name> + + <email>tabthorpe@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Max</given> + + <common>Brazhnikov</common> + </name> + + <email>makc@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Martin</given> + + <common>Wilke</common> + </name> + + <email>miwi@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://freebsd.kde.org" /> + + <url href="http://miwi.bsdcrew.de/category/kde/" /> + + <url href="http://blogs.freebsdish.org/tabthorpe/category/kde" /> + </links> + + <body> + <p>Since the spring, the FreeBSD KDE team has been busy upgrading + KDE from 4.2.0 up through to 4.3.1. As part of the ongoing + maintenance of KDE, the team also updated Qt4 from 4.4.3 through to + 4.5.2</p> + + <p>We added two new committers/maintainers to the team, Kris Moore + (kmoore@) and Dima Panov (fluffy@). We also granted enhanced area51 + access to contributors Alberto Villa and Raphael Kubo da Costa. + Alberto has been our key contributor updating and testing Qt + 4.6.0-tp1. Raphael is a KDE developer, who has become our Gitorious + liaison, he has been responsible for getting FreeBSD Qt patches + merged in upstream.</p> + + <p>Markus Brüffer (markus@) spent a lot of time patching widgets + and system plugins so they would work under FreeBSD. We would like + to thank him for all his effort!</p> + </body> + + <help> + <task>Update to Qt 4.6.0</task> + + <task>Update to KDE 4.4.0</task> + + <task>Work with our userbase on fixing an EOL for KDE3 in the ports + tree</task> + </help> + </project> + + <project cat='misc'> + <title>FreeBSD Developer Summit, Cambridge UK</title> + + <contact> + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/200909DevSummit" /> + </links> + + <body> + <p>Around 70 FreeBSD developers and guests attended the FreeBSD + developer summit prior to EuroBSDCon 2009 in Cambridge, UK. + Hosted at the University of Cambridge Computer Laboratory, the + workshop-style event consisted of prepared presentations, as well + as group hacking and discussion sessions. Talks covered topics + including 802.11 mesh networking, virtual network stacks and + kernels, a new BSD-licensed debugger, benchmarking, bugbusting, + NetFPGA, a port of Apple's GCD (Grand Central Dispatch) to + FreeBSD, security policy work, cryptographic signatures, + FreeBSD.org system administration, time geeks, a new console + driver, and the FreeBSD subversion migration. Slides for many + talks are now available on the wiki page. A good time was had by + all, including a punting outing on the River Cam!</p> + </body> + </project> + + <project cat='misc'> + <title>EuroBSDcon 2009</title> + + <contact> + <person> + <name> + <given>Sam</given> + + <common>Smith</common> + </name> + + <email>eurobsdcon@ukuug.org</email> + </person> + + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://2009.eurobsdcon.org/">2009</url> + + <url href="http://2010.eurobsdcon.org/">2010</url> + </links> + + <body> + <p>EuroBSDcon 2009 happened in Cambridge, with over 160 users, + developers, friends and others. Slides, papers and audio are now up + on the website for those who could not make it to Cambridge. Next + year's event in 2010 will take place in Karlsruhe from 8 to 10 October + 2010. If you are interested in what you missed in 2009, or to join + the mailing list so you do not miss out next year, visit + <a href="http://2009.eurobsdcon.org/">http://2009.eurobsdcon.org</a>. + + </p> + </body> + </project> + + <project cat='misc'> + <title>The FreeBSD Forums</title> + + <contact> + <person> + <name> + <given>FreeBSD Forums</given> + + <common>Admins</common> + </name> + + <email>forum-admins@FreeBSD.org</email> + </person> + + <person> + <name> + <given>FreeBSD Forums</given> + + <common>Moderators</common> + </name> + + <email>forum-moderators@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://forums.freebsd.org/" /> + </links> + + <body> + <p>Since their public launch in November 2008, the FreeBSD Forums + (the most recent addition to the user community and support + channels for the FreeBSD Operating System) have witnessed a + healthy and steady growth.</p> + + <p>The user population is now at over 8,000 registered users, who + have participated in over 6,000 topics, containing over 40,000 + posts in total. The sign-up rate hovers between 50-100 each week. + The total number of visitors (including 'guests') is hard to gauge + but is likely to be a substantial multiple of the registered + userbase.</p> + + <p>New topics and posts are actively 'pushed out' to search + engines. This in turn makes the Forums show up in search results + more and more often, making it a valuable and very accessible + source of information for the FreeBSD community.</p> + + <p>One of the contributing factors to the Forums' success is their + 'BSD-style' approach when it comes to administration and + moderation. The Forums have a strong and unified identity, they are + neatly divided into sub-forums (like 'Networking', 'Installing + & Upgrading', etc.), very actively moderated, spam-free, and + with a core group of very active and helpful members, dispensing + many combined decades' worth of knowledge to starting, intermediate + and professional users of FreeBSD.</p> + + <p>We expect the Forums to be, and to remain, a central hub in + FreeBSD's community and support efforts.</p> + </body> + </project> + + <project cat='misc'> + <title>New approach to the locale database</title> + + <contact> + <person> + <name> + <given>Edwin</given> + + <common>Groothuis</common> + </name> + + <email>edwin@FreeBSD.org</email> + </person> + + <person> + <name> + <given>i18n</given> + + <common>mailinglist</common> + </name> + + <email>freebsd-i18n@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/LocaleNewApproach"> + Documentation on FreeBSD wiki</url> + + <url href="svn://svn.freebsd.org/base/user/edwin/locale">Code</url> + </links> + + <body> + <p>Problem: Over the years the FreeBSD locale database + (share/colldef, share/monetdef, share/msgdef, share/numericdef, + share/timedef) has accumulated a total of 165 definitions (language + - country-code - character-set triplets). The contents of the files + for Western European languages are often low-ASCII but for Eastern + European and Asian languages partly or fully high-ASCII. Without + knowing how to display or interpret the character-sets, it is + difficult to make sure by the general audience that the local + language (language - country-code) definitions are displayed + properly in various character-sets.</p> + + <p>Suggested approach: With the + combination of the data in the Unicode project (whose goal is to + define all the possible written characters and symbols on this + planet) and the Common Locale Data Repository (whose goal is to + document all the different data and definitions needed for the + locale database), we can easily keep track of the data, without the + need of being able to display the data in the required + character sets or understand them fully when updates are submitted + by third parties.</p> + + <p>Current status: Conversion of share/monetdef, + share/msgdef, share/numericdef, share/timedef to the new design is + completed. The Makefile infrastructure is converted. Regression + checks are done. Most of the tools are in place, waiting on the + import of bsdiconv to the base system.</p> + </body> + + <help> + <task>At this moment the system is not self-hosted yet, because of + the lack of an iconv-kind of program in the base operating system. + Gabor@ is working on bsdiconv as a GSoC project and once that has been + imported we will be able to perform a clean install from the definitions in + Unicode text format to the required formats and + character sets.</task> + </help> + </project> + + <project cat='soc'> + <title>BSD-licensed iconv (Summer of Code 2009)</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/G%C3%A1borSoC2009">BSDL iconv on + FreeBSD wiki</url> + </links> + + <body> + <p>The code has been extracted from NetBSD and has been transformed + into an independent shared library. The basic encodings are + well supported. Almost all forward conversions + (foo -> UTF-32) are compatible with GNU but the reverse ones + are not so accurate because of GNU's advanced transliteration. + Some extra encodings have also been added. There are two modules, + which segfault; they need some debugging. I can keep working on this + project as part of my BSc thesis, so I hope to be able to solve + the remaining issues. Improved GNU compatibility is also very + desired (extra command line options for iconv(1), iconvctl(), + private interfaces, etc.).</p> + </body> + + <help> + <task>Fix segfaults in Big5 and HZ modules</task> + + <task>Improve transliteration in reverse encodings</task> + + <task>Improve GNU compatibility by implementing extra features</task> + + <task>Verify POSIX compatibility</task> + + <task>Verify GNU compatibility</task> + + <task>Check performance</task> + </help> + </project> + + <project cat="soc"> + <title>Ext2fs Status report (Summer of Code 2009)</title> + + <contact> + <person> + <name> + <given>Aditya</given> + + <common>Sarawgi</common> + </name> + + <email>sarawgi.aditya@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/SOC2009AdityaSarawgi">Wiki Page</url> + </links> + + <body> + <p>FreeBSD's ext2fs had some parts under GPL. The aim of my project was + to rewrite those parts and free ext2fs from GPL. I have been + successful in rewriting the parts and NetBSD's ext2fs was a great + help in this. Certain critical parts under GPL were also removed due + to which the write performance suffered. I also implemented Orlov + Block Allocator for ext2fs. Currently I am planning to make ext2fs + Multiprocessor Safe (MPSAFE). My work resides in truncs_ext2fs + branch of Perforce.</p> + </body> + + <help> + <task>Ext4 support for FreeBSD</task> + + <task>Directory indexing for ext2fs</task> + + <task>Journaling in ext2fs using gjournal</task> + </help> + </project> + + <project cat='docs'> + <title>The FreeBSD Hungarian Documentation Project</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gábor</given> + + <common>Páli</common> + </name> + + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/hu">Hungarian Web Page for FreeBSD</url> + + <url href="http://www.FreeBSD.org/doc/hu">Hungarian Documentation + for FreeBSD</url> + + <url href="http://wiki.FreeBSD.org/HungarianDocumentationProject">The + FreeBSD Hungarian Documentation Project's Wiki Page</url> + + <url href="http://p4web.freebsd.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83">Perforce + Depot for the FreeBSD Hungarian Documentation Project</url> + </links> + + <body> + <p>In the last months, we have not added new translations, although we + have been working on the existing ones to have them updated. We need + more translators and volunteers to keep the amount of the translated + documentation growing, so feel free to contribute. Every line of + submission or feedback is appreciated and highly welcome.</p> + + <p>If you want to join our work, please read the <a + href="http://www.freebsd.org/hu/docproj/hungarian.html">introduction</a> + to the project as well as the <a + href="http://www.freebsd.org/doc/hu/books/fdp-primer/">FDP Primer</a> + (both of them are available in Hungarian).</p> + </body> + + <help> + <task>Translate news entries, press releases</task> + + <task>Translate Release Notes for -CURRENT and 8.X</task> + + <task>Translate articles</task> + + <task>Translate web pages</task> + + <task>Read the translations, send feedback</task> + </help> + </project> + + <project cat='docs'> + <title>The FreeBSD Spanish Documentation Project</title> + + <contact> + <person> + <name> + <given>José Vicente</given> + + <common>Carrasco Vayá</common> + </name> + + <email>carvay@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/es">Spanish Web Page for FreeBSD</url> + + <url href="http://www.FreeBSD.org/doc/es">Spanish Documentation for + FreeBSD</url> + + <url href="http://www.freebsd.org/doc/es/articles/fdp-es/">Introduction + to the FreeBSD Spanish Documentation Project</url> + </links> + + <body> + <p>Recently, we have added one new article translation. The + existing translations have not been updated, though. We need + more human resources to keep up with the work and keep the + translations up-to-date.</p> + </body> + + <help> + <task>Update the Handbook translation</task> + + <task>Update the web page translation</task> + </help> + </project> + + <project cat='soc'> + <title>BSD-licensed text-processing tools (Summer of Code 2008)</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/G%C3%A1borSoC2008">Wiki page for the project</url> + </links> + + <body> + <p>This project was started as part of Google Summer of Code 2008 but + there is still a bit of work to complete some missing parts. + The BSD-licensed grep implementation is feature-complete and + has a good level of GNU compatibility. Our only current concern about + the BSD-licensed version is to improve its + performance. The GNU variant is much more complex, has about + 8 KSLOC, while BSD grep is tiny, has only 1.5 KSLOC. GNU uses + some shortcuts and optimizations to speed-up calls to the regex library; + that is why it is significantly faster. My point of view is that + such optimizations must be implemented in the regex library, + keeping the dependent utilities clean and easy to read. BSD + grep is so tiny that there is hardly any optimization opportunity + by simplifying the code, so the regex library is the next important + TODO. There is another issue with the current regex library. + It does not support some invalid regular expressions, which work + in GNU. We need to maintain compatibility, so we cannot just drop + this feature. Actually, BSD grep is linked to the GNU regex library + to maintain this feature but due to the lack of the mentioned + shortcuts, it is still slower than GNU. Anyway, if we can live + with this little performance hit until we get a modern regex library, + I think grep is ready to enter HEAD. As for the regex library, + NetBSD's result of the last SoC is worth taking a look.</p> + + <p>The sort utility has been rewritten from scratch. The existing + BSD-licensed implementation could not deal with wide characters + by design. The new implementation is still lacking some features + but is quite complete. There is a performance issue, though. + Sorting is a typical algorithmic subject but I am not an algorithmic + expert, so my implementation is not completely optimal. Some help + would be welcome with this part.</p> + + <p>The bc/dc utilities have been ported from OpenBSD. They pass + OpenBSD's and GNU's regression tests but they arrived too late to + catch 8.X, so they will go to HEAD after the release.</p> + </body> + + <help> + <task>Improve sort's sorting and file merging algorithms</task> + + <task>Complete missing features for sort</task> + + <task>Get a modern regex library for FreeBSD</task> + </help> + </project> + + <project cat='net'> + <title>Network Stack Virtualization</title> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + <common>Zeeb</common> + </name> + <email>bz@FreeBSD.ORG</email> + </person> + <person> + <name> + <given>Marko</given> + <common>Zec</common> + </name> + <email>zec@FreeBSD.ORG</email> + </person> + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.ORG</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/Image">Wiki VImage overview + page (incl. TODO).</url> + <url href="http://wiki.freebsd.org/200909DevSummit">FreeBSD + Developer Summit, 2009, Cambridge, UK.</url> + </links> + + <body> + <p>The network stack virtualization project aims at extending the + FreeBSD kernel to maintain multiple independent instances of + networking state. This allows for networking independence + between jail environment, each maintaining its private network + interfaces, IPv4 and IPv6 network and port address space, routing + tables, IPSec configuration, firewalls, and more.</p> + + <p>During the last months the remaining pieces of the VIMAGE work + were merged by Marko, Julian and Bjoern. Robert Watson developed + a vnet allocator to overcome ABI issues. Jamie Gritton merged + his hierarchical jail framework that now also is the management + interface for virtual network stacks.</p> + + <p>During the FreeBSD Developer Summit that took place at + EuroBSDCon 2009 in Cambridge, UK, people virtualized more code. + As a result SCTP and another accept filter were virtualized and + more people became familiar with the design of VImage and the underlying concepts. + Finally getting more hands involved was a crucial first step for + the long term success of kernel virtualization.</p> + + <p>The next steps will be to finish the network stack + virtualization, generalize the allocator framework before + thinking of virtualizing further subsystems and to update the related + documentation. Along with that a proper jail management + framework will be worked on. Long term goals, amongst others, + will be to virtualize more subsystems like SYS-V IPC, better + privilege handling, and resource limits.</p> + + <p>In the upcoming FreeBSD 8.0 Release, vnets are treated as an + experimental feature. As a result, they are not yet recommended for use in + production environments. There was lots of time spent to + finalize the infrastructure for vnets though, so that further + changes can be merged and we are aiming to have things + production ready for 8.2.</p> + + <p>In case you want to help to achieve this goal, feel free to + contact us and support or help virtualizing outstanding parts + like two firewalls, appletalk, netipx, ... as well as generating + regression tests.</p> + </body> + </project> + + <project cat='net'> + <title>Enhancing the FreeBSD TCP Implementation</title> + + <contact> + <person> + <name> + <given>Lawrence</given> + <common>Stewart</common> + </name> + <email>lstewart@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://caia.swin.edu.au/freebsd/etcp09/" /> + <url href="http://caia.swin.edu.au/urp/newtcp/" /> + <url href="http://www.freebsdfoundation.org/projects.shtml" /> + <url href="http://people.freebsd.org/~lstewart/patches/tcp_ffcaia2008/" /> + </links> + + <body> + <p>TCP appropriate byte counting (RFC 3465) support has been merged + into the FreeBSD 8 branch and will ship in FreeBSD 8.0-RELEASE.</p> + + <p>The reassembly queue auto-tuning and SIFTR work was not ready in + time to safely integrate for 8.0-RELEASE. Padding has been added + to necessary TCP structs to facilitate MFCing features back to the + 8-STABLE branch after 8.0 is released.</p> + + <p>Candidate patches against FreeBSD-CURRENT will be ready for wider + testing in the coming weeks. The <a + href="mailto:freebsd-net@FreeBSD.org">freebsd-net</a> mailing list + will be solicited for testing/feedback when everything is ready.</p> + </body> + + <help> + <task> + Solicit review/testing and integrate the ALQ kld and variable + length message support patch into FreeBSD-CURRENT. + </task> + <task> + Solicit review/testing and integrate the SIFTR tool into + FreeBSD-CURRENT. + </task> + <task> + Complete dynamic reassembly queue auto-tuning patch for FreeBSD-CURRENT. + </task> + <task> + Fix an identified bug in the SACK implementation's fast retransmit/fast + recovery behavior. + </task> + <task> + Profit! + </task> + </help> + </project> + + <project cat='net'> + <title>Modular Congestion Control</title> + + <contact> + <person> + <name> + <given>Lawrence</given> + <common>Stewart</common> + </name> + <email>lstewart@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://caia.swin.edu.au/urp/newtcp/" /> + <url href="http://svn.freebsd.org/viewvc/base/projects/tcp_cc_8.x/" /> + </links> + + <body> + <p>The patch has received some significant rototilling in the past + few months to prepare it for merging to FreeBSD-CURRENT. + Additionally, I completed an implementation of the CUBIC congestion + control algorithm to complement the existing NewReno and H-TCP + algorithm implementations already available.</p> + + <p>I have one further intrusive change to make, which will allow + congestion control modules to be shared between the TCP and SCTP + stacks. Once this is complete, I will be soliciting for + review/testing in the hope of committing the patch to + FreeBSD-CURRENT in time to be able to backport it for 8.1-RELEASE.</p> + </body> + + <help> + <task> + Abstract the congestion control specific variables out of the TCP and + SCTP control blocks into a new struct that can be passed into the API + instead of the control block itself. + </task> + </help> + </project> + + <project cat='net'> + <title>Stream Control Transmission Protocol (SCTP)</title> + + <contact> + <person> + <name> + <given>Randall</given> + <common>Stewart</common> + </name> + <email>rrs@FreeBSD</email> + </person> + </contact> + + <body> + <p>SCTP continues to have minor fixes added to it as well as some + new features. First and foremost, we now have VIMAGE and SCTP + working and playing together. This goal was accomplished with + the help of bz@, my new mentee tuexen@ and myself working + together at the FreeBSD DevSummit in Cambridge, UK. Also the + non-renegable SACK feature contributed by the university of + Delaware was fixed so that now its safe to turn on (its + sysctl). If you are using SCTP with CMT (Conncurrent + Multipath Transfer) you will want to enable this option + (CMT is also a sysctl). With CMT enabled you will be able to + send data to all the destinations of an SCTP peer.</p> + + <p>We welcomed a new mentee (soon to be a commiter) to FreeBSD. + Michael Tuexen is now a mentee of rrs@. Michael has been + contributing to the SCTP work for quite some time and also + moonlights as a Professor at the University of Muenster + in Germany (when not doing SCTP coding).</p> + </body> + </project> + + <project cat='kern'> + <title>FreeBSD/ZFS</title> + + <contact> + <person> + <name> + <given>Pawel</given> + <common>Dawidek</common> + </name> + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>We believe that the ZFS file system is now production-ready in + FreeBSD 8.0. Most (if not all) reported bugs were fixed and ZFS + is no longer tagged as experimental. There is also ongoing work + in Perforce to bring the latest ZFS version (v19) to FreeBSD.</p> + </body> + + <help> + <task> + Download 8.0 release candidates and test, test, test and report + any problems to the + <a href="mailto:freebsd-fs@FreeBSD.org">freebsd-fs@FreeBSD.org</a> + mailing list. + </task> + </help> + </project> + + <project cat='kern'> + <title>hwpmc for MIPS</title> + + <contact> + <person> + <name> + <given>George</given> + <common>Neville-Neil</common> + </name> + <email>gnn@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/FreeBSD/mips">Main FreeBSD MIPS Page</url> + <url href="http://wiki.freebsd.org/FreeBSD/mips/UBNT-RouterStationPro">Sub page for the board I am using.</url> + </links> + + <body> + <p>Currently working on board bringup. I have looked over the docs + for how MIPS provides performance counters and will begin adding + code soon.</p> + </body> + </project> + + <project cat='ports'> + <title>FreeBSD Gecko Project</title> + + <contact> + <person> + <name> + <given>Beat</given> + <common>Gaetzi</common> + </name> + <email>beat@FreeBSD.org</email> + </person> + <person> + <name> + <given>Martin</given> + <common>Wilke</common> + </name> + <email>miwi@FreeBSD.org</email> + </person> + <person> + <name> + <given>Andreas</given> + <common>Tobler</common> + </name> + <email>andreast-list@fgznet.ch</email> + </person> + </contact> + + <links> + <url href="https://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO">Gecko TODO</url> + </links> + + <body> + <p>Andreas Tobler made the classic mistake of sending us a lot of + powerpc and sparc64 related patches. The usual punishment, of + giving him a commit bit to the Gecko repository, has been + applied.</p> + + <p>We currently have some old ports in the ports tree:</p> + + <ul> + <li>www/mozilla is 5 year old now, no longer supported upstream, + and has a lot of security vulnerabilities. We can use + www/seamonkey instead.</li> + + <li>www/xulrunner is superseeded by www/libxul.</li> + </ul> + + <p>A patch that includes the following changes has been tested on + pointyhat and is ready for commit:</p> + + <ul> + <li>Remove references to www/mozilla/Makefile.common and + www/mozilla/bsd.gecko.mk</li> + <li>Switch USE_GECKO= xulrunner firefox mozilla to + USE_GECKO= libxul and remove www/xulrunner</li> + </ul> + + <p>We are also working on Firefox 3.6 (Alpha 2), Thunderbird 3.0 (Beta 4), + new libxul 1.9.1.3 and Seamonkey 2.0 (Beta 2) ports. All of them are + already committed to our Gecko repository.</p> + + <p>A current status and todo list can be found at + <a href="http://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO">http://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO</a>.</p> + </body> + + <help> + <task>Remove mozilla, xulrunner and firefox2 from the ports tree.</task> + <task>The www/firefox35 port should be moved to www/firefox.</task> + <task>The old (and somewhat stale) Gecko providers mozilla, nvu, + xulrunner, flock and firefox also need to be removed.</task> + </help> + </project> + + <project cat='ports'> + <title>Portmaster - utility to assist users with managing ports</title> + + <contact> + <person> + <name> + <given>Doug</given> + <common>Barton</common> + </name> + <email>dougb@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://dougbarton.us/portmaster.html" /> + </links> + + <body> + <p>I am currently seeking funding for further development work on + portmaster. There are several features that are regularly + requested by the community (such as support for installing + packages) that I would very much like to implement but that + will take more time than I can reasonably volunteer to implement + correctly. There is information about the funding proposal + available at the link above.</p> + + <p>Meanwhile I have recently completed another round of bug fixes + and feature enhancements. The often-requested ability to specify + the -x (exclude) option more than once on the command line was + added in version 2.12. Also in that version I added the + --list-origins option to make it easier to reinstall ports after + a major version upgrade, or install the same set of ports on + another system.</p> + </body> + + <help> + <task>See the funding proposal.</task> + </help> + </project> + + <project cat='ports'> + <title>Valgrind suite on FreeBSD</title> + + <contact> + <person> + <name> + <given>Stanislav</given> + <common>Sedov</common> + </name> + <email>stas@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/Valgrind">Valgrind Wiki page</url> + </links> + + <body> + <p>The Valgrind suite in the FreeBSD ports collection has been updated to + version 3.5.0 (the latest available version). Most of the issues of + the previous version should be resolved now: we expect memcheck, + callgrind and cachegrind to be fully functional on both i386 and + amd64 platforms as well as for i386 binaries running on amd64 + system. DRD/hellgrind should work too, though they generate + a lot of false-positives for now, so their output is a bit messy.</p> + </body> + + <help> + <task> + Port exp-ptrcheck valgrind tool and fix outstanding issues + that show up in memcheck/helgrind/DRD in the Valgrind regression + tests suite. + </task> + <task> + More testing (please, help). + </task> + <task> + Integrate our patches upstream. + </task> + </help> + </project> + + <project cat='arch'> + <title>FreeBSD/sparc64</title> + + <contact> + <person> + <name> + <given>Marius</given> + + <common>Strobl</common> + </name> + + <email>marius@FreeBSD.org</email> + </person> + </contact> + + <links/> + + <body> + <p>Noteworthy developments regarding FreeBSD/sparc64 since the last + Status Reports are:</p> + + <ul> + <li>Cas(4), a driver for Sun Cassini/Cassini+, as well as + National Semiconductor DP83065 Saturn Gigabit NICs has been + committed and thus will be part of FreeBSD beginning with + 8.0-RELEASE and 7.3-RELEASE, respectively. This means that + the on-board NICs found in Fire V440, as well as the add-on + cards based on these chips, are now supported, including on + non-sparc64 machines. Unfortunately, the cas(4) driver triggers what + seem to be secondary problems with the on-board NICs found in + B100 blades and Fire V480, which due to lack of access to such + systems could not be fixed so far.</li> + + <li>Initial support for sun4u machines based on the "Fire" + Host-PCI-Express bridge like Fire V215, V245, etc. has been + completed (including support for the on-board ATA controller, + which caused several problems at first, and MSI/MSI-X). Some + code like the quirk handling for the ALi/ULi chips found in + these machines needs to be revisited though and no stability + tests have been conducted so far. If all goes well, the code + will hit HEAD some time after FreeBSD 8.0-RELEASE has been + released. In theory, machines based on the "Oberon" + Host-PCI-Express bridge, at least for the most part, should + also be supported with these changes, but due to lack of access + to a Mx000 series machine the code could not be tested with + these so far.</li> + + <li>Some bugs in the snd_t4dwave(4) driver have been fixed, as + well as some special handling for sparc64 has been added so + it does 32-bit DMA and now generally works with the on-board + ALi M5451 found for example in Blade 100 and Blade 1500. + Unfortunately, it was only tested to work correctly in two out + of three Blade 100. Why it still does not work correctly in + the remaining one is currently unknown but at least no longer + causes IOMMU-panics so testing snd_t4dwave(4) on sparc64 is no + longer harmful. These changes will be part of + FreeBSD 8.0-RELEASE and 7.3-RELEASE.</li> + + <li>Ata-marvell(4) has been fixed to work on sparc64 (actually + also on anything that is not x86 with less than 4GB of RAM). + These fixes will be part of FreeBSD 8.0-RELEASE and + 7.3-RELEASE.</li> + + <li>A proper and machine-independent fix for the old problem + that the loader leaves the NIC opened by the firmware, + which could lead to panics during boot when netbooting, + has been developed but not committed yet.</li> + </ul> + </body> + + <help/> + </project> + + <project cat='proj'> + <title>NFSv4 ACLs</title> + + <contact> + <person> + <name> + <given>Edward Tomasz</given> + + <common>Napierala</common> + </name> + + <email>trasz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/NFSv4_ACLs"/> + </links> + + <body> + <p>During Google Summer of Code 2008, I have implemented native support + for NFSv4 ACLs for both ZFS and UFS. Most of the code has already been + merged to CURRENT. NFSv4 ACLs are unconditionally enabled in ZFS and + the usual tools, like getfacl(1) and setfacl(1) can be used to view and + change them. I plan to merge the remaining bits (UFS support) this month. + It should be possible to MFC it in order to ship in + FreeBSD 8.1-RELEASE.</p> + </body> + + <help> + <task>UFS changes review</task> + + <task>Support for NFSv4 ACLs in tar(1)</task> + </help> + </project> + + <project cat='soc'> + <title>About Google Summer of Code 2009</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@freebsd.org</email> + </person> + + <person> + <name> + <given>Tim</given> + + <common>Kientzle</common> + </name> + + <email>kientzle@freebsd.org</email> + </person> + + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + + <email>rwatson@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://socghop.appspot.com/org/home/google/gsoc2009/freebsd">FreeBSD + GSoC Homepage</url> + <url href="http://wiki.freebsd.org/SummerOfCode2009Projects">FreeBSD GSoC + 2009 Wiki</url> + </links> + + <body> + <p>2009 was The FreeBSD Project's fifth year of participation + in the Google Summer of Code. We had a total of 17 successful projects. + Some GSoC code will be shipping with FreeBSD 8.0-RELEASE and others + will be integrated into future releases.</p> + + <p>The FreeBSD GSoC admin team would like to thank Google and + our students and mentors of another great year!</p> + </body> + </project> + + <project cat='proj'> + <title>FreeBSD TDM Framework</title> + + <contact> + <person> + <name> + <given>Rafal</given> + + <common>Czubak</common> + </name> + + <email>rcz@semihalf.com</email> + </person> + + <person> + <name> + <given>Michal</given> + + <common>Hajduk</common> + </name> + + <email>mih@semihalf.com</email> + </person> + </contact> + + <body> + <p>This work's purpose is a generic and flexible framework for systems + equipped with Time Division Multiplexing (TDM) units, often found on + embedded telecom chips. The framework is designed to support various + controllers and many types of TDM channels e.g. voiceband, sound and + miscellaneous data channels. Currently, voiceband infrastructure is + being developed on Marvell RD-88F6281 reference board. It will serve + as an example of how to use the TDM framework for other channel types. + The direct objective of using TDM with voiceband channels is bringing + a FreeBSD based VoIP system, capable of bridging analog telephone world + with digital IP telephony. Together with third party VoIP software + (e.g. Asterisk), the design can serve as VoIP Private Branch Exchange + (PBX).</p> + + <p>Current state highlights:</p> + + <ul> + <li>TDM controller interface</li> + + <li>TDM channel interface</li> + + <li>TDM channel API for kernel modules</li> + + <li>codec interface</li> + + <li>voiceband channel character device driver</li> + + <li>TDM controller driver for Marvell Kirkwood and Discovery SoCs</li> + + <li>Si3215 SLIC driver</li> + + <li>Si3050 DAA driver</li> + </ul> + </body> + + <help> + <task>Develop demo application showing example usage of voiceband + channel.</task> + + <task>Integrate voiceband infrastructure with Zaptel/DAHDI telephony + hardware drivers.</task> + </help> + </project> + + <project cat='team'> + <title>Release Engineering Status Report</title> + + <contact> + <person> + <name> + <given>Release Engineering Team</given> + </name> + + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/" /> + </links> + + <body> + <p>The Release Engineering Team continues to work on FreeBSD + 8.0-RELEASE. Public testing has turned up quite a few problems, + many related to the low-level network (routing/ARP table) changes + and their interactions with IPv6.</p> + + <p>Progress continues to be made on fixing up the issues that have + been identified during the public testing. At this point in time + we are shooting for two more public test builds (RC2 and RC3) + followed by the release late October or early November.</p> + </body> + </project> + +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2009-10-2009-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2009-10-2009-12.xml new file mode 100644 index 0000000000..c42606793f --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2009-10-2009-12.xml @@ -0,0 +1,2033 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status +Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2009-10-2009-12.xml,v 1.16 2011/06/02 12:05:56 uqs Exp $ --> +<report> + <date> + <month>October-December</month> + + <year>2009</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report covers &os; 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 &os; Project. Besides + other notable things, a new major version of &os;, 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> + </section> + + <category> + <name>soc</name> + + <description>Google Summer of Code</description> + </category> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>team</name> + + <description>&os; Team Reports</description> + </category> + + <category> + <name>net</name> + + <description>Network Infrastructure</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <category> + <name>vendor</name> + + <description>Vendor / 3rd Party Software</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <category> + <name>bin</name> + + <description>Userland utilities</description> + </category> + + <project cat='vendor'> + <title>DAHDI (Zaptel) support for &os;</title> + + <contact> + <person> + <name> + <given>Max</given> + + <common>Khon</common> + </name> + + <email>fjoe@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://www.mail-archive.com/asterisk-dev@lists.digium.com/msg39598.html"> + Official Announcement</url> + + <url href="http://svn.digium.com/svn/dahdi/freebsd/trunk/">SVN + repository</url> + </links> + + <body> + <p>A DAHDI support module for &os; 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> + </body> + + <help> + <task>The port for dahdi_dynamic_eth and dahdi_dynamic_ethmf is + underway.</task> + + <task>More HW drivers need to be ported.</task> + + <task>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 &os; 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.</task> + </help> + </project> + + <project cat='kern'> + <title>CAM-based ATA implementation</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Motin</common> + </name> + + <email>mav@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Scott</given> + + <common>Long</common> + </name> + + <email>scottl@FreeBSD.org</email> + </person> + </contact> + + <body> + <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 &os; 8.0-RELEASE but + 8-STABLE now includes a much improved version.</p> + </body> + + <help> + <task>Improve timeout and transport error recovery.</task> + + <task>Improve hot-plug support.</task> + + <task>Find and fix any show stoppers for legacy ata(4) + deprecation.</task> + + <task>Write a new, more featured driver for Marvell SATA controllers + (specifications desired).</task> + + <task>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.</task> + </help> + </project> + + <project cat="ports"> + <title>Chromium web browser</title> + + <contact> + <person> + <name> + <given>Ben</given> + + <common>Laurie</common> + </name> + + <email>ben@links.org</email> + </person> + </contact> + + <links> + <url href="http://chromium.jaggeri.com">test builds and port + progress</url> + + <url href="http://www.links.org/?p=724">first build + information</url> + </links> + + <body> + <p>Chromium is a Webkit-based web browser that is largely BSD + licensed. It has been ported from Linux to &os; in October and we have been + posting patches and test builds periodically since then. Chromium + works well on &os; — 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 + &os; desktop systems.</p> + </body> + + <help> + <task>Fix sporadic rendering freezes.</task> + + <task>Fix JavaScript interpreter, v8, on i386 architecture.</task> + </help> + </project> + + <project cat='proj'> + <title>SUJ — Journaled SoftUpdates</title> + + <contact> + <person> + <name> + <given>Jeff</given> + + <common>Roberson</common> + </name> + + <email>jeff@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://jeffr_tech.livejournal.com/" /> + </links> + + <body> + <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 &os; + 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> + </body> + </project> + + <project cat='ports'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ports/">The &os; Ports + Collection</url> + + <url + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/"> + Contributing to the &os; Ports Collection</url> + + <url href="http://portsmon.FreeBSD.org/index.html">&os; ports + monitoring system</url> + + <url href="http://www.FreeBSD.org/portmgr/index.html">The &os; + Ports Management Team</url> + + <url href="http://tinderbox.marcuscom.com">marcuscom + Tinderbox</url> + </links> + + <body> + <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> + </body> + + <help> + <task>We are still trying to set up ports tinderboxes that can be + made available to committers for pre-testing.</task> + + <task>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.</task> + + <task>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.</task> + </help> + </project> + + <project cat='arch'> + <title>&os;/sparc64</title> + + <contact> + <person> + <name> + <given>Marius</given> + + <common>Strobl</common> + </name> + + <email>marius@FreeBSD.org</email> + </person> + </contact> + + <body> + <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>&os; 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 &os; 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> + </body> + </project> + + <project cat="proj"> + <title>3G USB support</title> + + <contact> + <person> + <name> + <given>Andrew</given> + + <common>Thompson</common> + </name> + + <email>thompsa@FreeBSD.org</email> + </person> + </contact> + + <body> + <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> + </body> + </project> + + <project cat="docs"> + <title>The &os; German Documentation Project</title> + + <contact> + <person> + <name> + <given>Johann</given> + + <common>Kois</common> + </name> + + <email>jkois@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Benedict</given> + + <common>Reuschling</common> + </name> + + <email>bcr@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Martin</given> + + <common>Wilke</common> + </name> + + <email>miwi@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://doc.bsdgroup.de">German Documentation Project + Homepage</url> + </links> + + <body> + <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 &os; 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> + </body> + + <help> + <task>Read the translations and report bugs to + de-bsd-translators@de.FreeBSD.org.</task> + + <task>Translate articles or missing sections listed above.</task> + </help> + </project> + + <project cat='docs'> + <title>The &os; Spanish Documentation Project</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Kövesdán</common> + </name> + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/doc/es/articles/fdp-es/">Introduction to the Spanish Documentation Project</url> + + <url href="https://listas.es.FreeBSD.org/mailman/listinfo/doc">Translators' Mailing List</url> + </links> + + <body> + <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> + </body> + + <help> + <task>Update Handbook translation.</task> + + <task>Update webpage translation.</task> + + <task>Add more article translations.</task> + </help> + </project> + + <project cat='docs'> + <title>The &os; Hungarian Documentation Project</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Kövesdán</common> + </name> + <email>gabor@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gábor</given> + <common>Páli</common> + </name> + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/hu/">Hungarian Web Page for &os;</url> + + <url href="http://www.FreeBSD.org/doc/hu/">Hungarian Documentation + for &os;</url> + + <url href="http://wiki.FreeBSD.org/HungarianDocumentationProject">The + &os; Hungarian Documentation Project's Wiki Page</url> + + <url href="http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83">Perforce + Depot for the &os; Hungarian Documentation Project</url> + </links> + + <body> + <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> + </body> + + <help> + <task>Translate release notes.</task> + + <task>Add more article translations.</task> + </help> + </project> + + <project cat='misc'> + <title>The &os; Forums</title> + + <contact> + <person> + <name> + <given>&os; Forums</given> + + <common>Admins</common> + </name> + + <email>forum-admins@FreeBSD.org</email> + </person> + + <person> + <name> + <given>&os; Forums</given> + + <common>Moderators</common> + </name> + + <email>forum-moderators@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://forums.FreeBSD.org/" /> + </links> + + <body> + <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 &os; 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 + &os;.</p> + </body> + </project> + + <project cat='kern'> + <title>V4L support in Linux emulator</title> + + <contact> + <person> + <name> + <given>J.R.</given> + + <common>Oldroyd</common> + </name> + + <email>fbsd@opal.com</email> + </person> + </contact> + + <links> + <url href="http://opal.com/freebsd/sys/compat/linux/" /> + </links> + + <body> + <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 &os; 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 &os;-8.0/amd64 and + &os;-7.2/i386.</p> + + <p>Note: to be clear, this does not add V4L support to all webcams. + The &os; 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> + </body> + </project> + + <project cat='proj'> + <title>The webcamd deamon</title> + + <contact> + <person> + <name> + <given>Hans Petter</given> + + <common>Selasky</common> + </name> + + <email>hselasky@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.selasky.org/hans_petter/video4bsd/" /> + </links> + + <body> + <p>The webcamd daemon enables hundreds of different USB based + webcam devices to be used under the &os;-8/9 operating system. The + webcam daemon is basically an application, which is a port of + Video4Linux USB webcam drivers into userspace on &os;. The daemon + currently depends on libc, pthreads, libusb and the VIDEO4BSD + kernel module.</p> + </body> + + <help> + <task>Add support for the remaining Video4Linux USB devices.</task> + + <task>Make patches for increased buffer sizes, due to higher + latency in userspace. Especially for High Speed USB.</task> + </help> + </project> + + <project cat='kern'> + <title>Group Limit Increase</title> + + <contact> + <person> + <name> + <given>Brooks</given> + <common>Davis</common> + </name> + <email>brooks@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Historically, &os; has limited the number of supplemental + groups per process to 15 (NGROUPS_MAX was incorrectly declared to be + 16). In &os; 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> + </body> + </project> + + <project cat='net'> + <title>Syncing pf(4) with OpenBSD 4.5</title> + + <contact> + <person> + <name> + <given>Ermal</given> + + <common>Luçi</common> + </name> + + <email>eri@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/"> + Viewing the changes.</url> + + <url href="http://svn.FreeBSD.org/base/user/eri/pf45/head/">The + actual repo to build from.</url> + </links> + + <body> + <p>This import is based on OpenBSD 4.5 state of pf(4). It includes + many improvements over the code currently present in &os;. 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> + </body> + + <help> + <task>pflow(4)/pflog(4)/pfsync(4) need to be made VIMAGE + aware.</task> + + <task>More regression testing is needed.</task> + </help> + </project> + + <project cat='kern'> + <title>NFSv4 ACL support</title> + + <contact> + <person> + <name> + <given>Edward Tomasz</given> + + <common>Napierala</common> + </name> + + <email>trasz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/NFSv4_ACLs" /> + </links> + + <body> + <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 &os; 8.1-RELEASE.</p> + </body> + + <help> + <task>Support for NFSv4 ACLs in tar(1).</task> + + <task>MFC.</task> + </help> + </project> + + <project cat='net'> + <title>Ralink wireless RT2700U/2800U/3000U run(4) USB driver</title> + + <contact> + <person> + <name> + <given>Akinori</given> + + <common>Furukoshi</common> + </name> + + <email>moonlightakkiy@yahoo.ca</email> + </person> + </contact> + + <links> + <url href="http://forums.FreeBSD.org/showthread.php?t=7562"> + Announcement on the &os; Forums</url> + </links> + + <body> + <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> + </body> + + <help> + <task>Solve USB_TIMEOUT problem when sending beacons, and/or + confirm which chipsets supports AP mode if all of them do not + support it.</task> + + <task>Read TX stats for AMRR on AP mode, and/or confirm which + chipsets supports AP mode if all of them do not support + it.</task> + + <task>Maintain the code.</task> + </help> + </project> + + <project cat='arch'> + <title>&os;/mips</title> + + <contact> + <person> + <name> + <given>The &os;/mips mailing list</given> + </name> + + <email>mips@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Warner</given> + + <common>Losh</common> + </name> + + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/projects/mips/index.html" /> + + <url href="http://wiki.FreeBSD.org/FreeBSD/mips" /> + </links> + + <body> + <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 &os;/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> + </body> + + <help> + <task>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.</task> + </help> + </project> + + <project cat='arch'> + <title>Flattened Device Tree for embedded &os;</title> + + <contact> + <person> + <name> + <given>Rafal</given> + <common>Jaworowski</common> + </name> + <email>raj@semihalf.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/FlattenedDeviceTree">Project wiki pages</url> + + <url href="http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/fdt/...">Project P4 branch</url> + </links> + + <body> + <p>The purpose of this project is to provide &os; 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 &os; 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 &os; + 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 &os; Foundation.</p> + </body> + + <help> + <task>Complete missing pieces for PowerPC (PCI bridge driver conversion to + FDT).</task> + + <task>Complete ARM support.</task> + + <task>Merge to SVN.</task> + </help> + </project> + + <project cat='proj'> + <title>HAST — Highly Available Storage</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + + <common>Dawidek</common> + </name> + + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <links> + <url + href="http://lists.FreeBSD.org/pipermail/freebsd-announce/2009-October/001279.html"> + Announcement</url> + </links> + + <body> + <p>HAST software will provide synchronous replication of any GEOM + provider (eg. disk, partition, mirror, etc.) or file from one &os; + 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 &os; 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 &os; 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 &os; Foundation, as your + donations make projects like this possible.</p> + + <p>Thank you!</p> + </body> + </project> + + <project cat='net'> + <title>Wireless mesh networking</title> + + <contact> + <person> + <name> + <given>Rui</given> + <common>Paulo</common> + </name> + <email>rpaulo@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/WifiMesh"/> + </links> + + <body> + <p>Development of the &os; 802.11s stack continues. The code in + &os; HEAD has been updated to comply with draft 4.0. Merge to + &os; 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> + </body> + </project> + + <project cat='proj'> + <title>&os; TDM Framework</title> + + <contact> + <person> + <name> + <given>Rafal</given> + <common>Czubak</common> + </name> + <email>rcz@semihalf.com</email> + </person> + + <person> + <name> + <given>Michal</given> + <common>Hajduk</common> + </name> + <email>mih@semihalf.com</email> + </person> + </contact> + + <body> + <p>Important changes regarding &os; 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> + </body> + + <help> + <task>Improve various issues regarding working drivers and demo + application.</task> + + <task>Test Si3050 codec driver operation with PSTN.</task> + + <task>Fully integrate voiceband infrastructure with Zaptel/DAHDI telephony + hardware drivers.</task> + </help> + </project> + + <project cat='proj'> + <title>POSIX utmpx for &os;</title> + + <contact> + <person> + <name> + <given>Ed</given> + <common>Schouten</common> + </name> + <email>ed@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://lists.FreeBSD.org/pipermail/freebsd-current/2010-January/014893.html">Announcement</url> + + <url href="http://www.opengroup.org/onlinepubs/9699919799/functions/endutxent.html">POSIX specification</url> + + <url href="http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/lib/libc/gen/utmpx.c">NetBSD's implementation</url> + + <url href="http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/gen/getutx.c">OpenSolaris' implementation</url> + </links> + + <body> + <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> + </body> + + <help> + <task>Get a list of broken ports.</task> + + <task>Fix them to comply to standards.</task> + + <task>Send patches upstream.</task> + </help> + </project> + + <project cat='soc'> + <title>BSD-licensed iconv</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Kövesdán</common> + </name> + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2009/gabor_iconv">Sources in the Perforce repository</url> + </links> + + <body> + <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> + </body> + + <help> + <task>Enhance conversion tables to make use of enhanced + transliteration.</task> + + <task>A performance optimization might be done later.</task> + </help> + </project> + + <project cat='bin'> + <title>BSD-licensed text processing tools</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Kövesdán</common> + </name> + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc">Perforce repository</url> + </links> + + <body> + <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> + </body> + + <help> + <task>Commit BSD bc/dc.</task> + + <task>Implement remaining features for sort and optimize + performance.</task> + </help> + </project> + + <project cat='vendor'> + <title>NVIDIA amd64 driver</title> + + <contact> + <person> + <name> + <given>John</given> + <common>Baldwin</common> + </name> + <email>jhb@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.nvnews.net/vbulletin/showthread.php?t=142120">Release Announcement</url> + </links> + + <body> + <p>NVIDIA has released the first BETA version of its graphics + drivers for &os;/amd64. Note that this driver will work on &os; + 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> + </body> + </project> + + <project cat='team'> + <title>&os; Bugbusting Team</title> + + <contact> + <person> + <name> + <given>Gavin</given> + <common>Atkinson</common> + </name> + <email>gavin@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Mark</given> + <common>Linimon</common> + </name> + <email>linimon@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Remko</given> + <common>Lodder</common> + </name> + <email>remko@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Volker</given> + <common>Werth</common> + </name> + <email>vwe@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/support.html#gnats">GNATS</url> + <url href="http://wiki.FreeBSD.org/BugBusting">BugBusting</url> + <url href="http://people.FreeBSD.org/~linimon/studies/prs/">Experimental + report pages</url> + <url href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html">PRs + recommended for committer evaluation by the bugbusting team</url> + <url href="http://people.FreeBSD.org/~linimon/recommended_subscribers.txt">Subscription + list for the above report)</url> + </links> + + <body> + <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 &os; 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> + </body> + + <help> + <task>Try to find ways to get more committers helping us with + closing PRs that the team has already analyzed.</task> + </help> + </project> + + <project cat='arch'> + <title>&os;/ia64</title> + + <contact> + <person> + <name> + <given>Marcel</given> + <common>Moolenaar</common> + </name> + <email>marcel@FreeBSD.org</email> + </person> + </contact> + + <body> + <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> + </body> + + <help> + <task>Continue to try to understand why multiple simultaneous + package builds bring the machines down.</task> + + <task>Upgrade the firmware on the two machines at Yahoo! to + see if that helps the problem.</task> + + <task>Configure a fourth machine that has been made available + to us.</task> + + <task>Figure out the problems with the latest GCC port on + ia64.</task> + + <task>We can use some help with reviewing the ia64 platform pages + and bringing them up-to-date.</task> + </help> + </project> + + <project cat='net'> + <title>bwn(4) — Broadcom Wireless driver</title> + + <contact> + <person> + <name> + <given>Weongyo</given> + <common>Jeong</common> + </name> + <email>weongyo@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/weongyo/wireless/src/sys/dev/bwn&HIDEDEL=NO">bwn(4) + sources in P4</url> + </links> + + <body> + <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 — as you might + know — 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> + </body> + + <help> + <task>MESH/IBSS/HOSTAP mode is not supported.</task> + + <task>LP/N PHYs are not supported.</task> + </help> + </project> + + <project cat='team'> + <title>&os; Release Engineering</title> + + <contact> + <person> + <name> + <given>Release Engineering Team</given> + </name> + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/" /> + </links> + + <body> + <p>The Release Engineering Team announced &os; 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 &os; Project but has stepped down + from the Release Engineering Team to focus on other + activities.</p> + </body> + </project> + + <project cat='net'> + <title>IP Payload Compression Protocol support</title> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + <common>Zeeb</common> + </name> + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>One of the longer outstanding feature problems with the &os; + 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> + </body> + + <help> + <task>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.</task> + </help> + </project> + + <project cat='team'> + <title>The &os; Foundation Status Report</title> + + <contact> + <person> + <name> + <given>Deb</given> + <common>Goodkin</common> + </name> + <email>deb@FreeBSDFoundation.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSDFoundation.org/">The &os; Foundation</url> + <url href="https://twitter.com/freebsdfndation">Follow us on Twitter</url> + </links> + + <body> + <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 &os; 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">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/">http://www.FreeBSDFoundation.org/donate/</a>.</p> + </body> + </project> + + <project cat='ports'> + <title>VirtualBox on &os;</title> + + <contact> + <person> + <name> + <given>Beat</given> + <common>Gaetzi</common> + </name> + <email>beat@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Bernhard</given> + <common>Froehlich</common> + </name> + <email>decke@bluelife.at</email> + </person> + + <person> + <name> + <given>Juergen</given> + <common>Lock</common> + </name> + <email>nox@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Martin</given> + <common>Wilke</common> + </name> + <email>miwi@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/VirtualBox" /> + </links> + + <body> + <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 + — virtualbox-ose-kmod.</li> + + <li>A separate port for guest additions for &os; guests has + been created — virtualbox-ose-additions.</li> + + <li>Proper &os; support for PulseAudio has been added.</li> + + <li>Procfs is not required anymore because vbox uses sysctl(3) + now.</li> + + <li>Juergen Lock's &os; 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 &os;</p> + </body> + </project> + + <project cat='misc'> + <title>BSDCan 2010 — The BSD Conference</title> + + <contact> + <person> + <name> + <given>BSDCan Information</given> + </name> + <email>info@BSDCan.org</email> + </person> + </contact> + + <links> + <url href="http://www.BSDCan.org/2010/" /> + </links> + + <body> + <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> + </body> + </project> + + <project cat='misc'> + <title>AsiaBSDCon 2010 — The BSD Conference</title> + + <contact> + <person> + <name> + <given>AsiaBSDCon Information</given> + </name> + <email>secretary@AsiaBSDCon.org</email> + </person> + </contact> + + <links> + <url href="http://2010.AsiaBSDCon.org/" /> + </links> + + <body> + <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> + </body> + </project> + + <project cat='misc'> + <title>meetBSD 2010 — The BSD Conference</title> + + <contact> + <person> + <name> + <given>meetBSD</given> + <common>Information</common> + </name> + <email>info@meetBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.meetBSD.org"/> + </links> + + <body> + <p>The meetBSD conference is an annual event gathering users and + developers of the BSD operating system family, mostly &os;, + 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> + </body> + </project> + + <project cat='proj'> + <title>Clang replacing GCC in the base system</title> + + <contact> + <person> + <name> + <given>Ed</given> + <common>Schouten</common> + </name> + <email>ed@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Roman</given> + <common>Divacky</common> + </name> + <email>rdivacky@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Brooks</given> + <common>Davis</common> + </name> + <email>brooks@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Pawel</given> + <common>Worach</common> + </name> + <email>pawel.worach@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" /> + </links> + + <body> + <p>We are again able to build bootable i386/amd64 kernel. Nathan + Whitehorn committed a fix to &os;, 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 — 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> + </body> + + <help> + <task>Help with ARM/MIPS/sparc64.</task> + + <task>More testing of clang on 3rd party apps (ports).</task> + + <task>Discussion on integrating LLVM/clang into &os;.</task> + </help> + </project> + + <project cat='proj'> + <title>Intel XScale hwpmc(9) support</title> + + <contact> + <person> + <name> + <given>Rui</given> + <common>Paulo</common> + </name> + <email>rpaulo@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Preliminary Hardware Performance Counter support for Intel + XScale ARM processors was committed to &os; 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> + </body> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2010-01-2010-03.xml b/en_US.ISO8859-1/htdocs/news/status/report-2010-01-2010-03.xml new file mode 100644 index 0000000000..3c93b767f1 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2010-01-2010-03.xml @@ -0,0 +1,2355 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status +Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2010-01-2010-03.xml,v 1.3 2010/04/24 08:57:00 danger Exp $ --> +<report> + <date> + <month>January-March</month> + + <year>2010</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report covers &os; related projects between January and + March 2010. Being the first of the four reports planned for 2010 with + 46 entries, it shows a good progress of the &os; Project and proves + that our committers are keeping up with the latest trends in the OS + development. During this period, a new minor version of &os;, + 7.3-RELEASE, has been released, while the release process for + 8.1-RELEASE is soon to begin and is planned to be released later this + summer.</p> + + <p>Thanks to all the reporters for their excellent work! We hope you + enjoy the reading.</p> + + <p>Please note that the deadline for submissions covering the + period between April and June 2010 is July 15th, 2010.</p> + </section> + + <category> + <name>soc</name> + + <description>Google Summer of Code</description> + </category> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>team</name> + + <description>&os; Team Reports</description> + </category> + + <category> + <name>net</name> + + <description>Network Infrastructure</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <category> + <name>bin</name> + + <description>Userland Programs</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat="net"> + <title>Enhancing the &os; TCP Implementation</title> + + <contact> + <person> + <name> + <given>Lawrence</given> + + <common>Stewart</common> + </name> + + <email>lstewart@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://caia.swin.edu.au/freebsd/etcp09/" /> + + <url href="http://caia.swin.edu.au/urp/newtcp/" /> + + <url href="http://www.FreeBSDFoundation.org/projects.shtml" /> + + <url + href="http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/" /> + </links> + + <body> + <p>The ALQ(9) implementation and KPI has been rototilled and modified + (one more patch needs to be committed) to support variable length + messages. In addition, it can now be compiled and loaded as a kernel + module.</p> + + <p>With the ALQ changes in head, SIFTR can finally be imported.</p> + + <p>Reassembly queue autotuning is in the project branch and needs to + be extracted as a patch people can easily test.</p> + </body> + + <help> + <task>Solicit external testing for and commit SIFTR.</task> + + <task>Solicit external testing for and commit reassembly queue + autotuning patch.</task> + </help> + </project> + + <project cat="proj"> + <title>Modular Congestion Control</title> + + <contact> + <person> + <name> + <given>Lawrence</given> + + <common>Stewart</common> + </name> + + <email>lstewart@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://caia.swin.edu.au/urp/newtcp/" /> + + <url + href="http://svn.FreeBSD.org/viewvc/base/projects/tcp_cc_head/" /> + </links> + + <body> + <p>I have just completed the last disruptive change to the KPI, which + laid the groundwork to allow different congestion aware transports to + share congestion control algorithms. The import into the head branch + is a big job and my time is limited, so progress will be slow and I + will not have it done and ready to MFC by 8.1 as I had hoped. I will + aim to have it in 8.2 though.</p> + </body> + + <help> + <task>Solicit external testing.</task> + + <task>Commit to head.</task> + </help> + </project> + + <project cat="net"> + <title>(Virtual) Network Stack resource cleanup</title> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + + <common>Zeeb</common> + </name> + + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>In February work was done to address resource leaks in the + (virtual) network stack, especially on teardown.</p> + + <p>During that time also multiple general run-time problems and leaks + were identified and fixed including leaked ipfw tables on module + unload, routing entries leaked, in case of interfaces going away, as + well as leaked link-layer entries in interaction with flowtable and + timers.</p> + + <p>For virtual network stacks resources are are no longer allocated + multiple times or freed upon teardown for eventhandlers, IP and upper + level layers, like TCP syncache and host cache, flowtable, and + especially radix/routing table memory.<br /> + In addition epair(4) was enhanced and debugging was improved.</p> + + <p>This work was sponsored by ISPsystem.</p> + </body> + + <help> + <task>Merge the remaining patches.</task> + + <task>Work on a better teardown model and get to the point where we + can free UMA zones without keeping pages for type stability and + timers around.</task> + </help> + </project> + + <project cat="soc"> + <title>Google Summer of Code 2010</title> + + <contact> + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Robert</given> + + <common>Watson</common> + </name> + + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://socghop.appspot.com/org/home/google/gsoc2010/freebsd"> + &os; GSoC Homepage</url> + + <url href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline"> + GSoC Timeline</url> + </links> + + <body> + <p>We are once again participating in the Google Summer of Code. This + is our 6th year of participation and we hope to once again see great + results from our students. Currently applications have all been + submitted and we are in the process of reviewing them. Accepted + students will be announced April 26th and coding officially begins + May 24th.</p> + </body> + </project> + + <project cat="team"> + <title>Release Engineering Team</title> + + <contact> + <person> + <name> + <given>Release Engineering Team</given> + </name> + + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/" /> + </links> + + <body> + <p>The Release Engineering Team announced &os;-7.3 on March 23rd, + 2010. The schedule has been set for &os;-8.1 with the release date + planned for mid July 2010.</p> + </body> + </project> + + <project cat="proj"> + <title>mfsBSD</title> + + <contact> + <person> + <name> + <given>Martin</given> + + <common>Matuska</common> + </name> + + <email>mm@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://mfsbsd.vx.sk" /> + </links> + + <body> + <p>mfsBSD is a set of scripts that generate a bootable image (e.g. an + ISO file) that creates a working minimal installation of &os; that is + completely loaded into memory (mfs).</p> + + <p>The project has now reached a stable and well tested state. Images + can be created from 8.0-RELEASE or 7.3-RELEASE ISO image files or + from a custom makeworld.</p> + + <p>A new feature is a script called "zfsinstall" that automates a + ZFS-only install of &os; from a mfsbsd ISO (script works with + 8-STABLE and 9-CURRENT, sample ISO images can be downloaded from the + project web site).</p> + </body> + + <help> + <task>Bundle distribution installation files (target: + 8.1-RELEASE).</task> + + <task>Make zfsinstall 7.3 compatible (mostly gpart syntax).</task> + + <task>Enable zfsinstall combination with sysinstall (zfsinstall + prepares drives, sysinstall installs distribution).</task> + + <task>Integrate toolset into &os; source (tools?).</task> + </help> + </project> + + <project cat="team"> + <title>The &os; Foundation</title> + + <contact> + <person> + <name> + <given>Deb</given> + + <common>Goodkin</common> + </name> + + <email>deb@FreeBSDFoundation.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSDFoundation.org" /> + </links> + + <body> + <p>We were proud to be a sponsor for AsiaBSDCon in March. We also + committed to sponsoring BSDCan 2010 and NYCBSDCon 2010. We provided + travel grants for AsiaBSDCon.</p> + + <p>We funded a project by Murray Stokely to provide Closed Captioning + of &os; Technical Videos in the BSD Conferences YouTube Channel. We + were very pleased that the foundation funded HAST project + completed.</p> + + <p>We solicited project proposals and were very pleased with the + number of proposals we received. With our project spending budget + increase, we will be able to fund more projects this year.</p> + + <p>We grew our board of directors by adding Erwin Lansing. This will + expand our representation in Europe. Erwin brings ports knowledge and + expertise to the board.</p> + + <p>We continued our work on infrastructure projects to beef up + hardware for package-building, network-testing, etc.</p> + + <p>Follow us on + <a href="https://twitter.com/freebsdfndation">Twitter</a> + + now!</p> + + <p>We are fund-raising for 2010 now! Find out more at + <a href="http://www.FreeBSDFoundation.org/donate/"> + http://www.FreeBSDFoundation.org/donate/</a>.</p> + </body> + </project> + + <project cat="proj"> + <title>The tbemd branch</title> + + <contact> + <person> + <name> + <given>Warner</given> + + <common>Losh</common> + </name> + + <email>imp@bsdimp.com</email> + </person> + </contact> + + <body> + <p>'tbemd' stands for Target Big Endian Must Die. The current build + systems requires that one define TARGET_BIG_ENDIAN for either big + endian MIPS or big endian ARM processors. There are many problems + with this approach. The resulting system will not create the proper + binaries without TARGET_BIG_ENDIAN defined. There is no easy way to + know what the endian is of the system you are running. There are + many issues with ports, since they do not use bsd make, so do not + pick up the extra flags that are added if TARGET_BIG_ENDIAN is + defined.</p> + + <p>The tbemd branch seeks to fix this. We will move from + MACHINE_ARCH=mips for all mips platforms to MACHINE_ARCH=mipsel, + mipseb, mips64eb and mips64el to match NetBSD's conventions. These + represent 32-bit mips little endian, 32-bit mips big endian, 64-bit + mips big endian and 64-bit mips little endian respectively. ARM will + move to arm (little endian) and armeb (big endian), again following + the standards set elsewhere. To facilitate a number of different + MACHINE_ARCHs all built from the same source, a new MACHINE_CPUARCH + is introduced and represents the sources needed to build CPU support + for a given MACHINE_ARCH.</p> + + <p>In addition, MACHINE_ARCH is overused in the build system today. + Many of its uses are gratuitous and can be simplified. Many of its + uses do not scale well and need to be refactored into a system that + will scale well. A per MACHINE/MACHINE_ARCH/MACHINE_CPUARCH selection + mechanism for makefile snippets will be introduced to move much of + the current if spaghetti into more controlled lists.<br /> + The branch can build everything we currently support with the new + names.</p> + </body> + + <help> + <task>Finish migrating to bsd.arch.inc.mk.</task> + + <task>Reduce diffs between the branch and the mainline before the + collapse.</task> + + <task>Documentation needs to be written for how to use all of + this.</task> + </help> + </project> + + <project cat="proj"> + <title>Out of Tree Toolchain</title> + + <contact> + <person> + <name> + <given>Warner</given> + + <common>Losh</common> + </name> + + <email>imp@bsdimp.com</email> + </person> + </contact> + + <body> + <p>Work is underway to allow the &os; build system to use out of tree + compilers and binary utililies (loaders, linkers, etc), especially in + a cross compilation environment. While it is possible to swap out the + compiler with a compatible compiler relatively easily, swapping out + the toolchain is more involved. In addition, when using an external + compiler to build the system, certain parts of buildworld can be + omitted.</p> + </body> + + <help> + <task>Create ports for latest binutils. This work is nearly complete, + and is waiting for integration of two branches that are collapsing + soon (the 'tbemd' branch from Warner and the mips collapse from Juli + Mallet).</task> + + <task>Create ports for gcc. This work has been started. Native builds + are straight forward, but cross builds have a buildworld dependency + at the moment. These dependencies are being worked out, as well as + some gcc library dependencies.</task> + + <task>Documentation needs to be written for how to use all of + this.</task> + </help> + </project> + + <project cat="ports"> + <title>Portmaster</title> + + <contact> + <person> + <name> + <given>Doug</given> + + <common>Barton</common> + </name> + + <email>dougb@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://dougbarton.us/portmaster-proposal.html" /> + </links> + + <body> + <p>Portmaster version 2.22 is now in the ports tree and has full + support for the following new features:</p> + + <ul> + <li>Using the INDEX file to show that an installed port needs + updating.</li> + + <li>Support for installation of packages in 'try packages first,' + --packages-only, --packages-if-newer, and --packages-build + modes.</li> + + <li>A new --delete-build-only option to delete ports/packages that + are not needed at run time.</li> + + <li>Updating of the terminal title bar to show what is being worked + on, and how much more is left to do.</li> + + <li>Support for custom definitions of the packages repository and + INDEX files.</li> + + <li>The ability to operate without any local ports tree at all with + the --index-only and --packages-only options.</li> + + <li>A new dialog to confirm the list of ports to be installed.</li> + </ul> + + <p>I am very excited about these new features, and owe a debt of + gratitude to the companies and especially the individuals who stepped + forward to support this work. I literally could not have done it + without them.</p> + </body> + + <help> + <task>There are still some interesting and oft-requested features + listed on the proposal web site that I would really like to + implement, including (but not limited to) downloading of all packages + before beginning the installation, and writing out a script that can + be re-run either on that machine, or on a set of identical + machines.</task> + </help> + </project> + + <project cat="arch"> + <title>&os;/arm port for TI DaVinci</title> + + <contact> + <person> + <name> + <given>Jakub</given> + + <common>Klama</common> + </name> + + <email>jceel@semihalf.com</email> + </person> + </contact> + + <links> + <url href="http://focus.ti.com/dsp/docs/dspplatformscontenttp.tsp?sectionId=2&familyId=1300&tabId=1854"> + DaVinci on TI's site</url> + + <url href="http://p4web.FreeBSD.org/@md=d&cd=//depot/user/jceel/davinci/"> + Project branch in P4</url> + </links> + + <body> + <p>DaVinci (TMS320DM644x) is an ARM9-based system-on-chip family from + Texas Instruments with built-in DSP core and powerful + multimedia/video features. This work is bringing support for &os; on + these systems - it works in multiuser mode, using root filesystem + mounted either via NFS or from SD/MMC card. The code is available in + P4 at //depot/user/jceel/davinci/.</p> + + <p>Current DaVinci support includes:</p> + + <ul> + <li>Booting from U-Boot bootloader</li> + + <li>Serial console</li> + + <li>Interrupt controller</li> + + <li>Integrated timers</li> + + <li>Power and sleep controller</li> + + <li>10/100 Ethernet controller</li> + + <li>SD/MMC controller</li> + </ul> + </body> + + <help> + <task>Remaining built-in peripherals drivers (USB, ATA, NAND flash, + I2C, DMA engine, sound, video input/output).</task> + + <task>Framework for communicating with DSP core.</task> + </help> + </project> + + <project cat="proj"> + <title>NAND Flash framework for embedded &os;</title> + + <contact> + <person> + <name> + <given>Grzegorz</given> + + <common>Bernacki</common> + </name> + + <email>gjb@semihalf.com</email> + </person> + + <person> + <name> + <given>Rafal</given> + + <common>Jaworowski</common> + </name> + + <email>raj@semihalf.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/NAND#head-9a32aaa85046b2f9f9219e36ba34947ca47a4153"> + Project wiki pages</url> + + <url href="http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/nand2/..."> + Project P4 branch</url> + </links> + + <body> + <p>The purpose of this project is to provide embedded &os; with a + generic and flexible scheme to support NAND Flash devices. The + framework provides a set of KOBJ interfaces inside the kernel, which + allow for uniform and flexible management of the NAND devices:</p> + + <ul> + <li>NAND Flash Controller (NFC) layer, into which back-end drivers + for individual controllers plug in (implementing low-level routines + specific to a given NAND controller)</li> + + <li>Generic (common) NAND layer which provides means to perform + operations on the flash devices in an abstract way (read, program, + erase, get status etc.)</li> + + <li>NAND character device, which exports chip device as a standard + character device and allows to read/write directly to a device, as + well as perform other specific operations by using ioctl.</li> + + <li>GEOM NAND class for basic access through GEOM.</li> + </ul> + + <p>Part of the infrastructure is a full system simulator of + ONFI-compliant devices (NANDsim), with a userland control application. + This allows for exercising of the framework on platforms without real + NAND chips.</p> + + <p>Current state highlights:</p> + + <ul> + <li>The framework is considered functionally complete (including + NANDsim).</li> + + <li>Framework compliant back-end drivers are available for the + following NAND Flash controller (NFC) chips:</li> + + <ul> + <li>Freescale MPC8572 (PowerPC)</li> + + <li>Marvell MV-78100 (ARM)</li> + + <li>Samsung S3C24X0 (ARM)</li> + </ul> + </ul> + </body> + + <help> + <task>Extend interface with features / options suggested by early + adopters of the code.</task> + + <task>Complete, clean up, merge with HEAD.</task> + </help> + </project> + + <project cat="ports"> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Thomas</given> + + <common>Abthorpe</common> + </name> + + <email>portmgr-secretary@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Port</given> + + <common>Management Team</common> + </name> + + <email>portmgr@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ports/" /> + + <url href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" /> + + <url href="http://portsmon.FreeBSD.org/index.html" /> + + <url href="http://www.FreeBSD.org/portmgr/index.html" /> + + <url href="http://tinderbox.marcuscom.com/" /> + </links> + + <body> + <p>Most of quarter one was spent dealing with the 7.3-RELEASE + process. With apparent success enforcing Feature Safe ports commits + during the 8.0-RELEASE, it was continued for the recent src/ + freeze.</p> + + <p>The ports count now exceeds 21,500 ports, and counting. The open + PR count currently is over 1000. With the release of &os; 7.3, it is + hoped this count will drop drastically.</p> + + <p>Since the last report, we added four new committers, and had an + old committer rejoin us.</p> + + <p>With the donation of an Apple Xserve, powerpc builds have resumed. + Renewed interest in ia64 has brought about new ports builds. A new + sparc64 machine hosted by skreuser will help us with this build.</p> + + <p>The Ports Management team have been running -exp runs on an + ongoing basis, verifying how src code updates may affect the ports + tree, as well as providing QA runs for major ports updates. Of note + -exp runs were done for; gabor's BSD licensed bc/dc in src/, mva's + OpenAL and SDL upgrades; brooks' removal of NGROUPS; ed's removal of + libcompat and regexp.h; dinoex's jpeg update; a test run for m4 + update; jilles' update for sh(1); johans' update for bison; and + roam's curl update.</p> + </body> + + <help> + <task>Looking for help fixing + <url link="http://wiki.FreeBSD.org/PortsBrokenOnCurrent">ports broken + on CURRENT</url>.</task> + + <task>Looking for help with + <url link="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures"> + Tier-2 architectures</url>.</task> + + <task>Most ports PRs are assigned, we now need to focus on testing, + committing and closing.</task> + + <task>Major commits expected soon include the latest Xorg, KDE4, and + Gnome updates.</task> + </help> + </project> + + <project cat="kern"> + <title>IPv6 without legacy IP kernel</title> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + + <common>Zeeb</common> + </name> + + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://p4web.FreeBSD.org/@md=d&cd=//&c=MNx@//depot/user/bz/noinet/src/sys/?ac=83"> + P4 workspace</url> + </links> + + <body> + <p>During 2009 work was done that allowed us to build a &os; kernel + without INET and without INET6 (again). This work was the foundation + for a prototype to get a kernel to compile and boot with only INET6 + but no INET compiled in earlier this year.</p> + + <p>The current focus is to identify general + architectural problems and dependencies we do have between these two + address families as well as with the upper layer protocols. This will + at some point allow us to discuss the issues and seek solutions, + preparing for a future where we can remove either INET or INET6 from + the system.</p> + + <p>Once we will have a stable, in-tree way to compile out either + address family, optimizations wrt. size, as well as user space + will need to be worked on. In addition to this, the work is believed + to help should we further head in the direction of network stack + modularization.</p> + </body> + </project> + + <project cat="kern"> + <title>geom_sched</title> + + <contact> + <person> + <name> + <given>Luigi</given> + + <common>Rizzo</common> + </name> + + <email>luigi@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Fabio</given> + + <common>Checconi</common> + </name> + + <email>fabio@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://info.iet.unipi.it/~luigi/geom_sched/" /> + </links> + + <body> + <p><b>geom_sched</b> is a GEOM module that supports pluggable schedulers + for disk I/O requests. The main algorithm supported at the moment is + an anticipatory Round Robin scheduler, which is especially effective + in presence of workloads with highly random disk accesses. Other + schedulers are available on the <a + href="http://info.iet.unipi.it/~luigi/geom_sched/">geom_sched</a> + page.</p> + + <p>Developed in early 2009 and refined as a GSOC2009 project, + geom_sched has been recently introduced in HEAD and is going to be + soon merged to stable/8. A version for stable/7 also exists, with + some restrictions.</p> + + <p>To use the module, say on disk <b>ad4</b>, all you need to do + is:</p> + +<pre> +kldload geom_sched +geom sched insert ad4 +</pre> + + <p>A number of sysctl variables under kern.geom.sched allow you to + tune the parameters of the algorithm, or bypass the scheduler + entirely so you can tell the difference of behaviour with and without + the scheduler.</p> + </body> + </project> + + <project cat="net"> + <title>Experimental NFS subsystem (NFSv4)</title> + + <contact> + <person> + <name> + <given>Rick</given> + + <common>Macklem</common> + </name> + + <email>rmacklem@uoguelph.ca</email> + </person> + </contact> + + <body> + <p>Although the bare bones of the NFS Version 4 support was released + in &os; 8.0, the integration has been progressing slowly and support + should be functional for &os; 8.1 for RFC3530 (NFS Version 4.0).</p> + + <p>Post &os; 8.1, I believe the focus will be on code cleanup and, + under a projects area of svn, some experimental work on aggressive + whole file caching to client disk.</p> + </body> + + <help> + <task>Handling of delegations on the server w.r.t. local processes + running on the server.</task> + + <task>Integration of recent changes to the regular NFS client, such + as Dtrace support.</task> + </help> + </project> + + <project cat="kern"> + <title>Rewrite of &os; read/write path using vnode page</title> + + <contact> + <person> + <name> + <given>Konstantin</given> + + <common>Belousov</common> + </name> + + <email>kib@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Peter</given> + + <common>Holm</common> + </name> + + <email>pho@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://svn.freebsd.org/viewvc/base/user/kib/vm6/">Branch for + the rewrite</url> + + <url href="http://wiki.FreeBSD.org/VM6" /> + </links> + + <body> + <p>Based on the idea of Jeff Roberson, we reimplemented the path for + read(2)/write(2) syscalls using page cache (in wide sense) to + eliminate the issues with recursive vnode and buffer lock + acquisitions. The usual reads and writes are no longer calls into + VOP_READ/VOP_WRITE; the operation is done by copying user buffers to + or from the pages of the vnode. This fixes known deadlocks when reads + or writes are done over file-mmaped buffers.</p> + + <p>The patch changes the performance characteristics of I/O, and we + observed both better and worse behaviour. If filesystem implements + VOP_GETPAGES and VOP_PUTPAGES without referencing buffer cache, + buffers are completely eliminated from the i/o path (not true for UFS + or NFS).</p> + </body> + + <help> + <task>We need wider testing and reviews.</task> + </help> + </project> + + <project cat="bin"> + <title>&os; port for libunwind</title> + + <contact> + <person> + <name> + <given>Konstantin</given> + + <common>Belousov</common> + </name> + + <email>kib@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.nongnu.org/libunwind/" /> + </links> + + <body> + <p>The alpha version of libunwind library port for &os; x86 and + x86_64 is completed and imported into the official libunwind git + repository. Libunwind is the library to perform dynamic unwinding of + stacks, using dwarf call frame information. The library features + remote unwinding using ptrace(2), very fast setjmp(3) implementation + and more interesting features.</p> + </body> + </project> + + <project cat="arch"> + <title>&os;/mips on D-Link DIR-320</title> + + <contact> + <person> + <name> + <given>Alexandr</given> + + <common>Rybalko</common> + </name> + + <email>ray@dlink.ua</email> + </person> + </contact> + + <links> + <url href="http://wiki.ddteam.net/wiki.cgi?page=DIR-320+FreeBSD" /> + </links> + + <body> + <p>&os;/mips has been ported to D-Link DIR-320, wireless router based + on BCM5354 SoC. Project aims to providing several working images + tailored for different purposes (profiles). So far + <a href="http://ipsec-tools.sourceforge.net/">racoon</a> + based router-ipsec image is available.</p> + </body> + + <help> + <task>bfeswitch configuration utility.</task> + + <task>Add router profile.</task> + + <task>Add wifi-router profile.</task> + + <task>Add openvpn-router profile.</task> + </help> + </project> + + <project cat="net"> + <title>ipfw and dummynet enhancements</title> + + <contact> + <person> + <name> + <given>Luigi</given> + + <common>Rizzo</common> + </name> + + <email>luigi@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://info.iet.unipi.it/~luigi/dummynet/">main dummynet + page</url> + + <url href="http://www.youtube.com/watch?v=r8vBmybeKlE">youtube video + on dummynet internals</url> + + <url href="http://info.iet.unipi.it/~luigi/qfq/">Description of the + qfq scheduler</url> + </links> + + <body> + <p>We have recently completed a massive revision of ipfw and + dummynet, and the result has been committed to HEAD and stable/8. + The main features introduced with this work are:</p> + + <ul> + <li>ipfw now has much faster skipto instructions, including + table-based ones. The complexity for rule lookups is now O(1) or + O(log N) as opposed to the O(N) that we had before. People using + "skipto tablearg" or "pipe tablearg" with large numbers of rules or + pipes should see a significant performance improvement;</li> + + <li>Expensive operations in response to userland reconfigurations + now do not interfere with kernel filtering for more than the time + required to swap a pointer;</li> + + <li>You can now use ports and the "tos" field as lookup argument + for tables. This might allow some simplifications in rulesets which + in turn result in faster execution time;</li> + + <li>ipfw can now send packets matching rules with a 'log' attribute + to the "ipfw0" pseudo interface, where you can run tcpdump to + implement additional filtering, logging etc.;</li> + + <li>dummynet now supports many different scheduler types, to adapt + to different needs people may have in terms of performance and + service guarantees. Existing schedulers now include FIFO, WF2Q+, + Deficit Round Robin, Priority, and QFQ. More schedulers can be + implemented as loadable kernel modules.;</li> + + <li>The kernel side has a backward-compatible interface so you can + use a RELENG_7 or RELENG_8 version of /sbin/ipfw to configure the + firewall and dummynet.</li> + </ul> + </body> + + <help> + <task>There is ongoing work on optimizing the deletion of idle + entries in dummynet. This should be completed shortly.</task> + + <task>A longer term goal is to parallelize operation in presence of + ipfw dynamic rules, which currently require exclusive lock on a hash + table containing dynamic rules.</task> + </help> + </project> + + <project cat="arch"> + <title>&os;/sparc64</title> + + <contact> + <person> + <name> + <given>Marius</given> + + <common>Strobl</common> + </name> + + <email>marius@FreeBSD.org</email> + </person> + </contact> + + <body> + <ul> + <li>Yet another bug causing unaligned accesses in NFS server + operation has been found and fixed in &os; 7 and 8. Unlike as + announced in the last Status Report, no Erratum Notices regarding + these problems have been issued as it quickly became obvious + that dealing with so many of them is impractical, especially + since the fixes unveiled secondary bugs.</li> + + <li>Alexander Motin has fixed several bugs in netgraph(4) nodes in + 9.0-CURRENT which also caused unaligned accesses, so these should + work now on sparc64.</li> + + <li>Peter Jeremy has contributed several fixes for the sparc64 FPU + emulation code, which now passes a test suite built around + TestFloat. These fixes were incorporated into &os; 6, 7 and 8 + but unfortunately did not quite make it into 7.3-RELEASE but will + be present in 8.1-RELEASE and 7.4-RELEASE.</li> + + <li>Support for UltraSPARC-IV and -IV+ CPUs has been added and will + be present in 8.1-RELEASE and 7.4-RELEASE. Thus Sun Fire V890 is + now supported and stable, though due to the lack of properly working + test hardware, not with configurations consisting of a mix of US-IV + and -IV+ CPUs. However, performance is not yet where it should be, + i.e. a buildworld on a 4x1.5GHz US-IV+ Sun Fire V890 takes nearly 3 + hours while on a Sun Fire V440 with (theoretically) less powerful + 4x1.5GHz US-IIIi CPUs it takes just over 1 hour. So far it is + unclear what is causing this, it might have to with what appears to + be a silicon bug of US-IV+ CPUs encountered and worked around while + adding support for these.</li> + + <li>Work on getting Sun Fire V1280 supported has been continued. + A third firmware bug has been worked around and a driver for + the BootBus controller, which provides console and time-of-day + services in these machines, has been written. It is now possible to + netboot Sun Fire V1280 into multi-user mode. Unfortunately, they do + not run stable as processes may hang when transitioning to another + CPU, likely due to what the OpenSolaris code refers to as Cheetah+ + erratum 25, but which unfortunately is not part of the publicly + available US-III+/++ errata document. Efforts on understanding this + problem are still ongoing.</li> + + <li>Mark Linimon is trying to find volunteers interested in helping + to fix packages on sparc64.</li> + </ul> + </body> + </project> + + <project cat="proj"> + <title>Chromium web browser</title> + + <contact> + <person> + <name> + <given>sprewell</given> + </name> + + <email>chromium@jaggeri.com</email> + </person> + </contact> + + <links> + <url href="http://chromium.jaggeri.com">Main chromium site</url> + + <url href="http://wiki.FreeBSD.org/Chromium">Build instructions for + older patches</url> + </links> + + <body> + <p>Chromium is a Webkit-based web browser that is mostly BSD + licensed. It works very well on &os; and even supports new features + like HTML 5 video. I have started offering subscriptions to fund the + porting effort to &os;, funding which has already paid to fix + Chromium on BSD-i386. I am using a new funding model where + subscriptions pay for development that is kept closed for at most 1 + year, after which all patches used in a build are released to + subscribers under the same BSD license as Chromium. Also, parts of + the closed patches are continually pushed upstream, + <a href="http://codereview.chromium.org/1543003">the BSD i386 fix has + already been committed upstream</a>. + The goal is to fund Chromium development on BSD while continually + pushing patches back to the BSD-licensed Chromium project. I will + spin off a Chromium port for ports soon, for those who do not mind + using an older, stable build that does not have all the paid features + in the subscriber builds. You can read about + <a href="http://chromium.jaggeri.com/issues">the issues that a + subscription would pay for, such as replacing the ALSA audio backend + with OSS</a>, and + <a href="http://chromium.jaggeri.com/subscriptions">find out more + about subscribing</a>.</p> + </body> + </project> + + <project cat="docs"> + <title>The &os; Hungarian Documentation Project</title> + + <contact> + <person> + <name> + <given>Gábor</given> + + <common>Kövesdán</common> + </name> + + <email>gabor@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gábor</given> + + <common>Páli</common> + </name> + + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/hu/">Hungarian &os; Web Pages</url> + + <url href="http://www.FreeBSD.org/doc/hu/">Hungarian &os; + Documentation</url> + + <url href="http://wiki.FreeBSD.org/HungarianDocumentationProject">The + &os; Hungarian Documentation Project's Web Page</url> + + <url href="http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83"> + The &os; Hungarian Documentation Project's Perforce Repository</url> + </links> + + <body> + <p>We restlessly keep the existing documentation and web page + translations up to date. However, this will not last forever, and + help is always welcome, so if you feel yourself Hungarian with some + interests in translation, please contact our Documentation Project + via the email addresses noted above.</p> + </body> + + <help> + <task>Translate release notes.</task> + + <task>Translate articles.</task> + + <task>Translate web pages.</task> + + <task>Read translations, send feedback.</task> + </help> + </project> + + <project cat="arcj"> + <title>&os;/mips on Octeon</title> + + <contact> + <person> + <name> + <given>Juli</given> + + <common>Mallett</common> + </name> + + <email>jmallett@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://svn.FreeBSD.org/base/user/jmallett/octeon/"> + Subversion branch</url> + </links> + + <body> + <p>Significant progress has been made in terms of stabilizing the + uniprocessor Octeon port and adding support for MIPS ABIs other than + o32 in the toolchain, rtld, libc and the kernel. Kernels built to the + n32 ABI are currently supported with changes that will not be merged + because they make invasive changes throughout the system with regard + to db_expr_t and register_t, which are larger than a pointer in the + n32 ABI. Once support for n64 kernels is completed (including the + ability to run n32 worlds) and the n32 hacks are removed, the branch + will be suitable for merging. Many nearby cleanups have occurred, + particularly in the area of TLB and pmap code.</p> + </body> + + <help> + <task>An import of select pieces of the Cavium simple executive as + vendor code is planned to make it possible to remove + locally-maintained copies of Cavium headers and shim functions, many + of which are vastly outdated.</task> + + <task>The Linux opencrypto port contains an opencrypto driver for the + cryptographic coprocessor which look relatively easy to port.</task> + + <task>Support for SMP is a high-priority item that will be addressed + after the 64-bit changes are stabilized.</task> + + <task>PCI and USB bus and device support is planned to follow the + import of the simple executive functions and headers.</task> + + <task>The rgmx ethernet driver currently copies packets in and out of + mbufs rather than putting pointers to mbuf storage into hardware, + which results in bad network performance.</task> + </help> + </project> + + <project cat="kern"> + <title>Dynamic Ticks in &os;</title> + + <contact> + <person> + <name> + <given>Tsuyoshi</given> + + <common>Ozawa</common> + </name> + + <email>ozawa@t-oza.net</email> + </person> + </contact> + + <links> + <url href="http://github.com/oza/FreeBSD-8.0-dyntick">Project page + (github).</url> + + <url href="http://tsuyoshiozawa.blogspot.com/2010/03/started-to-implement-dynticks-in.html"> + My weblog article which describes benchmark of dynamic ticks.</url> + </links> + + <body> + <p>I wrote experimental code (please see my project page) and threw + patch ( http://gist.github.com/350230 ) to freebsd-hackers. A lot of + &os; hackers gave me precious advice, so I am going to reflect it as + a next step.</p> + </body> + + <help> + <task>Run hard/stat/prof-clocks irregularly (in progress).</task> + + <task>Some timers which are added after the kernel's scheduling next + timer interrupt may be ignored (BUG).</task> + + <task>Make callout queue have the tick when the next timer event rise + up.</task> + </help> + </project> + + <project cat="docs"> + <title>The &os; German Documentation Project</title> + + <contact> + <person> + <name> + <given>Johann</given> + + <common>Kois</common> + </name> + + <email>jkois@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Benedict</given> + + <common>Reuschling</common> + </name> + + <email>bcr@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://doc.bsdgroup.de" /> + </links> + + <body> + <p>Our last status report listed a number of documents that needed + help. Thanks to the external contributions of Frank Boerner we were + able to update a substantial amount of documents. This has resulted + in a great reduction of our backlog. Subsequently, Benedict has + agreed to take Frank under mentorship for the German doc project. We + are looking forward to his future contributions and thank him for his + past efforts.</p> + + <p>Johann was busy keeping the German website in sync with updates to + FreeBSD.org. However, there are still parts of the website that + remain untranslated. We are looking for more support in maintaining + the German website.</p> + + <p>&os; users with German language skills are always welcome to join + our efforts in translating the documentation and/or fixing bugs.</p> + </body> + + <help> + <task>Translate more parts of the documentation and the German + website.</task> + + <task>Keep the current documentation up to date.</task> + + <task>Report bugs to <a href="mailto:de-bsd-translators@de.FreeBSD.org"> + de-bsd-translators@de.FreeBSD.org</a>.</task> + </help> + </project> + + <project cat="ports"> + <title>QAT</title> + + <contact> + <person> + <name> + <given>Ion-Mihai</given> + + <common>Tetcu</common> + </name> + + <email>itetcu@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Josh</given> + + <common>Paetzel</common> + </name> + + <email>jpaetzel@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>QAT has been running on a single server for about two years now + and has proven very effective at catching problems with ports + commits. Many of the problems it cannot catch are architecture or + branch related. By moving QAT to a VMware box capable of running + arbitrary versions of &os; on both amd64 and i386 this limitation + will be removed.</p> + </body> + + <help> + <task>Bring VMware server online and provision VMs.</task> + + <task>Refactor QAT code to handle concurrent builds.</task> + + <task>Migrate the existing QAT to the new setup.</task> + </help> + </project> + + <project cat="kern"> + <title>CAM-based ATA implementation</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Motin</common> + </name> + + <email>mav@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work on CAM-based ATA implementation continues. Since last report + handling of heavy errors and timeouts was improved, Hot-plug now + works for both Host and Port Multiplier ports. Series of changes were + made to CAM to fix some old issues and honor some new ATA + demands.</p> + + <p>New drivers ahci(4) and siis(4) got some fixes and are quite + stable now. "options ATA_CAM" kernel option shows good results in + supporting other controllers using existing ata(4) drivers, so it is + possible to start deprecating old ata(4) APIs now.</p> + + <p>Started work on new Marvell SATA driver for both PCI-X/PCIe cards + and ARM System-on-Chip SATA controllers. It is expected to support + NCQ, Port Multipliers with FIS-based switching and other new + features.</p> + + <p>Most of the code is present in 8-STABLE.</p> + </body> + + <help> + <task>Port ataraid(4) functionality to GEOM module.</task> + + <task>Write SAS-specific transport and drivers for SAS HBAs (specs + wanted). SAS controllers can support SATA devices and multipliers, so + it should fit nicely into new infrastructure.</task> + </help> + </project> + + <project cat="kern"> + <title>Multichannel playback in HDA sound driver (snd_hda)</title> + + <contact> + <person> + <name> + <given>Alexander</given> + + <common>Motin</common> + </name> + + <email>mav@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>snd_hda(4) audio driver got real multichannel playback support. It + now supports 4.0 (quadro), 5.1 and 7.1 analog speaker setups. Digital + multichannel AC3/DTS passthrough was already implemented earlier. + Digital multichannel LPCM output via HDMI could also be possible now, + but is not tested.</p> + + <p>To use multichannel playback you should have fresh 8-STABLE + kernel, instruct sound(4) vchans subsystem (if you are using it) + about your speaker setup using dev.pcm.X.play.vchanformat sysctls and + use your audio/video player application to play multichannel audio + content without down-mixing it to stereo.</p> + </body> + + <help> + <task>HDMI/DisplayPort often require some audio support from X11 + video drivers. This area still should be investigated and tested, + especially relayed to multichannel LPCM playback.</task> + </help> + </project> + + <project cat="team"> + <title>&os; Bugbusting Team</title> + + <contact> + <person> + <name> + <given>Gavin</given> + + <common>Atkinson</common> + </name> + + <email>gavin@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Remko</given> + + <common>Lodder</common> + </name> + + <email>remko@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Volker</given> + + <common>Werth</common> + </name> + + <email>vwe@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/support.html#gnats">GNATS</url> + + <url href="http://wiki.FreeBSD.org/BugBusting">BugBusting</url> + + <url href="http://people.FreeBSD.org/~linimon/studies/prs/"> + experimental report pages</url> + + <url href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html"> + PRs recommended for committer evaluation by the bugbusting team</url> + + <url href="http://people.FreeBSD.org/~linimon/recommended_subscribers.txt"> + (subscription list for the above report)</url> + + <url href="http://people.FreeBSD.org/~linimon/studies/prs/easy_prs.html"> + PRs considered 'easy' by the bugbusting team (these are low-hanging + fruit)</url> + + <url href="http://people.FreeBSD.org/~linimon/studies/prs/prs_for_all_groups.html"> + summary chart of PRs with tags</url> + + <url href="http://wiki.FreeBSD.org/AssigningPRs">Assigning PRs</url> + </links> + + <body> + <p>Bruce Cran (brucec) has graduated from GNATS-only access to having + a src commit bit. He has been making commits to help us catch up with + the PR backlog. Thanks!</p> + + <p>We continue to classify PRs as they arrive, adding 'tags' to the + subject lines corresponding to the kernel subsystem involved, or man + page references for userland PRs. These tags, in turn, produce lists + of PRs sorted both by tag and by manpage. The most recent use of + these tags is the creating of a new report, Summary Chart of PRs With + Tags, which sorts tagged PRs into logical groups such as filesystem, + network drivers, libraries, and so forth. The slice labels are + clickable. The chart is updated once a day. You can consider it as a + prototype for browsing "sub-categories" of kernel PRs.</p> + + <p>The "recommended list" has been split up into "non-trivial PRs + which need committer evaluation" and the "easy list" of trivial PRs, + to try to focus some attention on the latter.</p> + + <p>New reports were added for "PRs which are from &os; vendors or + OEMs", "PRs containing code for new device drivers", and "PRs + referencing other BSDs". These will primarily be of interest to + committers.</p> + + <p>Some other bitrot on the "experimental PR reports" pages has been + fixed.</p> + + <p>It is now possible for interested parties to be emailed a weekly, + customized, report along the lines of the above. If you are + interested in setting one up, contact <a + href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>.</p> + + <p>The overall PR count has recently jumped to around 6400. This may + be due to increasing uptake of &os; 8.</p> + + <p>Our clearance rate of PRs, especially in kern and bin, seems to be + improving.</p> + + <p>Mark Linimon polled various committers about their interest in + specific PRs. As a result, the AssigningPRs page on the wiki and the + src/MAINTAINERS file were updated based on feedback.</p> + + <p>As always, anybody interested in helping out with the PR queue is + welcome to join us in #freebsd-bugbusters on EFnet. We are always + looking for additional help, whether your interests lie in triaging + incoming PRs, generating patches to resolve existing problems, or + simply helping with the database housekeeping (identifying duplicate + PRs, ones that have already been resolved, etc). This is a great way + of getting more involved with &os;!</p> + </body> + + <help> + <task>We will be having a bugbusting session at BSDCan. If you are + developer who will be attending the conference, please stop + by.</task> + + <task>try to find ways to get more committers helping us with closing + PRs that the team has already analyzed.</task> + </help> + </project> + + <project cat="arch"> + <title>&os;/ia64</title> + + <contact> + <person> + <name> + <given>Mark</given> + + <common>Linimon</common> + </name> + + <email>linimon@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The stability of the machines under package build has been + improved by a number of recent commits. Some rework is underway to + run with WITNESS. However, we are still limited in the number of + simultaneous packages that can be built.</p> + + <p>Based on this, we have completed the first full ia64-8 package + build. 17187 were built (as compared to 19885 on a recent i386-8.) + Mark Linimon has gone through the results to denote which packages do + not build. A few fixes have already been committed based on this.</p> + + <p>We currently have 3 available machines that are stable enough for + package builds.</p> + + <p>Support for the SGI Altix 350 has made its start. Porting is done + on 2 SGI Altix 350 machines connected with NUMAFlex, giving a total + of 4 CPUs and 24GB of DDR. The kernel boots with code on the + projects/altix branch but since ACPI does not enumerate PCI busses, + no hardware devices are found. SMP has been disabled because waking + up the APs result in a machine check.</p> + </body> + + <help> + <task>Continue to try to understand why multiple simultaneous package + builds bring the machines down.</task> + + <task>Upgrade the firmware on the two machines at Yahoo! to see if + that helps the problem.</task> + + <task>Figure out why the fourth machine is not stable.</task> + + <task>Configure a fifth machine that has been made available to + us.</task> + + <task>Figure out the problems with the latest gcc port.</task> + + <task>We need documentation about the SGI SAL implementation to speed + up porting to the SGI Altix 350.</task> + + <task>The loader and kernel need to change to allow the kernel to be + loaded at a runtime-determined physical address as well as add + support for NUMA.</task> + </help> + </project> + + <project cat="arch"> + <title>&os;/powerpc</title> + + <contact> + <person> + <name> + <given>Nathan</given> + + <common>Whitehorn</common> + </name> + + <email>nwhitehorn@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>An Apple XServe G5 has been donated by Peter Grehan for package + building. Based on the last two months' worth of testing, a large + number of commits have been made to increase stability.</p> + + <p>We have completed the first full powerpc-8 package build. Only + 10918 were built (as compared to 19885 on a recent i386-8), primarily + due to a few high-impact packages failing (such as lang/python25). + Mark Linimon has gone through the results to denote which packages do + not build. A few fixes have already been committed based on this; we + have patches that are being tested in the next run.</p> + + <p>Mark Linimon is working on getting us more XServes.</p> + </body> + + <help> + <task>Start the hard work of fixing individual packages.</task> + </help> + </project> + + <project cat="bin"> + <title>LDAP support in base system</title> + + <contact> + <person> + <name> + <given>Xin</given> + + <common>ZHAO</common> + </name> + + <email>quakelee@geekcn.org</email> + </person> + + <person> + <name> + <given>Xin</given> + + <common>LI</common> + </name> + + <email>delphij@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>&os; is currently lacking support of LDAP based authentication and + user identity.</p> + + <p>We have integrated a stripped down + <a href="http://www.openldap.org/">OpenLDAP</a> + library (renamed to avoid conflict with ports OpenLDAP libraries), as + well as some changes to OpenSSH as well as plugins for PAM, NSS and + can support.</p> + + <p>We have used several existing works and updated them to use new + OpenLDAP API, fixed several bugs and integrated them together. All + these works are under BSD or similar license and our new work would be + under 2-clause BSD license. Currently, we support storing user + identity, password and SSH public keys in LDAP tree.</p> + </body> + + <help> + <task>Further code review.</task> + + <task>Make the changes less intrusive.</task> + + <task>Fix issues found in production deployment.</task> + </help> + </project> + + <project cat="proj"> + <title>EFI support for &os;/i386</title> + + <contact> + <person> + <name> + <given>Rui</given> + + <common>Paulo</common> + </name> + + <email>rpaulo@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Work on supporting EFI booting on &os;/i386 resumed. The boot + loader can now read an ELF file from the EFI FAT partition. We are + now working on trying to boot a kernel.</p> + </body> + </project> + + <project cat="arch"> + <title>&os;/powerpc64 port</title> + + <contact> + <person> + <name> + <given>Nathan</given> + + <common>Whitehorn</common> + </name> + + <email>nwhitehorn@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>A full 64-bit PowerPC port of &os; is now complete, and should + shortly be merged to HEAD, likely first appearing in &os; 9.0. This + port supports SLB-based 64-bit server CPUs, such as the IBM POWER4-7, + PowerPC 970 (G5), and Cell Broadband Engine. Current machine support + is limited to Apple single and dual processor G5 systems, with future + support planned for IBM Power Systems servers and the Sony + PlayStation 3.</p> + </body> + </project> + + <project cat="net"> + <title>net80211 rate control framework</title> + + <contact> + <person> + <name> + <given>Rui</given> + + <common>Paulo</common> + </name> + + <email>rpaulo@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~rpaulo/ratectl.diff" /> + </links> + + <body> + <p>The net80211 (wireless) stack will support a modular rate control + framework soon. The idea is to reduce some code in the drivers and + add more rate control algorithms in the tree. All drivers that do + rate control in software will automatically benefit from this + project. On this stage, we are working on changing all the necessary + drivers to cope with the new framework and making sure it all works + as expected. Later this year we will bring the necessary changes to + change the rate control algorithm with ifconfig(1).</p> + + <p>If you are doing rate control algorithm or research on rate + control algorithms for wireless networks, &os; is now an ideal + candidate for testing your project!</p> + </body> + </project> + + <project cat="net"> + <title>802.11n support</title> + + <contact> + <person> + <name> + <given>Rui</given> + + <common>Paulo</common> + </name> + + <email>rpaulo@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>802.11n support in the Atheros driver is being worked on. Right + now it can do AMPDU RX in software and we are working on TX AMPDU. + The code lives in a private Perforce branch, but some bits of it are + already committed to HEAD.</p> + + <p>This work is being sponsored by iXsystems, inc.</p> + </body> + </project> + + <project cat="net"> + <title>Atheros AR9285 support</title> + + <contact> + <person> + <name> + <given>Rui</given> + + <common>Paulo</common> + </name> + + <email>rpaulo@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Atheros AR9285 support was added to &os; HEAD and 8-STABLE. There + are still some issues but in general it works fine.</p> + </body> + </project> + + <project cat="proj"> + <title>webcamd</title> + + <contact> + <person> + <name> + <given>Hans Petter</given> + + <common>Selasky</common> + </name> + + <email>hselasky@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.selasky.org/hans_petter/video4bsd/" /> + </links> + + <body> + <p><B>Webcamd</B> + is a userland daemon that enables use of hundreds of different USB + based Linux device drivers under the &os;-8/9 operating system. + Current focus has been on USB webcam and USB DVB-T/S/C devices. + It is also possible to use the webcamd framework to make other Linux + kernel USB devices work under the &os;-8/9 operating system, without + violating the GPL license. The daemon currently depends on libc, + pthreads, libusb and libcuse4bsd. Cuse4BSD is a new character device + from userland implementation that fully supports open, read, write, + ioctl, mmap and close file operations.</p> + + <p>If you like this project or want me to spend more time on it, you + can support it by transferring money to hselasky@c2i.net via + paypal.</p> + </body> + + <help> + <task>Testing and bugfixes.</task> + + <task>Add support for more device drivers.</task> + </help> + </project> + + <project cat="misc"> + <title>meetBSD 2010 -- The BSD Conference</title> + + <contact> + <person> + <name> + <given>meetBSD</given> + + <common>Information</common> + </name> + + <email>info@meetbsd.org</email> + </person> + </contact> + + <links> + <url href="http://www.meetbsd.org" /> + </links> + + <body> + <p>meetBSD is an annual event gathering users and developers of the + BSD operating systems family, mostly &os;, NetBSD and OpenBSD. Afer + the special California edition, meetBSD Wintercamp in Livigno, this + year we are back to Krakow, Poland.</p> + + <p>meetBSD 2010 will be held on 2-3 July at Jagiellonian + University.</p> + + <p>See the conference main web site for more details.</p> + </body> + </project> + + <project cat="kern"> + <title>ZFS</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + + <common>Dawidek</common> + </name> + + <email>pjd@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Martin</given> + + <common>Matuska</common> + </name> + + <email>mm@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Xin</given> + + <common>LI</common> + </name> + + <email>delphij@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs"> + Perforce tree for latest ZFSv25 work</url> + + <url href="http://hub.opensolaris.org/bin/view/Community+Group+zfs/WebHome"> + OpenSolaris ZFS homepage</url> + </links> + + <body> + <p>The ZFS file system has been updated to version 14 on both -HEAD + and 8-STABLE. Ongoing work is undergoing to bring bug fixes and + performance improvements from upstream svn -HEAD to approximately ZFS + v15 in the near future, and a full upgrade of ZFS to version 24 + including the de-duplication functionality, etc. The de-duplication + functionality is currently partly supported, which is demonstrated + below:</p> + +<pre> +# uname -sr +FreeBSD 9.0-CURRENT +# zpool create tank ad{4,6,8,10} +# zpool get version tank +NAME PROPERTY VALUE SOURCE +tank version 24 default +# zfs set dedup=on tank +# dd if=/dev/random of=/tank/rand0 bs=1m count=1024 +# zpool get allocated,dedupratio tank +NAME PROPERTY VALUE SOURCE +tank allocated 1.00G - +tank dedupratio 1.00x - +# dd if=/tank/rand0 of=/tank/rand1 bs=1m +# dd if=/tank/rand0 of=/tank/rand2 bs=1m +# dd if=/tank/rand0 of=/tank/rand3 bs=1m +# zpool get allocated,dedupratio tank +NAME PROPERTY VALUE SOURCE +tank allocated 1.01G - +tank dedupratio 4.00x - +</pre> + </body> + + <help> + <task>Bring ZFS v15 changes to svn -HEAD and MFC.</task> + + <task>Further polish the code in perforce and test for functionality, + etc.</task> + </help> + </project> + + <project cat="proj"> + <title>Clang replacing GCC in the base system</title> + + <contact> + <person> + <name> + <given>Ed</given> + + <common>Schouten</common> + </name> + + <email>ed@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Roman</given> + + <common>Divacky</common> + </name> + + <email>rdivacky@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Brooks</given> + + <common>Davis</common> + </name> + + <email>brooks@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Pawel</given> + + <common>Worach</common> + </name> + + <email>pawel.worach@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" /> + + <url href="http://lists.FreeBSD.org/pipermail/FreeBSD-current/2010-April/016648.html" /> + </links> + + <body> + <p>Since the last status report we got to the state where we are able + to build all of &os; (the C and C++ bits) on i386/amd64 with clang. + The only exception is the bootloader which does not fit within the + given size constraint. This is where the current efforts are going + on. The C++ part got a big boost now being able to compile all C++ + code in &os; and itself.</p> + + <p>We saw some movement on Mips and PowerPC. Mips got its driver + definitions from Oleksander Tymoshenko and Nathan Whitehorn did the + same for PowerPC and tested the kernel. Currently, the PPC kernel + seems to boot but due to lack of va_arg implementation for PowerPC + nothing is printed out. Nathan is working on that.</p> + + <p>Overall ClangBSD is selfhosting on i386/amd64 and some progress + has been made on PowerPC/PPC. We also saw some contribution to the + Sparc64 but this seems to have stalled.</p> + + <p>We need people to try out ClangBSD (see the wiki) and runtime test + it. We also would appreciate help with other archs - namely ARM.</p> + </body> + + <help> + <task>Runtime test ClangBSD on amd64/i386.</task> + + <task>Help with ARM/Mips/Sparc64.</task> + + <task>More testing of clang on 3rd party apps (ports).</task> + + <task>Discussion on integrating LLVM/clang into &os;.</task> + </help> + </project> + + <project cat='kern'> + <title>SUJ: Journaled Softupdates</title> + + <contact> + <person> + <name> + <given>Jeff</given> + <common>Roberson</common> + </name> + <email>jeff@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://jeffr_tech.livejournal.com/" /> + </links> + + <body> + <p>The soft-updates journaling project is nearing completion and will + be available in head by the time this status report is released. + Backports to other releases are maintained in <a + href="svn://svn.FreeBSD.org/base/projects/suj">SVN</a>. SUJ is + fully backwards compatible with non-journaled softupdates. Existing + systems will not be affected. Journaling may be enabled and disabled + by tunefs on unmounted filesystems. Journaling provides near-instant + filesystem recovery after crash at the expense of some runtime + performance and extra disk I/O.</p> + </body> + </project> + + <project cat='proj'> + <title>PC-BSD PC-SysInstall Backend</title> + + <contact> + <person> + <name> + <given>Kris</given> + <common>Moore</common> + </name> + <email>kmoore@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.pcbsd.org" /> + <url href="http://trac.pcbsd.org/browser/pcbsd/trunk/pc-sysinstall"> + pc-sysinstall in Trac</url> + </links> + + <body> + <p>We are currently doing a lot of code cleanup in the new System + Installer backend for PC-BSD, pc-sysinstall, which can be used to + install regular &os; as well. Some new features have already been + implemented, such as:</p> + + <ul> + <li>Improved ZFS support, raidz, mirroring, multiple mount-points + per-pool, etc.</li> + <li>Support for GPT/EFI on "Full" installations, allowing us to go + beyond the 2TB barrier.</li> + <li>MBR Slice/Partition manager.</li> + <li>geli passphrase support.</li> + </ul> + </body> + + <help> + <task>We are mostly finished migrating to only using gpart instead of + fdisk, which gives us some new functionality for dealing with GPT/EFI + partitioning schemes.</task> + </help> + </project> + + <project cat='net'> + <title>TCP/UDP connection groups</title> + + <contact> + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + <person> + <name> + <common>&os; network mailing list</common> + </name> + <email>freebsd-net@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>This on-going project is to reduce tcbinfo/udbinfo lock and cache + line contention; this global lock protects access to connection lists, + and while it is a read-write lock, it is acquired for every in-bound + packet (briefly) to look up the connection. This project adds a new + connection group table, which assigns connections to groups, each of + which has CPU affinity and aligns with RSS-selected queues in high-end + 1gbps and most 10gbps implementations. The following tasks have been + completed:</p> + + <ul> + <li>Teach libkvm to handle dynamic per-cpu storage (DPCPU) to improve + crashdump analysis of per-CPU data.</li> + <li>Teach netstat to monitor netisr DPCPU queues for live kernels and + crashdumps.</li> + <li>Create a new inpcbgroup abstraction, used for UDP and TCP.</li> + <li>Distribute UDP and TCP connections (inpcbs) over groups based on + 4-tuple bindings.</li> + <li>Replicate membership across all groups for wildcard socket + bindings.</li> + <li>Write new TCP/UDP connection and binding regression tests.</li> + </ul> + + <p>The following tasks remain:</p> + + <ul> + <li>Migrate from naive work assignment algorithm to RSS + assignment.</li> + <li>Modify device driver KPI to allow consistent initialization and + configuration between stack and hardware.</li> + <li>Complete migration to dynamic, per-CPU network statistics in TCP, + UDP, and IP.</li> + <li>Add socket options to query effective CPU affinity of connections + from userspace.</li> + <li>On supporting hardware, allow affinity for a specific connection + to be explicitly migrated using a socket option.</li> + <li>Detailed performance evaluation and optimization.</li> + </ul> + + <p>This work is being performed in the &os; Perforce repository, and + is sponsored by Juniper Networks. Connection groups and related + features are slated for inclusion in &os; 9.0 (with possible + backports to 8-STABLE of some features).</p> + </body> + </project> + + <project cat='misc'> + <title>BSDCan 2010 — The BSD Conference</title> + + <contact> + <person> + <name> + <given>BSDCan Information</given> + </name> + <email>info@BSDCan.org</email> + </person> + </contact> + + <links> + <url href="http://www.BSDCan.org/2010/" /> + <url href="http://www.BSDCan.org/2010/schedule/">Tutorials and Talks Schedule</url> + </links> + + <body> + <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> + </body> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2010-04-2010-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2010-04-2010-06.xml new file mode 100644 index 0000000000..9688c9adeb --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2010-04-2010-06.xml @@ -0,0 +1,2381 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status +Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2010-04-2010-06.xml,v 1.8 2010/07/22 14:14:14 danger Exp $ --> +<report> + <date> + <month>April-June</month> + <year>2010</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report covers &os;-related projects between April and June + 2010. It is the second of the four reports planned for 2010, and + contains 47 entries. During this period, a lot of work has + gone into the development of new minor version of &os;, 8.1-RELEASE, + which should be released within days.</p> + + <p>Thanks to all the reporters for the excellent work! We hope you + enjoy reading.</p> + + <p>Please note that the deadline for submissions covering the + period between July and September 2010 is October 15th, 2010.</p> + </section> + + <category> + <name>soc</name> + <description>Google Summer of Code</description> + </category> + + <category> + <name>proj</name> + <description>Projects</description> + </category> + + <category> + <name>team</name> + <description>&os; Team Reports</description> + </category> + + <category> + <name>net</name> + <description>Network Infrastructure</description> + </category> + + <category> + <name>kern</name> + <description>Kernel</description> + </category> + + <category> + <name>docs</name> + <description>Documentation</description> + </category> + + <category> + <name>bin</name> + <description>Userland Programs</description> + </category> + + <category> + <name>arch</name> + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + <description>Ports</description> + </category> + + <category> + <name>misc</name> + <description>Miscellaneous</description> + </category> + + <project cat='docs'> + <title>The &os; German Documentation Project</title> + + <contact> + <person> + <name> + <given>Johann</given> + <common>Kois</common> + </name> + <email>jkois@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Benedict</given> + <common>Reuschling</common> + </name> + <email>bcr@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://doc.bsdgroup.de">Website of the &os; German + Documentation Project</url> + + <url href="http://www.FreeBSD.de/mailinglists.html">Mailing lists + for the coordination of our work and the place where you can report + bugs back to us</url> + </links> + + <body> + <p>A number of updates to the documentation were made since the + last status report. We are especially grateful for the + contributions from external people who sent the translations. People + like Fabian Ruch, who updated the porters-handbook to the latest + version (which had been on his to-do list for quite some time), and + Benjamin Lukas, who did a great job with the from-scratch + translation of the MAC chapter of the German handbook. We thank + them both for their contributions and hope they will continue their + efforts to enhance the German documentation.</p> + + <p>Frank Börner was released from Benedicts mentorship and is + now a full committer to the German Documentation Project. We are + always looking for fresh blood that is willing to be mentored by us + as a first step in becoming committers for the documentation project + themselves.</p> + + <p>Johann is keeping up the German website with the latest version. + But we could use more translators for sections that are not fully + translated yet.</p> + </body> + + <help> + <task>Read the translations and report bugs that you have found (even + small ones).</task> + + <task>Translate new parts of the documentation and the + website.</task> + </help> + </project> + + <project cat='soc'> + <title>Binary Package Patch Infrastructure — pkg_patch</title> + + <contact> + <person> + <name> + <given>Ivan</given> + <common>Voras</common> + </name> + <email>ivoras@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/IvanVoras/pkg_patch">Wiki + page</url> + </links> + + <body> + <p>The pkg_patch project is about creating a binary package patch + infrastructure which would allow users to patch their live system's + packages in an easy and efficient way. It is a C program written to + interface with libpkg (for things which are common to all pkg + utilities) meant to be included in the base system when it is done. + It comes with built-in mass patch creation and application + commands. It is funded by Google Summer of Code 2010.</p> + </body> + + <help> + <task>Finish the project.</task> + + <task>Get some testing for it.</task> + + <task>Convince the Port Management Team it is actually a Good + Thing to have even as an experimental feature.</task> + + <task>Agree upon the policy on which package patches will be + created (i.e. from which point in time to which point in time), + assuming the "stable" package tree idea has still not gotten + traction.</task> + </help> + </project> + + <project cat='kern'> + <title>Interrupt Threads</title> + + <contact> + <person> + <name> + <given>John</given> + <common>Baldwin</common> + </name> + <email>jhb@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>For a while I have wanted to rework interrupt threads to + address a few issues. The new design uses per-CPU queues of + interrupt handlers. Interrupt threads are allocated by a CPU from + a pool and bound to that CPU while draining that CPU's queue of + handlers. Non-filter handlers can also reschedule themselves at + the back of the current CPU's queue while executing. Filters with + handlers are now always enabled and should provide a full + replacement for the various uses of filters with "fast" + taskqueues. A new class of "manual" handlers are also available + which are not automatically scheduled, but are only explicitly + scheduled from a filter. Thus, a filter can potentially schedule + multiple handlers.</p> + + <p>The code has been tested on amd64, but it needs wider review + and testing. I hope to start soliciting review and feedback soon + with the goal of getting the code into 9.0.</p> + </body> + </project> + + <project cat='bin'> + <title>BSD-Licensed iconv in Base System</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Kövesdán</common> + </name> + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://kovesdan.org/patches/iconv-20100708.diff">The + latest patch for the base system</url> + </links> + + <body> + <p>The work has been completed and the GNU compatibility levels + seems to be quite high. One exception is the fallback support. It + is difficult to implement that facility in this implementation + because the design is somewhat different. Probably, it will not be + a big problem because that functionality is not even documented in + the GNU version so few applications might use it.</p> + </body> + + <help> + <task>Run a portbuild test and solve possible problems that show + up.</task> + </help> + </project> + + <project cat='bin'> + <title>BSD-Licensed grep in Base System</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Kövesdán</common> + </name> + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc/grep"> + Sources in Perforce</url> + </links> + + <body> + <p>A portbuild test showed that grep is basically ready to enter + HEAD, but there were a few failures that seem to be + related. These have to be investigated and fixed before + committing grep to 9-CURRENT.</p> + </body> + + <help> + <task>Investigate and fix some minor issues.</task> + </help> + </project> + + <project cat='soc'> + <title>Collective Resource Limits (aka. Jobs)</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Kövesdán</common> + </name> + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/G%C3%A1borSoC2010">Project page + on the wiki</url> + + <url href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2010/gabor_jobs/irix_jobs"> + Sources in Perforce</url> + </links> + + <body> + <p>The SGI IRIX operating system has a concept, called job, which + is used to group processes together and then apply resource limits + on them. The purpose of this project is to implement this facility + on &os;.</p> + + <p>I spent most of the time familiarizing myself with how + things are done inside the kernel, how syscalls work, etc. So far, + I have the basic understanding needed and I added the most + important syscalls to group processes together into jobs and + manipulate collective resource limits on them.</p> + + <p>There is a bug, which I am tracking down at the moment, after + this I can start to implement actual resource limit enforcement. + For some of the limit types, it will be relatively easy but some + others will take more effort and studies.</p> + </body> + + <help> + <task>Fix the showstopper bug, which prevent me working on actual + limit enforcement.</task> + + <task>Implement limit enforcements for all of the limits supported + by IRIX.</task> + + <task>Add support for userland facilities and make utilities + jobs-aware, like showing jobs in ps(1), etc.</task> + </help> + </project> + + <project cat='docs'> + <title>The &os; Spanish Documentation Project</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Kövesdán</common> + </name> + <email>gabor@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Vicente</given> + <common>Carrasco Vayá</common> + </name> + <email>carvay@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/doc/es/articles/fdp-es/">Primer + for translators</url> + </links> + + <body> + <p>We need manpower. Existing documentation set has not been + updated for quite some time because of lack of volunteers. Current + members are busy with other projects and real life at the moment + and we have not received anything from outside contributors. It is + a shame because there are lots of users in Spain and Latin-America, + as well. Besides, the world's first Free Software Street has been + recently inaugurated in Spain. This obviously means that there is + interest in free software but unfortunately, this translation + project is not going very well nowadays.</p> + </body> + + <help> + <task>Review and update existing translations.</task> + </help> + </project> + + <project cat='kern'> + <title>Kernel Event Timers Infrastructure</title> + + <contact> + <person> + <name> + <given>Alexander</given> + <common>Motin</common> + </name> + <email>mav@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Modern x86 systems include four different types of event timers: + i8254, RTC, LAPIC, and HPET. First three are already supported by + &os;. Depending on hardware and loader tunables, periodic + interrupts from them are used to trigger all time-based events in + kernel. That code has a long history, that made it tangled and + at the same time limited and hard-coded.</p> + + <p>New kernel event timers infrastructure was started to allow + different event timer hardware to be operated in uniform way and to + allow more features to be supported. Work consists of three main + parts: writing machine-independent timer driver API and management + code, updating existing drivers and improving HPET driver to + support event timers.</p> + + <p>The new driver API provides unified support for both per-CPU + (independent for every CPU core) and global timers in periodic and + one-shot modes. Management code at this moment uses only periodic + mode, while one-shot mode use is planned by later tickless kernel + work.</p> + + <p>Different kinds of timers have different capabilities and could + be present in hardware in different combinations. In every + situation the infrastructure automatically chooses two best event + timers to supply system with hardclock(), statclock(), and + profclock() events. If some timer is not functioning — it will be + replaced. If there is no second timer — it will be emulated. + The administrator may affect that choice using loader tunables during + boot and sysctl variables in run-time (kern.eventtimer.*, and so on).</p> + + <p>Most of the code was recently committed to HEAD. Now it is used + by i386 and amd64 architectures.</p> + </body> + + <help> + <task>Troubleshoot possible hardware and software issues.</task> + + <task>Port other architectures to the new infrastructure.</task> + + <task>Implement tickless kernel, utilizing new features, such as + per-CPU and one-shot timers.</task> + </help> + </project> + + <project cat='docs'> + <title>The &os; Hungarian Documentation Project</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Kövesdán</common> + </name> + <email>gabor@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gábor</given> + <common>Páli</common> + </name> + + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/hu/">Hungarian &os; web + pages</url> + + <url href="http://www.FreeBSD.org/doc/hu/">Hungarian &os; + documentation</url> + + <url href="http://wiki.FreeBSD.org/HungarianDocumentationProject"> + The &os; Hungarian Documentation Project's Wiki Page</url> + + <url href="http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83"> + Perforce Deport for the &os; Hungarian Documentation Project</url> + </links> + + <body> + <p>Thanks to Katalin Konkoly, the first few chapters of the &os; + Handbook translation have been reviewed, therefore many typos and + mistranslations were spotted and fixed. Apart from this, we are + still keeping the existing documentation and web page translations + up to date, currently without plans on further work. If you are + interested in helping us, or you have any comments, or requests + regarding the translations, do not hesitate to contact the project + via the email addresses mentioned in the entry.</p> + </body> + + <help> + <task>Review translations and send feedback.</task> + + <task>Translate release notes.</task> + + <task>Add more article translations.</task> + </help> + </project> + + <project cat='ports'> + <title>&os; Haskell</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Páli</common> + </name> + <email>pgj@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Giuseppe</given> + <common>Pilichi</common> + </name> + <email>jacula@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ashish</given> + <common>Shukla</common> + </name> + <email>ashish@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/Haskell">Wiki Page of the + Project</url> + + <url href="http://www.FreeBSD.org/ports/haskell.html">&os; Haskell + Ports</url> + + <url href="http://www.haskell.org/mailman/listinfo/freebsd-haskell"> + The freebsd-haskell Mailing List</url> + </links> + + <body> + <p>Our efforts on porting the generalized, general-purpose purely + functional programming language, <a + href="http://www.haskell.org/">Haskell</a> has rallied, since + two new committers, Giuseppe Pilichi and Ashish + Shukla joined recently, forming the &os; Haskell Team. + Over the last months, &os;/i386 and &os;/amd64 have become Tier-1 + platforms, featuring officially supported vanilla binary + distributions for the <a + href="http://www.haskell.org/ghc/">Glasgow Haskell Compiler</a> + starting from version 6.12.1. We introduced a unified ports + infrastructure for Haskell Cabal ports, which also makes possible + the <a + href="http://code.haskell.org/~pgj/projects/hsporter">direct + translation</a> of Cabal package descriptions to &os; ports. + The number of Haskell package ports increases steadily.</p> + </body> + + <help> + <task>Improve support for Haskell Cabal packages and their + translation.</task> + + <task>Create a port for Haskell Platform.</task> + + <task>Add more Haskell package ports.</task> + + <task>Test and send feedback.</task> + </help> + </project> + + <project cat='net'> + <title>libnetstat(3)</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Páli</common> + </name> + <email>pgj@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Aman</given> + <common>Jassal</common> + </name> + <email>aman@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/LibNetstat">Wiki Page</url> + + <url href="http://people.FreeBSD.org/~pgj/libnetstat/"> + Patches</url> + + <url href="http://p4web.freebsd.org/@md=d&cd=//depot/projects/soc2009/&c=mGl@//depot/projects/soc2009/pgj_libstat/?ac=83"> + Perforce Depot (SoC 2009)</url> + </links> + + <body> + <p>This project is about creating a wrapper library to support + monitoring and management of networking with avoiding direct use of + the &os; kvm(3) and sysctl(3) interfaces. This approach would allow + the kernel implementation to change and monitoring applications to + be extended without breaking applications and requiring them to be + recompiled. We decided to merge the sources from the last year's + Summer of Code project back to the &os; src/ repository piece by + piece, and we have defined several phases of integration.</p> + + <ul> + <li>Standardize the in-kernel networking statistics + structures.</li> + + <li>Build a sysctl(3) interface, and add export routines.</li> + + <li>Add a library, libnetstat(3) to work with the exported + information, and to provide further functions in order to support + extracting information via kvm(3). This library implements + abstractions over the gathered data.</li> + + <li>Adapt sources of the existing applications, i.e. netstat(1) + and bsnmpd(1) to use the abstractions offered by the library, + resulting in a cleaner and simpler code.</li> + + <li>Add new applications on the top of the library, e.g. + nettop(1).</li> + </ul> + + <p>The first phase has been already posted for review. Note that we + are looking for a sponsor with an src commit bit and enough time to + represent the effort towards the Project.</p> + </body> + + <help> + <task>Review the sources.</task> + + <task>Pick a task from the list, and send patches.</task> + + <task>Comment the patches, help them to improve.</task> + </help> + </project> + + <project cat='kern'> + <title>ZFS</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + <common>Dawidek</common> + </name> + <email>pjd@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Martin</given> + <common>Matuska</common> + </name> + <email>mm@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Xin</given> + <common>Li</common> + </name> + <email>delphij@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/ZFS">&os; ZFS Wiki</url> + + <url href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs"> + Latest &os; ZFS development tree</url> + </links> + + <body> + <p>The ZFS file system has been updated to version 15 on HEAD and + it will be MFC'ed to 8-STABLE around September 13th, 2010. Work + is in progress on porting the recent ZFS version 26 with + deduplication functionality.</p> + </body> + + <help> + <task>Fix bugs, unresolved issues and to-dos in Perforce.</task> + </help> + </project> + + <project cat='arch'> + <title>Flattened Device Tree for Embedded &os;</title> + + <contact> + <person> + <name> + <given>Rafal</given> + <common>Jaworowski</common> + </name> + <email>raj@semihalf.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/FlattenedDeviceTree">Project + wiki pages</url> + </links> + + <body> + <p>The purpose of this project was to provide &os; with support for + the Flattened Device Tree (FDT) technology. A mechanism for + describing computer hardware resources, which cannot be probed or + self enumerated, in a uniform and portable way. The primary + consumers of this technology are embedded &os; platforms (ARM, MIPS, + PowerPC), where a lot of designs are based on similar chips, but + have different assignment of pins, memory layout, addresses ranges, + interrupts routing and other resources.</p> + + <p>Current state highlights:</p> + + <ul> + <li>All code and documentation developed during the course of + this project was merged with HEAD, which covers FDT support for + the following platforms and systems:</li> + + <li>Marvell ARM</li> + + <ul> + <li>DB-88F5182</li> + + <li>DB-88F5281</li> + + <li>DB-88F6281</li> + + <li>DB-78100</li> + + <li>SheevaPlug</li> + </ul> + + <li>Freescale PowerPC</li> + + <ul> + <li>MPC8555CDS</li> + + <li>MPC8572DS</li> + </ul> + + <li>The FDT infrastructure (bus drivers, helper libraries, and + routines shared across architectures and platforms) allows for + easier porting to new platforms or variations. The initially + supported systems offer a working example of how to migrate + towards FDT approach.</li> + </ul> + + <p>Work on this project was sponsored by the &os; Foundation.</p> + </body> + + <help> + <task>Improve how-to and guidelines for new adopters (how to convert + to FDT and so on).</task> + + <task>Migrate more existing embedded &os; platforms (ARM, MIPS) to + FDT approach.</task> + </help> + </project> + + <project cat="docs"> + <title>The &os; Japanese Documentation Project</title> + + <contact> + <person> + <name> + <given>Hiroki</given> + <common>Sato</common> + </name> + <email>hrs@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ryusuke</given> + <common>Suzuki</common> + </name> + <email>ryusuke@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ja/">Japanese &os; Web + Pages</url> + + <url href="http://www.jp.FreeBSD.org/doc-jp/">The &os; Japanese + Documentation Project's Web Page</url> + </links> + + <body> + <p>This project focuses on updating the www/ja and doc/ja_JP.eucJP/ + trees. Since last year www/ja tree has been mostly synchronized + with the English counterpart and doc/ja_JP.eucJP has also been + updated steadily. We are now working on &os; Handbook and Porter's + Handbook.</p> + </body> + + <help> + <task>More Japanese translation of &os; Handbook and contents of + www.FreeBSD.org.</task> + + <task>Pre-/post-commit review of the translation.</task> + </help> + </project> + + <project cat='soc'> + <title>Google Summer of Code 2010</title> + + <contact> + <person> + <name> + <given>Brooks</given> + <common>Davis</common> + </name> + <email>brooks@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Tim</given> + <common>Kientzle</common> + </name> + <email>kientzle@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/SummerOfCode2010Projects">Summer + of Code 2010 Projects</url> + </links> + + <body> + <p>We are once again participating in the Google Summer of Code. + This is our 6th year of participation and we hope to once again see + great results from our 18 students. Coding officially began May + 24th, and we are in the middle of the mid-term evaluation period. + You can see and comment on weekly status reports on the <a + href="http://lists.freebsd.org/mailman/listinfo/soc-status">mailing + list</a> or on the <a + href="http://wiki.freebsd.org/SummerOfCode2010">wiki</a>.</p> + </body> + </project> + + <project cat='kern'> + <title>Jail-Based Virtualization</title> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + <common>Zeeb</common> + </name> + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSDFoundation.org/project%20announcements.shtml#Bjoern"> + &os; Foundation Announcement</url> + + <url href="http://p4web.FreeBSD.org/@md=d&cd=//&c=Z8Q@//depot/user/bz/vimage/src/?ac=83"> + Perforce Workspace</url> + </links> + + <body> + <p>The project started with some cleanup on the network stack after + all the import work and adjustments for virtualization to minimize + changes to earlier branches. These made it into the tree already + and to 8-STABLE, and it will be included in the upcoming 8.1 + release.</p> + + <p>The first major task was to generalize the virtualization + framework, so that virtualization of further subsystems would be + easier and could be achieved with less duplication.</p> + + <p>In addition some documentation on the virtual network stack + programming was written to help developers virtualizing their code. + The interactive kernel debugger support was improved and libjail + along with jls and netstat can work on core dumps now and query + individual jails and attached virtual network stacks.</p> + + <p>The second major task was network stack teardown, a concept + introduced with the network stack virtualization. The primary goal + was to prototype a shutdown of the (virtual) network stacks from + top to bottom, which means letting interfaces go last rather than + first. Work in this area is still in progress and will have to + continue to allow long term stability and a leak and panic free + shutdown.</p> + + <p>The work on this project had been sponsored by the &os; + Foundation and CK Software GmbH. Special thanks also to John + Baldwin and Philip Paeps for helping with review and + suggestions.</p> + </body> + + <help> + <task>Merge stabilised change sets.</task> + + <task>Work further down the network stack freeing all resources for + a stable, safe teardown.</task> + </help> + </project> + + <project cat='ports'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Thomas</given> + <common>Abthorpe</common> + </name> + <email>portmgr-secretary@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Port</given> + <common>Management Team</common> + </name> + <email>portmgr@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ports/" /> + + <url href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" /> + + <url href="http://portsmon.FreeBSD.org/index.html" /> + + <url href="http://www.FreeBSD.org/portmgr/index.html" /> + + <url href="http://blogs.FreeBSDish.org/portmgr/" /> + + <url href="http://www.twitter.com/freebsd_portmgr/" /> + + <url href="http://www.facebook.com/group.php?gid=135441496471197" /> + + <url href="http://tinderbox.marcuscom.com/" /> + </links> + + <body> + <p>A significant part of quarter two was spent coordinating efforts + for inclusion of Xorg 7.5, KDE 4, GNOME 2, plus preparation of ports + for the 8.1 release process. Due to the success of enforcing + Feature Safe ports commits during 7.3-RELEASE, it was continued + for the recent src/ freeze.</p> + + <p>The port count is approaching 22,000 ports. The open PR count + currently floats at about 1200 entries.</p> + + <p>Since the last report, we added four new committers, and had two + old committers rejoin us.</p> + + <p>The Ports Management Team is very grateful to the &os; + Foundation for sponsoring two new head nodes for the ports building + cluster, pointyhat. Each of the new head nodes has a larger + capacity, both with regard to performance but also in amount of + space available for the staging areas, allowing for faster, and + thus more, build cycles. Additionally, having two head nodes will + allow us to dedicate one of them for building production-ready + binary packages, adding predicability for our users to when what + types of packages are available for installation, and dedicate the + other for regression testing of large port updates, ports + infrastructure improvements, the cluster scheduling code, and &os; + itself. Over the last few weeks, Mark Linimon has been working hard + to get the first of the two new nodes online and has already + completed its first package build. This has involved a substantial + rework of our custom codebase.</p> + + <p>The Ports Management team have been running -exp runs on an + ongoing basis, verifying how base system updates may affect the + ports tree, as well as providing QA runs for major ports + updates. Of note, -exp runs were done for:</p> + + <ul> + <li>ale: Update of math/gmp.</li> + <li>delphij: Changes to Mk/bsd.ldap.mk.</li> + <li>gahr: Inclusion of USE_GL=glew.</li> + <li>pgollucci: Changes to Mk/bsd.*apache.mk plus updates to devel/apr + and www/apache*.</li> + <li>Testing of x11/xorg, x11/gnome2, x11/kde4, and + lang/mono</li> + <li>A test run make fetch run.</li> + <li>A test run for devel/gettext.</li> + <li>mm: Inclusion of USE_XZ.</li> + <li>ale: Request to switch default mysql from 5.0-EOL to + 5.1-GA.</li> + </ul> + + <p>alepulver's Licensing Framework Summer of Code project has made + it into the tree and the Port Management Team is currently + assessing the fallout and it will come up with guidelines and + documentation in due time.</p> + </body> + + <help> + <task>Looking for help fixing <a + href="http://wiki.FreeBSD.org/PortsBrokenOnCurrent">ports + broken on 9-CURRENT</a>.</task> + + <task>Looking for help with <a + href="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures"> + Tier-2 architectures</a>.</task> + + <task>Most ports PRs are assigned, we now need to focus on testing, + committing, and closing.</task> + </help> + </project> + + <project cat='arch'> + <title>&os;/powerpc64</title> + + <contact> + <person> + <name> + <given>Nathan</given> + <common>Whitehorn</common> + </name> + <email>nwhitehorn@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~nwhitehorn/FreeBSD-9.0-20100715-SNAP-powerpc64/"> + Install CDs for powerpc64</url> + </links> + + <body> + <p>On July 13, &os;/powerpc64 was integrated into HEAD. This + provides support for fully 64-bit operation on 64-bit PowerPC + machines conforming to the Book-S specification, including the + PowerPC 970, Cell, and POWER4-7. Hardware support is currently + limited to Apple machines, although this should expand in the near + future.</p> + + <p>Currently supported hardware:</p> + + <ul> + <li>Apple Xserve G5</li> + + <li>Apple Power Macintosh G5</li> + + <li>Apple iMac G5</li> + </ul> + </body> + </project> + + <project cat='arch'> + <title>&os; on the Sony Playstation 3</title> + + <contact> + <person> + <name> + <given>Nathan</given> + <common>Whitehorn</common> + </name> + <email>nwhitehorn@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://svn.FreeBSD.org/viewvc/base/user/nwhitehorn/ps3/"> + Playstation 3 SVN repository</url> + </links> + + <body> + <p>Work has begun to port &os;/powerpc64 to the IBM Cell-based Sony + Playstation 3, using the OtherOS feature present on some models of + the console. As of July 14, the &os; boot loader is ported, and it + is possible to netboot a kernel, which has support for the + framebuffer, MMU, and device discovery. Once work on drivers for + the network interface and interrupt controller is complete, it will + be possible to boot the console multi-user.</p> + </body> + </project> + + <project cat='proj'> + <title>OpenAFS Port</title> + + <contact> + <person> + <name> + <given>Benjamin</given> + <common>Kaduk</common> + </name> + <email>kaduk@mit.edu</email> + </person> + + <person> + <name> + <given>Derrick</given> + <common>Brashear</common> + </name> + <email>shadow@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://openafs.org">OpenAFS home page</url> + + <url href="http://web.mit.edu/freebsd/openafs/openafs.shar">&os; + port for the OpenAFS 1.5.75 release</url> + </links> + + <body> + <p>AFS is a distributed network filesystem that originated from the + Andrew Project at Carnegie-Mellon University; the OpenAFS client + implementation has not been particularly useful on &os; since the + 4.X releases. Recent work on the OpenAFS codebase has updated + it to be consistent with current versions of &os;, and the client, + though still considered experimental, is now relatively stable for + light (single-threaded) use on 9-CURRENT. The auxiliary utilities + for managing and examining the filesystem are functional, and + reading and writing files works sufficiently well to copy /usr/src + into and out of AFS. Compiling and running executables in AFS is + unsuccessful, though, as mmap() is not always reliable.</p> + + <p>There are several known outstanding issues that are being + worked on, but detailed bug reports are welcome at <a + href="mailto:port-freebsd@openafs.org">port-freebsd@openafs.org</a>.</p> + </body> + + <help> + <task>Fix the {get,put}pages vnode operations for more reliable + mmap() operation.</task> + + <task>Update VFS locking to allow the use of disk-based client + caches as well as memory-based caches.</task> + + <task>Track down races and deadlocks that appear under + load.</task> + + <task>Integrate with the bsd.kmod.mk kernel-module build + infrastructure.</task> + </help> + </project> + + <project cat='soc'> + <title>Package Management Library — libpkg</title> + + <contact> + <person> + <name> + <given>David</given> + <common>Forsythe</common> + </name> + <email>dforsyth@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/SOC2010DavidForsythe">Wiki + page</url> + + <url href="http://code.google.com/p/libpkg">Main project page</url> + </links> + + <body> + <p>The libpkg library will allow for fairly fine grained control + over package management.</p> + + <p>Presently libpkg has complete read functionality. Info and + delete tools that have most of the current package tool features + have already been implemented, and once they are completed they can + be considered replacements for their counterparts.</p> + + <p>Once the write and logging aspects of the library are more + mature, add and create tools can be created quickly. A new set of + more maintainable package tools that leverage libpkg will hopefully + be available soon after.</p> + </body> + </project> + + <project cat='proj'> + <title>General-Purpose DMA Framework</title> + + <contact> + <person> + <name> + <given>Jakub</given> + <common>Klama</common> + </name> + <email>jceel@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/SOC2010JakubKlama">Project + description on &os; wiki</url> + + <url href="http://p4web.FreeBSD.org/@md=d&cd=//&c=eCv@//depot/projects/soc2010/jceel_dma/?ac=83"> + Project branch on Perforce</url> + </links> + + <body> + <p>This project purpose is adding support for general purpose DMA + engines found in most embedded devices. GPDMA framework provides a + unified KOBJ interface to DMA engine drivers and unified + programming interface to use direct memory transfers in kernel and + userspace applications.</p> + + <p>This project is a part of Google Summer of Code 2010 and it is a + work in progress. Current status can be observed on the wiki + page.</p> + </body> + + <help> + <task>Add support for more DMA engines.</task> + + <task>Complete, clean up, and merge with HEAD.</task> + </help> + </project> + + <project cat='soc'> + <title>Making Ports Work with Clang</title> + + <contact> + <person> + <name> + <given>Andrius</given> + <common>Morkunas</common> + </name> + <email>hinokind@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/SOC2010AndriusMorkunas" /> + + <url href="http://wiki.FreeBSD.org/PortsAndClang" /> + + <url href="http://rainbow-runner.nl/~andrius/soc/">GSoC2010 + patches</url> + + <url href="http://rainbow-runner.nl/clang/patches/">All patches for + ports</url> + </links> + + <body> + <p>First part of the project is mostly complete. I added support + for new PORTS_CC variable which should be used in make.conf instead + of CC to change ports compiler. This allows user to change ports + compiler easily, while still respecting USE_GCC.</p> + + <p>Some patches were written to get ports to work with Clang, and + a lot of old patches written prior to the Google Summer of Code + project were updated. There are still a lot of broken ports, and + some that cannot be built because of Clang/LLVM bugs, but at + this point, Clang can build most ports.</p> + </body> + + <help> + <task>Fix broken ports that do not work with Clang.</task> + + <task>Test patched ports with Clang, report Clang bugs.</task> + </help> + </project> + + <project cat="team"> + <title>The &os; Foundation Status Report</title> + + <contact> + <person> + <name> + <given>Deb</given> + <common>Goodkin</common> + </name> + <email>deb@FreeBSDFoundation.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSDFoundation.org" /> + </links> + + <body> + <p>We were proud to be a sponsor for BSDCan in May. We also + committed to sponsoring MeetBSD 2010 Poland and California. We + provided 12 travel grants for BSDCan.</p> + + <p>The Foundation and Core Team held a summit on BSD-licensed + toolchains at BSDCan 2010.</p> + + <p>We officially kicked off five new projects that we are funding. + They are BSNMP Improvements by Shteryana Shopova, Userland DTrace + by Rui Paulo, &os; jail-based virtualization by Bjoern Zeeb, DAHDI + &os; driver port by Max Khon, and Resource Containers project by + Edward Tomasz Napierała.</p> + + <p>We continued our work on infrastructure projects to beef up + hardware for package building, network testing, etc. This includes + purchasing equipment as well as managing equipment donations.</p> + + <p>We are half way through the year and we have raised around + $48,000 towards our goal of $350,000. Find out how to make a + donation at <a + href="http://www.FreeBSDFoundation.org/donate/"> + http://www.FreeBSDFoundation.org/donate/</a>.</p> + + <p>Our semi-annual newsletter will be published soon. Check out our + <a href="http://www.FreeBSDFoundation.org/">website</a> to find + out more!</p> + </body> + </project> + + <project cat='proj'> + <title>GEOM-Based Pseudo-RAID Implementation — + geom_pseudoraid</title> + + <contact> + <person> + <name> + <given>Boris</given> + <common>Kochergin</common> + </name> + <email>spawk@acm.poly.edu</email> + </person> + </contact> + + <links> + <url href="http://acm.poly.edu/~spawk/geom_pseudoraid-20100715.tbz"> + Code snapshot</url> + </links> + + <body> + <p>The old ata(4) driver is believed to be going away sometime in + the future, to be replaced with ATA_CAM + [<a href="http://lists.FreeBSD.org/pipermail/freebsd-geom/2010-April/004106.html">1</a>]. + However, ATA pseudo-RAID support in &os;, ataraid(4), is + implemented as part of said ata(4) driver, which means that it, + too, will be going away. It was decided that pseudo-RAID support is + desirable and that it should be reimplemented in GEOM + [<a href="http://lists.FreeBSD.org/pipermail/freebsd-geom/2010-April/004150.html">2</a>] + [<a href="http://www.FreeBSD.org/news/status/report-2010-01-2010-03.html#CAM-based-ATA-implementation">3</a>], + which this project aims to do.</p> + + <p>Currently, RAID-1 arrays can be used on VIA Tech V-RAID and + Adaptec HostRAID controllers in a limited capacity. There is no + support for writing metadata yet, so disks are not marked degraded, + there is no rebuild support, etc. These features are planned, along + with support for more hardware and RAID-0 and SPAN arrays.</p> + + <p>A major setback for the current code is that it uses the + device(9) family of functions to identify ATA pseudo-RAID + controllers and constructs arrays based on that information. + Unfortunately, ATA_CAM does not appear to add its devices to the + device tree, so that tactic cannot be used with ATA_CAM. While this + is fine for development of the actual RAID parts of the code, the + project will be somewhat useless in the absence of the old ata(4) + driver. There has been talk of exporting PCI information to GEOM + [<a href="http://lists.FreeBSD.org/pipermail/freebsd-geom/2010-April/004167.html">4</a>] + [<a href="http://lists.FreeBSD.org/pipermail/freebsd-geom/2010-April/004158.html">5</a>], + but the work does not appear to have been completed yet.</p> + </body> + + <help> + <task>Obtain documentation for or reverse-engineer metadata formats + for which there is no write support in the ataraid(4) driver (for + example, Adaptec HostRAID).</task> + + <task>Add CAM support for exporting PCI information to GEOM.</task> + </help> + </project> + + <project cat='arch'> + <title>&os;/avr32</title> + + <contact> + <person> + <name> + <given>Oleksandr</given> + <common>Tymoshenko</common> + </name> + <email>gonzo@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/FreeBSD/avr32" /> + </links> + + <body> + <p>The &os;/avr32 project was started by Arnar Mar Sing, and actively + developed by him and Ulf Lilleengen. It successfully reached + single-user stage but since then has not progressed much. At the + moment I am trying to get it back into shape. So far some problems + with toolchain on i386 host have been fixed, buildkernel succeeds, + buildworld succeeds with some exceptions. Next step would be fixing + pmap and bringing port back to single-user stage.</p> + </body> + </project> + + <project cat='proj'> + <title>GPIO Framework</title> + + <contact> + <person> + <name> + <given>Luiz Otavio O</given> + <common>Souza</common> + </name> + <email>loos.br@gmail.com</email> + </person> + + <person> + <name> + <given>Oleksandr</given> + <common>Tymoshenko</common> + </name> + <email>gonzo@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/GPIO" /> + </links> + + <body> + <p>Implementation of General Purpose Input/Output interface for + &os;. Current GPIO bus implementation allows user to control pins + from userland and it could be expanded to support various type of + peripheral devices. So far there are two drivers:</p> + + <ul> + <li><b>gpioled</b> provides simple led(4) functionality.</li> + + <li><b>gpioiic</b> implements I2C over GPIO.</li> + </ul> + + <p>Framework is used in Alexandr Rybalko's port of &os; to D-Link + DIR-320 and in Luis Otavio O Souza's work of bringing &os; to + RouterBoard.</p> + </body> + </project> + + <project cat='ports'> + <title>Chromium Web Browser</title> + + <contact> + <person> + <name> + <given>Ruben</given> + </name> + <email>chromium@hybridsource.org</email> + </person> + </contact> + + <links> + <url href="http://chromium.hybridsource.org">Main chromium + site</url> + + <url href="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=146302">PR + for chromium port</url> + </links> + + <body> + <p>Chromium is a Webkit-based web browser that is largely + BSD-licensed. It works very well on &os; and supports new features + like HTML 5 video. This effort uses a new + hybrid-source model, where the &os; patches are largely kept closed + for a limited time. I submitted Chromium to ports a couple of + months ago and recently updated the submission to the stable 5.0.375 + branch. The port is ready to be committed pending final legal + approval by the &os; Foundation. Further work remains to port + Chromium to &os; completely, such as porting the task manager fully + and making sure extensions work properly.</p> + </body> + </project> + + <project cat='soc'> + <title>ExtFS Status Report</title> + + <contact> + <person> + <name> + <given>Zheng</given> + <common>Liu</common> + </name> + <email>gnehzuil@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/SOC2010ZhengLiu" /> + </links> + + <body> + <p>This project has two goals: pre-allocation algorithm and ext4 + read-only mode.</p> + + <p>The aim of pre-allocation algorithm is to implement a reservation + window mechanism. Now this mechanism has been introduced. The + performance comparison can be found on the <a + href="http://wiki.FreeBSD.org/SOC2010ZhengLiu">wiki</a>.</p> + + <p>The aim of ext4 read-only mode is to make it possible to read ext4 file + system in read-only mode when the hard disk is formatted with default + features. Currently it only supports a few features, such as extents, + huge_file. Others features will be added, such as dir_index, + uninit_bg, dir_nlink, flex_bg and extra_isize. My work resides in + extfs and ext4fs branch of Perforce.</p> + </body> + </project> + + <project cat='proj'> + <title>Distributed Audit</title> + + <contact> + <person> + <name> + <given>Sergio</given> + <common>Ligregni</common> + </name> + <email>ligregni@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://p4web.freebsd.org/@md=d&cd=//&c=wHa@//depot/projects/soc2010/disaudit/?ac=83"> + Perforce repository</url> + + <url href="http://wiki.FreeBSD.org/SOC2010SergioLigregni">Project + Wiki</url> + </links> + + <body> + <p>90% of the functionality is working, the daemons sync two + systems in a master-slave paradigm.</p> + </body> + + <help> + <task>Standardize the code to meet &os; requirements.</task> + + <task>Implement SSL in network communication.</task> + + <task>Perform security improvements and bug fixing, strlxxx() functions, + memcpy() instead of strcpy() when using non-char variables.</task> + + <task>Integrate with the current Audit subsystem.</task> + </help> + </project> + + <project cat='soc'> + <title>File System Changes Notification</title> + + <contact> + <person> + <name> + <given>Ilya</given> + <common>Putsikau</common> + </name> + <email>iputsikau@gmail.com</email> + </person> + </contact> + + <body> + <p>The aim of the project is to implement an inotify-compatible file system + change notification mechanism for &os; and later, and add inotify + support to linuxulator. The result, fsnotify is already functional + but not yet compatible with inotify in some details.</p> + </body> + + <help> + <task>Add access permissions checks.</task> + + <task>Port inotify test cases.</task> + + <task>Fix compatibility issues.</task> + + <task>Add linuxulator support.</task> + </help> + </project> + + <project cat='proj'> + <title>Resource Containers</title> + + <contact> + <person> + <name> + <given>Edward Tomasz</given> + <common>Napierała</common> + </name> + <email>trasz@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>As of now, &os; only offers very rudimentary resource controls — + resource limits for many resources (e.g. SysV IPC) are missing, and + there is no way to set resource limits for jails. As a result, + users who want to run many different workloads on a single physical + machine often have to replace jails with several &os; instances + running in virtual machines.</p> + + <p>The goal of this project is to implement resource containers + and a simple per-jail resource limits mechanism. Resource + containers are also a prerequisite for other resource management + mechanisms, such as Hierarchical Resource Limits, for + "Collective Limits on Set of Processes (aka. Jobs)" Google + Summer of Code 2010 project, for implementing mechanism similar + to Linux cgroups, and might be also used to e.g. provide + precise resource usage accounting for administrative or billing + purposes.</p> + + <p>This project is being sponsored by The &os; Foundation.</p> + </body> + </project> + + <project cat='soc'> + <title>Namecache Improvements — dircache</title> + + <contact> + <person> + <name> + <given>Gleb</given> + <common>Kurtsou</common> + </name> + <email>gk@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/SOC2010GlebKurtsov" /> + </links> + + <body> + <p>I have been reimplementing VFS namecache to make it granularly + locked and supporting reliable full-path lookup without calling + underlying file system routines. I have successfully implemented + directory cache that works in idealized environment with tmpfs. I am + currently working on adding support for entries without associated + vnodes and for "weak" entries and incomplete cached path.</p> + </body> + </project> + + <project cat='bin'> + <title>&os; Services Control — fsc</title> + + <contact> + <person> + <name> + <given>Tom</given> + <common>Rhodes</common> + </name> + <email>trhodes@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~trhodes/fsc/" /> + </links> + + <body> + <p>&os; Services Control is a mix of binaries which integrate into + the rc.d system and provide for service (daemon) monitoring. It + knows about signals, pidfiles, and uses very few resources.</p> + + <p>The fsc daemon (fscd) runs in the background once the system has + started. Services are then added to this daemon via the fscadm + control utility, and from there they will be monitored. When they + die, depending on the reason, they will be restarted. Certain + signals may be ignored (list not decided) and fscd will remove that + service from monitoring. Every action is logged to the system + logging daemon. Additionally, the fscadm utility may be used to + inquire about what services are monitored, their pidfile location, + and current process ID.</p> + + <p>FSC provides several advantages over the third-party + daemontools package. For example, fscd uses push notifications + instead of polling; fscd is an internal, &os;-maintained software + package accessible to all developers, where daemontools would have + to be a port and require us to maintain patches; fscd could be + easily integrated with the current rc.d infrastructure.</p> + + <p>Partially based on the ideas of daemontools and Solaris Service + Service Mangement Facility (SMF), this could be an extremely + useful tool for &os; systems.</p> + </body> + + <help> + <task>Testing. Get feedback on how it works in various + environments.</task> + + <task>Code review.</task> + + <task>Other ideas on the rc.d integration.</task> + + <task>Update the manual pages.</task> + </help> + </project> + + <project cat='net'> + <title>Enhancing the &os; TCP Implementation</title> + + <contact> + <person> + <name> + <given>Lawrence</given> + <common>Stewart</common> + </name> + <email>lstewart@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://caia.swin.edu.au/freebsd/etcp09/" /> + + <url href="http://caia.swin.edu.au/urp/newtcp/" /> + + <url href="http://www.FreeBSDfoundation.org/projects.shtml" /> + + <url href="http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/" /> + </links> + + <body> + <p>SIFTR was recently imported into HEAD and will be backported to + 8-STABLE in time to be included in 8.2-RELEASE.</p> + + <p>TCP reassembly queue autotuning will be ready for public testing + within the next week and will be committed soon after. It too will + be backported to 8-STABLE after an appropriate burn in period.</p> + </body> + + <help> + <task>Try SIFTR out and let me know if you run into any + problems.</task> + + <task>Solicit external testing for and commit the reassembly queue + autotuning patch.</task> + </help> + </project> + + <project cat='soc'> + <title>Packet-Capturing Stack — ringmap</title> + + <contact> + <person> + <name> + <given>Alexander</given> + <common>Fiveg</common> + </name> + <email>afiveg@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://code.google.com/p/ringmap/">Project-Page on + Google Code</url> + + <url href="http://ringmap.googlecode.com/files/ringmap_slides.pdf"> + Slides</url> + </links> + + <body> + <p>The ringmap stack is a complete &os; packet-capturing + mplementation specialized for very high-speed networks. Similar + to the "zero-copy BPF" implementation, the idea of ringmap is to + eliminate packet copy operations by using shared memory buffers. + However, unlike the "zero-copy BPF" model, ringmap eliminates + ALL packet copies during capturing: the network adapter's DMA + buffer is mapped directly into user-space. The ringmap stack + also adapts libpcap accordingly to provide userspace + applications with access to the captured packets without any + additional overhead.</p> + + <p>In the context of Google Summer of Code 2010:</p> + + <ul> + <li>The ringmap software was ported to 9-CURRENT.</li> + + <li>Ringmap was redesigned to make it easier to port to other + adapters and to integrate it with other network drivers.</li> + + <li>Also ringmap was extended to be multi-threaded.</li> + </ul> + </body> + + <help> + <task>Porting ringmap to 10GbE (integrating with ixgbe + driver).</task> + + <task>Porting the entire ringmap code from 9-CURRENT to + -STABLE.</task> + + <task>Evaluation tests.</task> + + <task>Documentation.</task> + </help> + </project> + + <project cat='arch'> + <title>&os;/sparc64</title> + + <contact> + <person> + <name> + <given>Marius</given> + <common>Strobl</common> + </name> + <email>marius@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Since the last status report some issues with cas(4) have been + fixed, allowing it to work with Sun GigaSwift Ethernet 1.0 MMF + cards (Cassini Kuheen, part no. 501-5524) as well as the on-board + interfaces of Sun Fire B100s server blades (for the Sun Fire + B1600 platform).</p> + + <p>Support for Fujitsu (Siemens) PRIMEPOWER 250 based on SPARC64 + V CPUs has been added. PRIMEPOWER 450, 650, and 850 likely also + work but have not been tested. This also means that the building + blocks for support of machines based on SPARC64 VI and VII CPUs + like the Fujitsu/Sun SPARC Enterprise Mx000 series are now in + place, but they need testing as well.</p> + + <p>The problems with Schizo version 7 bridges (actually the + firmware of these machines) triggering panics during boot finally + should be solved.</p> + + <p>The work on getting Sun Fire V1280 supported has been stalled + due to access to such machines no longer being available.</p> + + <p>The above mentioned improvements are/will be available in &os; + 8.1-RELEASE and 7.4-RELEASE.</p> + </body> + + <help> + <task>Access to machines based on SPARC64 VI and VII CPUs, like + the Fujitsu/Sun SPARC Enterprise Mx000 series would be + appreciated.</task> + + <task>Someone adding support for 64-bit SPARC V9 to Clang/LLVM, + and getting it on par with GCC would be appreciated.</task> + </help> + </project> + + <project cat='proj'> + <title>New System Installer — pc-sysinstall</title> + + <contact> + <person> + <name> + <given>Kris</given> + <common>Moore</common> + </name> + <email>kris@pcbsd.org</email> + </person> + + <person> + <name> + <given>M. Warner</given> + <common>Losh</common> + </name> + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://lists.FreeBSD.org/pipermail/svn-src-all/2010-June/025660.html"> + Initial commit message</url> + <url href="http://www.BSDCan.org/2010/schedule/attachments/142_pc-sysinstall-kris-moore-2010.pdf"> + BSDCan slides</url> + </links> + + <body> + <p>The new system installation backend, pc-sysinstall, was merged + into HEAD recently and work is already underway to make it more + functional and useful as a complete replacement to standard + "sysinstall". It is written 100% in shell, not requiring any + additional tools from what is standard to &os;. The backend already + supports a number of exciting features such as:</p> + + <ul> + <li>ZFS (Including support for raidz/mirror/multiple device pool + setups).</li> + + <li>Disk encryption via GELI(8).</li> + + <li>Auto labeling of file systems with glabel(8).</li> + + <li>Big disk support using GPT/EFI.</li> + + <li>Full Installation Logging, which is saved to disk for + post-install inspection.</li> + </ul> + + <p>In addition to the features above, pc-sysinstall is unique, in + that every install ends up being a scripted install. Front-ends, be + it GUI- or text-based, simply generate the appropriate system + configuration file, and pc-sysinstall does the grunt work of the + actual installation. This is important for a couple of reasons. + First, it makes the task of front-end development much easier by + not needing to worry about a backend-driven program flow. Second it + means that any front-end can be used to generate the installation + configuration file, which can then be copied or modified to perform + automated installs.</p> + + <p>While pc-sysinstall is still relatively new, it is already in + use as the default backend for PC-BSD 8.0 and 8.1, and has been + getting a very good reception and any bugs found are fixed quickly. + A text-based front-end is already in the works which will allow + installation media to be created without X11 support.</p> + </body> + </project> + + <project cat='proj'> + <title>DAHDI/&os; Project</title> + + <contact> + <person> + <name> + <given>Max</given> + <common>Khon</common> + </name> + <email>fjoe@samodelkin.net</email> + </person> + </contact> + + <links> + <url href="http://www.asterisk.org/dahdi/" /> + + <url href="https://spreadsheets.google.com/pub?key=0Arw6eRL10yIwdGhLdGJWUHF4b3ExQzBsd3BGd2tublE&hl=en&single=true&gid=0&output=html"> + Project Status</url> + </links> + + <body> + <p>The purpose of DAHDI/&os; project is to make it possible to use + &os; as a base system for software PBX solutions.</p> + + <p>DAHDI (Digium/Asterisk Hardware Device Interface) is an + open-source device driver framework and a set of hardware drivers for + E1/T1, ISDN digital, and FXO/FXS analog cards + [<a href="http://www.asterisk.org/dahdi/">1</a>]. Asterisk is one of the most + popular open-source software PBX solutions + [<a href="http://www.asterisk.org/">2</a>].</p> + + <p>The project includes porting DAHDI framework and hardware drivers for + E1/T1, FXO/FXS analog, and ISDN digital cards to &os;. This also + includes TDMoE support, software and HW echo cancellation (Octasic, + VPMADT032), and hardware transcoding support (TC400B). The work is ongoing + in the official DAHDI SVN repository with the close collaboration + with DAHDI folks at Digium.</p> + + <p>The project is nearing completion. The DAHDI framework and + hardware drivers telephony cards have been ported and tested. + There are a number of success stories from early adopters who + have been using E1/T1 and FXO/FXS cards on &os; for several + months.</p> + </body> + </project> + + <project cat='proj'> + <title>V4L Support in Linux Emulator</title> + + <contact> + <person> + <name> + <given>J.R.</given> + <common>Oldroyd</common> + </name> + <email>fbsd@opal.com</email> + </person> + </contact> + + <links> + <url href="http://opal.com/freebsd/sys/compat/linux/" /> + </links> + + <body> + <p>Some bug fixes were applied, and the code was also tested and + made to work with the cuse4bsd webcam driver, which supports a + great many camera chipsets.</p> + + <p>The code is still only in 9-CURRENT. We were going to MFC it to + 8.x but ran into the code freeze for 8.1, so missed that. However, + the code does work on 8-STABLE. We will try to get it MFC'd for + 8.2.</p> + </body> + </project> + + <project cat='proj'> + <title>Clang Replacing GCC in the Base System</title> + + <contact> + <person> + <name> + <given>Ed</given> + <common>Schouten</common> + </name> + <email>ed@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Roman</given> + <common>Divacky</common> + </name> + <email>rdivacky@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Brooks</given> + <common>Davis</common> + </name> + <email>brooks@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Pawel</given> + <common>Worach</common> + </name> + <email>pawel.worach@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" /> + </links> + + <body> + <p>In the past quarter we imported Clang into &os; and it is being + built by default on i386/amd64/powerpc. We have not yet committed + the necessary changes to let world compile with Clang.</p> + + <p>Some bugs and warnings were fixed in HEAD as a result of the Clang + import and people are exploring more and more areas (DTrace, etc). + There are some bug fixes in Clang/LLVM as well that stem from the + import (unknown pragmas warnings, etc).</p> + + <p>Roman Divacky and Matthew Fleming are working on ELF writer in + LLVM. This is meant as a replacement for assembler (currently we + use an outdated GNU as(1)). This work is progressing nice, currently it + is able to produce working variants of hello world in C and C++, and + some other small programs from "configure run".</p> + </body> + + <help> + <task>Import of newer Clang/LLVM into HEAD.</task> + + <task>Help with ARM/MIPS/SPARC64.</task> + + <task>Start pushing src patches into HEAD.</task> + + <task>More testing of Clang on third-party applications (ports).</task> + + <task>More work on the ELF writer.</task> + </help> + </project> + + <project cat='team'> + <title>FreeBSD Bugbusting Team</title> + + <contact> + <person> + <name> + <given>Gavin</given> + <common>Atkinson</common> + </name> + <email>gavin@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Mark</given> + <common>Linimon</common> + </name> + <email>linimon@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Remko</given> + <common>Lodder</common> + </name> + <email>remko@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Volker</given> + <common>Werth</common> + </name> + <email>vwe@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/support.html#gnats">&os; + Support page</url> + + <url href="http://wiki.FreeBSD.org/BugBusting">Resources and + documentation available for Bugbusting</url> + + <url href="http://wiki.FreeBSD.org/Bugathons">Information on + Bugathons</url> + + <url href="http://people.FreeBSD.org/~linimon/studies/prs/">Links to + all of the auto-generated PR reports</url> + + <url href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html"> + PRs recommended for committer evaluation by the bugbusting + team</url> + + <url href="http://people.FreeBSD.org/~linimon/studies/prs/easy_prs.html"> + PRs considered easy by the bugbusting team</url> + + <url href="http://people.FreeBSD.org/~linimon/studies/prs/prs_for_all_groups.html"> + Summary Chart of &os; PRs</url> + </links> + + <body> + <p>After a long hiatus, we aim to hold a bugathon on the weekend of + the 6th - 9th August. Everybody is welcome to help resolve or + progress PRs from the database. We appreciate the help of + committers and non-committers alike, please join us on IRC in + #freebsd-bugbusters on EFnet if you are free at any time over + that weekend and can help. Please see the "Bugathon" URL for more + information.</p> + + <p>Mark Linimon and Gavin Atkinson held a session on the State of + Bugbusting at BSDCan, which was well attended and led to some + interesting discussions. Time was also found to sit down with + several committers to discuss long-standing PRs.</p> + + <p>The bugbusting team continue work on trying to make the GNATS PR + database more accessible and easier for committers to find and + resolve PRs.</p> + + <p>As a result, PRs continue to be classified as they arrive, by + adding 'tags' to the subject lines corresponding to the kernel + subsystem involved, or man page references for userland PRs. + Reports are generated from these nightly, grouping related PRs in + one place, sorted by tag or man page. Mark Linimon continues work + on producing a new report, Summary Chart of PRs with Tags, which + sorts tagged PRs into logical groups such as file system, network + drivers, libraries, and so forth. The slice labels are clickable + and may further subdivide the groups. The chart is updated once + a day. You can consider it as a prototype for browsing + "subcategories" of kernel PRs.</p> + + <p>The "recommended list" has been split up into "non-trivial PRs + which need committer evaluation" and the "easy list" of trivial + PRs, to try to focus some attention on the latter. Various new + reports exist, including "PRs containing code for new device + drivers", "PRs which are from &os; vendors or OEMs", and + "PRs referencing other BSDs".</p> + + <p>It is now possible for interested parties to be emailed a weekly, + customized, report similar in style to the above. If you are + interested in setting one up, contact linimon@FreeBSD.org.</p> + + <p>Our clearance rate of PRs, especially in kern and bin, seems to + be improving. The number of non-ports PRs has stayed almost + constant since the last status report.</p> + + <p>As always, anybody interested in helping out with the PR queue is + welcome to join us in #freebsd-bugbusters on EFnet. We are always + looking for additional help, whether your interests lie in triaging + incoming PRs, generating patches to resolve existing problems, or + simply helping with the database housekeeping (identifying duplicate + PRs, ones that have already been resolved, etc). This is a great way + of getting more involved with &os;!</p> + </body> + + <help> + <task>Plan and manage the bugathon in August, and get as many people + as possible interested in participating.</task> + + <task>Try to find ways to get more committers helping us with closing + PRs that the team has already analyzed.</task> + </help> + </project> + + <project cat='misc'> + <title>BSDCan</title> + + <contact> + <person> + <name> + <given>Dan</given> + <common>Langille</common> + </name> + <email>dvl@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.BSDCan.org/2010/">BSDCan 2010</url> + </links> + + <body> + <p>BSDCan 2010 was our 7th conference. As has become the custom, + a &os; developer summit was held in the two days before the + conference. Record numbers attended the Dev Summit which carried + over into the conference proper. It was great to see + representatives from so many more companies. I saw many great + ideas take root and the start of cooperation on several + projects.</p> + + <p>The talks during the Dev Summit are beginning to attract a wider + audience, and we have been talking about opening this up to the + general audience by creating a fourth track at BSDCan 2011.</p> + + <p>As impossible as it sounds, each year has seen an increase in + the quality of talks and the number of proposals submitted.</p> + </body> + + <help> + <task>I need people to help with various pre-conference tasks: + website updates, booking travel, etc.</task> + </help> + </project> + + <project cat='misc'> + <title>meetBSD 2010 — The BSD Conference</title> + + <contact> + <person> + <name> + <given>meetBSD</given> + <common>Information</common> + </name> + <email>info@meetbsd.org</email> + </person> + </contact> + + <links> + <url href="http://www.meetbsd.org" /> + <url href="http://picasaweb.google.com/meetbsd/MeetBSD2010Day1#" /> + <url href="http://picasaweb.google.com/meetbsd/MeetBSD2010Day2#" /> + <url href="http://picasaweb.google.com/meetbsd/MeetBSD2010SocialEvent#" /> + </links> + + <body> + <p>meetBSD 2010 took place on July 2 - 3 in Krakow, Poland at the + Faculty of Mathematics and Computer Science building of the + Jagiellonian University.</p> + + <p>The gathering was a much successful event which brought together + developers, contributors, and users of the BSD systems from around the + world. We had many interesting presentations, of various character and + appeal for the diversified audience.</p> + + <p>Attendees had a chance for taking the BSD Certification exam during + the conference, as well as the advantage of face to face side + conversations and discussions, which continued long during the social + event on Friday night!</p> + + <p>The conference presentation slides are already available for + download. Video recordings edition is being finalized, and their + publication is expected shortly.</p> + + <p>We hope you enjoyed the event and had great time in Krakow. See you + again soon!</p> + </body> + </project> + + <project cat='team'> + <title>Release Engineering Team</title> + + <contact> + <person> + <name> + <given>Release Engineering Team</given> + </name> + + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/" /> + </links> + + <body> + <p>The Release Engineering Team has been working on the + &os; 8.1-RELEASE. At the time of this writing + the final builds have been completed and uploaded to + the master FTP site. The release announcement should + be made within the next couple of days.</p> + </body> + </project> + + <project cat='team'> + <title>&os; Core Team Election</title> + + <contact> + <person> + <name> + <given>Core</given> + <common>Team</common> + </name> + <email>core@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The 2010 &os; core team election was recently completed. The + &os; core team acts as the project's "board of directors" and is + responsible for approving new src committers, resolving disputes + between developers, appointing sub-committees for specific + purposes (security officer, release engineering, port managers, + webmaster, et cetera), and making any other administrative or + policy decisions as needed. The core team has been elected by + &os; developers every 2 years since 2000, and this marks our 6th + democratically elected core team.</p> + + <p>The new core team would like to thank outgoing members Kris + Kennaway, Giorgos Keramidas, George V. Neville-Neil, Murray + Stokely, and Peter Wemm for their service over the past two + (and in some cases, many more) years.</p> + + <p>The core team would also especially like to thank Dag-Erling + Smøgrav for running the election.</p> + + <p>The newly elected core team members are:</p> + + <ul> + <li>John Baldwin</li> + <li>Konstantin Belousov</li> + <li>Warner Losh</li> + <li>Pav Lucistnik</li> + <li>Colin Percival</li> + </ul> + + <p>The returning core team members are:</p> + + <ul> + <li>Wilko Bulte</li> + <li>Brooks Davis</li> + <li>Hiroki Sato</li> + <li>Robert Watson</li> + </ul> + </body> + </project> + + <project cat='misc'> + <title>BSD-Day@2010</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Páli</common> + </name> + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/BSDDay_2010"/> + </links> + + <body> + <p>The purpose of this one-day event is to gather Central European + developers of today's open-source BSD systems to popularize + their work and their organization, and to provide an interface + for real-life communication. There are no formalities, no + papers, and no registration or participation fee. However the + invited developers are encouraged to give a talk on their + favorite BSD-related topic or join the live forum, then have a + beer with the other folks around. The goal is to motivate + potential future developers and users, especially undergraduate + university students to work with BSD systems.</p> + + <p>This year's BSD-Day will be held in Budapest, Hungary at + Eötvös Loránd University, Faculty of Informatics + on November 20, 2010.</p> + </body> + + <help> + <task>Apply as a developer, we are still looking for BSD people in + the area.</task> + </help> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2010-07-2010-09.xml b/en_US.ISO8859-1/htdocs/news/status/report-2010-07-2010-09.xml new file mode 100644 index 0000000000..97261ba213 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2010-07-2010-09.xml @@ -0,0 +1,2683 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for +Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2010-07-2010-09.xml,v 1.8 2010/10/25 16:10:16 pgj Exp $ --> + +<report> + <date> + <month>July-September</month> + + <year>2010</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report covers &os;-related projects between July and + September 2010. It is the third of the four reports planned for + 2010. During this period, we were victims of one + of the biggest BSD events of the year — EuroBSDCon. + We hope that the ones of you who have been able to attend it + have enjoyed your stay. Another good news is that work on the + new minor versions of &os;, 7.4 and 8.2, is progressing well.</p> + + <p>This report, with 55 entries, is the longest report in + the whole history and shows a good condition of the &os; + community.</p> + + <p>Thanks to all the reporters for the excellent work! We hope you + enjoy reading it.</p> + + <p>Please note that the deadline for submissions covering the period + between October and December 2010 is January 15th, 2011.</p> + </section> + + <category> + <name>soc</name> + + <description>Google Summer of Code</description> + </category> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>team</name> + + <description>&os; Team Reports</description> + </category> + + <category> + <name>net</name> + + <description>Network Infrastructure</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <category> + <name>bin</name> + + <description>Userland Programs</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='soc'> + <title>Atheros AR913x SoC Support</title> + + <contact> + <person> + <name> + <given>Adrian</given> + <common>Chadd</common> + </name> + <email>adrian@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/AdrianChadd/AtherosStuff">(The + Atheros hackery will eventually live here)</url> + + <url href="http://wiki.FreeBSD.org/AdrianChadd/AtherosHalStuff"> + Atheros wireless device work</url> + </links> + + <body> + <p>&os;-CURRENT runs on the AR9132 SoC. Minor platform-specific + tweaks are needed to use it on a given piece of hardware (eg., + where in flash the Ethernet MAC address is stored.) The AR910x + wireless MAC/PHY is supported. The only available test platform + uses a 2.4GHz radio; 5GHz 11a mode has not been tested. As with + other Atheros chipset support in &os;, 11n support is not yet + finished. The current development platform is the TP-Link + TP-WN1043ND 802.11n wireless bridge/router. It is currently being + successfully used as a 11bg access point.</p> + </body> + + <help> + <task>USB support is currently not functional.</task> + + <task>There is currently no support for the Realtek Gigabit + switch/PHY chip. This is being worked on.</task> + </help> + </project> + + <project cat='soc'> + <title>Binary Package Patch Infrastructure — pkg_patch</title> + + <contact> + <person> + <name> + <given>Ivan</given> + <common>Voras</common> + </name> + <email>ivoras@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/IvanVoras/pkg_patch" /> + </links> + + <body> + <p>pkg_patch is a tool meant to be used with the rest of the + pkg_* utilities whose job is to create and apply binary patches + to &os; package archives. The SoC project was successfully + completed but there are some open issues about the integration of + the tool in the &os; system. Some changes are necessary to the + port/patch infrastructure to support the "update" mode instead of + "remove+add".</p> + </body> + + <help> + <task>Solve pending issues about the ports install/upgrade + workflow, probably within the <a + href="http://wiki.FreeBSD.org/Pkg_install2_specs">pkg_install2</a> + effort.</task> + </help> + </project> + + <project cat='soc'> + <title>ExtFS Status Report</title> + + <contact> + <person> + <name> + <given>Zheng</given> + <common>Liu</common> + </name> + <email>gnehzuil@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/SOC2010ZhengLiu">Project + wiki</url> + + <url href="http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/soc2010/extfs/src/sys/fs/&c=rFV@//depot/projects/soc2010/extfs/src/sys/fs/ext2fs/?ac=83"> + pre-allocation</url> + + <url href="http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/soc2010/ext4fs/src/sys/fs/&c=cc4@//depot/projects/soc2010/ext4fs/src/sys/fs/ext4fs/?ac=83"> + ext4 read-only mode</url> + </links> + + <body> + <p>This project has two goals: pre-allocation algorithm for ext2fs + and ext4 read-only mode. Aim of the pre-allocation algorithm is + to implement a reservation window mechanism. This mechanism has + been implemented and a patch have been submitted. The aim of + ext4 read-only mode is to make it possible to read ext4 file + systems in read-only mode when the disk is formatted with + default features. Until now it can read data from ext4 file + systems with default features in read-only mode. A patch has + been submitted a patch to the freebsd-fs mailing list and there + is a new kernel module, called ext4fs, is under development for + it.</p> + </body> + + <help> + <task>More testing of the pre-allocation algorithm.</task> + </help> + </project> + + <project cat='proj'> + <title>BSD# Project</title> + + <contact> + <person> + <name> + <given>Romain</given> + <common>Tartière</common> + </name> + <email>romain@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://code.google.com/p/bsd-sharp/">The BSD# project + on Google-code</url> + + <url href="http://www.mono-project.org/">Mono (Open source .Net + Development Framework)</url> + </links> + + <body> + <p>The BSD# Project is devoted to porting the Mono .NET framework + and applications to the &os; operating system.</p> + + <p>Mono 2.8 has been released a few days ago and is already + available in the BSD# repository. The update breaks a few ports + so the lang/mono update in the &os; ports tree will be delayed + until those programs are fixed for a smoother update + experience.</p> + + <p>Work is in progress to include some long-awaited ports such as + deskutils/gnome-do but they require a lot of testing and hacking + because they have clearly been designed to run on GNU/Linux and + portability has never been a priority (which is quite amusing if + you consider portability is the main reason to be for mono).</p> + </body> + + <help> + <task>If you have some time, test mono ports and send + feedback.</task> + + <task>If you have more time, join the BSD# Team! There are many + ways to help out!</task> + + <task>Currently low priority, some mono hackers who do not use + &os; would be interested in a debug live-image of &os; to help us + diagnose and fix bugs more effectively.</task> + </help> + </project> + + <project cat='proj'> + <title>Clang Replacing GCC in the Base System</title> + + <contact> + <person> + <name> + <given>Ed</given> + <common>Schouten</common> + </name> + <email>ed@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Roman</given> + <common>Divacky</common> + </name> + <email>rdivacky@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Brooks</given> + <common>Davis</common> + </name> + <email>brooks@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Pawel</given> + <common>Worach</common> + </name> + <email>pawel.worach@gmail.com</email> + </person> + + <person> + <name> + <given>Dimitry</given> + <common>Andric</common> + </name> + <email>dim@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" /> + </links> + + <body> + <p>We recently imported the 2.8 release of Clang into -CURRENT. + This release contains many new features and improvements. The + integrated assembler ships with this version, but it is not + ready for general use yet.</p> + + <p>Since r212979, all necessary changes have been committed to be + able to build world with Clang, at least on amd64 and i386. It + can also be installed and run, and we are now starting the + process of shaking out the inevitable bugs.</p> + + <p>Because LLVM and Clang are still being improved continuously, + we want to import new versions regularly, approximately every two + months, to gain access to new features, bug fixes and performance + improvements.</p> + + <p>There is also an effort on behalf of the ports people, to make + as many ports as possible compile and run properly with Clang. + Most of the time, this means fixing the incorrect assumption that + gcc is the only existing compiler, but sometimes more complicated + issues pop up. Help in this area is greatly appreciated.</p> + </body> + + <help> + <task>Importing new Clang snapshots fairly regularly + (approximately bi-monthly).</task> + + <task>Seeing if Clang can be used to build world for ARM + (volunteers and ARM experts wanted).</task> + + <task>Fixing as many ports as possible to build with Clang.</task> + + <task>Running periodical ports exp builds with Clang (on amd64 + and i386), for example once a month.</task> + </help> + </project> + + <project cat='bin'> + <title>Updating Base Tools to Accommodate Ports + Requirements</title> + + <contact> + <person> + <name> + <given>Gordon</given> + <common>Tetlow</common> + </name> + <email>gordon@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The goal of the project is to allow easier extension of base + system tools by the ports system. Ideally, no files in /etc + should need to be modified by a port installation.</p> + + <p>The man toolset was recently reimplemented as a BSDL version + instead of the old GPL version. It is also a single shell script + instead of multiple C programs. Ports can extend the man + functionality by dropping files into + /usr/local/etc/man.d/portname.conf.</p> + + <p>Next up on the list is to finish the implementation for + newsyslog thereby allowing ports that need logs rotated to take + advantage of that tool.</p> + </body> + </project> + + <project cat='arch'> + <title>&os;/mips on Octeon</title> + + <contact> + <person> + <name> + <given>Juli</given> + <common>Mallett</common> + </name> + <email>jmallett@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/FreeBSD/mips/Octeon" /> + </links> + + <body> + <p>All Octeon development is now ongoing in -CURRENT and most + Octeon-specific and general MIPS changes from the old Octeon + branch have been checked in. The Simple Executive from the Cavium + Octeon SDK has been checked into Subversion and most of the + Octeon port has been updated to use it where appropriate, + including moving to a port of the Linux Ethernet driver, octe. + SMP support is stable on 2-core systems and has seen some testing + on systems with up to 16 cores.</p> + </body> + + <help> + <task>Some PCI devices still do not seem to work + completely.</task> + + <task>Host-mode USB support is incomplete and needs further + testing and debugging.</task> + + <task>Work on an ATA-based Compact Flash driver for boards that + support DMA has begun.</task> + + <task>A GPIO driver should be trivial using the Simple + Executive.</task> + + <task>Performance in the Linux-derived octe Ethernet driver could + be improved. Support for some switch chipsets that are commonly + present in Octeon-based equipment is in progress.</task> + </help> + </project> + + <project cat='kern'> + <title>Kernel Event Timers Infrastructure</title> + + <contact> + <person> + <name> + <given>Alexander</given> + <common>Motin</common> + </name> + <email>mav@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/201010DevSummit?action=AttachFile&do=get&target=timers.pdf"> + Slides from DevSummit in Karlsruhe.</url> + + <url href="http://people.FreeBSD.org/~mav/tm6292_idle.patch"> + Proof of concept (dirty) patch, removing some timer events.</url> + </links> + + <body> + <p>Work on new event timers infrastructure continues. In -CURRENT + amd64, arm (Marvell), i386, mips, pc98, powerpc, sparc64, sun4v + architectures were refactored to use new timers API.</p> + + <p>New machine-independent timers management code was written. It + can utilize both legacy periodic and new one-shot timer + operation modes.</p> + + <p>Using one-shot mode allows to significantly reduce the number of + timer interrupts and respectively increase CPU sleep time + during idle periods. Timer interrupts on idle CPUs are now + generated only when they are needed to handle registered + time-based events. Busy CPUs unluckily still receive the full + interrupt rate for purposes of resource accounting, scheduling + and timekeeping.</p> + + <p>With some additional tuning it is now possible to have an + 8-core system, receiving only about 100 interrupts per second + and respectively have CPU idle periods up to 100ms. This + allows to effectively use any supported CPU idle states + (C-states), that reduces power consumption and increases effect + of the Intel TurboBoost technology.</p> + + <p>New manual pages were written to document this functionality: + eventtimers(7), attimer(4), atrtc(4), hpet(4).</p> + </body> + + <help> + <task>Troubleshoot possible hardware issues.</task> + + <task>Refactor remaining architectures (arm, ia64, XEN + PV).</task> + + <task>Do some optimizations in different subsystems to reduce + number of time-based events. Extend callout API with terms of + precision, allowing to group close events.</task> + + <task>Make schedulers tickless, or at least less depending on + time events to make skipping timer interrupts possible when CPUs + are busy.</task> + + <task>Merge code into 8-STABLE when it is considered ready.</task> + </help> + </project> + + <project cat='ports'> + <title>Ports Distfile and WWW Checker</title> + + <contact> + <person> + <name> + <given>Emanuel</given> + <common>Haupt</common> + </name> + <email>ehaupt@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~ehaupt/distilator/" /> + </links> + + <body> + <p>Given the current status of fenner's Distfiles Survey, a new + distfile checker was written in order to have an overview for the + state of each distfile in the ports tree. The distfile checker is + also able to verify WWW entries in pkg-descr files. This is an + attempt to weed out broken MASTER_SITES and outdated WWW + entries.</p> + + <p>The current version uses a MySQL database backend and is able + to verify 432512 distfiles (30 concurrent threads) within 24 + hours.</p> + </body> + + <help> + <task>Provide JavaScript to sort/filter/search tables.</task> + </help> + </project> + + <project cat='proj'> + <title>Userland DTrace</title> + + <contact> + <person> + <name> + <given>Rui</given> + <common>Paulo</common> + </name> + <email>rpaulo@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/DTrace/userland" /> + </links> + + <body> + <p>Userland DTrace support was a &os; Foundation sponsored + project that was developed during this summer. The project aimed + to bring the userland DTracing functionality to &os; as it is + available on OpenSolaris. &os; now supports the pid provider and + the usdt probes. plockstat is available with a separate patch. + Dtruss, a DTrace script that works similarly to ktrace, but with + other advantages was imported into &os;. The mysql-server and + postgresql-server ports also have DTrace support.</p> + </body> + </project> + + <project cat='arch'> + <title>&os; on the Playstation 3</title> + + <contact> + <person> + <name> + <given>Nathan</given> + <common>Whitehorn</common> + </name> + <email>nwhitehorn@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Peter</given> + <common>Grehan</common> + </name> + <email>grehan@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="svn://svn.FreeBSD.org/base/user/nwhitehorn/ps3">PS3 + SVN Repository</url> + + <url href="http://people.FreeBSD.org/~nwhitehorn/ps3">Pre-built + PS3 kernel</url> + </links> + + <body> + <p>&os;/powerpc64 now boots multi-user SMP and is self-hosting on + the Playstation 3. Booting requires a PS3 console with the + OtherOS capability (fat model console with firmware < 3.21). + The only supported hardware at present is USB and the Ethernet + controller.</p> + </body> + + <help> + <task>SATA support.</task> + + <task>Boot loader enhancements to allow user input at the loader + prompt.</task> + + <task>Support for the Cell SPU units.</task> + </help> + </project> + + <project cat='arch'> + <title>Bringing up ARM to &os; Tree</title> + + <contact> + <person> + <name> + <given>Warner</given> + <common>Losh</common> + </name> + <email>imp@bsdimp.com</email> + </person> + + <person> + <name> + <given>Mohammed</given> + <common>Farrag</common> + </name> + <email>mfarrag@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>We are still in the beginning of the project since we started + it after the summer of code.</p> + </body> + + <help> + <task>Reading ARM structure.</task> + <task>Reading MicroC OS.</task> + <task>Using Qemu to emulate the work.</task> + </help> + </project> + + <project cat='ports'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Thomas</given> + <common>Abthorpe</common> + </name> + <email>portmgr-secretary@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Port</given> + <common>Management Team</common> + </name> + <email>portmgr@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ports/" /> + + <url href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" /> + + <url href="http://portsmon.FreeBSD.org/index.html" /> + + <url href="http://www.FreeBSD.org/portmgr/index.html" /> + + <url href="http://blogs.FreeBSDish.org/portmgr/" /> + + <url href="http://www.twitter.com/freebsd_portmgr/" /> + + <url href="http://www.facebook.com/group.php?gid=135441496471197" /> + + <url href="http://tinderbox.marcuscom.com/" /> + </links> + + <body> + <p>The ports tree count now exceeds 22,000. With the assistance + of many people, especially Philip Gollucci, the open PR count is + below 1000 for the first time in quite a while. This is very + encouraging progress.</p> + + <p>Since the last report, we added five new committers, and took + in two commit bits for safe keeping.</p> + + <p>With onsite assistance from jhb@, gnn@, skreuzer@, and + pgollucci@, we now have 11 new servers at NYI. The machines still + need testing for stability and will soon be assigned for package + building.</p> + + <p>The Ports Management team have been running -exp runs on an + on-going basis, verifying how base system updates may affect the + ports tree, as well as providing QA runs for major ports updates. + Of note, -exp runs were done for:</p> + + <ul> + <li>des: test libfetch</li> + <li>gabor: tests for BSD iconv and grep</li> + <li>mezz: switch www/neon28 to www/neon29</li> + <li>beat: update www/libxul</li> + <li>johans: update devel/bison and devel/m4</li> + <li>dinoex: update graphics/tiff</li> + <li>jpaetzel: update devel/popt</li> + <li>ade: multiple runs autotools upgrade</li> + <li>gerald: setting USE_GCC=4.5 as default</li> + <li>ashish: changes to Mk/bsd.license.mk</li> + <li>kwm: test of Clang in -CURRENT</li> + </ul> + </body> + + <help> + <task>Looking for help fixing <a + href="http://wiki.FreeBSD.org/PortsBrokenOnCurrent">ports + broken on -CURRENT</a>.</task> + + <task>Looking for help with <a + href="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures"> + Tier-2 architectures</a>.</task> + + <task>Most ports PRs are assigned, we now need to focus on + testing, committing and closing.</task> + </help> + </project> + + <project cat='misc'> + <title>&os; Developer Summit, Karlsruhe</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Páli</common> + </name> + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/201010DevSummit" /> + </links> + + <body> + <p>We were happy to have more than 40 &os; developers and guests + attending the &os; Developer Summit prior to EuroBSDCon 2010 + in Karlsruhe, Germany. This workshop-style event was hosted at + Karlsruhe Institute of Technology, and included prepared + presentations in the morning, as well as group hacking and + discussion sections in the afternoon. We had various talks on + several topics, covering the USB subsystem, state of the + toolchain, the &os; documentation, NanoBSD improvements, &os; + port of PF, jails, Virtual Private Systems, cooperation with the + PC-BSD Project, FreeNAS, the new event timers subsystems, + bugbusting discussions and Ports Tinderbox presentations, and + many of this year's and last year's Google Summer of Code + projects. Photos, videos, and slides for most of the talks are + available on the wiki page.</p> + </body> + </project> + + <project cat='kern'> + <title>USB Stack</title> + + <contact> + <person> + <name> + <given>Hans Petter</given> + <common>Selasky</common> + </name> + <email>hselasky@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://svn.FreeBSD.org/viewvc/base/head/sys/dev/usb/controller/xhci.c?view=log"> + XHCI driver</url> + </links> + + <body> + <p>During the last two months the USB stack in -CURRENT has been + enhanced to support USB 3.0 and the XHCI USB 3.0 chipset from + Intel. The XHCI chip will eventually replace the EHCI, OHCI and + UHCI chips.</p> + </body> + + <help> + <task>&os; testers which have access to USB 3.0 hardware are + wanted.</task> + </help> + </project> + + <project cat='arch'> + <title>&os;/mips Ralink RT3052F/Broadcom BCM5354</title> + + <contact> + <person> + <name> + <given>Aleksandr</given> + <common>Rybalko</common> + </name> + <email>ray@dlink.ua</email> + </person> + </contact> + + <links> + <url href="http://wiki.ddteam.net/wiki.cgi?page=DIR-320+FreeBSD"> + Description</url> + + <url href="http://my.ddteam.net/hg/BASE/">Mercurial + repository</url> + </links> + + <body> + <p>&os;/mips has been ported to D-Link DAP-1350, wireless + AP/router based on Ralink RT3052F SoC.</p> + + <p>Drivers status:</p> + + <ul> + <li>rt2860: Ralink RT2860 802.11n — Worked, but RT3022 + 2.4G 2T2R radio tuning required.</li> + + <li>rt: Ralink RT3052F onChip Ethernet MAC — Done.</li> + + <li>rtsw: OnChip Ethernet switch — Not done (initialized + by UBoot).</li> + + <li>usb-otg: DWC like USB OTG controller — Worked.</li> + + <li>gpio: RT3052F onChip GPIO — Worked (LEDs, + Buttons).</li> + + <li>cfi: CFI NOR Flash — Worked.</li> + </ul> + + <p>&os;/mips D-Link DIR-320 project(BCM5354 SoC).</p> + + <p>New profile openvpn-router available for testing.</p> + </body> + + <help> + <task>Debug/Fix USB OTG driver (RT3052F).</task> + + <task>Debug/Fix 802.11n driver (RT3052F).</task> + + <task>Write rtswitch driver (RT3052F).</task> + + <task>Implement Timer unit driver (RT3052F).</task> + + <task>Implement Hardware NAT/PPPoE/VLAN offload (RT3052F).</task> + + <task>Implement I2C/I2S/PCM/SPI drivers (RT3052F).</task> + + <task>switch configuration utility (BCM5354).</task> + </help> + </project> + + <project cat='docs'> + <title>Web Feeds for UPDATING Files</title> + + <contact> + <person> + <name> + <given>Alexander</given> + <common>Kojevnikov</common> + </name> + <email>alexander@kojevnikov.com</email> + </person> + </contact> + + <links> + <url href="http://updating.versia.com/" /> + </links> + + <body> + <p><a href="http://updating.versia.com/">updating.versia.com</a> + features web feeds for UPDATING files from ports, head, stable/7 + and stable/8. These feeds provide an easy way to track + important changes in the ports tree and the base system.</p> + </body> + </project> + + <project cat='arch'> + <title>&os;/sparc64</title> + + <contact> + <person> + <name> + <given>Marius</given> + <common>Strobl</common> + </name> + <email>marius@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Apart from the constant bug fixing and adaptions to + machine-independent changes that pretty much always take place, + not much has happened in the area of sparc64 since the last + status report. The only noteworthy exception are some performance + optimizations which take advantage of features of Fujitsu SPARC64 + CPUs. These were a bit too risky for putting them in shortly + before &os; 8.1-RELEASE but will be part of 7.4-RELEASE and + 8.2-RELEASE now that they have received the necessary + testing.</p> + + <p>Part of reasons why not much has happened in this spot was some + lack of time on my side but also due to nobody showing up with a + not yet supported sun4u machine lately and me delving in the + network land instead, which yielded some things to report about + in the next status report. On the other hand I recently got a + hold of a Sun Fire 3800, so these and other models from the same + family likely will be supported by &os; at some point in the + future.</p> + </body> + </project> + + <project cat='docs'> + <title>The &os; German Documentation Project</title> + + <contact> + <person> + <name> + <given>Johann</given> + <common>Kois</common> + </name> + <email>jkois@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Benedict</given> + <common>Reuschling</common> + </name> + <email>bcr@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://doc.bsdgroup.de">Website of the &os; German + Documentation Project.</url> + </links> + + <body> + <p>The committers to the German Documentation Project were mostly + trying to keep the documents and the website translations in sync + with the ones on &os;.org. Fabian Ruch was helpful in catching up + with the changes to the Porters Handbook. Benedict translated the + Solid State article into German because this is becoming a good + addition to traditional hard drive storage.</p> + + <p>We tried to re-activate committers who did not contribute for + some time but most of them are currently unable to free up enough + time. We hope to gain fresh contributor blood as we are getting + occasional reports about bugs and grammar in the German + translation.</p> + </body> + + <help> + <task>Submit grammar, spelling or other errors you find in the + German documents and the website.</task> + + <task>Translate more articles and other open handbook + sections.</task> + </help> + </project> + + <project cat='docs'> + <title>mandoc/mdocml — groff Replacement for Rendering Manual + Pages in &os;</title> + + <contact> + <person> + <name> + <given>Ulrich</given> + <common>Spörlein</common> + </name> + <email>uqs@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://mdocml.bsd.lv/">Kristaps' mdocml project page.</url> + <url href="https://www.spoerlein.net/cgit/cgit.cgi/freebsd.work/log/?h=mdocml"> + Git branch for &os; mdocml related work.</url> + </links> + + <body> + <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 &os;.</p> + + <p>mandoc(1) is more strict in what it accepts as input and is still + lacking some features that are used by some selected few manpages.</p> + + <p>Getting manual page fixes accepted by upstream vendors has been + challenging. Waiting for them to round-trip back into &os; will + take even longer. Future work will therefore result in direct + commits to our contrib/ and gnu/ repository areas, in the hope + this will not impact future vendor imports too much.</p> + </body> + + <help> + <task>Finish the Big Manpage Cleanup of 2010.</task> + + <task>Write a textproc/groff port for the latest groff version.</task> + + <task>Import mandoc(1), switch to catpages for base.</task> + + <task>Supply necessary ports infrastructure to opt-in to + mandoc(1).</task> + + <task>Discuss future of groff(1) in base wrt. share/doc.</task> + </help> + </project> + + <project cat='ports'> + <title>pkg_upgrade (sysutils/bsdadminscripts)</title> + + <contact> + <person> + <name> + <given>Dominic</given> + <common>Fandrey</common> + </name> + <email>kamikaze@bsdforen.de</email> + </person> + </contact> + + <links> + <url href="http://sf.net/projects/bsdadminscripts"> + bsdadminscripts SF project</url> + + <url href="http://sf.net/projects/bsdadminscripts/files/publications/2010-10-eurobsdcon/"> + EuroBSDCon 2010 slides and paper</url> + </links> + + <body> + <p>pkg_upgrade was (to my knowledge) the first binary packages + only update tool for the &os; ports. Using it does not require a + copy of the ports tree.</p> + + <p>Currently the tool is in the final stages of a recode, that + will greatly improve support for sharing packages over NFS or + nullfs mounts (e.g. for distributing packages into jails) and + also offers improved dependency tracking and performance, more in + line with how pointyhat and Tinderbox build packages.</p> + + <p>I recently had the opportunity to present my work at the + EuroBSDCon 2010.</p> + </body> + + <help> + <task>Complete session code.</task> + + <task>Add INDEX generator script that harvests information + directly from packages and hence is always accurate.</task> + + <task>Testing.</task> + </help> + </project> + + <project cat='soc'> + <title>Registration of Optional Kernel Subsystems via + sysctl</title> + + <contact> + <person> + <name> + <given>Ilya</given> + <common>Bakulin</common> + </name> + <email>kibab@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2010/freebsd/t127230759508"> + Project description on GSoC website</url> + + <url href="http://wiki.FreeBSD.org/201010DevSummit?action=AttachFile&do=view&target=kibab_sysctlreg.pdf"> + Slides (from &os; DevSummit in Karlsruhe)</url> + </links> + + <body> + <p>All work is now in Perforce. Rich set of features is added to + the kernel, userland tools and libc modifications are ready, + documentation is ready.</p> + </body> + + <help> + <task>Documentation review.</task> + + <task>Presentation of feature set on the various mailing + lists.</task> + + <task>Committing to -CURRENT, possibly merging to stable branches + (changes do not break ABI/KBI).</task> + </help> + </project> + + <project cat='proj'> + <title>Kernel-level Stacked Cryptographic File System — + PEFS</title> + + <contact> + <person> + <name> + <given>Gleb</given> + <common>Kurtsou</common> + </name> + <email>gk@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/PEFS" /> + + <url href="http://github.com/glk/pefs" /> + </links> + + <body> + <p>PEFS is a kernel level stacked cryptographic file system, i.e. + it stacks on top of existing mounted filesystems. AES and + Camellia algorithms in XTS mode are supported. The project has + matured since Summer of Code 2009, most important improvements + for last few months include: switch to use XTS encryption mode, + implementation of sparse file support, fixing rename bugs + including race and livelock conditions, addition of ext2 support. + PEFS suite contains pam module facilitating user authentication + with file system key and adding keys to mounted file system on + login. PEFS passes fsx, pjdfstest, blogbench and dbench tests + running on top of UFS and ZFS.</p> + </body> + </project> + + <project cat='soc'> + <title>Packet Capturing Stack — ringmap</title> + + <contact> + <person> + <name> + <given>Alexander</given> + <common>Fiveg</common> + </name> + <email>afiveg@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://code.google.com/p/ringmap/">Project-Page on + Google Code</url> + + <url href="http://ringmap.googlecode.com/files/ringmap_slides.pdf"> + Slides</url> + + <url href="http://wiki.FreeBSD.org/AlexandreFiveg">Wiki</url> + </links> + + <body> + <p>Ringmap is a complete &os; packet capturing stack specialized for + very high-speed networks. The goal of this project is to develop the + software for efficient packet capturing and integrate it with the + generic network drivers and libpcap.</p> + + <p>Current Status:</p> + + <ul> + <li>Integrated with the lem driver. Intel network controllers: + 8254X are supported.</li> + + <li>Packet filtering using BPF in both kernel and user space.</li> + + <li>Partly integrated with ixgbe driver for 10Gb capturing.</li> + </ul> + </body> + + <help> + <task>Support for hardware timestamping.</task> + + <task>Writing packets to the disc from within the kernel.</task> + + <task>Multiqueue support.</task> + + <task>Extending the "ringmap" for packet transmission.</task> + </help> + </project> + + <project cat="team"> + <title>The &os; Foundation Status Report</title> + + <contact> + <person> + <name> + <given>Deb</given> + <common>Goodkin</common> + </name> + <email>deb@FreeBSDFoundation.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSDFoundation.org" /> + </links> + + <body> + <p>We were proud to be a sponsor for MeetBSD 2010 Poland and + KyivBSD 2010 in Kiev, Ukraine. We also committed to + sponsoring BSDDay Argentina 2010, MeetBSD California 2010, and + NYBSDCon 2010 all in November. The Foundation was also + represented at MeetBSD Poland and Ohio LinuxFest.</p> + + <p>Completed the Foundation funded projects: "&os; Jail-Based + Virtualization" by Bjoern Zeeb and "DTrace Userland" by Rui + Paulo.</p> + + <p>We kicked off a new project by Swinburne University called + "Five New TCP Congestion Control Algorithms for &os;".</p> + + <p>We continued our work on infrastructure projects to beef up + hardware for package-building, network-testing, etc. This + includes purchasing equipment as well as managing equipment + donations.</p> + + <p>We are three quarters of the way through the year and we have + raised around $160,000 towards our goal of $350,000. Find out how + to make a donation at + <a href="http://www.FreeBSDFoundation.org/donate/"> + http://www.FreeBSDFoundation.org/donate/</a> + </p> + + <p>Stop by and visit with us at MeetBSD California (Nov 5-6), + LISA (Nov 10-11), and NYCBSDCon (Nov 12-14).</p> + </body> + </project> + + <project cat='ports'> + <title>Chromium Web Browser</title> + + <contact> + <person> + <name> + <given>Ruben</given> + </name> + <email>chromium@hybridsource.org</email> + </person> + </contact> + + <links> + <url href="http://chromium.hybridsource.org">Main chromium + site</url> + + <url href="http://chromium.hybridsource.org/issues">Porting + summary</url> + </links> + + <body> + <p>Chromium is a Webkit-based web browser that is largely BSD + licensed and was recently committed to ports. It has been working + well on &os; and supports new features like HTML 5 video. Newer + builds use the Clang compiler, Clang first compiled a non-debug + build of Chromium, a very large C++ project, on &os;. This + porting effort employs a new hybrid-source model: portions of the + latest &os; patches are kept closed for a limited time and new + builds are made available only to paying subscribers, while older + builds are eventually spun off to ports. Further work remains to + port all of Chromium to &os;, I am now porting the task manager + to use &os;'s libkvm and the ALSA audio backend needs to be + ported to OSS. There are other issues listed at the porting + summary, contact me if you would like to pitch in.</p> + </body> + </project> + + <project cat='misc'> + <title>BSD-Day@2010</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Páli</common> + </name> + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/BSDDay_2010" /> + </links> + + <body> + <p>The purpose of this one-day event is to gather Central + European developers of today's open-source BSD systems to + popularize their work and their organizations, and to meet each + other in the real life. We would also like to motivate potential + future developers and users, especially undergraduate university + students to work with BSD systems. This year's BSD-Day will be + held in Budapest, Hungary at Eötvös Loránd + University, Faculty of Informatics on November 20, 2010. + Everybody is welcome!</p> + </body> + </project> + + <project cat='net'> + <title>Five New TCP Congestion Control Algorithms for &os;</title> + + <contact> + <person> + <name> + <given>David</given> + <common>Hayes</common> + </name> + <email>dahayes@swin.edu.au</email> + </person> + + <person> + <name> + <given>Lawrence</given> + <common>Stewart</common> + </name> + <email>lstewart@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Grenville</given> + <common>Armitage</common> + </name> + <email>garmitage@swin.edu.au</email> + </person> + + <person> + <name> + <given>Rui</given> + <common>Paulo</common> + </name> + <email>rpaulo@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://caia.swin.edu.au/freebsd/5cc/" /> + + <url href="http://caia.swin.edu.au/urp/newtcp/" /> + + <url href="http://www.FreeBSDFoundation.org/projects.shtml" /> + + <url href="http://people.FreeBSD.org/~lstewart/patches/5cc/" /> + </links> + + <body> + <p>Work has commenced on a newly funded &os; Foundation project + to bring six modular TCP congestion control (CC) algorithm + implementations (the existing NewReno and five new algorithms: + HTCP, CUBIC, Vegas, HD and CHD) to the &os; kernel. See the + CAIA 5cc and NewTCP websites for more details on the + algorithms.</p> + + <p>To support the project's primary deliverable, we will also + be incorporating the CAIA modular CC and Khelp frameworks into + the &os; kernel, along with the Enhanced Round Trip Time Khelp + module.</p> + + <p>The project will make a sizable, state-of-the-art + contribution to &os; and in certain areas, add completely novel + work unavailable in any other operating system known to us.</p> + + <p>We anticipate a number of benefits, including vastly + improved researcher friendliness, reduced work for TCP oriented + vendors of &os;-based appliances, and greater choice for system + administrators who operate &os; systems in atypical network + scenarios.</p> + + <p>Keep an eye on the freebsd-net mailing list for project-related + announcements.</p> + </body> + </project> + + <project cat='net'> + <title>Enhancing the &os; TCP Implementation</title> + + <contact> + <person> + <name> + <given>Lawrence</given> + <common>Stewart</common> + </name> + <email>lstewart@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://caia.swin.edu.au/freebsd/etcp09/" /> + + <url href="http://caia.swin.edu.au/urp/newtcp/" /> + + <url href="http://www.FreeBSDFoundation.org/projects.shtml" /> + + <url href="http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/" /> + </links> + + <body> + <p>All outstanding patches have been committed to -CURRENT after a + lengthy review process. It is anticipated to merge all of the + project's SIFTR and reassembly queue-related patches from + -CURRENT to the stable branches in time for the upcoming 7.4 and + 8.2 releases.</p> + </body> + </project> + + <project cat='kern'> + <title>Resource Containers</title> + + <contact> + <person> + <name> + <given>Edward Tomasz</given> + <common>Napierala</common> + </name> + <email>trasz@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The goal of this project is to implement resource containers + and a simple per-jail resource limits mechanism. Resource + containers are also a prerequisite for other resource management + mechanisms, such as Hierarchical Resource Limits, for "Collective + Limits on Set of Processes (aka. Jobs)" Google Summer of Code + 2010 project, for implementing mechanism similar to Linux + cgroups, and might be also used to e.g. provide precise resource + usage accounting for administrative or billing purposes. So far, + a generic resource usage framework has been developed, along with + limit enforcement for most resources. Work is on-going on adding + limits for remaining resources, debugging and generally improving + the implementation. This project is being sponsored by The &os; + Foundation.</p> + </body> + </project> + + <project cat='proj'> + <title>BSNMP Enhancements</title> + + <contact> + <person> + <name> + <given>Shteryana</given> + <common>Shopova</common> + </name> + <email>syrinx@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Philip</given> + <common>Paeps</common> + </name> + <email>philip@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/CategorySNMP">bsnmpd(1)-related + pages on &os; wiki</url> + + <url href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/syrinx/snmp_ieee80211&HIDEDEL=NO"> + snmp_wlan(3) P4 code tree</url> + + <url href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/syrinx/syrinx_bsnmpv3&HIDEDEL=NO"> + SNMPv3 for bnmspd(1) P4 code tree</url> + </links> + + <body> + <p>During the previous few months several additions were + developed to &os;'s built-in SNMP daemon — bsnmpd(1).</p> + + <p>First a snmp_wlan(3) module was developed that allows + monitoring and configuration of wlan(4) interfaces operating in + various modes, including statistics, attached/neighboring + station information, MAC access control entries and mesh routing + information. The module's code was submitted in SVN and is now + a part of the &os; base system.</p> + + <p>Next, SNMPv3 authentication and encryption support were added + to bsnmplib(3), bsnmpd(1) and bsnmptools (which are available + via the ports system currently). The message digest and cipher + calculation calls use the implementation of the relevant + cryptographic algorithm implementation in OpenSSL's crypto(3) + library. bsnmpd(1) may still optionally be compiled without the + crypto(3) library, in which case only unauthenticated plain-text + SNMPv3 PDUs may be processed.</p> + + <p>In addition, a snmp_usm(3) module was developed that is used to + configure SNMPv3 users parameters (name, authentication & + encryption algorithms used and relevant keys, etc.) into + bsnmpd(1) as per RFC 3414.</p> + + <p>Finally, a snmp_vacm(3) module was developed that allows + configuration of view-based access control as per RFC 3415, and + relevant checks are made by bsnmpd(1) that allow or restrict + access to specific SNMPv1/SNMPv2 communities or SNMPv3 users to + certain MIB subtrees as per the configuration in the + snmp_vacm(3) module. If none of the SNMPv3-related modules is + loaded, bsnmpd(1) preserves its current behavior with + SNMPv1/SNMPv2c PDUs.</p> + + <p>This work is being funded by the &os; Foundation.</p> + </body> + + <help> + <task>Update Wiki Page to reflect latest work and document proper + use.</task> + + <task>Finish cleanup and have it reviewed.</task> + + <task>More extensive user testing.</task> + </help> + </project> + + <project cat='bin'> + <title>&os; Services Control (fsc)</title> + + <contact> + <person> + <name> + <given>Tom</given> + <common>Rhodes</common> + </name> + <email>trhodes@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~trhodes/fsc/" /> + </links> + + <body> + <p>&os; Services Control is a mix of binaries which integrate + into the rc.d system and provide for service (daemon) + monitoring. It knows about signals, pidfiles, and uses very + little resources.</p> + + <p>The fsc daemon (fscd) runs in the background once the system + has started. Services are then added to this daemon via the + fscadm control utility and from there they will be monitored. + When they die, depending on the reason, they will be restarted. + Certain signals may be ignored (list not decided), and fscd + will remove that service from monitoring. Every action is + logged to the system logging daemon. Additionally, the fscadm + utility may be used to inquire about what services are + monitored, their pidfile location, and current process id.</p> + + <p>FSC provides several advantages over the third-party + daemontools package. For example, fscd uses push notifications + instead of polling; fscd is an internal, &os;-maintained + software package accessible to all developers where daemontools + would have to be a port and require us to maintain patches; + fscd could be easily integrated with the current rc.d + infrastructure.</p> + + <p>Partially based on the ideas of daemontools and Solaris + Service Management Facility (SMF), this could be an extremely + useful tool for &os; systems.</p> + + <p>Since the last status report, two bugs have been fixed and + the documentation has been updated. In the coming weeks we hope + to get more developer attention and review, perhaps even push + to commit the code into &os;.</p> + </body> + + <help> + <task>Testing and feedback would be really helpful.</task> + </help> + </project> + + <project cat='kern'> + <title>Netdump Support</title> + + <contact> + <person> + <name> + <given>Attilio</given> + <common>Rao</common> + </name> + <email>attilio@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ed</given> + <common>Maste</common> + </name> + <email>emaste@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/Netdump" /> + + <url href="svn://svn.FreeBSD.org/base/project/sv/" /> + </links> + + <body> + <p>Netdump provides kernel core dumping over the network, instead + of to a local disk. It implements a very minimal TCP/IPv4 stack + and uses a custom UDP protocol to transmit the dump to the + netdump server running on another host. Network interfaces + selected for dumping perform I/O in polling mode.</p> + + <p>Netdump should find its use in diskless workstation clusters, + PXE-booted test machines, and perhaps when doing disk driver + development.</p> + </body> + + <help> + <task>General &os; dumping mechanism refinements.</task> + + <task>Implement checksum on UDP packets.</task> + + <task>Investigate the possibility to replace the custom protocol + with tftp.</task> + + <task>Investigate the possibility to replace the custom TCP/IPv4 + stack with Contiki.</task> + + <task>Implement network console and gdb backend using a shared + debug context stack.</task> + + <task>Add IPv6 support.</task> + </help> + </project> + + <project cat='misc'> + <title>PC-BSD</title> + + <contact> + <person> + <name> + <given>Kris</given> + <common>Moore</common> + </name> + <email>kmoore@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.pcbsd.org">PC-BSD Website</url> + + <url href="http://trac.pcbsd.org/browser/pcbsd/current/">PC-BSD + Current Repo</url> + </links> + + <body> + <p>Work is progressing quickly on a major re-factoring of PC-BSD + tools and the PBI format for 9.0. Our GUI tools have been + converted to compile / run within native QT without KDE now, + allowing us to begin offering support for other desktop + environments for 9.0, such as Gnome, XFCE, LXDE, KDE, etc. The + PBI format has undergone a complete evolution, and is now + entirely command-line based for all aspects of it, with only a + few dependencies upon curl & xdg-utils. This will allow us to + begin offering PBIs for traditional &os; users starting with 9.0, + who will be able to install the pbi-manager from ports in the + near future.</p> + </body> + + <help> + <task>We are still busy converting / fixing all our tools to play + nicely with various DE's, but making quick progress.</task> + + <task>The new PBI format is still undergoing extensive testing, + and bugs are being isolated and fixed.</task> + </help> + </project> + + <project cat='bin'> + <title>xz Compression for Packages and Log Files</title> + + <contact> + <person> + <name> + <given>Martin</given> + <common>Matuska</common> + </name> + <email>mm@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Support for xz compression has been enabled in bsdtar (-CURRENT + 8-STABLE) and added to pkg_create(1) and pkg_add(1) (-CURRRENT). + Packages with the .txz suffix can be created and installed. + Log file compression using xz in newsyslog(8) will be integrated + soon. Benchmarks show 15-30% better compression ratios and up to + halved decompression times when compared to bzip2. A switch from + the default package format from .tbz to .txz is to be + considered.</p> + </body> + + <help> + <task>Test building all &os; packages with xz compression.</task> + </help> + </project> + + <project cat='misc'> + <title>&os; Developer Summit, meetBSD California 2010</title> + + <contact> + <person> + <name> + <given>Warner</given> + <common>Losh</common> + </name> + <email>imp@ixsystems.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/201011DevSummit">Information + page</url> + </links> + + <body> + <p>We will be having a developers summit meeting at meetBSD + California 2010 on November 4th, the day before the conference. + Based on who is in attendance, we will be talking about the + status of pressing issues; working on pressing problems and + using the opportunity for face to face meetings to work out + issues that are difficult in email. This is an invitation-only + event, but any developer can invite people they think would help + drive this meeting forward. An agenda will be published closer + to the date.</p> + </body> + </project> + + <project cat='proj'> + <title>External Toolchain Support</title> + + <contact> + <person> + <name> + <given>Warner</given> + <common>Losh</common> + </name> + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>One problem that the project has with its push towards + embedded platforms is with the toolchain. The compilers and + linkers and such in the current &os; support the architectures + generically, but often times silicon vendors produce specialized + toolchains to wring the most performance out of their silicon. + Right now, it is difficult to compile &os; with these tools, as + many manual steps are required to make things 'just so'.</p> + + <p>The external toolchain project will leverage some of the work + done by the Clang team to support Clang in the base system + (breaking the strict dependency on CC=cc (except for the broken + intel CC support)). In addition, the orchestration of the build + (make buildworld) will change to avoid bootstrapping certain + tools, or compiling the compilers at all. In addition, support + for using alternate assemblers, linkers, etc., will be added. + The work will be done in subversion in projects/xtc (for + eXternal Tool Chain).</p> + </body> + </project> + + <project cat='proj'> + <title>Target Big Endian Must Die</title> + + <contact> + <person> + <name> + <given>Warner</given> + <common>Losh</common> + </name> + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The "tbemd" or Target Big Endian Must Die effort is nearing + completion. Most of the big sweeping changes to the tree have + been committed. The last change, actually pulling the switch, is + stalled waiting for make universe improvements. This work will + change the TARGET_ARCH from a plain 'mips' to 'mipsel' or + 'mipseb' based on which endian the platform has. It introduces + the concept of multiple architectures being implemented with one + set of files, and regularizes that design pattern into the &os; + build process. In the past, you had to set TARGET_BIG_ENDIAN=t to + compile for big endian, but that had a number of problems: can not + share /usr/obj between little and big endian targets, sometimes + the produced compilers will not work right unless TARGET_BIG_ENDIAN + is defined in the environment, etc.</p> + </body> + + <help> + <task>Update make universe to cope with the new architectures + when building kernels.</task> + </help> + </project> + + <project cat='team'> + <title>&os; KDE Team</title> + + <contact> + <person> + <name> + <given>&os; KDE</given> + <common>Team</common> + </name> + <email>kde@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Thomas</given> + <common>Abthorpe</common> + </name> + <email>tabthorpe@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Max</given> + <common>Brazhnikov</common> + </name> + <email>makc@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Kris</given> + <common>Moore</common> + </name> + <email>kmoore@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Dima</given> + <common>Panov</common> + </name> + <email>fluffy@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Alberto</given> + <common>Villa</common> + </name> + <email>avilla@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://FreeBSD.kde.org" /> + </links> + + <body> + <p>The &os; KDE team has been actively keeping pace with <a + href="http://techbase.kde.org/Schedules">development cycle</a> + as it is released by the KDE developers. Often having KDE in the + ports tree within the same week it has been released.</p> + + <p>An integral part of maintaining KDE exists in supporting the + Qt toolchain. As Nokia releases <a + href="http://qt.nokia.com/">Qt</a>, + our team is keeping pace making it available in our <a + href="http://area51.pcbsd.org/">development repository</a>.</p> + + <p>We are fortunate to have a strong contributor base that helps to + keep the process moving along. Our heartfelt thanks go out to all + that have helped with patches, maintaining ports, and responding + with help on the mailing lists.</p> + </body> + + <help> + <task>KDE 4.5.4 is due out at the end of November, with 4.6.0 to + be released early in 2011.</task> + + <task>The &os; KDE team is always looking for helpers, if you are + interested in assisting, please feel free to contact any of our + team members.</task> + </help> + </project> + + <project cat='proj'> + <title>pc-sysinstall</title> + + <contact> + <person> + <name> + <given>Kris</given> + <common>Moore</common> + </name> + <email>kmoore@FreeBSD.org</email> + </person> + + <person> + <name> + <given>John</given> + <common>Hixson</common> + </name> + <email>john@ixsystems.com</email> + </person> + + <person> + <name> + <given>Josh</given> + <common>Paetzel</common> + </name> + <email>jpaetzel@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://it.toolbox.com/blogs/bsd-guru/eurobsdcon-presentation-on-pcsysinstall-41831" /> + </links> + + <body> + <p>pc-sysinstall was imported into CURRENT recently. For the moment + it is feature complete, although progress on the text front end + for it may expose additional functionality it needs.</p> + </body> + + <help> + <task>The automated/scripted install features of pc-sysinstall + need wider testing and use to expose potential weaknesses, bugs, + and additional features it may require.</task> + + <task>Related tasks include getting a text front-end to + pc-sysinstall working and hooking up pc-sysinstall to the build + so install media is generated that runs pc-sysinstall.</task> + </help> + </project> + + <project cat='proj'> + <title>DAHDI/&os; Project</title> + + <contact> + <person> + <name> + <given>Max</given> + <common>Khon</common> + </name> + <email>fjoe@samodelkin.net</email> + </person> + </contact> + + <links> + <url href="http://www.asterisk.org/dahdi/" /> + + <url href="http://svn.digium.com/svn/dahdi/freebsd/" /> + + <url href="https://spreadsheets.google.com/pub?key=0Arw6eRL10yIwdGhLdGJWUHF4b3ExQzBsd3BGd2tublE&hl=en&single=true&gid=0&output=html"> + Project Status</url> + </links> + + <body> + <p>The purpose of DAHDI/&os; project is to make it possible to + use &os; as a base system for software PBX solutions.</p> + + <p>DAHDI (Digium/Asterisk Hardware Device Interface) is an + open-source device driver framework and a set of hardware drivers + for E1/T1, ISDN digital, and FXO/FXS analog cards [<a + href="http://www.asterisk.org/dahdi/">1</a>]. + Asterisk is one of the most popular open-source software PBX + solutions [<a href="http://www.asterisk.org/">2</a>].</p> + + <p>The project includes porting DAHDI framework and hardware + drivers for E1/T1, FXO/FXS analog, and ISDN digital cards to + &os;. This also includes TDMoE support, software and hardware + echo cancellation (Octasic, VPMADT032), and hardware transcoding + support (TC400B). The work is ongoing in the official DAHDI SVN + repository with the close collaboration with DAHDI folks at + Digium.</p> + + <p>DAHDI/&os; project is completed. ports/misc/dahdi now contains + the most recent DAHDI/&os; version and additional stuff that is + not available in DAHDI/&os; SVN repository due to licensing and + copyright restrictions (OSLEC echo canceler, experimental zaphfc + driver). Experimental sparc64 support is also implemented and is + currently being tested.</p> + + <p>There is a pile of minor changes in queue that will be handled + soon:</p> + + <ul> + <li>Add ability to run asterisk+dahdi under non-root user + account.</li> + + <li>Add support for bri_net_ptmp ISDN signalling to asterisk + port and drop old and outdated zaptel+asterisk-bristuff + ports.</li> + </ul> + + <p>Periodic merges from DAHDI/Linux SVN will be continued on a + regular basis with rolling out new DAHDI/&os; releases (most + likely synchronized with DAHDI/Linux releases).</p> + </body> + </project> + + <project cat='proj'> + <title>V4L Support in Linux Emulator</title> + + <contact> + <person> + <name> + <given>J.R.</given> + <common>Oldroyd</common> + </name> + <email>fbsd@opal.com</email> + </person> + </contact> + + <links> + <url href="http://opal.com/freebsd/sys/compat/linux/" /> + </links> + + <body> + <p>The V4L support in the Linux emulator has been merged to + 8-STABLE allowing use of video in Skype calls using a camera + supported by the pwcbsd or video4bsd drivers. A known issue for + Skype is that your camera must support YUV420 mode which is what + Skype uses. Note that V4L2 support is not included in the current + work, and remains as a project for anyone interested.</p> + </body> + </project> + + <project cat='net'> + <title>Syncing pf(4) with OpenBSD 4.5</title> + + <contact> + <person> + <name> + <given>Ermal</given> + <common>Luçi</common> + </name> + <email>eri@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/"> + Viewing the changes.</url> + + <url href="http://svn.FreeBSD.org/base/user/eri/pf45/head/">The + actual repo to build from.</url> + + <url href="http://lists.FreeBSD.org/pipermail/freebsd-pf/2010-October/005842.html"> + Public announcement.</url> + </links> + + <body> + <p>This work is based on OpenBSD 4.5 state of pf(4). It includes + many improvements over the code currently present in &os;. The + actual new feature present in pf45 repository is support for + divert(4), which should allow tools like snort_inline to work + with pf(4) too. This work also enables pfsync(4) to be loaded as + a module as well.</p> + + <p>Currently, this work is considered stable and a patch against + -CURRENT has been released on freebsd-pf mailing list.</p> + + <p>The reason why this work is based off of OpenBSD 4.5 is that + after this release they have changed the syntax which is not + backwards compatible.</p> + + <p>After importing this one the work will go on the newest + version and decisions on it will then be done.</p> + </body> + + <help> + <task>Make a decision whether we need pflow(4) in base.</task> + + <task>More regression testing is needed.</task> + </help> + </project> + + <project cat='ports'> + <title>OpenAFS Port</title> + + <contact> + <person> + <name> + <given>Benjamin</given> + <common>Kaduk</common> + </name> + <email>kaduk@mit.edu</email> + </person> + + <person> + <name> + <given>Derrick</given> + <common>Brashear</common> + </name> + <email>shadow@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://openafs.org">OpenAFS home page</url> + + <url href="http://web.mit.edu/freebsd/openafs/openafs.shar"> + &os; port for the OpenAFS 1.5.77 release</url> + </links> + + <body> + <p>AFS is a distributed network file system that originated from + the Andrew Project at Carnegie-Mellon University; the OpenAFS + client implementation has not been particularly useful on &os; + since the &os; 4.X releases. The previous status report + brought the OpenAFS client to a useful form on -CURRENT, + though with many rough edges. Only a couple of those edges have + been smoothed out during the past few months, as developer time + was scarce. A mismatch between file size and vmobject size + tracking was resolved (allowing executables to be run from AFS), + and our system call entry has been updated on -CURRENT and 8-STABLE + to match reality. Thanks to Kostik Belusov for both of those! + The code is useful enough that we plan to submit an + openafs-devel port to the Ports Collection in the coming + cycle.</p> + + <p>There are several known outstanding issues that are being + worked on, but detailed bug reports are welcome at + port-freebsd@openafs.org.</p> + </body> + + <help> + <task>Rework vnode locking for lookup operations to avoid an + easily-triggered deadlock between two threads when one is looking + up the parent directory.</task> + + <task>Update VFS locking to allow the use of disk-based client + caches as well as memory-based caches.</task> + + <task>Track down races and deadlocks that appear under + load.</task> + + <task>Integrate with the bsd.kmod.mk kernel-module build + infrastructure.</task> + </help> + </project> + + <project cat='proj'> + <title>gptboot Improvements</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + <common>Dawidek</common> + </name> + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://lists.FreeBSD.org/pipermail/svn-src-head/2010-September/020957.html" /> + </links> + + <body> + <p>The gptboot now fully follows GPT specification (verifies + checksums and falls back to backup header and table if primary is + corrupted).</p> + + <p>One can now use new attributes to configure partition that + gptboot will try to boot only once from and in case of a failure + it will fall back to the previous one.</p> + + <p>For more information check out the commit message.</p> + </body> + </project> + + <project cat='proj'> + <title>HAST (Highly Available Storage) Improvements</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + <common>Dawidek</common> + </name> + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>HAST is now better than ever! Some recent improvements + include:</p> + + <ul> + <li>Hooks supports — HAST will execute the given command + on various events (connect, disconnect, synchronization start, + synchronization completed, synchronization interrupted, + split-brain condition, role change).</li> + + <li>Configuration reload on SIGHUP, a very missing + functionality.</li> + + <li>Internal keepalive mechanism.</li> + + <li>Many bug fixes, majority of them reported by Mikolaj + Golub.</li> + </ul> + </body> + </project> + + <project cat='proj'> + <title>ZFSv28 is Ready for Wider Testing</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + <common>Dawidek</common> + </name> + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://lists.FreeBSD.org/pipermail/freebsd-fs/2010-August/009197.html" /> + </links> + + <body> + <p>ZFS v28 which includes data deduplication and plenty of other + shiny new features is ready for testing. For more information + check out the announcement.</p> + </body> + </project> + + <project cat='proj'> + <title>GELI Additions</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + <common>Dawidek</common> + </name> + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>There are three new GELI (a disk encryption GEOM class) + features available in -CURRENT:</p> + + <ul> + <li>AES-XTS encryption. XTS mode is a standard that is + recommended these days for storage encryption. This is the + default now. AES-XTS support was also added to opencrypto + framework and aesni(4) driver.</li> + + <li>Multiple encryption keys. GELI will use one encryption key + for at most 2^20 blocks (sectors), as it is not recommended to + use the same encryption key for too much data. It generates a key + array from the master key on attach and uses it accordingly. This + is the default now.</li> + + <li>Passphrase can now also be loaded from a file (-J and -j + options).</li> + </ul> + </body> + </project> + + <project cat='ports'> + <title>Valgrind Port</title> + + <contact> + <person> + <name> + <given>Stanislav</given> + <common>Sedov</common> + </name> + <email>stas@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ed</given> + <common>Maste</common> + </name> + <email>emaste@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.freebsd.org/Valgrind">Wiki page</url> + + <url href="http://bitbucket.org/stass/valgrind-freebsd/overview"> + bibtbucket repository</url> + + <url href="https://bugs.kde.org/show_bug.cgi?id=208531">Bug + tracker</url> + </links> + + <body> + <p>Valgrind is a tool for detecting memory management and + threading bugs, and profiling. Version 3.6.0 has recently been + released and the &os; port has now been updated.</p> + + <p>Development of the Valgrind port has moved from Perforce to + bitbucket.org, in order to make it easier for others to track + changes as we progress towards getting the port into shape to + commit upstream. The repository's Bitbucket address is at the + beginning of the report.</p> + + <p>A bugzilla entry has been submitted to track the &os; Valgrind + port. You can see the status and vote for the bug to express your + interest at <a + href="https://bugs.kde.org/show_bug.cgi?id=208531"> + https://bugs.kde.org/show_bug.cgi?id=208531</a>.</p> + </body> + + <help> + <task>Port exp-ptrcheck valgrind tool and fix outstanding issues + that show up in memcheck/helgrind/DRD in the Valgrind regression + tests suite.</task> + + <task>More testing (please, help).</task> + + <task>Integrate our patches upstream.</task> + </help> + </project> + + <project cat='proj'> + <title>Capsicum: Practical Capabilities for UNIX</title> + + <contact> + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Jonathan</given> + <common>Anderson</common> + </name> + <email>anderson@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ben</given> + <common>Laurie</common> + </name> + <email>benl@google.com</email> + </person> + + <person> + <name> + <given>Kris</given> + <common> Kennaway </common> + </name> + <email>kennaway@google.com</email> + </person> + </contact> + + <links> + <url href="http://www.cl.cam.ac.uk/research/security/capsicum/"> + Capsicum: practical capabilities for UNIX</url> + + <url href="https://lists.cam.ac.uk/mailman/listinfo/cl-capsicum-discuss"> + Capsicum project mailing list</url> + + <url href="http://www.cl.cam.ac.uk/research/security/capsicum/papers/2010usenix-security-capsicum-website.pdf"> + USENIX Security 2010 paper on Capsicum</url> + </links> + + <body> + <p>Capsicum is a lightweight OS capability and sandbox framework + developed at the University of Cambridge Computer Laboratory, + supported by a grant from Google. Capsicum extends the POSIX API, + providing several new OS primitives to support object-capability + security on UNIX-like operating systems: capabilities, a new + sandboxed capability mode for processes, anonymous shared memory + objects, process descriptors, and a modified C runtime able to + support distributed applications within sandboxes. Capsicum + has been prototyped on &os; -CURRENT, with a 8-STABLE + backport.</p> + + <p>Capsicum is intended to supplement existing system-centric + mandatory access control protections by providing an + application-centric protection model, which better supports + compartmentalised user programs that set up one (or many) + sandboxes to process untrustworthy data in. A number of + applications, from tcpdump to the Chromium web browser, have been + modified to use sandboxing to confine risky activities such as + the parsing of untrusted packets and HTML/JavaScript + rendering.</p> + + <p>We plan to begin merging the core Capsicum kernel features + to &os; -CURRENT in November/December 2010 once a number of + known problems have been resolved. Following a KBI analysis, we + will consider merging our 8-STABLE backport to Subversion. For + the time being, and while APIs stabilise, we plan to distribute + the Capsicum libraries via ports. However, simply having the + kernel features in place is sufficient to support sandboxing in + tcpdump and Chromium.</p> + + <p>The Capsicum paper by Robert Watson / Jonathan Anderson + (Cambridge) and Ben Laurie / Kris Kennaway (Google) won a best + paper award at the 2010 USENIX Security Symposium!</p> + </body> + + <help> + <task>More aggressively test (and as needed, fix) possible UNIX + domain socket garbage collector interactions with Capsicum.</task> + + <task>Using results of our recent model checking analysis of the + namei() sandboxing approach, make robustness improvements.</task> + + <task>Merge to &os; -CURRENT in November/December.</task> + + <task>KBI analysis for possible 8-STABLE merge.</task> + + <task>Convert more applications to use Capsicum sandboxing!</task> + </help> + </project> + + <project cat='team'> + <title>&os; Bugbusting Team</title> + + <contact> + <person> + <name> + <given>Gavin</given> + <common>Atkinson</common> + </name> + <email>gavin@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Mark</given> + <common>Linimon</common> + </name> + <email>linimon@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Remko</given> + <common>Lodder</common> + </name> + <email>remko@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Volker</given> + <common>Werth</common> + </name> + <email>vwe@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/support.html#gnats" /> + <url href="http://wiki.FreeBSD.org/BugBusting" /> + <url href="http://people.FreeBSD.org/~linimon/studies/prs/" /> + </links> + + <body> + <p>The bugbusting team continue work on trying to make the contents + of the GNATS PR database cleaner, more accessible and easier for + committers to find and resolve PRs, by tagging PRs to indicate the + areas involved, and by ensuring that there is sufficient info + within each PR to resolve each issue.</p> + + <p>July saw the addition of Alexander Best (arundel@) to this + bugbusting team, he is helping with the triaging PRs as they come + in, creating patches for problems and working with submitters to + get the solutions tested, and working through the PR backlog.</p> + + <p>Also in July, Gavin Atkinson worked with Hans Petter Selasky on + the USB PRs, attempting to go through many of them and determine + the status of each of them. As a result, nearly 10% of the USB + PRs were determined to be closeable, with many more either being + marked as patched already or able to be committed quickly. + Several PRs that only affect the old (pre-8.0) USB stack were + also identified and marked as such. More work will take place + in this area in the future.</p> + + <p>August saw us host another bugathon, with an aim of + investigating and getting into a committable state several of the + PRs with patches. Turnout was not as great as in the past + — mainly believed to be due to the short notice, but still + several PRs were progressed, with several commits made and + several PRs closed.</p> + + <p>The number of PRs has held steady over the last three months, + with improvements in numbers in some categories (especially usb + and bin) being offset by slight increases in others.</p> + + <p>Reports continue to be produced from the PR database, all of + which can be found from the links above. Committers interested + in custom reports are encouraged to discuss requirements with + bugmeister@ — we are happy to create new reports where + needs are identified.</p> + + <p>As always, anybody interested in helping out with the PR queue is + welcome to join us in #freebsd-bugbusters on EFnet. We are + always looking for additional help, whether your interests lie in + triaging incoming PRs, generating patches to resolve existing + problems, or simply helping with the database housekeeping + (identifying duplicate PRs, ones that have already been resolved, + etc). This is a great way of getting more involved with + &os;!</p> + </body> + + <help> + <task>Try to find ways to get more committers helping us with + closing PRs that the team has already analyzed.</task> + + <task>Try to get more non-committers involved with the triaging + of PRs as they come in, and generating patches to fix reported + problems.</task> + </help> + </project> + + <project cat='team'> + <title>&os; Release Engineering Team</title> + + <contact> + <person> + <name> + <given>Release Engineering Team</given> + </name> + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/" /> + </links> + + <body> + <p>The Release Engineering Team has announced the schedule for the + upcoming joint release of &os; 7.4 and 8.2. The schedules + are available on the web site:</p> + + <ul> + <li><a href="http://www.freebsd.org/releases/7.4R/schedule.html"> + 7.4-RELEASE schedule</a></li> + <li><a href="http://www.freebsd.org/releases/8.2R/schedule.html"> + 8.2-RELEASE schedule</a></li> + </ul> + + <p>It is expected that 7.4 will be the last of the 7.X releases.</p> + </body> + </project> + + <project cat="docs"> + <title>The &os; Japanese Documentation Project</title> + + <contact> + <person> + <name> + <given>Hiroki</given> + <common>Sato</common> + </name> + <email>hrs@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ryusuke</given> + <common>Suzuki</common> + </name> + <email>ryusuke@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ja/">Japanese &os; Web Pages</url> + + <url href="http://www.jp.FreeBSD.org/doc-jp/">The + &os; Japanese Documentation Project Web Page</url> + </links> + + <body> + <p>The www/ja and doc/ja_JP.eucJP/ have been updated constantly + since the last status report. We committed a big patch for + the "Installing &os;" chapter of the &os; Handbook which was + contributed by many people since a long time. This chapter is + still outdated and needs more work. Some progress was made in + the Porter's Handbook as well.</p> + </body> + + <help> + <task>Further translation of the &os; Handbook and contents of + the <a href="http://www.FreeBSD.org">www.FreeBSD.org</a> site to + the Japanese language.</task> + + <task>Pre-/post-commit review of the translation.</task> + </help> + </project> + + <project cat='misc'> + <title>EuroBSDCon 2010</title> + + <contact> + <person> + <name> + <given>Wolfgang</given> + <common>Zenker</common> + </name> + <email>eurobsdcon2010@egeling.de</email> + </person> + + <person> + <name> + <given>Gábor</given> + <common>Páli</common> + </name> + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://2010.EuroBSDCon.org/" /> + <url href="http://2011.EuroBSDCon.org/" /> + </links> + + <body> + <p>EuroBSDCon 2010 happened in Karlsruhe, Germany, with many + users, developers, friends, and others. We had many tutorials, + and 22 interesting presentations on various topics connected to + &os;, OpenBSD, NetBSD, like the new USB stack, jail + improvements, Virtual Private Systems, SSH and PGP convergence, + ZFS, journaled Soft-Updates, BSD certification, porting to the + latest ARM processors, and pc-sysinstall. The event was opened by + a keynote speech from Poul-Henning Kamp on software tools and + their future, and it was closed by short status reports on + different BSD flavors.</p> + </body> + </project> + + <project cat='misc'> + <title>EuroBSDCon 2011</title> + + <contact> + <person> + <name> + <given>Philip</given> + <common>Paeps</common> + </name> + <email>philip@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://2011.eurobsdcon.org/">EuroBSDCon 2011 Placeholder</url> + <url href="http://2011.eurobsdcon.org/CfP.html">Call for Proposals</url> + </links> + + <body> + <p>EuroBSDCon is the European technical conference for users and + developers on BSD based systems. The EuroBSDCon 2011 conference + will be held in the Netherlands from Thursday 6 October 2011 + to Sunday 9 October 2011, with tutorials on Thursday and Friday + and talks on Saturday and Sunday.</p> + + <p>The EuroBSDCon conference is inviting developers and users of + BSD based systems to submit innovative and original papers not + submitted to other European conferences on BSD-related topics.</p> + + <p>Please see the EuroBSDCon 2011 website for more details.</p> + </body> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2010-10-2010-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2010-10-2010-12.xml new file mode 100644 index 0000000000..48d6722e2c --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2010-10-2010-12.xml @@ -0,0 +1,1974 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for +Status Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2010-10-2010-12.xml,v 1.4 2011/01/23 18:55:11 danger Exp $ --> +<report> + <date> + <month>October-December</month> + + <year>2010</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report covers &os;-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 &os;, 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> + </section> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>team</name> + + <description>&os; Team Reports</description> + </category> + + <category> + <name>net</name> + + <description>Network Infrastructure</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <category> + <name>bin</name> + + <description>Userland Programs</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <category> + <name>misc</name> + + <description>Miscellaneous</description> + </category> + + <project cat='net'> + <title>Ethernet Switch Framework</title> + + <contact> + <person> + <name> + <given>Luiz</given> + <common>Otavio O. Souza</common> + </name> + <email>loos.br@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://loos.no-ip.org/rspro/switch-1.diff" /> + </links> + + <body> + <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> + </body> + + <help> + <task>Finish the IP175C driver (and maybe IP178x).</task> + + <task>Better integration with miibus (rewrite of switchbus).</task> + + <task>Fix (some) ifconfig keywords (better keywords, better usage + compatibility).</task> + + <task>Export the ports statistics through SNMP (if available on + switch chip).</task> + + <task>Add a swctl tool (?) for global settings management.</task> + + <task>Write usage examples and the man page information about the + new ifconfig(8) keywords.</task> + </help> + </project> + + <project cat='ports'> + <title>Robot Operating System</title> + + <contact> + <person> + <name> + <given>René</given> + <common>Ladan</common> + </name> + <email>rene@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.ros.org/wiki/">ROS website</url> + + <url href="ftp://rene-ladan.nl/pub/ros-freebsd.pdf"> + Presentation</url> + </links> + + <body> + <p>Porting ROS to &os; 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 &os;.</p> + </body> + + <help> + <task>Port the software required for nxt-rviz-plugin, which is part + of devel/ros-nxt but currently excluded from the build.</task> + </help> + </project> + + <project cat='net'> + <title>&os; 802.11n</title> + + <contact> + <person> + <name> + <given>Adrian</given> + <common>Chadd</common> + </name> + <email>adrian@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/AdrianChadd/AtherosStuff" /> + </links> + + <body> + <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> + </body> + </project> + + <project cat='docs'> + <title>mdocml Replacing groff For manpage Rendering</title> + + <contact> + <person> + <name> + <given>Ulrich</given> + <common>Spörlein</common> + </name> + <email>uqs@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://mdocml.bsd.lv/" /> + + <url href="https://www.spoerlein.net/cgit/cgit.cgi/freebsd.work/log/?h=mdocml" /> + </links> + + <body> + <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 &os;. 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> + </body> + + <help> + <task>Get ru@ to review WITHOUT_GROFF changes.</task> + + <task>Get textproc/groff tested and committed.</task> + + <task>Push more mdoc fixes into the tree.</task> + + <task>Import mandoc(1), switch to catpages for base. Discuss future + of groff in base wrt. share/doc.</task> + + <task>Supply necessary ports infrastructure to opt-in to + mandoc(1).</task> + </help> + </project> + + <project cat='ports'> + <title>Port-Sandbox</title> + + <contact> + <person> + <name> + <given>Marcelo</given> + <common>Araujo</common> + </name> + <email>araujo@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.arjmobile.com/Marcelo_Araujo/Blog/Entries/2010/11/22_Port-sandbox.html"> + A little bit about</url> + + <url href="http://gitorious.org/port-sandbox/port-sandbox/trees/master"> + Source</url> + + <url href="http://www.arjmobile.com/Marcelo_Araujo/My_Albums/Pages/Port-Sandbox.html"> + Screenshots</url> + </links> + + <body> + <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> + </body> + + <help> + <task>Change the way how it connects to database, fix it to maintain + a persistent connection.</task> + + <task>Remove any kind of internal configuration from source code to + an external file configuration.</task> + + <task>Create a Port-Sandbox port with all dependencies related to + it and test it in a clean system.</task> + + <task>Create some documentation to let other people to keep + helping Port-Sandbox to grow up.</task> + + <task>Finally, release it.</task> + </help> + </project> + + <project cat='ports'> + <title>Chromium</title> + + <contact> + <person> + <name> + <given>René</given> + <common>Ladan</common> + </name> + <email>freebsd-chromium@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.chromium.org/Home">Chromium homepage</url> + + <url href="http://people.FreeBSD.org/~bapt/chrome9-fbsd.png"> + Screenshot</url> + </links> + + <body> + <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> + </body> + </project> + + <project cat="docs"> + <title>The &os; Japanese Documentation Project</title> + + <contact> + <person> + <name> + <given>Hiroki</given> + <common>Sato</common> + </name> + <email>hrs@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ryusuke</given> + <common>Suzuki</common> + </name> + <email>ryusuke@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ja/">Japanese &os; Web + Pages</url> + + <url href="http://www.jp.FreeBSD.org/doc-jp/">The &os; Japanese + Documentation Project Web Page</url> + </links> + + <body> + <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 + &os; as well.</p> + </body> + + <help> + <task>Further translation of the &os; <a + href="http://www.FreeBSD.org/doc/ja_JP.eucJP/books/handbook/"> + Handbook</a> and contents of the + <a href="http://www.FreeBSD.org">www.FreeBSD.org</a> + website to the Japanese language.</task> + + <task>Pre-/post-commit review of the translation.</task> + </help> + </project> + + <project cat='docs'> + <title>The &os; German Documentation Project Status Report</title> + + <contact> + <person> + <name> + <given>Johann</given> + <common>Kois</common> + </name> + <email>jkois@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Benedict</given> + <common>Reuschling</common> + </name> + <email>bcr@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://doc.bsdgroup.de">Website of the &os; German + Documentation Project.</url> + </links> + + <body> + <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 &os; 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> + </body> + + <help> + <task>Submit grammar, spelling or other errors you find in the + german documents and the website.</task> + + <task>Translate more articles and other open handbook + sections.</task> + </help> + </project> + + <project cat='net'> + <title>Generic IEEE 802.3 annex 31B full duplex flow control support + for Ethernet in mii(4)</title> + + <contact> + <person> + <name> + <given>Marius</given> + <common>Strobl</common> + </name> + <email>marius@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://en.wikipedia.org/wiki/Ethernet_flow_control" /> + </links> + + <body> + <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 /> + + bge0: CHIP ID 0x00002003; ASIC REV 0x02; CHIP REV 0x20; PCI-X + <br /> + + miibus0: <MII bus> on bge0 + <br /> + + brgphy0: <BCM5704 10/100/1000baseTX PHY> PHY 1 on miibus0 + <br /> + + 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> + </body> + + <help> + <task>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.</task> + </help> + </project> + + <project cat='arch'> + <title>&os;/sparc64</title> + + <contact> + <person> + <name> + <given>Marius</given> + <common>Strobl</common> + </name> + <email>marius@FreeBSD.org</email> + </person> + </contact> + + <body> + <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 &os;/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> + </body> + </project> + + <project cat='proj'> + <title>Webcamd</title> + + <contact> + <person> + <name> + <given>Hans Petter</given> + <common>Selasky</common> + </name> + <email>hselasky@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.selasky.org/hans_petter/video4bsd" /> + + <url href="http://www.freshports.org/multimedia/webcamd/" /> + </links> + + <body> + <p>Webcamd is a small daemon that enables about 1500 different USB + based webcam, DVB and remote control USB devices under the + &os;-8.0 and later operating system. The webcam daemon is + basically an application which is a port of Video4Linux USB drivers + into userspace on &os;. The daemon currently depends on libc, + pthreads, libusb and libcuse4bsd.</p> + + <p>During Q3 2010 webcamd got manpages thanks to Dru Lavigne.</p> + </body> + + <help> + <task>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 &os;. Webcamd is not a + replacement for native &os; kernel drivers and will only be used + when no existing &os; 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.</task> + </help> + </project> + + <project cat='ports'> + <title>Ports Additions</title> + + <contact> + <person> + <name> + <given>Josh</given> + <common>Paetzel</common> + </name> + <email>jpaetzel@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://bigbluebutton.org" /> + + <url href="http://smb4k.berlios.de/" /> + + <url href="http://www.freeswitch.org/" /> + </links> + + <body> + <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 &os; + source code submitted by PC-BSD's Kris Moore. This application + greatly eases the task of working with samba shares in a &os; + 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> + </body> + </project> + + <project cat='kern'> + <title>TRIM support for UFS</title> + + <contact> + <person> + <name> + <given>Kirk</given> + <common>McKusick</common> + </name> + <email>mckusick@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Konstantin</given> + <common>Belousov</common> + </name> + <email>kib@FreeBSD.org</email> + </person> + </contact> + + <body> + <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> + </body> + </project> + + <project cat='proj'> + <title>Non-executable Stacks</title> + + <contact> + <person> + <name> + <given>Konstantin</given> + <common>Belousov</common> + </name> + <email>kib@FreeBSD.org</email> + </person> + </contact> + + <body> + <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> + </body> + </project> + + <project cat='kern'> + <title>SYSCTL Type Safety</title> + + <contact> + <person> + <name> + <given>Matthew</given> + <common>Fleming</common> + </name> + <email>mdf@FreeBSD.org</email> + </person> + </contact> + + <body> + <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> + </body> + + <help> + <task>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.</task> + </help> + </project> + + <project cat='proj'> + <title>BSDInstall</title> + + <contact> + <person> + <name> + <given>Nathan</given> + <common>Whitehorn</common> + </name> + <email>nwhitehorn@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/BSDInstall">BSDInstall Wiki + Page</url> + </links> + + <body> + <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> + </body> + + <help> + <task>Wireless networking configuration wizard.</task> + + <task>ZFS installation support.</task> + + <task>Itanium disk setup.</task> + </help> + </project> + + <project cat='arch'> + <title>&os; on the Playstation 3</title> + + <contact> + <person> + <name> + <given>Nathan</given> + <common>Whitehorn</common> + </name> + <email>nwhitehorn@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>On January 5, support for the Playstation 3 was imported into + &os; 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 &os; 9.0 is + released. The port uses the OtherOS mechanism, and so requires a + "fat" console with firmware earlier than 3.21.</p> + </body> + + <help> + <task>SATA driver.</task> + + <task>Sound support.</task> + + <task>SPU driver.</task> + </help> + </project> + + <project cat='bin'> + <title>GEOM-based ataraid(4) Replacement — geom_raid</title> + + <contact> + <person> + <name> + <given>Alexander</given> + <common>Motin</common> + </name> + <email>mav@FreeBSD.org</email> + </person> + + <person> + <name> + <given>M. Warner</given> + <common>Losh</common> + </name> + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~mav/graid_design.h">General + design description.</url> + + <url href="http://svn.FreeBSD.org/viewvc/base/projects/graid/"> + Project SVN branch.</url> + </links> + + <body> + <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> + </body> + + <help> + <task>Complete error recovery/rebuild work and stabilize modules + API.</task> + + <task>Implement metadata modules for other formats.</task> + + <task>Implement transformation modules for other RAID + levels.</task> + </help> + </project> + + <project cat='arch'> + <title>&os;/EC2</title> + + <contact> + <person> + <name> + <given>Colin</given> + <common>Percival</common> + </name> + <email>cperciva@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.daemonology.net/freebsd-on-ec2/">&os;/EC2 + status page</url> + </links> + + <body> + <p>&os; is now able to run on t1.micro instances in the Amazon + EC2 cloud. &os; 9.0 is not very stable, but it seems likely that + &os; 8.2-RELEASE will approach the stability normally expected + of &os;.</p> + + <p>A list of available &os; AMIs (EC2 machine images) appears on + the &os;/EC2 status page.</p> + </body> + + <help> + <task>Bring &os; to a wider range of EC2 instance types.</task> + + <task>Completely rework the locking in head/sys/i386/xen/pmap.c to + eliminate races and make 9.0-CURRENT stable under + paravirtualization.</task> + + <task>Track down several possibly-related problems with scheduling + and timekeeping.</task> + + <task>Fix other issues shown on the &os;/EC2 status page.</task> + </help> + </project> + + <project cat='ports'> + <title>Portmaster</title> + + <contact> + <person> + <name> + <given>Doug</given> + <common>Barton</common> + </name> + <email>dougb@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://dougbarton.us/portmaster-proposal.html" /> + </links> + + <body> + <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> + </body> + + <help> + <task>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.</task> + </help> + </project> + + <project cat='net'> + <title>IPv6 and VIMAGE</title> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + <common>Zeeb</common> + </name> + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://ecdysis.viagenie.ca/">NAT64 patches for pf</url> + </links> + + <body> + <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> + </body> + </project> + + <project cat='ports'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Thomas</given> + <common>Abthorpe</common> + </name> + <email>portmgr-secretary@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Port</given> + <common>Management Team</common> + </name> + <email>portmgr@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ports/" /> + + <url href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" /> + + <url href="http://portsmon.FreeBSD.org/index.html" /> + + <url href="http://www.FreeBSD.org/portmgr/index.html" /> + + <url href="http://blogs.FreeBSDish.org/portmgr/" /> + + <url href="http://www.twitter.com/freebsd_portmgr/" /> + + <url href="http://www.facebook.com/group.php?gid=135441496471197" /> + + <url href="http://tinderbox.marcuscom.com/" /> + </links> + + <body> + <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 &os; 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 &os; 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> + </body> + + <help> + <task>Looking for help fixing <url + link="http://wiki.FreeBSD.org/PortsBrokenOnCurrent">ports + broken on CURRENT</url>.</task> + + <task>Looking for help with <url + link="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures"> + Tier-2 architectures</url>.</task> + + <task>Most ports PRs are assigned, we now need to focus on testing, + committing and closing.</task> + </help> + </project> + + <project cat='arch'> + <title>Bringing up OMAP3</title> + + <contact> + <person> + <name> + <given>Warner</given> + <common>Losh</common> + </name> + <email>imp@bsdimp.com</email> + </person> + + <person> + <name> + <given>Mohammed</given> + <common>Farrag</common> + </name> + <email>mfarrag@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~raj/patches/arm/dove_v6.diff">an + old patch for arm</url> + </links> + + <body> + <p>The attached file is an old patch for ARM. We are developing new + patch and then we are going toward Porting OMAP3.</p> + </body> + </project> + + <project cat='team'> + <title>Release Engineering Team Status Report</title> + + <contact> + <person> + <name> + <given>Release Engineering Team</given> + </name> + + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/" /> + </links> + + <body> + <p>The Release Engineering Team reports the joint release of + &os; 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> + </body> + </project> + + <project cat='kern'> + <title>Resource Containers</title> + + <contact> + <person> + <name> + <given>Edward Tomasz</given> + <common>Napierala</common> + </name> + <email>trasz@FreeBSD.org</email> + </person> + </contact> + + <body> + <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> + </body> + </project> + + <project cat="ports"> + <title>&os; as Home Theater PC</title> + + <contact> + <person> + <name> + <given>Bernhard</given> + <common>Froehlich</common> + </name> + <email>decke@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Juergen</given> + <common>Lock</common> + </name> + <email>nox@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/HTPC" /> + </links> + + <body> + <p>&os; 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> + </body> + + <help> + <task>Improve remote control support in webcamd and with + lirc.</task> + + <task>Port more Media Center applications (Enna, me-tv, ...).</task> + + <task>Create a small guide on how to build a great &os; Home + Theater PC.</task> + </help> + </project> + + <project cat='team'> + <title>The &os; Foundation Status Report</title> + + <contact> + <person> + <name> + <given>Deb</given> + <common>Goodkin</common> + </name> + <email>deb@FreeBSDFoundation.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSDFoundation.org" /> + </links> + + <body> + <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 &os; 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"> + 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/"> + http://www.FreeBSDFoundation.org/donate/</a>.</p> + </body> + </project> + + <project cat='net'> + <title>Five New TCP Congestion Control Algorithms for &os;</title> + + <contact> + <person> + <name> + <given>David</given> + <common>Hayes</common> + </name> + <email>dahayes@swin.edu.au</email> + </person> + + <person> + <name> + <given>Lawrence</given> + <common>Stewart</common> + </name> + <email>lastewart@swin.edu.au</email> + </person> + + <person> + <name> + <given>Grenville</given> + <common>Armitage</common> + </name> + <email>garmitage@swin.edu.au</email> + </person> + + <person> + <name> + <given>Rui</given> + <common>Paulo</common> + </name> + <email>rpaulo@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Bjoern</given> + <common>Zeeb</common> + </name> + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://caia.swin.edu.au/freebsd/5cc/" /> + + <url href="http://caia.swin.edu.au/urp/newtcp/" /> + + <url href="http://www.FreeBSDFoundation.org/projects.shtml" /> + + <url href="http://people.FreeBSD.org/~lstewart/patches/5cc/" /> + </links> + + <body> + <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> + </body> + + <help> + <task>Import the ERTT Khelp module.</task> + + <task>Import the VEGAS, HD and CHD delay based congestion control + algorithm modules.</task> + + <task>Import the documentation dump for all the code + contributed/developed as part of the project.</task> + </help> + </project> + + <project cat='net'> + <title>DIstributed Firewall and Flow-shaper Using Statistical + Evidence (DIFFUSE)</title> + + <contact> + <person> + <name> + <given>Sebastian</given> + <common>Zander</common> + </name> + <email>szander@swin.edu.au</email> + </person> + + <person> + <name> + <given>Grenville</given> + <common>Armitage</common> + </name> + <email>garmitage@swin.edu.au</email> + </person> + </contact> + + <links> + <url href="http://caia.swin.edu.au/urp/diffuse/" /> + + <url href="http://caia.swin.edu.au/urp/diffuse/downloads.html" /> + </links> + + <body> + <p> + <p>DIFFUSE is a system enabling &os;'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 &os;-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> + </body> + </project> + + <project cat='bin'> + <title>gpart Improvements</title> + + <contact> + <person> + <name> + <given>Andrey V.</given> + <common>Elsukov</common> + </name> + <email>ae@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>GEOM class PART is the default disk partitioning class since + &os; 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> + </body> + </project> + + <project cat='proj'> + <title>xz Compression for Packages and Log Files</title> + + <contact> + <person> + <name> + <given>Martin</given> + <common>Matuska</common> + </name> + <email>mm@FreeBSD.org</email> + </person> + </contact> + + <body> + <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> + </body> + + <help> + <task>Import xz(1) compression support into newsyslog(8).</task> + + <task>Add .txz package support to ports-mgmt/portmaster.</task> + + <task>Add .txz package support to the &os; port building + cluster (pointyhat).</task> + + <task>Test building all packages in .txz format and compare + results with .tbz.</task> + </help> + </project> + + <project cat='proj'> + <title>ZFS pool version 28</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + <common>Dawidek</common> + </name> + <email>pjd@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Martin</given> + <common>Matuska</common> + </name> + <email>mm@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010292.html" /> + <url href="http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010321.html" /> + </links> + + <body> + <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 &os;-CURRENT after 8.2 is released.</p> + </body> + + <help> + <task>Import of ZFS v28 into &os;-CURRENT.</task> + </help> + </project> + + <project cat='net'> + <title>&os; VirtIO Network Driver</title> + + <contact> + <person> + <name> + <given>Bryan</given> + <common>V.</common> + </name> + <email>deboomerang@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://www.linux-kvm.org/page/Virtio" /> + <url href="http://lists.FreeBSD.org/pipermail/freebsd-current/2011-January/022036.html" /> + </links> + + <body> + <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> + </body> + </project> + + <project cat='net'> + <title>TCP SMP scalability project</title> + + <contact> + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>A long-running TCP SMP scalability project is beginning to wrap + up, with the goal of committing a large outstanding patch to the + &os; 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> + </body> + + <help> + <task>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().</task> + + <task>Add missing socket options to query (and override) default + CPU affinity for connections, which is derived from the active + software or hardware hash model.</task> + + <task>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.</task> + + <task>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.</task> + + <task>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.</task> + + <task>Commit.</task> + </help> + </project> + + <project cat='team'> + <title>&os; Bugbusting Team Status Report</title> + + <contact> + <person> + <name> + <given>Gavin</given> + <common>Atkinson</common> + </name> + <email>gavin@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Mark</given> + <common>Linimon</common> + </name> + <email>linimon@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Remko</given> + <common>Lodder</common> + </name> + <email>remko@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Volker</given> + <common>Werth</common> + </name> + <email>vwe@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/support.html#gnats" /> + <url href="http://wiki.FreeBSD.org/BugBusting" /> + <url href="http://people.FreeBSD.org/~linimon/studies/prs/" /> + </links> + + <body> + <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 &os; 7.4 and + &os; 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 &os; 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 &os;!</p> + </body> + + <help> + <task>Try to find ways to get more committers helping us with + closing PRs that the team has already analyzed.</task> + + <task>Try to get more non-committers involved with the triaging + of PRs as they come in, and generating patches to fix reported + problems.</task> + </help> + </project> + + <project cat='bin'> + <title>&os; Services Control (fsc)</title> + + <contact> + <person> + <name> + <given>Tom</given> + <common>Rhodes</common> + </name> + <email>trhodes@FreeBSD.org</email> + </person> + </contact> + + <links>http://people.FreeBSD.org/~trhodes/fsc/</links> + + <body> + <p>&os; 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> + </body> + </project> + + <project cat='misc'> + <title>FOSDEM 2011</title> + + <contact> + <person> + <name> + <given>Marius</given> + <common>Nuennerich</common> + </name> + <email>marius@nuenneri.ch</email> + </person> + + <person> + <name> + <given>Daniel</given> + <common>Seuffert</common> + </name> + <email>ds@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FOSDEM.org" /> + </links> + + <body> + <p>FOSDEM 2011 will be held from Saturday, February 5th to + Sunday February 6th in Brussels, Belgium. We will have a &os; + booth and a developers room. At the booth there will be + friendly supporters and a &os; 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> + </body> + + <help> + <task>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.</task> + </help> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2011-01-2011-03.xml b/en_US.ISO8859-1/htdocs/news/status/report-2011-01-2011-03.xml new file mode 100644 index 0000000000..19769c6ec4 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2011-01-2011-03.xml @@ -0,0 +1,1813 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for +Status Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2011-01-2011-03.xml,v 1.4 2011/04/27 10:26:58 danger Exp $ --> +<report> + <date> + <month>January-March</month> + <year>2011</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report covers &os;-related projects between January and March + 2011. It is the first of the four reports planned for 2011. During + this quarter, the work was focused on releasing the new minor + versions of &os;, 7.4 and 8.2, which were released in February 2011. + Currently, the project is starting to work on the next major version, + 9.0.</p> + + <p>Thanks to all the reporters for the excellent work! This report + contains 34 entries and we hope you enjoy reading it.</p> + + <p>Please note that the deadline for submissions covering the period + between April and June 2011 is July 15th, 2011.</p> + </section> + + <category> + <name>proj</name> + <description>Projects</description> + </category> + + <category> + <name>team</name> + <description>&os; Team Reports</description> + </category> + + <category> + <name>net</name> + <description>Network Infrastructure</description> + </category> + + <category> + <name>kern</name> + <description>Kernel</description> + </category> + + <category> + <name>docs</name> + <description>Documentation</description> + </category> + + <category> + <name>arch</name> + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + <description>Ports</description> + </category> + + <category> + <name>misc</name> + <description>Miscellaneous</description> + </category> + + <category> + <name>gsoc</name> + <description>Google Summer of Code</description> + </category> + + <project cat='gsoc'> + <title>Google Summer of Code 2011</title> + <contact> + <person> + <name> + <given>Brooks</given> + <common>Davis</common> + </name> + <email>brooks@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.google-melange.com/gsoc/org/google/gsoc2011/freebsd" /> + <url href="http://wiki.freebsd.org/SummerOfCode2011">GSoC Wiki + Homepage</url> + </links> + + <body> + <p>&os; is proud to be participating in our seventh year of Google + Summer of Code. On Monday, April 25th we accepted 17 + proposals from an overall excellent field. A full list of <a + href="http://www.google-melange.com/gsoc/org/google/gsoc2011/freebsd">accepted + proposals</a> can be found on the <a + href="http://www.google-melange.com/gsoc/homepage/google/gsoc2011">GSoC + website</a>. We look forward to working with these students + over the summer.</p> + + <p>As we did last year we plan to ask students to submit weekly + status reports to the + <a href="http://lists.FreeBSD.org/mailman/listinfo/soc-status"> + soc-status</a> mailing list. Those wishing to keep up with + the work in progress and offer review may wish to + subscribe.</p> + </body> + </project> + + <project cat='team'> + <title>&os; Bugbusting Team</title> + + <contact> + <person> + <name> + <given>Gavin</given> + <common>Atkinson</common> + </name> + <email>gavin@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Mark</given> + <common>Linimon</common> + </name> + <email>linimon@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Remko</given> + <common>Lodder</common> + </name> + <email>remko@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Volker</given> + <common>Werth</common> + </name> + <email>vwe@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/support.html#gnats">&os; Support + page</url> + + <url href="http://wiki.FreeBSD.org/BugBusting">Resources and + documentation available for Bugbusting</url> + + <url href="http://people.FreeBSD.org/~linimon/studies/prs/">Links + to all of the auto-generated PR reports</url> + </links> + + <body> + <p>The bugmeister team is happy to welcome Eitan Adler (eadler@) as + the newest GNATS-only contributor. Eitan has been helping triage + new bugs as they come in, as well as making good progress on many + of the older bugs, closing duplicates and obsolete bugs and + contacting submitters for extra information where necessary. For + the first time in a long time we managed to get below 6000 open + PRs, in no small part due to Eitan's efforts. Welcome aboard!</p> + + <p>PRs continue to be classified as they arrive, by adding 'tags' + to the subject lines corresponding to the kernel subsystem + involved, or man page references for userland PRs. Reports are + generated from these nightly, grouping related PRs into one place, + sorted by tag or man page. This allows an interested party working + in one area or on one subsystem to easily find related bugs and + issues in the same area, which has proven quite effective in + getting some of the older bug reports closed. These reports can all + be found by following the third link above.</p> + + <p>We continue to look for ideas for other reports that may help + improve the PR closure rate. If you have any suggestions for + reports which would contribute positively to the way you work, + please email bugmeister@ and we shall try to produce such a + report.</p> + + <p>Our clearance rate of PRs, especially in kern and bin, seems to + be improving. The number of non-ports PRs has stayed almost + constant since the last status report.</p> + + <p>As always, anybody interested in helping out with the PR queue + is welcome to join us in #freebsd-bugbusters on EFnet. We are + always looking for additional help, whether your interests lie in + triaging incoming PRs, generating patches to resolve existing + problems, or simply helping with the database housekeeping + (identifying duplicate PRs, ones that have already been resolved, + etc). This is a great way of getting more involved with &os;!</p> + </body> + + <help> + <task>Try to find ways to get more committers helping us with + closing PRs that the team has already analyzed.</task> + </help> + </project> + + <project cat='net'> + <title>Five New TCP Congestion Control Algorithms for &os;</title> + + <contact> + <person> + <name> + <given>David</given> + <common>Hayes</common> + </name> + <email>dahayes@swin.edu.au</email> + </person> + + <person> + <name> + <given>Lawrence</given> + <common>Stewart</common> + </name> + <email>lastewart@swin.edu.au</email> + </person> + + <person> + <name> + <given>Grenville</given> + <common>Armitage</common> + </name> + <email>garmitage@swin.edu.au</email> + </person> + + <person> + <name> + <given>Rui</given> + <common>Paulo</common> + </name> + <email>rpaulo@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Bjoern</given> + <common>Zeeb</common> + </name> + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://caia.swin.edu.au/freebsd/5cc/" /> + <url href="http://caia.swin.edu.au/urp/newtcp/" /> + <url href="http://www.FreeBSDFoundation.org/projects.shtml" /> + <url href="http://FreeBSDfoundation.blogspot.com/2011/03/summary-of-five-new-tcp-congestion.html" /> + <url href="http://people.FreeBSD.org/~lstewart/patches/5cc/" /> + </links> + + <body> + <p>The project is now complete, with the following code available + in the svn head branch:</p> + + <ul> + <li>Modular congestion control framework.</li> + <li>Khelp (Kernel Helper) and Hhook (Helper Hook) + frameworks.</li> + <li>Basic Khelp/Hhook integration with the TCP stack.</li> + <li>Enhanced Round Trip Time (ERTT) Khelp module.</li> + <li>Modularised implementations of NewReno, CUBIC, H-TCP, Vegas, + Hamilton-Delay and CAIA-Hamilton-Delay congestion control + algorithms.</li> + </ul> + + <p>In addition to the code, a large set of documentation was + committed (see the following man pages: cc(4), cc_newreno(4), + cc_cubic(4), cc_htcp(4), cc_vegas(4), cc_hd(4), cc_chd(4), + h_ertt(4), cc(9), khelp(9), hhook(9)) and a <a + href="http://caia.swin.edu.au/reports/110228A/CAIA-TR-110228A.pdf"> + technical report</a> was released which evaluates the + computational overhead associated with TCP before and after + the project's changes.</p> + + <p>A candidate patch to MFC the modular congestion control + framework to the 8-STABLE branch is ready for testing <a + href="http://people.FreeBSD.org/~lstewart/patches/5cc/modularcc_mfc_8.x.r219091.patch"> + here</a>. If you try the patch, please send a note detailing + your experience (positive or negative) to Lawrence + Stewart.</p> + + <p>Thanks go to the &os; Foundation for funding this work, to the + project's technical reviewers for providing detailed feedback, and + to all &os; users who have provided testing feedback thus far.</p> + </body> + + <help> + <task>Test <a + href="http://people.FreeBSD.org/~lstewart/patches/5cc/modularcc_mfc_8.x.r219091.patch"> + 8-STABLE MFC candidate patch</a> and do the merge in time + for 8.3-RELEASE.</task> + </help> + </project> + + <project cat="team"> + <title>The &os; Foundation Status Report</title> + + <contact> + <person> + <name> + <given>Deb</given> + <common>Goodkin</common> + </name> + <email>deb@FreeBSDFoundation.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSDfoundation.org" /> + </links> + + <body> + <p>We created our <a + href="http://www.FreeBSDfoundation.org/documents/Budget2011.pdf"> + 2011 budget</a>. Some of our plans for 2011 include spending + $125,000 on project development and $75,000 on equipment to + build up &os; facilities in three locations.</p> + + <p>We were proud to be a sponsor for AsiaBSDCon 2011 in Tokyo. We + also committed to sponsoring BSDCan 2011 in May, and EuroBSDCon + 2011 in October. The Foundation was also represented at SCALE in + Los Angeles, Indiana LinuxFest in Indianapolis, and Flourish in + Chicago.</p> + + <p>Completed Foundation-funded projects: <a + href="http://www.FreeBSDfoundation.org/announcements.shtml#Swinburne"> + Five New TCP Congestion Control Algorithms project</a> by + Swinburne University and Resource Containers project by + Edward Napierala.</p> + + <p>In February we visited companies in the Bay Area that use &os;. + Our goal was to promote &os;, better understand their interests and + needs, and help facilitate stronger relationships between these + companies and the Project. The presentations we gave included the + benefits of &os;, Project road-map, potential areas of + collaboration, case studies, and how the Foundation supports the + project. By visiting in person we were able to show our commitment + to the Project and respond directly to questions and concerns they + may have had. We were pleased with the positive responses we + received and plan on visiting more companies in the future.</p> + + <p>We are funding two new projects. The first project is + Implementing Support of GEM, KMS, and DRI for Intel Drivers by + Konstantin Belousov. The second is Improving the Maturity of IPv6 + Support of &os; and PC-BSD by Bjoern Zeeb.</p> + + <p>We continued our work on infrastructure projects to beef up + hardware for package-building, network-testing, etc. This includes + purchasing equipment as well as managing equipment donations.</p> + + <p>Stop by and visit with us at BSDCan (May 13-14) and SouthEast + LinuxFest (June 10-12).</p> + + <p>The work above as well as many other tasks we do for the + project, couldn't be done without donations. Please help us by + making a donation or asking your company to make a donation. We + would be happy to send marketing literature to you or your company. + Find out how to make a donation at <a + href="http://www.FreeBSDfoundation.org/donate/"> + http://www.FreeBSDfoundation.org/donate/</a>.</p> + </body> + </project> + + <project cat='ports'> + <title>KDE-&os;</title> + + <contact> + <person> + <name> + <given>KDE</given> + <common>&os;</common> + </name> + <email>kde-freebsd@kde.org</email> + </person> + </contact> + + <links> + <url href="http://FreeBSD.kde.org">KDE-&os;</url> + </links> + + <body> + <p>The KDE on &os; team have continued to improve the experience of + KDE and Qt under &os;. The latest round of improvements + include:</p> + + <ul> + <li>Improved shared resources (i.e. pixmaps for KDE)</li> + <li>Improved file monitoring (using kevent)</li> + <li>Improved KSysGuard support (new and refined sensors)</li> + </ul> + + <p>The team have also made many releases and upstreamed many fixes + and patches. The latest round of releases include:</p> + + <ul> + <li>Qt: 4.7.2</li> + <li>KDE: 4.5.5; 4.6.1; 4.6.2</li> + <li>KOffice: 2.3.3</li> + <li>KDevelop: 4.2.0; 4.2.2 (KDevPlatform: 1.2.0; 1.2.2)</li> + <li>many smaller ports</li> + </ul> + + <p>The team needs more testers and porters so please visit us at + kde-freebsd@kde.org</p> + </body> + + <help> + <task>Continue improvements of KSysGuard.</task> + <task>General maintenance.</task> + <task>General testing.</task> + <task><b>Porting</b>.</task> + </help> + </project> + + <project cat='ports'> + <title>&os; Chromium</title> + + <contact> + <person> + <name> + <given>&os;</given> + <common>Chromium Team</common> + </name> + <email>chromium@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://trillian.chruetertee.ch/chromium" /> + <url href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-chromium" /> + <url href="http://www.chromium.org/Home" /> + </links> + + <body> + <p>Thanks to a great collaborative effort from the &os; community, the + OpenBSD community, and the Chromium developers, Chromium has been + updated in the Ports tree.</p> + + <p>In the spirit of release early and release often, updates to + Chromium happen frequently. The contributors of the &os; Chromium + team have demonstrated great agility in keeping pace with updates + in the development repository hosted at <a + href="http://trillian.chruetertee.ch/chromium"> + http://trillian.chruetertee.ch/chromium</a>.</p> + </body> + + <help> + <task>A task that lies ahead is working with the Chromium + developers at integrating the &os; patches into the codebase. + Volunteers are welcome.</task> + </help> + </project> + + <project cat='net'> + <title>DIstributed Firewall and Flow-shaper Using Statistical + Evidence (DIFFUSE)</title> + + <contact> + <person> + <name> + <given>Sebastian</given> + <common>Zander</common> + </name> + <email>szander@swin.edu.au</email> + </person> + + <person> + <name> + <given>Grenville</given> + <common>Armitage</common> + </name> + <email>garmitage@swin.edu.au</email> + </person> + </contact> + + <links> + <url href="http://caia.swin.edu.au/urp/diffuse/" /> + <url href="http://caia.swin.edu.au/urp/diffuse/downloads.html" /> + </links> + + <body> + <p>DIFFUSE is a system enabling &os;'s IPFW firewall subsystem to + classify IP traffic based on statistical traffic properties.</p> + + <p>With DIFFUSE, IPFW computes statistics (such as packet lengths + or inter-packet time intervals) for observed flows, and uses ML + (machine learning) to classify flows into classes. In addition to + traditional packet inspection rules, IPFW rules may now also be + expressed in terms of traffic statistics or classes identified by + ML classification. This can be helpful when direct packet + inspection is problematic (perhaps for administrative reasons, or + because port numbers do not reliably identify applications).</p> + + <p>DIFFUSE also enables one instance of IPFW to send flow + information and classes to other IPFW instances, which then can act + on such traffic (e.g. prioritise, accept, deny, etc.) according to + its class. This allows for distributed architectures, where + classification at one location in your network is used to control + fire-walling or rate-shaping actions at other locations.</p> + + <p>DIFFUSE is a set of patches for &os;-CURRENT. It can be + downloaded from the project's web site. The web site also contains + a more comprehensive introduction, including application examples, + links to related work and documentation.</p> + + <p>In February 2011 we released DIFFUSE v0.2.2. This release + contains a number of bug fixes and new features. Most notably since + version 0.2 there is a tool to build classifier models, and there + is a feature module and classifier model to classify Skype + traffic.</p> + + <p>We hope to release DIFFUSE v0.3 soon. Keep an eye on the + freebsd-ipfw and freebsd-net mailing lists for project-related + announcements.</p> + </body> + </project> + + <project cat="ports"> + <title>&os; as Home Theater PC</title> + + <contact> + <person> + <name> + <given>Bernhard</given> + <common>Froehlich</common> + </name> + <email>decke@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Juergen</given> + <common>Lock</common> + </name> + <email>nox@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/HTPC" /> + </links> + + <body> + <p>&os; could be a much better platform for a Home Theater PC than + it currently is. We are focusing on improving support for media + center applications by extending the major ports (MythTV, VDR, XBMC) + and creating some documentation to guide interested people.</p> + + <p>In the last months we continued to work on HTPC relevant ports, + improved lirc and multimedia/webcamd remote control support. The + last missing major HTPC application VDR (Video Disk Recorder) has + finally been committed to the portstree as multimedia/vdr including + 17 vdr plugin ports.</p> + </body> + + <help> + <task>Improve remote control support in webcamd and with + lirc.</task> + + <task>Port more Media Center applications (Enna, me-tv, ...)</task> + + <task>Create a small guide on how to build a great &os; Home + Theater PC.</task> + </help> + </project> + + <project cat='proj'> + <title>Bringing up OMAP3</title> + + <contact> + <person> + <name> + <given>Warner</given> + <common>Losh</common> + </name> + <email>imp@bsdimp.com</email> + </person> + + <person> + <name> + <given>Mohammed</given> + <common>Farrag</common> + </name> + <email>mfarrag@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>OMAP3 Emulation:</p> + + <ul> + <li>Step #1: qemu-omap3 isn't ported to &os; yet. So,</li> + <li>Step #2: Use qemu-omap3 on Gentoo Host ..</li> + <li>Step #3: Is the end reached ?! No, bcz qemu-omap3 is not + full. So, go to step #4.</li> + <li>Step #4: Use Meego >> Download Ubuntu 10.10 >> + Install it, and</li> + <li>Step #5: Compile &os; kernel, Create root file system, + mkimage, Emulate using Meego.</li> + </ul> + </body> + + <help> + <task>Device Drivers for OMAP3 Processors.</task> + </help> + </project> + + <project cat='proj'> + <title>New &os; Installer</title> + + <contact> + <person> + <name> + <given>Nathan</given> + <common>Whitehorn</common> + </name> + <email>nwhitehorn@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/BSDInstall">BSDInstall Wiki Page + (with test images)</url> + + <url href="http://wiki.FreeBSD.org/PCBSDInstallMerge">Wiki for + Integration Plan with PC-BSD installer</url> + </links> + + <body> + <p>On March 14th, sysinstall was replaced on the 9.0 snapshot media + by a new, modular installer called BSDInstall. This adds support + for a wide variety of new features while simplifying the + installation process. Testing before the 9.0 release will be very + much appreciated -- CD and memory stick images for a variety of + platforms are linked from the BSDInstall wiki page.</p> + + <p>Interesting features:</p> + + <ul> + <li>Install CD media are always live CDs</li> + <li>Installations spanning multiple disks</li> + <li>Wireless setup</li> + <li>GPT disk formatting</li> + <li>Virtualization friendly: can install from a live system onto + disk images</li> + <li>Easily hackable and more modular than sysinstall</li> + <li>Greater flexibility: shells available throughout the + installation</li> + </ul> + + <p>Work is presently ongoing to integrate this installer with the + backend provided by pc-sysinstall (second wiki link).</p> + </body> + + <help> + <task>ZFS installation support.</task> + <task>IA64 disk setup.</task> + </help> + </project> + + <project cat='docs'> + <title>Webcam and DVB Compatibility List</title> + + <contact> + <person> + <name> + <given>Matthias</given> + <common>Apitz</common> + </name> + <email>guru@unixarea.de</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/WebcamCompat" /> + </links> + + <body> + <p><strong>Webcam and DVB Compatibility List</strong></p> + + <p>This is the &os; Webcam, DVB, and Remote Control Compatibility + List. The main goal of this page is to give an exact answer about + which application works with a given cam or DVB. Combinations of + the hardware and software mentioned in this table are known to + work.</p> + + <p>Please add more lines to the table or ask me to do so by just + sending a mail with your Cam/DVB information. Please note: you + should only add information you have seen working and not you may + think of or imagine that they could work. The contact information + (name and/or email addr) is optional.</p> + </body> + + <help> + <task>Move this to a real database in where &os; enduser could self + insert their gadgets, like the &os; Laptop Compat List.</task> + </help> + </project> + + <project cat='proj'> + <title>OpenAFS Port</title> + + <contact> + <person> + <name> + <given>Benjamin</given> + <common>Kaduk</common> + </name> + <email>kaduk@mit.edu</email> + </person> + + <person> + <name> + <given>Derrick</given> + <common>Brashear</common> + </name> + <email>shadow@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://openafs.org">OpenAFS home page</url> + + <url href="http://web.mit.edu/freebsd/openafs/openafs.shar">&os; + port for OpenAFS 1.6.0 prerelease 4</url> + </links> + + <body> + <p>AFS is a distributed network filesystem that originated from the + Andrew Project at Carnegie-Mellon University. The OpenAFS client + implementation has not been particularly useful on &os; since the + &os; 4.X releases. Work covered in previous reports brought the + OpenAFS client to a useful form on 9.0-CURRENT, though with some + rough edges. Since our last report, we have fixed several bugs that + were impacting usability, and we expect the upcoming 1.6.0 release + to be usable for regular client workloads (though not heavy load). + Accordingly, we have submitted packaging for inclusion in the Ports + Collection (PR ports/152467).</p> + + <p>There are several known outstanding issues that are being worked + on, but detailed bug reports are welcome at + port-freebsd@openafs.org.</p> + </body> + + <help> + <task>Update VFS locking to allow the use of disk-based client + caches as well as memory-based caches.</task> + + <task>Track down races and deadlocks that may appear under + load.</task> + + <task>Integrate with the bsd.kmod.mk kernel-module build + infrastructure.</task> + + <task>Eliminate a moderate memory leak from the kernel + module.</task> + + <task>PAG (Process Authentication Group) support is not + functional.</task> + </help> + </project> + + <project cat='team'> + <title>&os; NYI Admins Status Report</title> + + <contact> + <person> + <name> + <given>NYI Admins Team</given> + </name> + <email>nyi-admin@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The FreeBSD.org site at New York Internet is progressing, though + more slowly than we had hoped. Due to problems with the old power + controllers and serial console servers, new equipment has been + bought by the &os; Foundation. Installing the new equipment + required re-racking all the existing servers which was done by the + local &os; team (Steven Kreuzer and John Baldwin).</p> + + <p>For basic infrastructure at the site (such as DHCP, DNS, console + etc.) the &os; Foundation bought some new servers which are in the + process of being configured.</p> + + <p>The &os; Ports team are currently using 9 of the NYI servers for + package building.</p> + </body> + + <help> + <task>We are looking for a storage system (15TB+) for keeping + replicas of all the main FreeBSD.org systems, a full ftp-archive + mirror, site local files etc.</task> + </help> + </project> + + <project cat='proj'> + <title>RCTL, aka Resource Containers</title> + + <contact> + <person> + <name> + <given>Edward Tomasz</given> + <common>Napierala</common> + </name> + <email>trasz@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Most of the code has already been merged into CURRENT. There are + two remaining problems I would like to solve before 9.0-RELEASE - see + below - but otherwise, the code is stable; please test and report + any problems. You will need to rebuild the kernel with "options + RACCT" and "options RCTL". The rctl(8) manual page should be a good + introduction on how to use it.</p> + + <p>This project was sponsored by The &os; Foundation.</p> + </body> + + <help> + <task>Reimplementing %CPU accounting and CPU throttling.</task> + + <task>Making jail rules persistent - right now, one cannot add jail + rule before that jail is created, which makes it impossible to put + them into /etc/rctl.conf; also, rules disappear when jail gets + destroyed.</task> + </help> + </project> + + <project cat='ports'> + <title>Portmaster</title> + + <contact> + <person> + <name> + <given>Doug</given> + <common>Barton</common> + </name> + <email>dougb@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://dougbarton.us/portmaster-proposal.html" /> + </links> + + <body> + <p>The latest version of portmaster contains numerous improvements + aimed at large-scale enterprise users. Particularly, support for + the --index-only/--packages-only code has been significantly + improved. Some of the highlights include:</p> + + <ul> + <li>New --update-if-newer option which takes a list of ports + and/or a glob pattern on the command line and only updates those + that are out of date. This feature is very useful for ensuring + that the packages needed for updating a system are all available + and up to date on the package building system.</li> + + <li>The portmaster.rc file can now be stored in the same + directory as the script itself, which aids in shared access to + the script (for example over an NFS mount)</li> + + <li>More features now work (or work better) with --index-only, + including --check-depends</li> + </ul> + </body> + + <help> + <task>I have received some support for items E.2 and E.3 on the web + page listed above so I will be putting some effort into those areas + in the coming months. I also have in mind to split out the "fetch" + code to be its own script, in part to support goal E.2, and to + allow for more efficient parallelization when downloading multiple + distfiles (especially for multiple ports that download the same + distfile). This will also allow me to set a global limit for the + number of parallel fetches which should aid users on slow + links.</task> + </help> + </project> + + <project cat='proj'> + <title>pfSense</title> + + <contact> + <person> + <name> + <given>Scott</given> + <common>Ullrich</common> + </name> + <email>sullrich@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Chris</given> + <common>Buechler</common> + </name> + <email>cmb@pfsense.org</email> + </person> + + <person> + <name> + <given>Ermal</given> + <common>Luci</common> + </name> + <email>eri@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.pfsense.org">pfSense home page</url> + </links> + + <body> + <p>Work on 2.0 is rapidly coming to an end. We released RC1 around + Feb 25 2011 and so far it seems to be rather stable. 2.0 is our first + major release in 2 years and almost all limitations of the previous + version has been overcome.</p> + </body> + + <help> + <task>Finish testing RC1 and certify for release.</task> + </help> + </project> + + <project cat='kern'> + <title>Linux Compatibility Layer - DVB and V4L2 Support</title> + + <contact> + <person> + <name> + <given>Juergen</given> + <common>Lock</common> + </name> + <email>nox@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~nox/dvb/" /> + </links> + + <body> + <p>Following (separate) discussions on the mailing lists I have + made patches to add DVB and V4L2 ioctl translation support to the + Linux compatibility layer, allowing Linux apps like SageTV, Skype, + and Flash to use DVB/ATSC tuners and webcams that previously only + worked for native &os; apps. (Most of this hardware uses Linux + drivers via the <a + href="http://www.freshports.org/multimedia/webcamd"> + multimedia/webcamd</a> port.)</p> + </body> + + <help> + <task>Handle the remaining ioctls that (I think) are not used by + DVB tuners/cameras supported by webcamd (it only supports USB + devices, the unhandled ioctls mostly have to do with video overlays + and hardware MPEG2 decoding on analog or DVB tuners, features that + AFAIK don't exist on USB hardware.)</task> + + <task>Make the DVB support a port because there were concerns + putting it in base due to the LGPL in one of the header files even + though I already separated out the code into an extra kld. + (linux_dvbwrapper.ko)</task> + + <task>Get the patches polished and committed. :) (Until they are + you can check my <a + href="http://people.FreeBSD.org/~nox/dvb/">DVB page</a> + and the freebsd-emulation@ mailing list for updates.)</task> + </help> + </project> + + <project cat='arch'> + <title>&os;/powerpc on Freescale QorIQ</title> + + <contact> + <person> + <name> + <given>Michal</given> + <common>Dubiel</common> + </name> + <email>md@semihalf.com</email> + </person> + + <person> + <name> + <given>Rafal</given> + <common>Jaworowski</common> + </name> + <email>raj@semihalf.com</email> + </person> + </contact> + + <body> + <p>QorIQ is a brand of Power Architecture-based communications + microprocessors from Freescale. It is an evolutionary step from the + PowerQUICC platform (MPC85xx) and is built around one or more Power + Architecture e500/e500mc cores. This work is bringing up &os; on + these system-on-chip devices along with device drivers for + integrated peripherials.</p> + + <p>Current &os; QorIQ support includes:</p> + + <ul> + <li>QorIQ P2020 support</li> + <li>Booting via U-Boot bootloader</li> + <li>L1, L2 cache</li> + <li>Serial console (UART)</li> + <li>Interrupt controller</li> + <li>Ethernet (TSEC, SGMII mode)</li> + <li>I2C</li> + <li>EHCI controller (no Transaction Translation Unit)</li> + <li>Security Engine (SEC) 3.1</li> + <li>PCI Express controller (host mode)</li> + <li>Enhanced SDHC (no MMC support)</li> + <li>Dual-core (SMP) support</li> + </ul> + </body> + </project> + + <project cat='arch'> + <title>&os;/arm on Marvell Raid-on-Chip</title> + + <contact> + <person> + <name> + <given>Grzegorz</given> + <common>Bernacki</common> + </name> + <email>gjb@semihalf.com</email> + </person> + + <person> + <name> + <given>Rafal</given> + <common>Jaworowski</common> + </name> + <email>raj@semihalf.com</email> + </person> + </contact> + + <body> + <p>Marvell 88RC8180 is an integrated RAID-on-Chip controller, based + on the Feroceon 88FR331 CPU core (ARMv5TE). The 88RC9580 is a next + generation version, based on the Sheeva 88SV581 CPU core (ARMv6) of + this system-on-chip devices family.</p> + + <p>Current &os; suppport for 88RC8180 and 88RC9580 includes:</p> + + <ul> + <li>Booting via U-Boot bootloader</li> + <li>L1, L2 cache</li> + <li>Serial console support (UART)</li> + <li>Interrupt controller</li> + <li>Integrated timers</li> + <li>PCI Express (root complex and endpoint modes)</li> + <li>Doorbells and messages</li> + <li>Ethernet controller</li> + </ul> + </body> + + <help> + <task>Complete, clean up, merge with HEAD.</task> + </help> + </project> + + <project cat='misc'> + <title>BSDCan</title> + + <contact> + <person> + <name> + <given>Dan</given> + <common>Langille</common> + </name> + <email>dvl@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.bsdcan.org/2011/">BSDCan 2011</url> + </links> + + <body> + <p>Our <a + href="http://www.bsdcan.org/2011/schedule/events.en.html">list + of talks</a> has been settled, and the <a + href="http://www.bsdcan.org/2011/schedule/index.en.html"> + schedule</a> is pretty much finalized. There is still time + to get into the <a + href="http://www.bsdcan.org/2011/schedule/events/259.en.html"> + Works In Progress</a> session.</p> + + <p>Best to book your <a + href="http://www.bsdcan.org/2011/campus.php">on-campus + accommodation</a> now. Or stay at one of the <a + href="http://www.bsdcan.org/2011/travel.php">nearby + hotels</a>.</p> + </body> + + <help> + <task>Show up. Enjoy. Profit.</task> + </help> + </project> + + <project cat='ports'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Thomas</given> + <common>Abthorpe</common> + </name> + <email>portmgr-secretary@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Port</given> + <common>Management Team</common> + </name> + <email>portmgr@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ports/" /> + <url href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" /> + <url href="http://portsmon.FreeBSD.org/index.html" /> + <url href="http://www.FreeBSD.org/portmgr/index.html" /> + <url href="http://blogs.FreeBSDish.org/portmgr/" /> + <url href="http://www.twitter.com/freebsd_portmgr/" /> + <url href="http://www.facebook.com/group.php?gid=135441496471197" /> + <url href="http://tinderbox.marcuscom.com/" /> + </links> + + <body> + <p>The ports tree slowly moves up closer to 23,000. The PR count + still remains at about 1000.</p> + + <p>In Q1 we added 2 new committers, and took in 4 commit bits for + safe keeping.</p> + + <p>After a year of serving as the team secretary, Thomas Abthorpe's + membership was upgraded to full voting status.</p> + + <p>The Ports Management team have been running -exp runs on an + ongoing basis, verifying how base system updates may affect the + ports tree, as well as providing QA runs for major ports updates. + Of note, -exp runs were done for:</p> + + <ul> + <li>erwin did a clang -exp run, and sent results to interested + parties</li> + + <li>kde@ requested an -exp run for KDE 4.6.1 and Qt 4.7.2</li> + + <li>linimon -exp for update of default zope version to 3.2</li> + + <li>miwi performed the following -exp runs, make fetch-original, + xorg, cmake, pear, kde4 / py-qt / sip, and python2.7</li> + + <li>mm requested an -exp run to test the last GPLv2 version of + gcc 4.2.2</li> + + <li>pav completed open-motif and mono -exp runs for respective + submitters</li> + + <li>ports/127214, -exp run to make copy/paste of portaudit user + friendly</li> + + <li>ports/144482, -exp run to fix package depends</li> + + <li>ports/152102, -exp run to make dirrmtry more friendly</li> + + <li>ports/152268, -exp run to update binutils</li> + + <li>ports/153539, -exp run to allow checking STRIP when + WITH_DEBUG is defined</li> + + <li>ports/153547, -exp run to remove NO_SIZE</li> + + <li>ports/153625, -exp run to pass CPPFLAGS to + MAKE/CONFIGURE_ENV</li> + + <li>ports/153634, -exp run to remove redundant PKGNAMEPREFIX for + localised ports</li> + + <li>ports/154121, -exp run to use --title for new libdialog</li> + + <li>ports/154122, -exp run to update libtool to 2.4</li> + + <li>ports/154186, -exp to allow using linux 2.4 emulation on &os; + 8+</li> + + <li>ports/154390, -exp run to make fetching output copy/paste + friendly</li> + + <li>ports/154653, -exp run to remove superfluous slash</li> + + <li>ports/154799, -exp run to update glib + gtk</li> + + <li>ports/154994, -exp run for MASTER_SITE_PERL_CPAN + enhancements</li> + + <li>ports/155502, -exp run to remove sanity check for + X_WINDOW_SYSTEM</li> + + <li>ports/155504, -exp run to remove USE_XPM from b.p.m.</li> + + <li>ports/155505, -exp run to update GNU m4</li> + </ul> + </body> + + <help> + <task>Looking for help fixing <a + href="http://wiki.FreeBSD.org/PortsBrokenOnCurrent">ports + broken on CURRENT</a>.</task> + + <task>Looking for help with <a + href="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures"> + Tier-2 architectures</a>.</task> + + <task>Most ports PRs are assigned, we now need to focus on testing, + committing and closing.</task> + </help> + </project> + + <project cat='proj'> + <title>GEOM-based ataraid(4) Replacement — geom_raid.</title> + + <contact> + <person> + <name> + <given>Alexander</given> + <common>Motin</common> + </name> + <email>mav@FreeBSD.org</email> + </person> + + <person> + <name> + <given>M. Warner</given> + <common>Losh</common> + </name> + <email>imp@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>A new RAID GEOM class (geom_raid) was added to &os; 9-CURRENT, to + replace ataraid(4) in supporting various BIOS-based software RAIDs. + Unlike ataraid(4) this implementation does not depend on legacy + ata(4) subsystem and can be used with any disk drivers, including + new CAM-based ones (ahci(4), siis(4), mvs(4) and ata(4) with + `options ATA_CAM`). To make code more readable and extensible, this + implementation follows modular design, including a core part and two + sets of modules, implementing support for different metadata + formats and RAID levels.</p> + + <p>Support for such popular metadata formats is now implemented: + Intel, JMicron, NVIDIA, Promise (also used by AMD/ATI) and + SiliconImage.</p> + + <p>Such RAID levels are now supported: RAID0, RAID1, RAID1E, + RAID10, SINGLE, CONCAT.</p> + + <p>For any all of these RAID levels and metadata formats this class + supports full cycle of volume operations: reading, writing, + creation, deletion, disk removal and insertion, rebuilding, dirty + shutdown detection and resynchronization, bad sector recovery, + faulty disks tracking, hot-spare disks. For Intel and Promise + formats there is support for multiple volumes per disk set.</p> + + <p>See the graid(8) manual page for additional details.</p> + + <p>Sponsored by: Cisco Systems, Inc. and iXsystems, Inc.</p> + </body> + + <help> + <task>Implement metadata modules for other formats (DDF, Highpoint, + VIA, ...).</task> + + <task>Implement transformation modules for other RAID levels + (RAID5, ...).</task> + </help> + </project> + + <project cat='ports'> + <title>www/apache22 Default</title> + + <contact> + <person> + <name> + <given>Philip</given> + <common>Gollucci</common> + </name> + <email>pgollucci@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Olli</given> + <common>Hauer</common> + </name> + <email>ohauer@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Apache</given> + <common>Apache</common> + </name> + <email>apache@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~pgollucci/FreeBSD/prs/maintainers.html#apache"> + prs</url> + + <url href="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/147009">-exp + request</url> + + <url href="http://wiki.FreeBSD.org/Apache" /> + + <url href="http://lists.FreeBSD.org/pipermail/freebsd-apache/2011-March/002174.html" /> + </links> + + <body> + <p>95% done, pending final -exp run, and pulling the switch. HEADS-UP + announcement already sent to relevant lists. This will be for + 8.3/9.0.</p> + </body> + </project> + + <project cat='arch'> + <title>&os;/EC2</title> + + <contact> + <person> + <name> + <given>Colin</given> + <common>Percival</common> + </name> + <email>cperciva@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.daemonology.net/freebsd-on-ec2/">&os;/EC2 + status page</url> + </links> + + <body> + <p>&os; is now able to run on t1.micro and cc1.4xlarge instances in + the Amazon EC2 cloud. &os; 8.2-RELEASE is stable subject to the + limitations of the instance type (e.g., running ZFS on a micro + instance with only 600 MB of RAM doesn't work very well), but &os; + 9.0 has significant stability issues.</p> + + <p>A list of available &os; AMIs (EC2 machine images) appears on + the &os;/EC2 status page.</p> + </body> + + <help> + <task>Bring &os; to a wider range of EC2 instance types.</task> + + <task>Completely rework the locking in head/sys/i386/xen/pmap.c to + eliminate races and make 9.0-CURRENT stable under + paravirtualization.</task> + + <task>Track down several possibly-related problems with scheduling + and timekeeping.</task> + + <task>Fix other issues shown on the &os;/EC2 status page.</task> + </help> + </project> + + <project cat='ports'> + <title>&os; Haskell Ports</title> + + <contact> + <person> + <name> + <given>Gábor János</given> + <common>PÁLI</common> + </name> + <email>pgj@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ashish</given> + <common>SHUKLA</common> + </name> + <email>ashish@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Giuseppe</given> + <common>Pilichi</common> + </name> + <email>jacula@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/Haskell">&os; Haskell Wiki + Page</url> + + <url href="https://github.com/freebsd-haskell/freebsd-haskell">&os; + Haskell ports repository</url> + + <url href="http://haskell.org/mailman/listinfo/freebsd-haskell/"> + &os; Haskell mailing list</url> + </links> + + <body> + <p>We are proud to announce that the &os; Haskell team has updated + GHC to 7.0.3, and all other existing Haskell ports to the latest + stable versions, as well as added new ports. The total number of + Haskell ports in the &os; repository is now more than 200. These + ports are still waiting to be committed. At the moment, they are + available from <a + href="https://github.com/freebsd-haskell/freebsd-haskell">&os; + Haskell ports repository</a>. Any users who would like to get + early access to them, please refer to the <a + href="http://www.haskell.org/pipermail/freebsd-haskell/2011-April/000278.html"> + &os; Haskell ports Call For Testing</a>.</p> + </body> + + <help> + <task>Create a metaport for Haskell Platform.</task> + <task>Create a port for Happstack.</task> + <task>Create a port for gitit.</task> + </help> + </project> + + <project cat='kern'> + <title>Journaled Soft Updates</title> + + <contact> + <person> + <name> + <given>Jeff</given> + <common>Roberson</common> + </name> + <email>jeff@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Kirk</given> + <common>McKusick</common> + </name> + <email>mckusick@mckusick.com</email> + </person> + </contact> + + <body> + <p>All known problems with journaled soft updates have been fixed + in head. If you have any problems while running with journaled soft + updates, please report them to us.</p> + + <p>We have addressed several performance issues that have been + brought to our attention. If you have any performance problems + while running with journaled soft updates, please report them to + us.</p> + + <p>We have improved the recovery of resources when running with + soft updates on small (root) filesystems. We anticipate being able + to use soft updates for root filesystems in the 9.0 system.</p> + + <p>We expect to have journaled soft updates default to enabled in + the 9.0 system. We encourage users of -CURRENT to enable journaled + soft updates to help shake out any remaining performance problems + and bugs.</p> + </body> + </project> + + <project cat='arch'> + <title>MIPS/Octeon Support and bootinfo</title> + + <contact> + <person> + <name> + <given>Andrew</given> + <common>Duane</common> + </name> + <email>aduane@juniper.net</email> + </person> + </contact> + + <body> + <p>Working on improving support for Octeon processors and + integrating with other MIPS processor families. Currently working + on support for the standard MIPS bootinfo structure as a boot API + (to supplement/replace the Caviums-specific structure). Other + Octeon improvements including cleanups to CF and USB drivers to + come.</p> + </body> + </project> + + <project cat='docs'> + <title>The &os; German Documentation Project Status Report</title> + + <contact> + <person> + <name> + <given>Johann</given> + <common>Kois</common> + </name> + <email>jkois@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Benedict</given> + <common>Reuschling</common> + </name> + <email>bcr@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://doc.bsdgroup.de">Website of the &os; German + Documentation Project.</url> + </links> + + <body> + <p>Benedict Reuschling contributed the translation of the new + handbook section about HAST, while Benjamin Lukas was working on + the first translation of the firewall chapter of the handbook. The + committers to the German Documentation Project were busy with + keeping the existing German documentation up-to-date. The website + translations were also kept in sync with the ones on &os;.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> + </body> + + <help> + <task>Submit grammar, spelling or other errors you find in the + german documents and the website.</task> + + <task>Translate more articles and other open handbook + sections.</task> + </help> + </project> + + <project cat="docs"> + <title>The &os; Japanese Documentation Project</title> + + <contact> + <person> + <name> + <given>Hiroki</given> + <common>Sato</common> + </name> + <email>hrs@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ryusuke</given> + <common>Suzuki</common> + </name> + <email>ryusuke@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ja/">Japanese &os; Web + Pages</url> + + <url href="http://www.jp.FreeBSD.org/doc-jp/">The &os; Japanese + Documentation Project Web Page</url> + </links> + + <body> + <p>The www/ja and doc/ja_JP.eucJP/books/handbook have constantly + been updated. During this period, translation of the handbook + installation page was finished. The following chapters are now + synchronized with the English version:</p> + + <ul> + <li>introduction</li> + <li>install</li> + <li>ports</li> + <li>x11</li> + <li>desktop</li> + <li>multimedia</li> + <li>mirrors</li> + <li>pgpkeys</li> + </ul> + + <p>Merging translation results from the www tree on a separate + repository for the translation work into the main tree was also + finished. Since outdated and/or non-translated documents also + remain in both doc/ja_JP.eucJP and www, further translation work is + still needed. Some progress has been made in the Porter's Handbook + as well in this period.</p> + </body> + </project> + + <project cat='gsoc'> + <title>Extfs Status Report</title> + + <contact> + <person> + <name> + <given>Zheng</given> + <common>Liu</common> + </name> + <email>lz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/soc2010/extfs/src/sys/fs/&c=rFV@//depot/projects/soc2010/extfs/src/sys/fs/ext2fs/?ac=83"> + ext2fs</url> + + <url href="http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/soc2010/ext4fs/src/sys/fs/&c=cc4@//depot/projects/soc2010/ext4fs/src/sys/fs/ext4fs/?ac=83"> + ext4fs</url> + </links> + + <body> + <p>I have implemented a reallocblks in ext2fs, like in ffs, + and submitted a patch file to mailing list. Next I will try to + implement htree directory index in ext2fs.</p> + </body> + </project> + + <project cat='ports'> + <title>Linux Emulation Ports</title> + + <contact> + <person> + <name> + <given>Alexander</given> + <common>Leidinger</common> + </name> + <email>netchild@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Emulation</given> + <common>Mailinglist</common> + </name> + <email>freebsd-emulation@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.leidinger.net/blog/2011/02/25/howto-creating-your-own-updated-linux-rpm-for-the-freebsd-linuxulator/"> + HOWTO: creÂatÂing your own updated linux RPM for the &os; + linuxulator</url> + </links> + + <body> + <p>Old linux_base ports (all which are not used by default in some + release) where marked as deprecated with a short expiration + period. The reason is that all those ports are long past their end + of life and do not receive security updates anymore. Unfortunately + this is also true for the linux_base ports which are still used by + default in the releases, but no replacement is available ATM (see + open tasks).</p> + + <p>The linux-f10-pango port was updated to a more recent version + whoch does not have a security problem by generating a linux-RPM in + a VM with "&os;" as the vendor (see the links section for a + HOWTO).</p> + </body> + + <help> + <task>Decide which RPM based linux distribution+version to track + next for the linux_base ports, create ports for it and test for + compatibility with our kernel code.</task> + </help> + </project> + + <project cat='proj'> + <title>HAST (Highly Available Storage)</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + <common>Dawidek</common> + </name> + <email>pjd@FreeBSD.org</email> + </person> + </contact> + <contact> + <person> + <name> + <given>Mikolaj</given> + <common>Golub</common> + </name> + <email>trociny@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>HAST development is progressing nicely. Mikolaj Golub who contributes + to HAST is now a &os; src committer. Some changes worth noting since + the last report:</p> + + <ul> + <li>Compression of the data being sent over the network. This can + speed up especially synchronization process.</li> + <li>Optional checksuming for the data being send over the + network.</li> + <li>Capsicum sandboxing for secondary node and hastctl.</li> + <li>Chroot+setuid+setgid sandboxing for primary node.</li> + <li>Allow administrators to specify source IP address for + connections.</li> + <li>When changing role wait for a while for the other node to + switch from primary to secondary to avoid split-brain.</li> + <li>Many bug fixes.</li> + </ul> + </body> + </project> + + <project cat='proj'> + <title>ZFSv28 available in &os; 9-CURRENT</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + <common>Dawidek</common> + </name> + <email>pjd@FreeBSD.org</email> + </person> + </contact> + <contact> + <person> + <name> + <given>Martin</given> + <common>Matuska</common> + </name> + <email>mm@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>ZFS v28 is now in HEAD! Test, test, test and test. Pretty please. + New features include:</p> + + <ul> + <li>Data deduplication.</li> + <li>Triple parity RAIDZ (RAIDZ3).</li> + <li>zfs diff.</li> + <li>zpool split.</li> + <li>Snapshot holds.</li> + <li>zpool import -F. Allows to rewind corrupted pool to earlier + transaction group.</li> + <li>Possibility to import pool in read-only mode.</li> + </ul> + </body> + </project> + + <project cat='docs'> + <title>New &os; Handbook Section Covering HAST</title> + + <contact> + <person> + <name> + <given>Daniel</given> + <common>Gerzo</common> + </name> + <email>danger@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/disks-hast.html" /> + </links> + + <body> + <p>A new &os; Handbook section covering the Highly Available + STorage, or HAST developed by Pawel Jakub Dawidek has been + recently added. In this section, you will learn what HAST is, + how it works, which features it provides and how to set it up. + It also includes a working example on how it can be used + together with devd(8) and CARP. Enjoy your reading.</p> + </body> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2011-04-2011-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2011-04-2011-06.xml new file mode 100644 index 0000000000..3b32bc686b --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2011-04-2011-06.xml @@ -0,0 +1,1944 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for +Status Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2011-04-2011-06.xml,v 1.7 2011/09/14 22:33:53 jkois Exp $ --> + +<report> + <date> + <month>April-June</month> + + <year>2011</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report covers &os;-related projects between April and June + 2011. It is the second of the four reports planned for 2011. Since + this quarter, the work is being focused on the next major version of + &os;, 9.0, which is to be released in September.</p> + + <p>Thanks to all the reporters for the excellent work! This report + contains 36 entries and we hope you enjoy reading it.</p> + + <p>Please note that the deadline for submissions covering the period + between July and September 2011 is October 15th, 2011.</p> + </section> + + <category> + <name>proj</name> + <description>Projects</description> + </category> + + <category> + <name>team</name> + <description>&os; Team Reports</description> + </category> + + <category> + <name>net</name> + <description>Network Infrastructure</description> + </category> + + <category> + <name>kern</name> + <description>Kernel</description> + </category> + + <category> + <name>docs</name> + <description>Documentation</description> + </category> + + <category> + <name>arch</name> + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + <description>Ports</description> + </category> + + <category> + <name>misc</name> + <description>Miscellaneous</description> + </category> + + <category> + <name>gsoc</name> + <description>Google Summer of Code</description> + </category> + + <project cat='gsoc'> + <title>Disk device error counters</title> + + <contact> + <person> + <name> + <given>Oleksandr</given> + <common>Dudinskyi</common> + </name> + <email>dudinskyj@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/Disk%20device%20error%20counters"> + Wiki page</url> + </links> + + <body> + <p>Currently, I work on schedule, I printed the information of + disk error in utility iostat option -E. While only displays five + types of errors. Further analysis will give me the opportunity to + identify other types of disk errors.</p> + </body> + + <help> + <task>Search other type of error and the place of their + registration.</task> + + <task>Maybe find a better place registration of errors than + xpt_done().</task> + </help> + </project> + + <project cat='docs'> + <title>&os; June 6th, 2011 Doc Sprint</title> + + <contact> + <person> + <name> + <given>Benedict</given> + <common>Reuschling</common> + </name> + <email>bcr@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Dru</given> + <common>Lavigne</common> + </name> + <email>dru@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/DocSprints">The DocSprints page + in the &os; wiki</url> + + <url href="http://people.FreeBSD.org/~bcr/doc/sprints/20110606-final.html"> + Results of the June 6 Doc Sprint</url> + + <url href="http://people.FreeBSD.org/~linimon/annotated_prs.docsprint.html"> + Closed PRs during the doc sprint</url> + + <url href="http://openhelpconference.com/">Website of the Open Help + conference</url> + </links> + + <body> + <p>On June 6, the &os; documentation project held a doc sprint + where a number of documentation issues were discussed. The sprint + took place primarily in IRC channel #bsddocs on EFNet. Notes were + taken in an Etherpad document where all participants could + concurrently edit them in an easy to use interface. Parallel to the + discussion, a number of doc problem reports have been closed. There + are still some doc PRs that have been identified that could also be + closed, because their original issue was already committed but the + PR is still open. This needs to be investigated on a case by case + basis.</p> + + <p>Dru Lavigne brought in her experiences from the Open Help + conference that she was attending during the sprint. It would be + good to have some &os; documentation people at a future Open + Help conference to exchange ideas with other open source + documentation projects and how they go about doing their work.</p> + + <p>The primary discussion focused on the issues that have been + talked about at the documentation working group at BSDCan's + DevSummit in May. Subjects like converting the documentation + repository from CVS to SVN, the move from DocBook SGML to XML-based + documentation as well as other formats like RST (re-restructured + text), and publication efforts of the handbook in electronic and + dead-tree form were thoroughly debated.</p> + + <p>Overall participation was good, but we would like to have more + documentation folks to participate in future sprints. The next + sprint is planned before EuroBSDCon 2011 and will be announced in + time so that interested people can set aside some time for it. We + also plan to include different time zones so that we can have more + input from various areas. We hope to establish these kind of + sprints on a regular basis to deal with documentation issues that + affect the whole community.</p> + + <p>Thanks to everyone who participated and helped bring some of the + issues we talked about forward.</p> + </body> + + <help> + <task>Schedule the next documentation sprint before the next + EuroBSDCon and include different timezones.</task> + + <task>Work on the todo items identified during the sprint.</task> + + <task>Resolve open documentation problem reports identified to be + fixed, but still open for some reason.</task> + </help> + </project> + + <project cat='gsoc'> + <title>Replacing the Regular Expression Code</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Kövesdán</common> + </name> + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/G%C3%A1borSoC2011">Wiki + page</url> + </links> + + <body> + <p>The current regular expression code in libc is quite outdated + and does not support wide characters. There are various open + source regular expression libraries but replacing the code is + not a simple task because there are quite many considerations + and requirements. The best candidate is TRE, which is a + BSD-licensed, supports wide and multibyte characters, conforms + to POSIX and it performs well compared to another available + alternatives, so the work has been started with TRE. Apart + from the replacement, the plan is to implement heuristical + matching, which will speed up the pattern matching + significantly. Besides, grep and diff in the base system have + been using the GNU regex code, which has a more permissive + syntax. It is desired to have a single regex engine in the + base system, so the GNU syntax has to be implemented (as an + optional feature), as well.</p> + + <p>So far, a fast string matching algorithm has been added, + which is a variant of the Turbo Boyer-Moore algorithm. It has + been slightly tuned to support not only literal patterns but + patterns containing $^. symbols. This algorithm is used + automatically when the pattern makes it possible.</p> + + <p>Besides, heuristic matching has also been implemented. If + the fast matcher cannot be applied directly, it parses the + pattern and separates the fixed-length prefix and suffix of + the pattern. Then it can be used to locate the possibly + matching regions of the text, using a more efficient algorithm + than the full regex NFA and the latter only has to be applied + to the narrow context that has been located.</p> + </body> + + <help> + <task>Implement GNU regex syntax.</task> + + <task>Add test suite GNU-specific behavior and also add some + tests for locale-specific behavior.</task> + + <task>Test and review the code. Contact the author and check if + these improvements can be added to the upstream code so that + more people can benefit from this.</task> + </help> + </project> + + <project cat='team'> + <title>ArabBSD</title> + + <contact> + <person> + <name> + <given>Mohammed</given> + <common>Farrag</common> + </name> + <email>mfarrag@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="https://sites.google.com/site/arabbsd/">Official + Website</url> + </links> + + <body> + <p>&os; Awareness, Handbook Translation and &os; Kernel + Development Summer Course.</p> + </body> + + <help> + <task>&os; Kernel Development Summer Course.</task> + </help> + </project> + + <project cat='arch'> + <title>&os;/powerpc on AppliedMicro APM86290</title> + + <contact> + <person> + <name> + <given>Grzegorz</given> + <common>Bernacki</common> + </name> + <email>gjb@semihalf.com</email> + </person> + + <person> + <name> + <given>Rafal</given> + <common>Jaworowski</common> + </name> + <email>raj@semihalf.com</email> + </person> + </contact> + + <body> + <p>The APM86290 system-on-chip device is a member of AppliedMicro's + PACKETpro family of embedded processors. The chip includes two + Power Architecture PPC465 processor cores, which are compliant with + Book-E specification of the architecture, and a number of + integrated peripherals. This work is extending current Book-E + support in &os; towards PPC4xx processors variation along with + device drivers for integrated peripherials. Current &os; + APM86290 support includes:</p> + + <ul> + <li>Booting via U-Boot bootloader</li> + <li>Support for PPC465 core</li> + <li>L1 cache</li> + <li>Serial console (UART)</li> + </ul> + + <p>Next steps:</p> + <ul> + <li>Interrupt controller</li> + <li>EHCI USB driver attachment</li> + <li>Ethernet controller</li> + <li>Queue Manager/Traffic Manager</li> + <li>L2 cache support</li> + </ul> + </body> + </project> + + <project cat='arch'> + <title>&os;/arm on Marvell Armada XP</title> + + <contact> + <person> + <name> + <given>Grzegorz</given> + <common>Bernacki</common> + </name> + <email>gjb@semihalf.com</email> + </person> + + <person> + <name> + <given>Rafal</given> + <common>Jaworowski</common> + </name> + <email>raj@semihalf.com</email> + </person> + </contact> + + <body> + <p>Marvell Armada XP is a complete system-on-chip solution based on + Sheeva embedded CPU. These devices integrate up to four ARMv6/v7 + compliant Sheeva CPU cores with shared L2 cache. This work is + extending &os;/arm infrastructure towards support for recent ARM + architecture variations along with a basic set of device drivers + for integrated peripherials. Current &os; suppport for Armada XP + includes:</p> + + <ul> + <li>Booting via U-Boot bootloader</li> + <li>ARMv6/v7 support</li> + <ul> + <li>Reworked CPU indentification scheme</li> + <li>New cache identification scheme</li> + <li>Support for PIPT caches</li> + <li>Reworked PMAP for ARMv6/v7 features</li> + </ul> + <li>Serial console support (UART)</li> + <li>Interrupt controller</li> + <li>Integrated timers</li> + <li>USB driver attachment</li> + <li>Ethernet controller driver</li> + </ul> + + <p>Next steps:</p> + <ul> + <li>L2 cache support</li> + <li>SMP support</li> + <li>PCI-Express and SATA drivers</li> + </ul> + </body> + </project> + + <project cat='misc'> + <title>bsd_day(2011)</title> + + <contact> + <person> + <name> + <given>Martin</given> + <common>Matuska</common> + </name> + <email>mm@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gábor</given> + <common>Páli</common> + </name> + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://bsdday.eu/2011" /> + </links> + + <body> + <p>The purpose of this one-day event is to gather Central European + developers of today's open-source BSD systems to popularize their + work and their organizations, and to meet each other in the real + life. We would also like to motivate potential future developers + and users, especially undergraduate university students to work + with BSD systems.</p> + + <p>This year's BSD-Day will be held in Bratislava, Slovakia at + Slovak University of Technology, Faculty of Electrical + Engineering and Information Technology on November 5, 2011.</p> + + <p>Everybody is welcome!</p> + </body> + + <help> + <task>Apply. We are looking for you!</task> + </help> + </project> + + <project cat='net'> + <title>TCP User Timeout Option (UTO)</title> + + <contact> + <person> + <name> + <given>Catalin</given> + <common>Nicutar</common> + </name> + <email>cnicutar@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Bjoern</given> + <common>Zeeb</common> + </name> + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/CatalinNicutar/TCPUTO">Project + Wiki</url> + + <url href="http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/soc2011/&dw=u&c=kml@//depot/projects/soc2011/cnicutar_tcputo_8/?ac=83"> + Repository</url> + </links> + + <body> + <p>The goal of the User Timeout option is to allow an application + to tweak the time TCP waits for acknowledgements. Using UTO, an + application can choose the exact time it is willing to wait for + data to be acknowledged. Also, an application can suggest to its + peer the time it should wait before dropping the connection (the + peer may or may not allow this).</p> + + <p>As an example, a SSH client can request a large timeout (4 + hours) for a connection. After some time the client is + disconnected, reconnecting 2 hours later (with the same IP). Due + to UTO, the connection should still be alive and any lost data + should be retransmitted.</p> + + <p>Current testing is done on TCP over IPv4. Timeouts can be + limited by global sysctls and an application can choose how to + send or accept timeout values via socket options. In addition to + regression tests, support has been added to telnet, ssh and + netcat.</p> + </body> + + <help> + <task>Regression tests for TCP over IPv6.</task> + + <task>Add support to more userland applications.</task> + + <task>Implement strategies and regression tests to handle and + simulate DoS scenarios.</task> + </help> + </project> + + <project cat='ports'> + <title>Portbuilder</title> + + <contact> + <person> + <name> + <given>David</given> + <common>Naylor</common> + </name> + <email>naylor.b.david@gmail.com</email> + </person> + </contact> + + <links> + <url href="https://github.com/DragonSA/portbuilder">GIT + Repository</url> + + <url href="https://github.com/DragonSA/portbuilder/blob/0.1.3/README"> + README</url> + + <url href="https://github.com/DragonSA/portbuilder/blob/0.1.3/TODO"> + TODO</url> + </links> + + <body> + <p>I would like to introduce a project that has been in the works + for the last 3 years. From the projects README:</p> + + <p>A concurrent ports building tool. Although &os; ports + supports building a single port using multiple jobs (via + MAKE_JOBS), it cannot build multiple ports concurrently. This tool + accomplishes just that.</p> + + <p>Some of its key features:</p> + + <ul> + <li>Concurrent port building</li> + <li>Load control</li> + <li>Top like UI</li> + <li>Persistent builds (by default)</li> + </ul> + + <p>Portbuilder originally used threads to control each port at each + stage of the build however the required locks resulting in + deadlocks, and some ports would not build correctly. To resolve + those issues a rewrite was done to use only a single thread, making + all locking code redundant. Thanks to the use of kqueue(2) the + overhead of managing concurrent port builds is minimal. Further + work to reduce that overhead is underway.</p> + + <p>Portbuilder is installable from ports under + ports-mgmt/portbuilder, see the README for usage details. Please + note that this is considered BETA quality, that the feature set and + API are expected to change, and that portbuilder may crash or fail + to behave properly.</p> + </body> + + <help> + <task>Wiki page.</task> + + <task>Testing.</task> + + <task>See TODO.</task> + </help> + </project> + + <project cat='net'> + <title>IPv6 RA Handling Improvements</title> + + <contact> + <person> + <name> + <given>Hiroki</given> + <common>Sato</common> + </name> + <email>hrs@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>ICMPv6 Router Advertisement (RA) message is a part of IPv6 + Neighbor Discovery Protocol in RFC 4861 and takes an important role + in IPv6 basic functionality. &os; supports it in the kernel, and + the rtadvd(8) and rtsold(8) programs derived from KAME project + handle it in userland.</p> + + <p>This small project aims to improve the current RA handling by + removing limitations and adding new functionality found in the + latest RFCs. Changes committed are as follows:</p> + + <ul> + <li>&os; now supports RA receiving even if + net.inet6.ip6.forwarding=1 and enabling/disabling the receiving + in a per-interface basis. The traditional "host" and "router" + node model in IPv6 RFCs is translated into a concept of + "RA-receiving interfaces" and "RA-sending interfaces" in + &os; 9.0 or later, not depending only on system-wide IP + forwarding capability. This is useful for a system with + multiple IPv6-capable interfaces (such as a customer-edge + router) which require SLAAC (Stateless Address + Autoconfiguration) feature described in RFC 4862.</li> + + <li>The rtadvd(8) and rtsold(8) programs now support IPv6 Router + Advertisement Options for DNS Configuration in RFC 6106. This + enables updating /etc/resolv.conf by using RAs.</li> + + <li>The rtadvd(8) daemon now supports dynamically-added/removed + interfaces. Although it was needed that all of RA-sending + interfaces exist before the daemon was invoked, the new version + no longer requires it. When a new interface arrived, it will be + configured on the fly.</li> + + <li>The rtadvctl(8) utility has been added. This displays + RA-sending status on each interface and provides a way to + control the daemon. This utility makes system administration + much easier.</li> + </ul> + + <p>All of the changes described above have already been committed + to 9-CURRENT and a part of them will be merged to 8-STABLE.</p> + </body> + </project> + + <project cat='net'> + <title>DIstributed Firewall and Flow-shaper Using Statistical + Evidence (DIFFUSE)</title> + + <contact> + <person> + <name> + <given>Sebastian</given> + <common>Zander</common> + </name> + <email>szander@swin.edu.au</email> + </person> + + <person> + <name> + <given>Grenville</given> + <common>Armitage</common> + </name> + <email>garmitage@swin.edu.au</email> + </person> + </contact> + + <links> + <url href="http://caia.swin.edu.au/urp/diffuse/" /> + <url href="http://caia.swin.edu.au/urp/diffuse/downloads.html" /> + </links> + + <body> + <p>DIFFUSE is a system enabling &os;'s IPFW firewall subsystem + to classify IP traffic based on statistical traffic properties.</p> + + <p>With DIFFUSE, IPFW computes statistics (such as packet lengths + or inter-packet time intervals) for observed flows, and uses ML + (machine learning) to classify flows into classes. In addition to + traditional packet inspection rules, IPFW rules may now also be + expressed in terms of traffic statistics or classes identified by + ML classification. This can be helpful when direct packet + inspection is problematic (perhaps for administrative reasons, or + because port numbers do not reliably identify applications).</p> + + <p>DIFFUSE also enables one instance of IPFW to send flow + information and classes to other IPFW instances, which then can act + on such traffic (e.g. prioritise, accept, deny, etc.) according to + its class. This allows for distributed architectures, where + classification at one location in your network is used to control + fire-walling or rate-shaping actions at other locations.</p> + + <p>The DIFFUSE prototype is a set of patches for &os;-CURRENT + that can be downloaded from the project's web site. The web site + also contains a more comprehensive introduction, as well as links + to related work and documentation.</p> + + <p>In July 2011, we released DIFFUSE v0.4. This release contains a + number of bug fixes and new features. Most notably we improved the + functionality of the tools used for training classification models, + and performing offline analysis.</p> + + <p>DIFFUSE v0.4 is the last release, as the DIFFUSE project has + concluded. However, we may release bug fixes in the future if + necessary.</p> + </body> + </project> + + <project cat="kern"> + <title>Status Report for NFS</title> + + <contact> + <person> + <name> + <given>Rick</given> + <common>Macklem</common> + </name> + <email>rmacklem@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The new NFS client and server are no longer considered + experimental and will most likely be the default for &os; 9.0. + Included is support for NFSv4.0 as well as NFSv3 and NFSv2. The + NFSv4.0 support was tested at a recent NFSv4 Interoperability + Bakeathon held at CITI of the University of Michigan. Also tested + at the Bakeathon was a basic client implementation of NFSv4.1 which + will soon be available as a test patch against the &os; 9.0 + kernel sources. If you are interested in testing NFSv4.1, stay + tuned to the freebsd-fs@FreeBSD.org mailing list. + zkirsch@FreeBSD.org and friends will be taking on a majority of the + NFSv4 server work while I concentrate on the client, with hopes + that the NFSv4.1 support will mature over the next year or so.</p> + + <p>I will also be making a patch for an experimental aggressive + client side on-disk caching mechanism for NFSv4 I call Packrats + available. An announcement about this will be made on + freebsd-fs@FreeBSD.org as well.</p> + </body> + </project> + + <project cat='proj'> + <title>ZFS pool version 28</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + <common>Dawidek</common> + </name> + <email>pjd@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Martin</given> + <common>Matuska</common> + </name> + <email>mm@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>ZFS pool version 28 has been merged into 8-STABLE as of + June 6, 2011. In addition, several bugfixes and improvements + from the Illumos project have been imported.</p> + </body> + + <help> + <task>Investigation of ZFS problem reports.</task> + </help> + </project> + + <project cat='proj'> + <title>libarchive, bsdtar, bsdcpio</title> + + <contact> + <person> + <name> + <given>Tim</given> + <common>Kientzle</common> + </name> + <email>kientzle@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Michihiro</given> + <common>Nakajima</common> + </name> + <email>ggcueroad@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://code.google.com/p/libarchive" /> + </links> + + <body> + <p>Libarchive, bsdtar and bsdcpio in 9-CURRENT have been updated to + version 2.8.4 (thanks to mm@FreeBSD.org) and bsdtar now supports + extracting XAR and RPM archive formats.</p> + + <p>There is ongoing development in trunk with many improvements + including support for new formats both on the read (e.g. cab, lha, + rar) and write parts (e.g. iso9660, xar).</p> + </body> + </project> + + <project cat='net'> + <title>&os; IPv6-only Support</title> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + <common>Zeeb</common> + </name> + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSDFoundation.org/project%20announcements.shtml#Bjoern"> + &os; Foundation project announcement</url> + + <url href="http://www.ixsystems.com/ix/media/freebsd-foundation-and-ixsystems-announce-ipv6-only-testing-versions-of-freebsd-and-pc-bsd"> + &os; Foundation and iXsystems press release</url> + + <url href="http://www.FreeBSD.org/ipv6/ipv6only.html">&os; + IPv6-only Support</url> + + <url href="http://www.pcbsd.org/IPv6">PC-BSD IPv6</url> + </links> + + <body> + <p>As a follow-up work to the no-IP kernel, a &os; IPv6-only + prototype kernel was build beginning of 2010. This work was now + carried on and merged to mainstream &os; and will be part of the + upcoming 9.0-RELEASE allowing for custom no-IPv4 kernels to be + built. In addition IPv6 installation and configuration support for + &os; and PC-BSD were improved.</p> + + <p>An IPv6-only kernel and continued efforts to build world without + IPv4, like &os; had supported compiling out IPv6 for a long + time, will allow easier IPv6 validation work to happen. This will + not only help &os; or &os;-derived commercial product + builders but we are also hoping to motivate other Open Source + projects to test their software for IPv6-readiness on &os; or + PC-BSD.</p> + + <p>We have provided and will continue to provide IPv6-only + snapshots for &os;. In IPv6-only PC-BSD snapshots have been + released to provide a great Open Source desktop environment to test + GUI applications for IPv6-readiness as well.</p> + + <p>I would like to thank the &os; Foundation and iXsystems for their + support of the project, as well as George Neville-Neil for + providing review and Kris Moore for helping on the PC-BSD + integration and building and providing the PC-BSD snapshots.</p> + </body> + </project> + + <project cat='gsoc'> + <title>Google Summer of Code</title> + + <contact> + <person> + <name> + <given>Brooks</given> + <common>Davis</common> + </name> + <email>brooks@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Robert</given> + <common>Watson</common> + </name> + <email>rwatson@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/SummerOfCode2011">Summer of Code + 2011 Project Wiki Pages</url> + </links> + + <body> + <p>We are happy to be participating in our 7th Google Summer of + Code. After the mid-term evaluation we have 15 projects working + towards the final evaluation. You can see the latest status on + student's individual wiki pages or by subscribing to the soc-status + mailing list.</p> + </body> + </project> + + <project cat='ports'> + <title>Chromium</title> + + <contact> + <person> + <name> + <given>Chromium on &os; Team</given> + </name> + <email>chromium@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.chromium.org/Home">Main project site</url> + + <url href="http://trillian.chruetertee.ch/chromium">&os; + porting site</url> + </links> + + <body> + <p>During the last quarter we have been keeping the Chromium + browser up to date, with new major releases being imported into the + Ports Collection the same day as the upstream release. As time + passes by, more patches are incorporated or otherwise became + obsolete by virtue of upstream code cleanups. Version 13 is already + available from the Chruetertee repository, with 70 patches + less than version 12.</p> + </body> + </project> + + <project cat='kern'> + <title>Overhaul of the mii(4)-subsystem</title> + + <contact> + <person> + <name> + <given>Marius</given> + <common>Strobl</common> + </name> + <email>marius@FreeBSD.org</email> + </person> + </contact> + + <links> + </links> + + <body> + <p>The mii(4)-subsystem has been overhauled and fixes and + enhancements from NetBSD/OpenBSD since mii(4) originally has been + ported over have been merged. As a result a lot of code duplication + and hacks have been removed from the PHY drivers and we are now + able again to share the miidevs file with NetBSD. Due to KPI + breakages the majority of this work will not be merged back into + 8-STABLE and earlier.</p> + + <p>Additionally shorthand aliases for common media+option combinations + as announced by mii(4) have been added to the ifmedia code so that + now one can actually supply the media strings found in the dmesg + output to ifconfig(8). Support for this will be merged back to + 8-STABLE prior to 8.3-RELEASE.</p> + </body> + </project> + + <project cat='arch'> + <title>&os;/sparc64</title> + + <contact> + <person> + <name> + <given>Marius</given> + <common>Strobl</common> + </name> + <email>marius@FreeBSD.org</email> + </person> + </contact> + + <body> + <ul> + <li>The iommu(4) driver has been changed to take advantage of + the streaming buffers of the host-PCI and host-SBus bridges if + present, which in at least some configurations results in a + modest performance improvement due to the caching of DMA + transactions. As a prerequisite, the bus_dma(9) usage of all + drivers compiled as part of the sparc64 GENERIC kernel has been + reviewed and fixed and in case of sound(4) and sym(4) at least + worked around as necessary in order to be able to use the + streaming buffers. + <br /> + + Support for this will be merged back to 8-STABLE prior to + 8.3-RELEASE.</li> + + <li>Following the update of the in-tree binutils to 2.17.50, + which now for the first time include support for GNUTLS on + sparc64 in the base, support for TLS relocations on sparc64 was + added to rtld(1) and enabled in the base GCC and + malloc(3).</li> + + <li>Support and a workaround necessary for Sun Fire V890 + equipped with UltraSPARC-IV was added. + <br /> + + Support for these will be merged back to 8-STABLE prior to + 8.3-RELEASE.</li> + + <li>The schizo(4) driver has been updated to also support the + XMITS Fireplane/Safari to PCI-X bridges and a workaround for + Casinni/Skyhawk combinations has been added. Chances are that + the latter solves the crashes seen when using the the on-board + Casinni NICs of Sun Fire V480 equipped with centerplanes other + than 501-6780 or 501-6790. + <br /> + + These changes have been merged back to 8-STABLE and will be + part of 8.3-RELEASE.</li> + + <li>As part of the largeSMP project which had the goal of + supporting more than 32 CPU cores in &os; several parts of + the sparc64 specific code had to be adapted mainly in the + assembler bits but as a result now also supports more than 32 + CPU cores.</li> + + <li>On machines where we do not need to lock the kernel TSB + into the dTLB and thus may basically use the entire 64-bit + kernel address space, i.e. on machines equipped with + UltraSPARC-III+ and greater CPUs, the kernel virtual memory was + increased to not be limited by VM_KMEM_SIZE_MAX and + VM_KMEM_SIZE_SCALE decreased to 1 allowing kernel to use more + memory as for example useful for ZFS. + <br /> + + These changes will be merged back to 8-STABLE prior to + 8.3-RELEASE.</li> + + <li>The shortcut taken in the code responsible for flushing + user mappings from the TLBs of UltraSPARC-III and greater CPUs + turned out to not scale well on MP-systems with more than 8 CPU + cores and thus was re-written. As a result it now scales up to + at least 16-way machines. + <br /> + + These changes will be merged back to 8-STABLE prior to + 8.3-RELEASE.</li> + </ul> + </body> + </project> + + <project cat="docs"> + <title>The &os; Japanese Documentation Project</title> + + <contact> + <person> + <name> + <given>Hiroki</given> + <common>Sato</common> + </name> + <email>hrs@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ryusuke</given> + <common>Suzuki</common> + </name> + <email>ryusuke@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ja/">Japanese &os; Web + Pages</url> + + <url href="http://www.jp.FreeBSD.org/doc-jp/">The &os; Japanese + Documentation Project Web Page</url> + </links> + + <body> + <p>The www/ja and doc/ja_JP.eucJP/books/handbook subtrees have + constantly been updated. During this period, many part of out-dated + contents in the www/ja subtree were updated to the latest versions + in the English counterpart. Thus most of the files in the subtree + are already synchronized with www/en at this moment, and this + updating work will be finished within this year.</p> + + <p>For &os; Handbook, translation work for the kernelconfig section + was just started. In addition, we are planning to translate the + upcoming release announcement because it is also important for + Japanese people.</p> + </body> + + <help> + <task>Further translation work for outdated and/or non-translated + documents in both doc/ja_JP.eucJP and www/ja.</task> + </help> + </project> + + <project cat='ports'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Thomas</given> + <common>Abthorpe</common> + </name> + <email>portmgr-secretary@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Port</given> + <common>Management Team</common> + </name> + <email>portmgr@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ports/" /> + <url href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" /> + <url href="http://portsmon.FreeBSD.org/index.html" /> + <url href="http://www.FreeBSD.org/portmgr/index.html" /> + <url href="http://blogs.FreeBSDish.org/portmgr/" /> + <url href="http://www.twitter.com/freebsd_portmgr/" /> + <url href="http://www.facebook.com/group.php?gid=135441496471197" /> + <url href="http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-baptiste-daroussin.html" /> + <url href="http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-julien-laffaye.html" /> + <url href="http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-thomas-abthorpe.html" /> + <url href="http://blogs.FreeBSDish.org/portmgr/2011/05/26/thankyoufoundation/" /> + </links> + + <body> + <p>The ports tree slowly moves up closer to 23,000. The PR count + still remains at about 1100.</p> + + <p>In Q2 we added 3 new committers, took in 2 commit bits for safe + keeping, and added a new member to portmgr.</p> + + <p>The Ports Management team have been running -exp runs on an + ongoing basis, verifying how base system updates may affect the + ports tree, as well as providing QA runs for major ports updates. + Of note, -exp runs were done for:</p> + + <ul> + <li>ports/154044, -exp run to update x11-toolkits/open-motif</li> + + <li>ports/155269, -exp run to fix problem with base/ports + ncurses</li> + + <li>ports/155215, -exp run to update gmake, completed by + linimon</li> + + <li>ports/156575, -exp run to generate a subset of ports in + INDEX</li> + + <li>ports/155983, -exp run to reroot md5 in /sbin</li> + + <li>ports/139116, -exp run to call target "install-rc-script" + before "post-install"</li> + + <li>ports/155510, -exp run to remove support for pre 7.X</li> + + <li>ports/156533, -exp run to patch bsd.apache.mk</li> + + <li>ports/152498, -exp run to improve USERS/GROUPS handling</li> + + <li>flz has been performing clang -exp runs</li> + + <li>erwin performed -exp run for perl 5.12.4 update</li> + + <li>pav performed multiple -exp runs for gtk3</li> + </ul> + </body> + + <help> + <task>Looking for help getting + <a href="http://wiki.FreeBSD.org/PortsAndClang">ports to build with + clang</a>.</task> + + <task>Looking for help fixing <a + href="http://wiki.FreeBSD.org/PortsBrokenOnCurrent">ports broken + on CURRENT</a>. (List needs updating, too)</task> + + <task>Looking for help with <a + href="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures"> + Tier-2 architectures</a>. (List needs updating, too)</task> + + <task>Most ports PRs are assigned, we now need to focus on testing, + committing, and closing.</task> + </help> + </project> + + <project cat='gsoc'> + <title>Capsicum adaptation and core libraries</title> + + <contact> + <person> + <name> + <given>Ilya</given> + <common>Bakulin</common> + </name> + <email>kibab@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.cl.cam.ac.uk/research/security/capsicum" /> + <url href="http://wiki.FreeBSD.org/SOC2011IlyaBakulin" /> + </links> + + <body> + <p>Some applications from the base system received sandboxing + support, current task is to adapt lightweight resolver daemon for + using it in sandboxes — this fixes problems with applications that + need to convert IP addresses into domain names while in + sandbox.</p> + </body> + + <help> + <task>Add sandboxing to even more applications in the base + system.</task> + + <task>Help Jonathan Anderson and Robert Watson to merge + &os;-Capsicum into &os;-HEAD.</task> + </help> + </project> + + <project cat='ports'> + <title>&os; Haskell Ports</title> + + <contact> + <person> + <name> + <given>Gábor János</given> + <common>PÁLI</common> + </name> + <email>pgj@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ashish</given> + <common>SHUKLA</common> + </name> + <email>ashish@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Giuseppe</given> + <common>Pilichi</common> + </name> + <email>jacula@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/Haskell">&os; Haskell wiki + page</url> + + <url href="https://github.com/freebsd-haskell/freebsd-haskell/"> + &os; Haskell ports repository</url> + + <url href="http://haskell.org/mailman/listinfo/freebsd-haskell/"> + &os; Haskell mailing list</url> + </links> + + <body> + <p>We are proud to announce that the &os; Haskell Team has + committed Haskell Platform 2011.2.0.1 to the &os; Ports Collection, + as well as updated existing ports to their latest stable versions. + Apart from the ports officially available there, many ports (Snap + web framework, Leksah, and their dependencies) are still waiting to + be added. Any users who like to get early access to them, please + refer to the instructions at <a + href="https://github.com/freebsd-haskell/freebsd-haskell/">our + development repository</a>.</p> + </body> + + <help> + <task>Update Haskell Platform (along with GHC) to 2011.4.0.0 as + soon as it gets out.</task> + + <task>Add more ports to the Ports Collection.</task> + + <task>Create a port for Happstack.</task> + + <task>Create a port for gitit.</task> + </help> + </project> + + <project cat='net'> + <title>netmap</title> + + <contact> + <person> + <name> + <given>Luigi</given> + <common>Rizzo</common> + </name> + <email>rizzo@iet.unipi.it</email> + </person> + </contact> + + <links> + <url href="http://info.iet.unipi.it/~luigi/netmap/" /> + </links> + + <body> + <p>netmap is a novel framework to achieve wire-speed packet + processing in &os;, while retaining the safety and richness of + features provided by the user space environment, and using only + standard system calls. With netmap, it takes as little as 70 clock + cycles to move one packet between the user program and the wire. As + an example, a single core running at 900MHz can generate the + 14.8Mpps that saturate a 10GigE interface. This is a 5-10x + improvement over the use of a standard device driver. netmap is + implemented with a relatively small kernel device driver (less than + 2000 lines of code), plus individual network card patches (300-500 + lines each; currently supported are Intel 1 and 10 Gbit cards, and + RealTek 1 Gbit cards). No special user libraries are needed, + although we have a small libpcap-over-netmap which enables the use + of existing applications on top of the new API with no source or + binary modifications. The netmap home page contains a more detailed + description of the project, source code, papers and slides.</p> + </body> + </project> + + <project cat='kern'> + <title>Intel GPU Driver</title> + + <contact> + <person> + <name> + <given>Konstantin</given> + <common>Belousov</common> + </name> + <email>kib@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/Intel_GPU" /> + </links> + + <body> + <p>The &os; Foundation sponsored project to port the Linux + kernel-mode driver for Intel GPU progressed to the point where some + machines can use Xorg with ddx driver from the git head and latest + Mesa. On my test machine I was able to run uhexen2 and + ioquake3.</p> + + <p>Nonetheless, the driver is still in the early stages of + debugging. Read the wiki page for more details, guidelines on + installation and initial bug analysis.</p> + + <p>Main efforts right now are directed on getting the required VM + changes into the base system, ideally before 9.0 is released.</p> + </body> + </project> + + <project cat='docs'> + <title>The &os; Dutch Documentation Project</title> + + <contact> + <person> + <name> + <given>Remko</given> + <common>Lodder</common> + </name> + <email>remko@FreeBSD.org</email> + </person> + + <person> + <name> + <given>René</given> + <common>Ladan</common> + </name> + <email>rene@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/DutchDocumentationProject">Wiki + Page</url> + + <url href="http://p4web.freebsd.org/@md=d&cd=//depot/projects/&c=Hid@//depot/projects/docproj_nl/?ac=83"> + Perforce repository</url> + </links> + + <body> + <p>During the last period most work went into keeping the Handbook + up to date; it is currently up-to-date except for a section on + network servers. Other areas being worked on are the FAQ and the + web site. The latter two are still a work-in-progress.</p> + </body> + + <help> + <task>Volunteers! The best part is that you do not need to be an + expert on &os; nor the Dutch language to join, just some + enthusiasm and spare time.</task> + </help> + </project> + + <project cat='arch'> + <title>&os;/powerpc64 on IBM pSeries machines</title> + + <contact> + <person> + <name> + <given>Nathan</given> + <common>Whitehorn</common> + </name> + <email>nwhitehorn@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Andreas</given> + <common>Tobler</common> + </name> + <email>andreast@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="svn://svn.FreeBSD.org/base/projects/pseries/"> + Development Branch</url> + </links> + + <body> + <p>The goal of this project is to make &os; running on PAPR + compliant machines like the IBM pSeries family.</p> + + <p>Currently we can boot a POWER7 emulation under a recent qemu + snapshot.</p> + + <p>The boot process stops when trying to find a PIC.</p> + + <p>The same applies for an IntelliStation-285. (POWER5+).</p> + </body> + + <help> + <task>Implement interrupt controller.</task> + <task>PCI bus scanning.</task> + <task>Drivers, drivers, drivers.</task> + <task>Improve memory management.</task> + </help> + </project> + + <project cat='net'> + <title>New ipfw features</title> + + <contact> + <person> + <name> + <given>Vadim</given> + <common>Goncharov</common> + </name> + <email>vadim_nuclight@mail.ru</email> + </person> + </contact> + + <links> + <url href="http://svnweb.FreeBSD.org/base?view=revision&revision=223666" /> + </links> + + <body> + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+9.0-RELEASE"> + ipfw(4)</a> packet filter now supports <tt>call</tt> + and <tt>return</tt> rule actions. When a packet matches a rule + with the <tt>call</tt> action, the rule number is saved in the + internal stack and rules processing continues from the first + rule with specified number (similar to <tt>skipto</tt> action, + but backward jumps are allowed). If later a rule with + <tt>return</tt> action is encountered, the processing returns to + the first rule with number greater than the number saved in the + internal stack. This makes it possible to organize "subroutines" + with rules, e.g. to call one subroutine several times from + different places in the ruleset. For more details, see <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=8&manpath=FreeBSD+9.0-RELEASE&format=html"> + ipfw(8)</a>.</p> + </body> + </project> + + <project cat='ports'> + <title>KDE-&os;</title> + + <contact> + <person> + <name> + <given>KDE</given> + <common>&os;</common> + </name> + <email>kde-freebsd@kde.org</email> + </person> + </contact> + + <links> + <url href="http://FreeBSD.kde.org">KDE-&os; home page</url> + + <url href="http://dot.kde.org/2011/06/29/platform-frameworks-kde-hackers-meet-switzerland"> + Dot article on the KDE sprints in Switzerland</url> + + <url href="http://blogs.FreeBSDish.org/avilla/2011/06/14/call-for-tests-kde-pim-4-6-0"> + Call for test of KDE PIM 4.6.0</url> + + <url href="http://FreeBSD.kde.org/area51.php">area51 + Switzerland</url> + </links> + + <body> + <p>Alberto Villa and Raphael Kubo da Costa went to Randa, + Switzerland, to attend, respectively, the KDE Multimedia/Kdenlive + sprint and the Platform 11 sprint. The sprints afforded them the + opportunity to form closer bonds with the upstream KDE community, + to learn about the future of Qt and KDE and make sure &os;'s + needs are taken into account. For more information see the article + "From Platform to Frameworks -- KDE hackers meet in Switzerland" at + dot.kde.org.</p> + + <p>The KDE on &os; team have continued to improve the experience + of KDE and Qt under &os;. The latest round of improvements + include:</p> + + <ul> + <li>Qt supports Clang as a compiler</li> + </ul> + + <p>The team has also made many releases and upstreamed many fixes + and patches. The latest round of releases include:</p> + + <ul> + <li>Qt: 4.7.3</li> + <li>KDE: 4.6.3; 4.6.4; 4.6.5</li> + <li>Amarok: 2.4.1</li> + <li>Digikam (and KIPI-plugins): 1.9.0</li> + </ul> + + <p>Further testing is requested for KDE PIM 4.6.0 and Calligra + 2.3.72 before the ports are committed. To test the ports please + visit Alberto Villa's call for test and area51.</p> + + <p>The team is always looking for more testers and porters so + please visit us at kde-freebsd@kde.org and our homepage.</p> + </body> + + <help> + <task>Testing KDE PIM 4.6.0.</task> + </help> + </project> + + <project cat='team'> + <title>The &os; Foundation</title> + + <contact> + <person> + <name> + <given>Deb</given> + <common>Goodkin</common> + </name> + <email>deb@FreeBSDFoundation.org</email> + </person> + </contact> + + <links> + <url href="www.FreeBSDFoundation.org" /> + </links> + + <body> + <p>We were a proud sponsor of BSDCan. We also sponsored 6 + developers to attend the conference. And, we brought in over + $1,000 in donations! The Foundation was also represented at + FlourishConf in Chicago, IL and SouthEast LinuxFest in + Spartanburg, SC.</p> + + <p>We acquired a non-exclusive copyright license to the <a + href="http://www.FreeBSDFoundation.org/press/Pathscale-PRrelease.shtml"> + libcxxrt C++ runtime</a> software from PathScale.</p> + + <p>Sponsored a project to create an <a + href="http://www.FreeBSDFoundation.org/press/IPv6%20Day-PRrelease.shtml"> + IPv6-only version</a> of &os; and PC-BSD.</p> + + <p>We're pleased announce the addition of Ed Maste to our Board + of Directors. Ed has been involved with &os; since 2003. And, + has been a committer since 2005. Ed leads the OS team at Sandvine + and is responsible for a number of developers who bring + enhancements from &os; into Sandvine's OS and contribute their + own changes back to &os;.</p> + + <p>We continued our work on infrastructure projects to beef up + hardware for package-building, network-testing, etc. This + includes purchasing equipment as well as managing equipment + donations. In fact we just placed an order for a 80-core server + for SMP performance work.</p> + + <p>Stop by and visit with us at Ohio LinuxFest, Columbus, OH, on + September 10.</p> + + <p>The work above, as well as many other tasks we do for the + project, couldn't be done without donations. Please help us by + making a donation or asking your company to make a donation. We + would be happy to send marketing literature to you or your + company. Find out how to make a donation at <a + href="http://www.FreeBSDFoundation.org/donate/"> + http://www.FreeBSDFoundation.org/donate/</a>.</p> + + <p>Find out more up-to-date Foundation news by reading our + <a href="http://FreeBSDFoundation.blogspot.com/">blog</a> + and <a + href="https://www.facebook.com/FreeBSDFoundation">Facebook + page</a>.</p> + </body> + </project> + + <project cat='kern'> + <title>OpenAFS port</title> + + <contact> + <person> + <name> + <given>Benjamin</given> + <common>Kaduk</common> + </name> + <email>kaduk@mit.edu</email> + </person> + + <person> + <name> + <given>Derrick</given> + <common>Brashear</common> + </name> + <email>shadow@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://openafs.org">OpenAFS home page</url> + <url href="http://wiki.FreeBSD.org/afs">&os; Wiki on AFS</url> + </links> + + <body> + <p>AFS is a distributed network filesystem that originated from the + Andrew Project at Carnegie-Mellon University. Since our last + report, upstream OpenAFS has updated to a 1.6.0pre6 release + candidate, which is available in the &os; Ports Collection. We + still expect the upcoming 1.6.0 release to be usable for regular + client workloads (though not heavy load). We have also made + progress on integration with the bsd.kmod.mk kernel-module-building + infrastructure, with a working prototype implementation. Further + cleanup and testing is needed before it is ready to be + committed.</p> + + <p>There are several known outstanding issues that are being worked + on, but detailed bug reports are welcome at + port-freebsd@openafs.org.</p> + </body> + + <help> + <task>Update VFS locking to allow the use of disk-based client + caches as well as memory-based caches.</task> + + <task>Track down races and deadlocks that may appear under + load.</task> + + <task>Integrate with the bsd.kmod.mk kernel-module build + infrastructure.</task> + + <task>Eliminate a moderate memory leak from the kernel + module.</task> + + <task>PAG (Process Authentication Group) support is not + functional.</task> + </help> + </project> + + <project cat='proj'> + <title>Fix clang warnings</title> + + <contact> + <person> + <name> + <given>Ben</given> + <common>Laurie</common> + </name> + <email>benl@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>In order to assist with the process of moving away from gcc, + while I learn the ropes of being a contributor, I am + systematically fixing clang warnings, so we can turn on -Werror + again.</p> + + <p>Down from > 42,000 warnings at the end of May to < 9,000 + warnings now.</p> + </body> + + <help> + <task>Always happy if someone else finds and fixes a + warning!</task> + </help> + </project> + + <project cat='gsoc'> + <title>nvi-iconv</title> + + <contact> + <person> + <name> + <given>Zhihao</given> + <common>Yuan</common> + </name> + <email>lichray@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/zy/1"> + Project proposal</url> + + <url href="https://github.com/lichray/nvi2">GitHub page</url> + </links> + + <body> + <p>This project creates a multibyte aware nvi fork. While most of + the userland tools in the &os; base system support multibyte + encodings, there is no pure-licensed nvi fork comes with + sufficient multibyte encoding (both Unicode and non-Unicode) + support prior to this.</p> + + <p>Currently, functionally, the new nvi is ready for testing. The + description is at https://github.com/lichray/nvi2/wiki (the patch + is deprecated). I will commit a new one latter.</p> + + <p>The features dropped from nvi-1.79 are:</p> + + <ul> + <li>Perl and Tcl interpreter supports;</li> + + <li>The whole Perl/Tcl/Tk scripting framework;</li> + + <li>A third-party gtags support.</li> + </ul> + + <p>and the features adopted from nvi-1.81.6 includes:</p> + + <ul> + <li>Multibyte encoding supports (wchar_t + libiconv + + libncursesw);</li> + + <li>fileencoding and inputencoding options;</li> + + <li>Undocumented :vsplit command, which vertically splits the + screen.</li> + </ul> + + <p>Many known bugs, incomplete code from nvi-devel are fixed. + However, I find a serious memory leaking (via valgrind) in the + nvi-devel iconv framework. This requires a careful review.</p> + </body> + + <help> + <task>Reviews the iconv part and fixes the memory leak.</task> + + <task>Ex scripts for testing. But it seems that I have no + experience on that...</task> + + <task>File encoding detection. My plan it to detect UTF-16 BOM + first, then UTF-8. If all fails, uses locale. UTF-8 BOM is not + supported by iconv, and we need to discuss whether we should + support it in the editor.</task> + </help> + </project> + + <project cat='proj'> + <title>Clang replacing GCC in the base system</title> + + <contact> + <person> + <name> + <given>Dimitry</given> + <common>Andric</common> + </name> + <email>dim@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Roman</given> + <common>Divacky</common> + </name> + <email>rdivacky@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Brooks</given> + <common>Davis</common> + </name> + <email>brooks@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Pawel</given> + <common>Worach</common> + </name> + <email>pawel.worach@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" /> + <url href="http://wiki.FreeBSD.org/PortsAndClang" /> + </links> + + <body> + <p>We imported newer snapshot of clang/llvm. This features quite + a lot of goodies. Most notably there's a new register + allocator that brings much better runtime performance. If you + did a performance evaluation of clang/llvm in the past now + it's the time to rerun it with the new register allocator!</p> + + <p>There was some progress on Mips and PowerPC in addition to + the usual influx of improvements on ARM, i386 and amd64. We've + managed to get clang compiled arm kernel booting. ARM world is + blocked by &os; using old ARM ABI.</p> + + <p>We got a buildbot that periodically builds clang/llvm on + &os; and &os; (amd64 and i386) using clang/llvm, including + booting the resulting image.</p> + + <p>We ran a few ports exp runs and got many ports bugs fixed so + right now we're able to build more than 15000 ports with + clang. We expect this number to grow rapidly as the problems + are mostly trivial.</p> + </body> + + <help> + <task>Fix your ports.</task> + + <task>Performance evaluate the new clang/llvm.</task> + + <task>Fix clang warnings in src.</task> + + <task>Implement proper support for cross compiling.</task> + </help> + </project> + + <project cat='arch'> + <title>&os; on the Sony Playstation 3</title> + + <contact> + <person> + <name> + <given>Nathan</given> + <common>Whitehorn</common> + </name> + <email>nwhitehorn@freebsd.org</email> + </person> + </contact> + + <links> + <url href="http://people.freebsd.org/~nwhitehorn/ps3/" /> + </links> + + <body> + <p>The &os; Playstation 3 port is now fairly mature and will be + included in the 9.0 release, starting with BETA2. Most internal + devices, including the USB ports, bluetooth, ethernet, and SATA + devices are now supported, and the operating system can be + installed to and boot from the internal hard disk.</p> + + <p>There are several remaining pieces to the port (Wireless, + Sound, X11, and the SPUs), which may be interesting + projects for those interested in non-PC architectures.</p> + </body> + + <help> + <task>Built-in wireless. The 802.11 wireless interface on the + Playstation 3 is multiplexed through the wired ethernet MAC and + is currently unsupported.</task> + + <task>The sound hardware is not currently supported.</task> + + <task>The framebuffer driver does not currently support X11. + This would involve writing a simple X11 framebuffer driver to + connect to syscons.</task> + + <task>The synergistic processing units (SPUs) on the Cell + processor are not supported yet. They present an interesting + model of heterogeneous computing, more suited for full treatment + by a UNIX-type kernel than GPGPU computing: each SPU has a + concept of user and supervisor mode, as well as interrupts, and + can share MMU context with the main CPU cores. As such, they in + principle can support a full UNIX process model.</task> + </help> + </project> + + <project cat='ports'> + <title>libvirt networking port</title> + + <contact> + <person> + <name> + <given>Jason</given> + <common>Helfman</common> + </name> + <email>jhelfman@experts-exchange.com</email> + </person> + + <person> + <name> + <given>Daniel P.</given> + <common>Berrange</common> + </name> + <email>berrange@redhat.com</email> + </person> + </contact> + + <links> + <url href="http://www.libvirt.org/" /> + </links> + + <body> + <p>Libvirt, a Toolkit to interact with virtualization + capabilities, has been ported to &os;, however the networking + capabilities have been disabled as they are incompatible with + &os;. Libvirt currently supports connecting to many types of + hypervisors, however it can be a far more useful tool if the + networking capabilities were ported to &os;.</p> + + <p>In contacting Daniel P. Berrange, he was kind enough to + advise on what is required to port networking of libvirt to + &os;. His response is paraphrased below:</p> + + <p>There are two aspects to networking in libvirt:</p> + + <ul> + <li>The virtual network driver (in + src/network/bridge_driver.c) uses the Linux kernel's + native 'bridge' functionality to provide an isolated, or + routed, or NATed network connection to guests. There is a + bridge device on the host created, and guest TAP devices are + added to it. There is no physical ethernet device added to the + bridge, and iptables is used to control whether the host OS + routes traffic to/from the bridge & physical LAN.<br/> + Porting bridge and bridge control functionality to &os; + would need to be done, and how to nat/routed/isolated guest + configs and write a compatible version of bridge_driver.c + for &os;.</li> + + <li>The host interface driver (in src/inteface/netcf_driver.c) + uses the netcf library to manage configuration of host network + interfaces to do things like bonding, vlans, bridging and controlling + the interfaces availability. The core job is to port netcf to work + with &os;. A netcf backend that understands &os;'s networking + configuration files and calls appropriate tools to bring + interfaces online/offline would need to be created.</li> + </ul> + + <p>Both these jobs are pretty much independent, so can easily be + done in parallel.</p> + </body> + + <help> + <task>Port bridge network driver for libvirt.</task> + + <task>Port netcf driver for libvirt.</task> + </help> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2011-07-2011-09.xml b/en_US.ISO8859-1/htdocs/news/status/report-2011-07-2011-09.xml new file mode 100644 index 0000000000..5680ce3b1d --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2011-07-2011-09.xml @@ -0,0 +1,1495 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for +Status Report//EN" +"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2011-07-2011-09.xml,v 1.3 2011/11/09 13:10:33 danger Exp $ --> +<report> + <date> + <month>July-September</month> + + <year>2011</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report covers &os;-related projects between July and + September 2011. It is the third of the four reports planned for 2011. + This quarter was mainly devoted to polishing the bits for the next + major version of &os;, 9.0, which is to be released by then end + of this year.</p> + + <p>Thanks to all the reporters for the excellent work! This report + contains 28 entries and we hope you enjoy reading it.</p> + + <p>Please note that the deadline for submissions covering the period + between October and December 2011 is January 15th, 2012.</p> + </section> + + <category> + <name>proj</name> + <description>Projects</description> + </category> + + <category> + <name>team</name> + <description>&os; Team Reports</description> + </category> + + <category> + <name>net</name> + <description>Network Infrastructure</description> + </category> + + <category> + <name>kern</name> + <description>Kernel</description> + </category> + + <category> + <name>docs</name> + <description>Documentation</description> + </category> + + <category> + <name>arch</name> + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + <description>Ports</description> + </category> + + <category> + <name>misc</name> + <description>Miscellaneous</description> + </category> + + <category> + <name>gsoc</name> + <description>Google Summer of Code</description> + </category> + + <project cat='docs'> + <title>The &os; German Documentation Project Status Report</title> + + <contact> + <person> + <name> + <given>Johann</given> + <common>Kois</common> + </name> + <email>jkois@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Benedict</given> + <common>Reuschling</common> + </name> + <email>bcr@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="https://doc.bsdgroup.de">Website of the &os; German + Documentation Project.</url> + </links> + + <body> + <p>We managed to update the German version of the documentation + just in time to get it included in the upcoming 9.0-RELEASE. The + website translations were also kept in sync with the ones on + FreeBSD.org.</p> + + <p>We tried to re-activate committers who did not contribute for + some time but most of them are currently unable to free up enough + time. We hope to gain fresh contributor blood as we are getting + occasional reports about bugs and grammar in the German + translation.</p> + </body> + + <help> + <task>Submit grammar, spelling or other errors you find in the + German documents and the website</task> + + <task>Translate more articles and other open handbook sections + (especially the new chapter about the new &os; + installer).</task> + </help> + </project> + + <project cat='docs'> + <title>The &os; Japanese Documentation Project</title> + + <contact> + <person> + <name> + <given>Hiroki</given> + <common>Sato</common> + </name> + <email>hrs@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ryusuke</given> + <common>Suzuki</common> + </name> + <email>ryusuke@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ja/">Japanese &os; Web + Pages</url> + <url href="http://www.jp.FreeBSD.org/doc-jp/">The &os; Japanese + Documentation Project Web Page</url> + </links> + + <body> + <p>The www/ja and doc/ja_JP.eucJP/books/handbook subtrees have + constantly been updated since the last report.</p> + + <p>www/ja: During this period, many areas of outdated content in + the www/ja subtree were updated to the latest versions of the + English counterparts. The Japanese version of the 8.2R release + announcement was added and the upcoming 9.0R announcement will be + translated in a timely manner.</p> + + <p>Handbook: The Japanese "kernelconfig" section finally caught up with + the original English version. The next targets are "cutting-edge" + and the new installer section.</p> + </body> + + <help> + <task>Further translation work for outdated documents in both + doc/ja_JP.eucJP and www/ja.</task> + </help> + </project> + + <project cat='team'> + <title>Ports Collection</title> + + <contact> + <person> + <name> + <given>Thomas</given> + <common>Abthorpe</common> + </name> + <email>portmgr-secretary@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Port</given> + <common>Management Team</common> + </name> + <email>portmgr@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ports/" /> + <url href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" /> + <url href="http://portsmon.FreeBSD.org/index.html" /> + <url href="http://www.FreeBSD.org/portmgr/index.html" /> + <url href="http://blogs.FreeBSDish.org/portmgr/" /> + <url href="http://www.twitter.com/freebsd_portmgr/" /> + <url href="http://www.facebook.com/group.php?gid=135441496471197" /> + </links> + + <body> + <p>The ports tree slowly moves up closer to the 23,000 mark. The PR count + still remains at about 1000.</p> + + <p>In Q2 we added 4 new committers, but took in 6 commit bits for safe + keeping.</p> + + <p>The Ports Management team have been running -exp runs on an + ongoing basis, verifying how base system updates may affect the + ports tree, as well as providing QA runs for major ports updates. + Of note, -exp runs were done for:</p> + + <ul> + <li>Python update</li> + <li>Boost updates</li> + <li>Gtk3 updates</li> + <li>clang testing</li> + <li>pkgng testing</li> + <li>testing ruby19</li> + <li>setting the default fortran to lang/gcc46</li> + <li>setting apache22 as default</li> + <li>setting the default LDFLAGS in CONFIGURE_ENV</li> + </ul> + + <p>Work continues to refine the new build master pointyhat-west. An + upgrade to -current done in September has proven problematic. We + have enlisted ISC and Josh Paetzel to try to determine a fix. In + the meantime, the source will be downgraded to RELENG_9.</p> + + <p>The portsmon instance is being re-homed at Yahoo. Users should + not see any changes. The new instance is currently visible at + portsmonj.FreeBSD.org but will soon take on the + portsmon.FreeBSD.org name. The team would like to express its + appreciation to TDC A/S for the loan of the existing machine for + several years.</p> + + <p>Work is underway to create a new QAT instance at NYI/NJ.</p> + + <p>portmgr also assisted in setting up a sparc64 machine for + general develop access at Yahoo.</p> + + <p>Thanks to on-site work by Sean Bruno and Ben Haga, we once again + have access to the powerpc build machine at ISC, and powerpc builds + have been restarted. They also helped us get one more i386 machine + back online.</p> + + <p>linimon is working on a set of scripts to more quickly produce + pre-configured PXEboot images for package build nodes.</p> + + <p>The update of __FreeBSD_version in param.h to 1000000 proved very + disruptive to the ports tree, triggering lots of bad assumption in + code that interpreted it as &os; 1. A great deal of work has + gone into identifying the instances of broken code and fixing and + upstreaming them. While this is taking place, one recommended + workaround is to set your version to 999999.</p> + </body> + + <help> + <task>Looking for help getting <a + href="http://wiki.FreeBSD.org/PortsAndClang">ports to build with + clang</a>.</task> + + <task>Looking for help fixing <a + href="http://wiki.FreeBSD.org/PortsBrokenOnCurrent">ports broken + on CURRENT</a>. (List needs updating, too)</task> + + <task>Looking for help with <a + href="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures"> + Tier-2 architectures</a>. (List needs updating, too)</task> + + <task>Most ports PRs are assigned, we now need to focus on testing, + committing and closing.</task> + </help> + </project> + + <project cat='ports'> + <title>KDE/&os;</title> + + <contact> + <person> + <name> + <given>KDE</given> + <common>&os;</common> + </name> + <email>kde-freebsd@KDE.org</email> + </person> + </contact> + + <links> + <url href="http://FreeBSD.KDE.org">KDE/&os; home page</url> + <url href="http://FreeBSD.KDE.org/area51.php">area51</url> + </links> + + <body> + <p>The KDE/&os; team has continued to improve the experience + of KDE software and Qt under &os;. The latest round of + improvements include:</p> + + <ul> + <li>Splitting some of the KDE modules into smaller ports</li> + <li>Reduced startup time by ~15 seconds</li> + <li>Allowed auto-login out-of-the-box</li> + <li>Kopete supports GoogleTalk</li> + <li>Kalzium installs with its molecular editor</li> + <li>Zeitgeist support added</li> + <li>Porting Calligra to &os; (work-in-progress)</li> + </ul> + + <p>The team has also made many releases and upstreamed many fixes + and patches. The latest round of releases include:</p> + + <ul> + <li>Qt: 4.7.4</li> + <li>PyQt: 4.8.5 (SIP: 4.12.4)</li> + <li>KDE SC: 4.7.2</li> + <li>Amarok: 2.4.3</li> + <li>KDevelop: 4.2.3 (KDevPlatform: 1.2.3)</li> + </ul> + + <p>The team is always looking for more testers and porters so + please contact us at kde-freebsd@KDE.org and visit our home page at + <a href="http://FreeBSD.KDE.org/">http://FreeBSD.KDE.org</a>.</p> + </body> + + <help> + <task>Testing KDE PIM 4.7.2</task> + <task>Testing phonon-gstreamer and phonon-vlc as the phonon-xine + backend was deprecated (and will remain in ports)</task> + </help> + </project> + + <project cat='proj'> + <title>ZFSguru</title> + + <contact> + <person> + <name> + <given>Jason</given> + <common>Edwards</common> + </name> + <email>guru@ZFSguru.com</email> + </person> + </contact> + + <links> + <url href="http://zfsguru.com">ZFSguru main website</url> + <url href="http://zfsguru.com" /> + </links> + + <body> + <p>ZFSguru is a newly designed Network Attached Storage operating + system, much like FreeNAS. The difference is that ZFSguru + focuses heavily on ZFS and user friendly operation, and uses a full + &os; distribution with no elements stripped down. This allows + people new to &os; and UNIX in general to access the power + of ZFS, while still allowing more advanced users to tweak their NAS + with additional functionality and use it as a normal &os; + distribution.</p> + + <p>Started a little over a year ago, the ZFSguru project is making + good progress. It should already be one of the most user friendly + distributions focused on ZFS, and sports some very unique features. + The advanced ZFS benchmarking and convenient Root-on-ZFS + installation are good examples. Priority is given to finishing the + missing core functionality, and extending the number of available + service addons which currently are limited to iSCSI-target and + VirtualBox extensions.</p> + </body> + + <help> + <task>Finish ZFS and network related functionality in the + web-interface.</task> + + <task>Introduce new service addons, adding optional functionality + to ZFSguru.</task> + + <task>Extend the documentation.</task> + </help> + </project> + + <project cat='kern'> + <title>VM layer for allocations larger than a page</title> + + <contact> + <person> + <name> + <given>Alan</given> + <common>Cox</common> + </name> + <email>alc@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Davide</given> + <common>Italiano</common> + </name> + <email>davide.italiano@gmail.com</email> + </person> + </contact> + + <body> + <p>The aim of this project is to create a new layer that sits + between UMA and the virtual memory system managing chunks of kernel + virtual memory on the order of 2 to 4 MB in size. At the end of the + work, UMA page_alloc() would no longer call directly into the VM + system. It would instead call into this new layer. Thus, + uma_large_malloc() and uma_large_free() would no longer be + immediately allocating and deallocating kernel virtual memory. This + results in a gain in terms of performances (there is a relatively + high cost in the approach adopted until now), and also in terms of + reduction of fragmentation (the VM system uses a first-fit policy of + allocation so there is room for improvements).</p> + </body> + </project> + + <project cat='proj'> + <title>HAST (Highly Available Storage) status update</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + <common>Dawidek</common> + </name> + <email>pjd@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Mikolaj</given> + <common>Golub</common> + </name> + <email>trociny@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>HAST is under active development. Some changes since Q1 + report:</p> + + <ul> + <li>Async replication mode. Unfortunately it will not make it into + 9.0-RELEASE (pjd@).</li> + <li>IPv6 support (pjd@).</li> + <li>Activemap fix that significantly reduces number of metadata + updates (trociny@).</li> + <li>Provider's write cache flush after metadata updates + (pjd@).</li> + <li>Possibility to specify pidfile in configuration file + (pjd@).</li> + <li>Many bug fixes and other improvments.</li> + </ul> + </body> + </project> + + <project cat='proj'> + <title>GELI status update</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + <common>Dawidek</common> + </name> + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Selected GELI (disk encryption GEOM class) changes since 2010/Q3 + report:</p> + + <ul> + <li>Implementation of suspend/resume functionality.</li> + <li>New version subcommand to check GELI providers version.</li> + <li>New -V option for init subcommand, which allows to create + GELI providers for older &os; versions.</li> + <li>Significant aesni(4) performance improvements for AES-XTS + algorithm.</li> + </ul> + </body> + </project> + + <project cat='gsoc'> + <title>Multibyte Encoding Support in Nvi</title> + + <contact> + <person> + <name> + <given>Zhihao</given> + <common>Yuan</common> + </name> + <email>lichray@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/ZhihaoSoC2011">&os; + Wiki</url> + <url href="https://github.com/lichray/nvi2">Github page</url> + </links> + + <body> + <p>nvi-iconv keeps the behaviors and the license of nvi-1.79 in the + base system and adopts the multibyte encoding support from + nvi-1.8x.</p> + + <p>Status:</p> + + <ul> + <li>Known memory leaks, bugs are fixed. make buildworld clear, + under WARNS=1 (the old one was WARNS=0).</li> + <li>UTF-16 is supported with less hacks.</li> + <li>The 'windowname' option now restores the xterm title through + xprop.</li> + <li>The file encoding detection modified from file(1) is finished + and considered stable. The detection is always on as nvi-iconv + never changes the actual encoding, and the detection falls back to + locale.</li> + <li>Pavel Timofeev provided a full Russian translation of the + catalog. Thanks to him.</li> + <li>Now nvi-iconv is able to be compiled with widechar only and + without iconv (inspired by a user on FreeBSDChina.org). In + that case, it only supports your locale.</li> + </ul> + </body> + + <help> + <task>The wide character support in nvi's message (feedback over + the last line) system.</task> + + <task>Collect more testing results and get code review.</task> + </help> + </project> + + <project cat='arch'> + <title>&os;/powerpc on AppliedMicro APM86290</title> + + <contact> + <person> + <name> + <given>Grzegorz</given> + <common>Bernacki</common> + </name> + <email>gjb@semihalf.com</email> + </person> + + <person> + <name> + <given>Rafal</given> + <common>Jaworowski</common> + </name> + <email>raj@semihalf.com</email> + </person> + </contact> + + <body> + <p>The APM86290 system-on-chip device is a member of AppliedMicro's + PACKETpro family of embedded processors.</p> + + <p>The chip includes two Power Architecture PPC465 processor cores, + which are compliant with the Book-E specification of the architecture, + and a number of integrated peripherals.</p> + + <p>This work is extending current Book-E support in &os; towards + PPC4xx processor variants along with device drivers for + integrated peripherials.</p> + + <p>The following drivers have been created since the last report:</p> + + <ul> + <li>Interrupt controller</li> + <li>EHCI USB driver attachment</li> + <li>Queue Manager/Traffic Manager support</li> + <li>Initial support of Ethernet controller</li> + <li>GPIO, I2C</li> + </ul> + + <p>Next steps:</p> + + <ul> + <li>Finalize Ethernet controller driver</li> + <li>L2 cache support</li> + </ul> + </body> + </project> + + <project cat='arch'> + <title>&os;/arm on Marvell Armada XP</title> + + <contact> + <person> + <name> + <given>Grzegorz</given> + <common>Bernacki</common> + </name> + <email>gjb@semihalf.com</email> + </person> + + <person> + <name> + <given>Rafal</given> + <common>Jaworowski</common> + </name> + <email>raj@semihalf.com</email> + </person> + </contact> + + <body> + <p>Marvell Armada XP is a complete system-on-chip solution based on + the Sheeva embedded CPUs. These devices integrate up to four ARMv6/v7 + compliant Sheeva CPU cores with shared L2 cache.</p> + + <p>This work is extending &os;/arm infrastructure towards + support for recent ARM architecture variations along with a basic + set of device drivers for integrated peripherals.</p> + + <p>The following code has been implemented since the last status + report:</p> + + <ul> + <li>PCI-Express support</li> + <li>SMP support</li> + <ul> + <li>Created framework for ARM platform dependent code.</li> + <li>Initialization and starting of Application Processor.</li> + <li>Implementation of sending/handling IPI</li> + </ul> + </ul> + + <p>Next steps:</p> + + <ul> + <li>Finalize SMP support (TLB/cache operation broadcast, + etc.)</li> + <li>L2 cache support</li> + <li>SATA driver</li> + </ul> + </body> + </project> + + <project cat='ports'> + <title>&os; Haskell Ports</title> + + <contact> + <person> + <name> + <given>Gabor Janos</given> + <common>PaLI</common> + </name> + <email>pgj@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ashish</given> + <common>SHUKLA</common> + </name> + <email>ashish@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>We updated existing ports to their latest versions and hunted down + a bug in the 9-CURRENT rtld which was causing GHC to crash + intermittently. We also started work on Haskell Platform 2011.3.0.0 + (development version) in a <a + href="https://github.com/freebsd-haskell/freebsd-haskell/tree/haskell-platform-2011.3.0.0"> + separate git branch in our development repository</a>.</p> + </body> + + <help> + <task>Test GHC to work with clang/LLVM.</task> + + <task>Add an option to the GHC port to be able to build it with already + installed GHC instead of requiring a separate GHC boostrap + tarball.</task> + + <task>Update Haskell Platform (along with GHC) to 2011.4.0.0 as + soon as it gets out.</task> + + <task>Add more ports to the Ports collection.</task> + </help> + </project> + + <project cat='kern'> + <title>The new CARP</title> + + <contact> + <person> + <name> + <given>Gleb</given> + <common>Smirnoff</common> + </name> + <email>glebius@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~glebius/newcarp/" /> + </links> + + <body> + <p>I am now working on significant rewrite of CARP in &os;.</p> + + <p>The reason for this work is that the CARP protocol actually does + not bring a new interface, but is a property of interface address. + Rewriting it in this way helps to remove several hacks from + incoming packet processing, simplifies some code, makes CARP + addresses more sane from the viewpoint of routing daemons such as + quagga/zebra and closes many CARP-related PRs in GNATS. It also + brings support for a single redundant address on the subnet, the + thing that is called "carpdev feature" in OpenBSD, long awaited in + &os;.</p> + + <p>For this moment I have a patch against head/ that compiles and + works in my test environment that I am going to deploy soon on some + of servers under my control.</p> + + <p>The patch has been reviewed by Bjoern Zeeb (bz@).</p> + </body> + + <help> + <task>More testing requested!</task> + + <task>Implement arpbalance and ipbalance features. This requires a + next step of rewriting, probably borrowing some ideas from + OpenBSD.</task> + + <task>Update documentation.</task> + </help> + </project> + + <project cat='proj'> + <title>pfSense</title> + + <contact> + <person> + <name> + <given>Scott</given> + <common>Ullrich</common> + </name> + <email>sullrich@gmail.com</email> + </person> + + <person> + <name> + <given>Chris</given> + <common>Buechler</common> + </name> + <email>cbuechler@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://www.pfsense.org/">pfSense Home</url> + </links> + + <body> + <p>pfSense 2.0 has been released to the world. This brings the past + three years of new feature additions, with significant enhancements + to almost every portion of the system. The changes and new features + are <a + href='http://doc.pfsense.org/index.php/2.0_New_Features_and_Changes'> + summarized here</a>. This is by far the most widely deployed + release we have put out, thanks to the efforts of thousands of + members of the community.</p> + </body> + + <help> + <task>Work on 2.1 is underway with the biggest changes being IPV6 + support and PBI packaged binaries for the package system.</task> + </help> + </project> + + <project cat='ports'> + <title>OpenAFS port</title> + + <contact> + <person> + <name> + <given>Benjamin</given> + <common>Kaduk</common> + </name> + <email>kaduk@mit.edu</email> + </person> + + <person> + <name> + <given>Derrick</given> + <common>Brashear</common> + </name> + <email>shadow@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://openafs.org">OpenAFS home page</url> + <url href="http://wiki.FreeBSD.org/afs">&os; Wiki on AFS</url> + </links> + + <body> + <p>AFS is a distributed network filesystem that originated from the + Andrew Project at Carnegie-Mellon University. OpenAFS 1.6.0 has + been released, and is available in the &os; Ports Collection; it is + usable under light load, but heavy usage reveals some issues that + remain unresolved. The OpenAFS kernel module is now built using the + bsd.kmod.mk infrastructure on the git master branch; unfortunately + this change required a minor change in the OS-independent Makefiles + and could not be merged in time for 1.6.0. Some attention has been + given to memory leaks, but only one small leak has been patched so + far.</p> + + <p>There are several known outstanding issues that are being worked + on, but detailed bug reports are welcome at + port-freebsd@openafs.org.</p> + </body> + + <help> + <task>Update VFS locking to allow the use of disk-based client + caches as well as memory-based caches.</task> + + <task>Track down races and deadlocks that may appear under + load.</task> + + <task>Eliminate a moderate memory leak from the kernel + module.</task> + + <task>PAG (Process Authentication Group) support is not + functional.</task> + </help> + </project> + + <project cat='net'> + <title>DIstributed Firewall and Flow-shaper Using Statistical + Evidence (DIFFUSE)</title> + + <contact> + <person> + <name> + <given>Sebastian</given> + <common>Zander</common> + </name> + <email>szander@swin.edu.au</email> + </person> + + <person> + <name> + <given>Lawrence</given> + <common>Stewart</common> + </name> + <email>lastewart@swin.edu.au</email> + </person> + + <person> + <name> + <given>Grenville</given> + <common>Armitage</common> + </name> + <email>garmitage@swin.edu.au</email> + </person> + </contact> + + <links> + <url href="http://caia.swin.edu.au/freebsd/diffused/" /> + <url href="http://www.FreeBSDFoundation.org/project%20announcements.shtml#diffuse" /> + <url href="http://caia.swin.edu.au/urp/diffuse/" /> + <url href="http://caia.swin.edu.au/urp/diffuse/downloads.html" /> + </links> + + <body> + <p>DIFFUSE enables &os;'s IPFW firewall subsystem to classify IP + traffic based on statistical traffic properties.</p> + + <p>With DIFFUSE, IPFW computes statistics (such as packet lengths + or inter-packet time intervals) for observed flows, and uses ML + (machine learning) to classify flows into classes. In addition to + traditional packet inspection rules, IPFW rules may now also be + expressed in terms of traffic statistics or classes identified by + ML classification. This can be helpful when direct packet + inspection is problematic (perhaps for administrative reasons, or + because port numbers do not reliably identify applications).</p> + + <p>DIFFUSE also enables one instance of IPFW to send flow + information and classes to other IPFW instances, which then can act + on such traffic (e.g. prioritise, accept, deny, etc.) according to + its class. This allows for distributed architectures, where + classification at one location in your network is used to control + fire-walling or rate-shaping actions at other locations.</p> + + <p>The &os; Foundation has funded the Centre for Advanced + Internet Architectures at Swinburne University of Technology to + undertake the DIFFUSED (DIFFUSE for freebsD) project, which aims to + refine our publicly released DIFFUSE prototype and integrate all + components of the architecture into &os;.</p> + + <p>The project is progressing well in the diffused_head project + branch of the &os; Subversion repository, and is due to be + completed by the end of October 2011. Once the project is + completed, the code will be merged from the project branch into the + head branch. An MFC of the code to 8.x and 9.x should be possible + after an appropriate amount of soak time has elapsed.</p> + </body> + </project> + + <project cat='misc'> + <title>bsd_day(2011)</title> + + <contact> + <person> + <name> + <given>Martin</given> + <common>Matuska</common> + </name> + <email>mm@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Gabor</given> + <common>Pali</common> + </name> + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://bsdday.eu/2011">Home page of bsd_day(2011)</url> + </links> + + <body> + <p>The purpose of this one-day event was to gather Central European + developers of today's open-source BSD systems to popularize their + work and their organizations, and to meet each other in the real + life. We wanted to motivate potential future developers + and users, especially undergraduate university students, to work + with BSD systems.</p> + + <p>This year's BSD-Day was held in Bratislava, Slovakia at the + Slovak University of Technology, Faculty of Electrical Engineering + and Information Technology on November 5, 2011.</p> + </body> + </project> + + <project cat='misc'> + <title>EuroBSDcon 2011</title> + + <contact> + <person> + <name> + <given>EuroBSDcon</given> + <common>Organizers</common> + </name> + <email>oc-2011@eurobsdcon.org</email> + </person> + + <person> + <name> + <given>Gabor</given> + <common>Pali</common> + </name> + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://2011.eurobsdcon.org/">EuroBSDcon 2011 web + site</url> + </links> + + <body> + <p>The 10th anniversary European BSD Conference was organized in + Maarssen, The Netherlands with more than 250 registered visitors. + There were many interesting tutorials, including introductions to + DTrace and working with Netgraph. It featured 26 high-quality talks + and 2 keynote speakers on various topics related to &os;, + OpenBSD, NetBSD, or even MINIX: OpenBSD PF, NetBSD NPF, IPv6 + support in &os;, virtualization in the BSD domain, recent + developments in OpenSSH, exploration of the recent FreeNAS, system + management with ZFS, practical capabilities for UNIX known as + Capsicum.</p> + + <p>It also had a dedicated track for the attendees of the &os; + developer summit, where one could learn more about what is + happening currently in the Project. We had presentations on the new + package management solution, Google Summer of Code 2011, a stacked + cryptographic file system, conversion of documents of different + formats, and status reports on the sparc64 port and the NAND flash + support.</p> + </body> + </project> + + <project cat='misc'> + <title>&os; Developer Summit, Maarssen</title> + + <contact> + <person> + <name> + <given>Gabor</given> + <common>Pali</common> + </name> + <email>pgj@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/201110DevSummit">Home page of + the summit</url> + </links> + + <body> + <p>We had 60 &os; developers and invited guests attending the + &os; Developer Summit organized as part of EuroBSDcon 2011 in + Maarssen, The Netherlands. This year EuroBSDcon organizers offered + us their generous support in handling the details, like + registrations, renting the venue, and providing food for keeping + attendees happy.</p> + + <p>The Maarssen developer summit spanned over 3 days. It is + generally a workshop-style event that has now adopted the layout of + the developer summit organized successfully in Canada earlier in + May. On the first day, there were working groups on various topics, + e.g. Capsicum, toolchain issues, ports, and documentation. On the + second day, there were various plenary discussions, like how + &os; relates to virtualization or how vendors relate to &os;. + Finally, on the third day, there were many interesting + work-in-progress reports given in a dedicated developer summit + track at the main conference.</p> + + <p>Photos and slides for the most of the talks are available on the + home page of the summit.</p> + </body> + </project> + + <project cat='docs'> + <title>Doc sprint on IRC, September 5, 2011</title> + + <contact> + <person> + <name> + <given>Benedict</given> + <common>Reuschling</common> + </name> + <email>bcr@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Dru</given> + <common>Lavigne</common> + </name> + <email>dru@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~bcr/doc/sprints/20110905-final.html"> + Results and Notes written down during the sprint</url> + </links> + + <body> + <p>On September 5, we held another documentation sprint on IRC + channel #bsddocs to discuss various issues that are important for + the whole &os; documentation community. We talked about the + status of the planned documentation repository conversion to SVN + and the status of the XML docbook conversion. At that point in + time, we did not have any documentation regarding the new + bsdinstaller in the upcoming release, which would have been very + bad for users that were trying to install the release. Luckily, a + small team formed quickly to start working on a new bsdinstall + chapter from scratch using a separate Google code repository that + gjb@ had set up.</p> + + <p>Some of the topics we discussed were moved forward and their + status was revisited at EuroBSDcon's devsummit documentation + session. Before the end of the conference, we had a new bsdinstall + chapter committed into the official documentation tree, thanks to + the efforts put into the new chapter by Gavin Atkinson, Warren + Block, and Glen Barber. Garrett Cooper provided valuable + instructions on the various installation methods that are possible + with the new bsdinstaller. Thanks to all who helped make this a + reality.</p> + + <p>It is nice to see that the things we talked about at the + documentation sprint developed further, which is why we are trying + to do these sprints in regular intervals.</p> + </body> + + <help> + <task>Plan the next documentation sprint</task> + + <task>Continue working on the issues that are still open like the + conversion of the repository to SVN</task> + </help> + </project> + + <project cat='proj'> + <title>ZRouter.org project — a &os;-based firmware for embedded + devices</title> + + <contact> + <person> + <name> + <given>Aleksandr</given> + <common>Rybalko</common> + </name> + <email>ray@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://zrouter.org">Redmine project interface</url> + <url href="http://lists.zrouter.org">Mailing lists</url> + <url href="http://zrouter.org/hg/zrouter/">Main ZRouter.org + mercurial repository</url> + <url href="http://zrouter.org/hg/FreeBSD/head/">&os; HEAD copy + with our modifications</url> + </links> + + <body> + <p>ZRouter.org is a young project that aims to produce + &os;-based firmware for small boxes such as SOHO router, APs, etc. + At the present time ZRouter.org is able to build working firmware + for:</p> + + <ul> + <li>D-Link DAP-1350</li> + <li>D-Link DIR-320</li> + <li>D-Link DIR-320-NRU</li> + <li>D-Link DIR-330</li> + <li>D-Link DIR-615-E4</li> + <li>D-Link DIR-620</li> + <li>D-Link DIR-632</li> + <li>D-Link DSA-3110-A1</li> + <li>D-Link DSR-1000N</li> + <li>NorthQ NQ-900</li> + <li>TPLink TL-WR941ND-v3_2</li> + <li>Ubiquiti RSPRO</li> + </ul> + + <p>Currently we are working on most parts of the core system but we + are also in the planning phase for implementing a simple web-based + GUI which we hope will have taken form before the next &os; status + report.</p> + + <p>We still have many items not done, so devices in that list + cannot be called "Production Ready" yet. But we work on that.</p> + + <p>It is easy to add new devices, because we have separate + definition of board and SoC(System on Chip), so if you have "Asus + WL-500g Premium v2" for example, you can copy D-Link/DIR-320 + directory and tweak to work for your device. We already have basic + support for:</p> + + <ul> + <li>Broadcom BCM5354</li> + <li>Broadcom BCM5836</li> + <li>Ralink RT3052F</li> + <li>Ralink RT3050F</li> + <li>Ralink RT5350F</li> + <li>Atheros AR7161</li> + <li>Atheros AR7242</li> + <li>Atheros AR7241</li> + <li>Atheros AR7240</li> + <li>Atheros AR9132</li> + <li>Intel ixp435</li> + <li>Cavium CN5010</li> + </ul> + + <p>If you have ability and time, please join us at http://zrouter.org + (Redmine interface and mailing lists)</p> + </body> + + <help> + <task>Device drivers</task> + <task>Web UI</task> + <task>Control scripts</task> + <task>Watchdog</task> + <task>etc.</task> + </help> + </project> + + <project cat='net'> + <title>Ethernet Switch Framework</title> + + <contact> + <person> + <name> + <given>Aleksandr</given> + <common>Rybalko</common> + </name> + <email>ray@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://zrouter.org/hg/FreeBSD/head/file/default/head/sys/dev/switch"> + Code here.</url> + </links> + + <body> + <p>Many embedded devices have an Ethernet switch on board; such + switches are even embedded on some multiport NICs. This + embedded switch framework is designed to give users the + ability to easily control basic features present in managed + switches, such as VLANs, QoS, port mirroring, etc. Currently + we are able to control only VLANs on:</p> + + <ul> + <li>Atheros AR8216/AR8316 (standalone and embedded in + AR724X)</li> + <li>Broadcom BCM5325 switch family (also embedded in BCM5354 + SoC)</li> + <li>Ralink RT3050F/RT3052F internal switch</li> + <li>Realtek RTL8309</li> + <li>IP175X</li> + <li>IP178X</li> + </ul> + </body> + + <help> + <task>Fix AR8216/AR8316 driver</task> + <task>Fix BCM5325 driver, not all ports pass data</task> + <task>Add tick handler for RTL8309 to automatically unisolate ports</task> + <task>Unify MIB statistic counters access</task> + <task>Add mii read/write bus methods</task> + <task>Implement pseudo interfaces for switch PHYs</task> + </help> + </project> + + <project cat='proj'> + <title>Tool for providing &os; VM Images</title> + + <contact> + <person> + <name> + <given>Alexander</given> + <common>Yerenkow</common> + </name> + <email>yerenkow@gmail.com</email> + </person> + </contact> + + <links> + <url href="https://github.com/yerenkow/freebsd-vm-image">Main + github repo</url> + </links> + + <body> + <p>A set of scripts to make building &os; VM images easy.</p> + + <p>Providing a way to make regular build images of the latest version + from SVN. Images currently can be copied with `dd` to USB + flash (for testing on real hardware) and VirtualBox + (.vdi).</p> + </body> + + <help> + <task>Build images with ports-set from main port-tree</task> + + <task>Build images with ports-set from main port-tree plus + overrides from area51 (like experimental images)</task> + + <task>Build images with special development branches included (like + for testing drivers)</task> + </help> + </project> + + <project cat='docs'> + <title>The &os; Greek Documentation Project</title> + + <contact> + <person> + <name> + <given>Manolis</given> + <common>Kiagias</common> + </name> + <email>manolis@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Giorgos</given> + <common>Keramidas</common> + </name> + <email>keramida@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSDgr.org">The &os; Greek + Documentation Project</url> + <url href="http://www.FreeBSD.org/doc/el/books/handbook">The + &os; Greek Handbook</url> + </links> + + <body> + <p>After a few rather quiet months, the &os; Greek Documentation + Project is back on track, translating and improving the Handbook, + FAQ and &os; articles. The new bsdinstall chapter has been + translated and is now present in the Handbook. Our <a + href="http://www.FreeBSDgr.org/handbook">experimental Handbook + builds</a> are also available at the project's hub. Three new + status pages have been added:</p> + + <ul> + <li><a + href="http://www.FreeBSDgr.org/versions.html">Merge Status for + the en_US tree</a> shows whether the local en_US repo is in + sync with the official CVS</li> + + <li><a + href="http://www.FreeBSDgr.org/versionsel.html">Merge Status + for the el_GR tree</a> - as above but for the Greek + tree</li> + + <li><a + href="http://www.FreeBSDgr.org/pending.html">Pending + Commits</a> shows newer yet to be committed versions of the + Greek docs</li> + </ul> + + <p>For more information, please visit <a + href="http://www.FreeBSDgr.org">http://www.freebsdgr.org</a>. + Patches, fixes and contributions are always welcome.</p> + </body> + + <help> + <task>Translate the remaining chapters of the Handbook to + Greek.</task> + + <task>Complete the translation of the &os; FAQ.</task> + + <task>Keep the currently translated docs in sync with the English + versions.</task> + </help> + </project> + + <project cat='ports'> + <title>Portmaster</title> + + <contact> + <person> + <name> + <given>Doug</given> + <common>Barton</common> + </name> + <email>dougb@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://dougbarton.us/portmaster-proposal.html" /> + </links> + + <body> + <p>Portmaster offers several new features since the last quarterly + update; some bug fixes for the package installation code, and + various internal optimizations. The most exciting new feature is + probably the ability to specify the -r option more than once for + the same portmaster run. This greatly increases efficiency when + several "branch" and/or "trunk" ports need updates at the same + time, especially for package-building systems.</p> + </body> + + <help> + <task>Splitting out the fetch code is still "on the list" of work + to be done, but it was sidetracked by other priorities in the past + months. I hope to complete it in the quarter to come.</task> + + <task>Another new feature in the works is support for a list of + files for portmaster to preserve and restore during upgrades of a + port.</task> + </help> + </project> + + <project cat='net'> + <title>802.11n / atheros</title> + + <contact> + <person> + <name> + <given>Adrian</given> + <common>Chadd</common> + </name> + <email>adrian@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/AdrianChadd/AtherosTxAgg" /> + </links> + + <body> + <p>AR5416, AR9160, and AR9280 functions in both station and hostap + mode. Performance is good.</p> + + <p>Software retry of frames is implemented. Aggregation is + implemented.</p> + + <p>BAR TX is not yet handled. HT protection is not implemented; neither + is MIMO powersave.</p> + </body> + + <help> + <task>BAR TX</task> + <task>MIMO powersave</task> + <task>Correct handling of flushing TX queues during interface + reset/reconfigure</task> + <task>Correct handling of 20<->20/40mhz transitions (without + dropping frames)</task> + <task>More intelligent rate control</task> + </help> + </project> + + <project cat='team'> + <title>The &os; Foundation</title> + + <contact> + <person> + <name> + <given>Deb</given> + <common>Goodkin</common> + </name> + <email>deb@FreeBSDFoundation.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSDFoundation.org/" /> + </links> + + <body> + <p>The Foundation sponsored KyivBSD 2011 which was held in Kiev, + Ukraine on September 24. We were represented at Ohio LinuxFest in + Columbus, Ohio. And, we approved six travel grants for EuroBSDCon. + Stop by and visit us at the &os; booth during LISA '11, December + 7-8, in Boston, MA.</p> + + <p>Three Foundation funded projects were completed during this + period: implementing xlocale APIs to enable porting libc++ by David + Chisnall, implementing DIFFUSE for &os; by Swinburne University, + and adding GEM, KMS, and DRI support for Intel drivers by + Konstantin Belousov.</p> + + <p>We published our <a + href="http://www.FreeBSDFoundation.org/press/2011Aug-newsletter.shtml"> + semi-annual newsletter</a>. We purchased servers and other + hardware for the &os; co-location centers at Sentex and + NYI.</p> + + <p>The work above, as well as many other tasks which we do for the + &os; Project, could not be done without donations. Please help us + by making a donation or asking your company to make a donation. We + would be happy to send marketing literature to you or your company. + Find out how to make a donation at <a + href="http://www.FreeBSDFoundation.org/donate/">our donate + page</a>.</p> + + <p>Find out more up-to-date Foundation news by reading our <a + href="http://FreeBSDFoundation.blogspot.com/">blog</a> and + <a href="http://www.facebook.com/FreeBSDFoundation">Facebook</a> + page.</p> + </body> + </project> + + <project cat='team'> + <title>The &os; Release Engineering Team</title> + + <contact> + <person> + <name> + <given>Release Engineering Team</given> + </name> + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/" /> + </links> + + <body> + <p>The Release Engineering Team has been coordinating the upcoming + &os; 9.0-RELEASE. Thanks to work done by many of the + developers. The release, though delayed, is taking the shape + nicely. We have reached the stage of doing the second + Release Candidate. At this time we expect to have one more + Release Candidate, to be followed by the final release itself.</p> + </body> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2011-10-2011-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2011-10-2011-12.xml new file mode 100644 index 0000000000..3b5221e7da --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2011-10-2011-12.xml @@ -0,0 +1,1925 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status +Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2011-10-2011-12.xml,v 1.12 2012/01/26 02:27:54 gjb Exp $ --> +<report> + <date> + <month>October-December</month> + + <year>2011</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report covers &os;-related projects between October and + December 2011. It is the last of the four reports planned for 2011. + This quarter was mainly devoted to polishing the bits for the next + major version of &os;, 9.0, which was already successfully released in + the beginning of January 2012.</p> + + <p>Thanks to all the reporters for the excellent work! This report + contains 32 entries and we hope you enjoy reading it.</p> + + <p>Please note that the deadline for submissions covering the period + between January and March 2012 is April 15th, 2012.</p> + </section> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>bin</name> + + <description>User-land Programs</description> + </category> + + <category> + <name>team</name> + + <description>&os; Team Reports</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <project cat='ports'> + <title>&os; Ruby Ports</title> + + <contact> + <person> + <name> + <given>Philip</given> + <common>Gollucci</common> + </name> + <email>pgollucci@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Steve</given> + <common>Wills</common> + </name> + <email>swills@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/Ruby">Wiki</url> + + <url href="http://people.FreeBSD.org/~pgollucci/FreeBSD/prs/prefixes.html#ruby-"> + PRs</url> + + <url href="http://people.FreeBSD.org/~pgollucci/FreeBSD/prs/prefixes.html#rubygem-"> + PRs</url> + </links> + + <body> + <p>Work is underway to convert the remaining ruby- ports to + rubygem-* ports in order to keep up with the gem community.</p> + + <p>A second attempt will be made to change the default ruby from + 1.8 to 1.9. There will be some unavoidable casualties of this + transition. The sysutils/rubygem-chef-server port was contributed by + RideCharge Inc / Taxi Magic who is now using it exclusively.</p> + </body> + + <help> + <task>Need some fresh -exp runs to check the new status especially with + ruby 1.9.3-p0.</task> + </help> + </project> + + <project cat='proj'> + <title>BSD-Licensed C++ Stack</title> + + <contact> + <person> + <name> + <given>David</given> + <common>Chisnall</common> + </name> + <email>theraven@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Two new libraries, libc++ (providing a C++11 STL implementation) + and libcxxrt (providing an implementation of the C++ ABI + specification) have been added. This is enabled by adding + WITH_LIBCPLUSPLUS=yes to src.conf. It is not enabled by default + because libc++ does not build with the version of gcc in the base + system and requires you to build with clang.</p> + + <p>Once it is built, you can select between using GNU libstdc++ and + libc++ by adding -stdlib=libc++ or -stdlib=libstdc++ to your + compile and link flags (when building with clang).</p> + + <p>If you are running head (or have a spare [virtual] machine you + can try it on) then please try building your C++ code with libc++ + and let me know of any failures, ideally with reduced test + cases.</p> + </body> + + <help> + <task>Test ports with libc++. Hopefully most will Just Work., but + others may need patches or have a hard dependency on + libstdc++.</task> + + <task>Make libstdc++ dynamically link to libsupc++. This will allow + us to use libmap.conf to switch between libsupc++ and + libcxxrt.</task> + + <task>Enable building libc++ by default (hopefully in the 9.1 + time-frame, when clang becomes the default system compiler) and + switch to using libcxxrt instead of libsupc++ by default.</task> + + <task>Lots more testing. Followed by even more testing.</task> + + <task>Removing libstdc++ from the base system and making it + available through ports for backwards compatibility.</task> + </help> + </project> + + <project cat='kern'> + <title>GEOM MULTIPATH Rewrite</title> + + <contact> + <person> + <name> + <given>Alexander</given> + <common>Motin</common> + </name> + <email>mav@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~mav/gmultipath5.patch">Patch + committed into the HEAD.</url> + </links> + + <body> + <p>The GEOM MULTIPATH class underwent a major rewrite to fix many + problems and improve functionality, including:</p> + + <ul> + <li>Improved locking and destruction process to fix crashes.</li> + + <li>"Automatic" configuration method improved to make it safe by + reading metadata back from all specified paths after writing to + one.</li> + + <li>"Manual" configuration method added to work without using + on-disk metadata. New "add" and "remove" commands allow to manage + paths manually.</li> + + <li>Failed paths are no longer dropped from GEOM, but only marked + as failed and excluded from I/O operations. Failed paths can be + automatically restored when all other paths are lost or marked as + failed, for example, because of device-caused (not transport) + errors. "Fail" and "restore" commands added to manually control + failure status.</li> + + <li>Added Active/Active mode support. Unlike the default + Active/Passive mode, the load is evenly distributed between all + working paths. If supported by the device, it allows to + significantly improve performance, utilizing bandwidth of all + paths. It is controlled by the -A option during creation.</li> + + <li>Provider size check added to reduce chance of conflict with + other GEOM classes.</li> + + <li>GEOM is now destroyed on last provider disconnection.</li> + + <li>`status` and `list` commands output was improved.</li> + </ul> + + <p>These changes are now committed into the &os; HEAD branch. Merge + to 9-STABLE and 8-STABLE is planned after 9.0 release.</p> + + <p>Project sponsored by iXsystems, Inc.</p> + </body> + + <help> + <task>Implement some additional request ordering mechanism for the + Active/Active mode. Some consumers in theory may not wait for + previous requests completion before submitting new overlapping or + dependent requests. Those requests may be reordered on device if + run via different paths simultaneously.</task> + </help> + </project> + + <project cat='docs'> + <title>A Tool to Check for Mistakes in Documentation — igor</title> + + <contact> + <person> + <name> + <given>Warren</given> + <common>Block</common> + </name> + <email>wblock@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.wonkity.com/~wblock/igor/" /> + </links> + + <body> + <p>igor is a program that proofreads man pages, DocBook SGML + source, and other text files for many common mistakes.</p> + + <p>Files are tested for spelling mistakes, repeated words, and + white-space problems. Man pages are also checked for minimal + structure, and DocBook SGML source files are checked for formatting + and tag problems.</p> + + <p>If you write or edit &os; documentation, let igor help you check + it for correctness.</p> + </body> + + <help> + <task>Find a testing or parsing framework that can do a faster or + better job, or that can understand the state of DocBook + tags.</task> + + <task>Add more tests.</task> + + <task>Improve speed.</task> + </help> + </project> + + <project cat='kern'> + <title>The New CARP</title> + + <contact> + <person> + <name> + <given>Gleb</given> + <common>Smirnoff</common> + </name> + <email>glebius@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Bjoern</given> + <common>Zeeb</common> + </name> + <email>bz@FreeBSD.org</email> + </person> + + <person> + <name> + <given>George</given> + <common>Neville-Neil</common> + </name> + <email>gnn@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://svnweb.FreeBSD.org/base?view=revision&revision=228571"> + The main commit</url> + </links> + + <body> + <p>Significantly updated CARP protocol has been committed to head/. + I expect the new code to be easier to maintain and less buggy, + since it uses less hacks in the networking stack.</p> + + <p>The new CARP does not bring a lot of new features, however here + is a couple:</p> + + <ul> + <li>One can put a single redundant address on an interface.</li> + + <li>Master/backup state can be switched via ifconfig.</li> + + <li>Feature that demotes carp(4) during pfsync(4) update has been + restored (it was lost in 7.0).</li> + + <li>The overall ifconfig(8) output is now more readable, since + addresses are exactly on the interfaces they are running. Yes, + this is feature, too :)</li> + </ul> + + <p>The code has been developed by glebius@ with lots of help from + bz@.</p> + </body> + + <help> + <task>Work on arpbalance/ipbalance features. Since I do not utilize + them at all, first I need to find somebody eager to see these + features and willing to test patches. Sponsoring work is also + appreciated. glebius@ to handle.</task> + + <task>Estimate whether we need to catch up with OpenBSD on putting + demotion counter into datagrams. glebius@ to handle.</task> + + <task>Update tcpdump(8) to enable nice printing of CARP packets. + gnn@ to handle.</task> + + <task>Work with IANA to get an official protocol number. gnn@ to + handle.</task> + </help> + </project> + + <project cat='arch'> + <title>&os;/390</title> + + <contact> + <person> + <name> + <given>Pau</given> + <common>Amma</common> + </name> + <email>fduuvrzv@yahoo.com</email> + </person> + + <person> + <name> + <given>Bjoern A.</given> + <common>Zeeb</common> + </name> + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>I wandered in and started working on &os;/390 about 1 month ago + based on source Bjoern provided. My short term goals are to sync it + with the current HEAD and write a minimal IPLabel loader, so we do + not have to depend on Hercules-only commands to test the kernel + boot process.</p> + + <p>Then it will be time to make the crossbuild work again and get + the kernel booting.</p> + </body> + </project> + + <project cat='bin'> + <title>System Configuration Utilities</title> + + <contact> + <person> + <name> + <given>Devin</given> + <common>Teske</common> + </name> + <email>dteske@vicor.com</email> + </person> + </contact> + + <links> + <url href="http://druidbsd.sourceforge.net/">The DruidBSD + Project</url> + </links> + + <body> + <p>On December 31st, 2011 sysutils/sysrc was added to the + ports-tree. On January 6th, 2012 sysutils/host-setup was added to + the ports-tree. Still pending is the addition of + sysutils/tzdialog.</p> + + <p>Together or separately, these utilities try to make configuring + the system easier and more efficient.</p> + + <p>sysrc(8) allows you to safely modify rc.conf(5) without fear or + trepidation; making remote-management and scripted changes a simple + transaction. Also useful in managing puppet installations.</p> + + <p>host-setup(8) allows you to configure your time zone, hostname, + network interfaces, default router/gateway, DNS nameservers in + resolv.conf(5) all via dialog(1) (or Xdialog(1)) interface. + Designed to replace sysinstall(8), host-setup is written entirely + in sh(1) and is completely stand-alone.</p> + + <p>tzdialog(8) is an ISO-3166 compatible sh(1) rewrite of + tzsetup(8). It is designed to be a drop-in replacement for tzsetup. + The major difference between the two is tzdialog(8) adds supports + for graphical user interface via Xdialog(1) (by passing the `-X' + argument), whereas tzsetup(8) only supports console-based + interaction.</p> + </body> + + <help> + <task>Write a man-page for tzdialog(8).</task> + + <task>Submit current tzdialog(8) version (1.1) and yet-to-be + completed man-page to ports-tree as sysutils/tzdialog.</task> + </help> + </project> + + <project cat='ports'> + <title>Perl Ports Testing</title> + + <contact> + <person> + <name> + <given>Steve</given> + <common>Wills</common> + </name> + <email>swills@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Sunpoet Po-Chuan</given> + <common>Hsieh</common> + </name> + <email>sunpoet@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Many Perl modules in ports come with test cases included with + their source. This project's goal is to ensure that all these tests + pass. Patches have been added to the ports tinderbox to allow test + related dependencies to be installed and many ports have + TEST_DEPENDS now. A patch is available to enable testing for those + who wish to help out. All p5- ports have been built and tests + attempted. Approximately 61% of the Perl ports pass currently. Many + ports have been updated to include missing dependencies or make + other changes which allow tests to pass. Long term goals include a + more generic framework for testing ports and automated tests + executed when ports are updated.</p> + </body> + + <help> + <task>Many Perl ports which do not pass tests remain.</task> + + <task>Need to figure out how to move testing out of + tinderbox.</task> + + <task>A patch to build Perl with -pthread (but not enable + useithreads in Perl) is pending. It will fix many currently broken + tests</task> + </help> + </project> + + <project cat='kern'> + <title>Status Report for NFS</title> + + <contact> + <person> + <name> + <given>Rick</given> + <common>Macklem</common> + </name> + <email>rmacklem@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The new NFS client and server are no longer considered + experimental and are the default for &os; 9.0. Included is fairly + complete support for NFSv4.0, as well as NFSv3 and NFSv2. NFSv4.0 + delegations are not enabled by default for the server, since there + is no handling of them for local system calls done on the server, + as yet. So far, the transition seems to have gone alright, with only + a couple of obscure issues identified that did not get fixed + for &os; 9.0. Patches for these can be found at + <a href="http://people.FreeBSD.org/~rmacklem"> + http://people.FreeBSD.org/~rmacklem</a> + </p> + + <p>Work is ongoing with respect to NFSv4.1 client support. The + current code includes functioning support for the required + components, in particular, sessions for both fore and back + channels. Development for the big optional component pNFS is in + progress and will hopefully be functional for the Files layout in a + few months. The modified sources can be found at <a + href="http://svn.FreeBSD.org/viewvc/base/projects/nfsv4.1-client"> + http://svn.FreeBSD.org/viewvc/base/projects/nfsv4.1-client</a>.</p> + + <p>There is also a patch for what I call packrats, where threads + perform aggressive on-disk caching of delegated file in the NFSv4.0 + client. It currently seems to function OK, but does not yet have + client reboot recovery implemented, so it can only be used + experimentally at this time. This patch can be found at <a + href="http://people.FreeBSD.org/~rmacklem/packrat-patches"> + http://people.FreeBSD.org/~rmacklem/packrat-patches</a>.</p> + </body> + </project> + + <project cat='docs'> + <title>The &os; Japanese Documentation Project</title> + + <contact> + <person> + <name> + <given>Hiroki</given> + <common>Sato</common> + </name> + <email>hrs@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ryusuke</given> + <common>Suzuki</common> + </name> + <email>ryusuke@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ja/">Japanese &os; Web + Pages</url> + + <url href="http://www.jp.FreeBSD.org/doc-jp/">The &os; Japanese + Documentation Project Web Page</url> + </links> + + <body> + <p>During this period, many part of the outdated contents in the + www/ja subtree were updated to the latest versions in the English + counterpart. The "bsdinstall" section in Handbook was newly + translated and the "cutting-edge" section is now + work-in-progress.</p> + </body> + + <help> + <task>Further translation work for outdated documents in both + doc/ja_JP.eucJP and www/ja.</task> + </help> + </project> + + <project cat='ports'> + <title>&os;/KDE</title> + + <contact> + <person> + <name> + <given>&os;</given> + <common>KDE</common> + </name> + <email>kde@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://FreeBSD.kde.org">&os;/KDE home page</url> + + <url href="http://FreeBSD.kde.org/area51.php">area51</url> + </links> + + <body> + <p>The KDE/&os; team have continued to improve the experience of + KDE software and Qt under &os;. The latest round of improvements + include:</p> + + <ul> + <li>Many fixes upstream to make KDE and Qt build with Clang</li> + + <li>Making automoc not freeze with parallel builds</li> + </ul> + + <p>The team has also made many releases and upstreamed many fixes + and patches. The latest round of releases include:</p> + + <ul> + <li>KDE SC: 4.7.3, 4.7.4 (in the area51 experimental + repository)</li> + + <li>Qt: 4.8.0 (in the area51 experimental repository)</li> + + <li>CMake: 2.8.6, 2.8.7</li> + </ul> + + <p>The team is always looking for more testers and porters so + please contact us at kde@FreeBSD.org and visit our home page at + <a href="http://FreeBSD.kde.org">http://FreeBSD.kde.org</a>.</p> + </body> + + <help> + <task>Testing KDE SC 4.8.0.</task> + + <task>Testing KDE PIM 4.7.4.</task> + + <task>Testing phonon-gstreamer and phonon-vlc as the phonon-xine + backend was deprecated (but will remain in the ports for + now).</task> + + <task>Testing the Calligra beta releases (in the area51 + repository).</task> + </help> + </project> + + <project cat='ports'> + <title>&os; Haskell Ports</title> + + <contact> + <person> + <name> + <given>Gábor János</given> + <common>PÁLI</common> + </name> + <email>pgj@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ashish</given> + <common>SHUKLA</common> + </name> + <email>ashish@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/Haskell">&os; Haskell wiki + page</url> + + <url href="https://github.com/freebsd-haskell/freebsd-haskell/"> + &os; Haskell ports repository</url> + + <url href="http://haskell.org/mailman/listinfo/freebsd-haskell/"> + &os; Haskell mailing list</url> + </links> + + <body> + <p>We are proud to announce that the &os; Haskell Team has updated + the Haskell Platform to 2011.4.0.0, as well as updated GHC to 7.0.4 + in &os; Haskell ports repository. We also added a number of new + Haskell ports, and their count is now more than 300. Some of the + new ports include Yesod, Happstack (popular web development + frameworks in Haskell), ThreadScope (a graphical profiler tool for + parallel Haskell programs).</p> + + <p>Due to ports repository freeze for 9.0-RELEASE, these updates + are not in official ports tree yet. They will be committed to the + ports repository after it is unfrozen again, in the meantime + they can be accessed through &os; Haskell ports repository.</p> + </body> + + <help> + <task>Commit pending Haskell ports to &os; ports repository.</task> + + <task>Test GHC to work with clang/LLVM.</task> + + <task>Add an option to the <tt>lang/ghc</tt> port to be able to + build it with already installed GHC instead of requiring a + separate GHC bootstrap tarball.</task> + </help> + </project> + + <project cat='ports'> + <title>Public &os; Ports Development Infrastructure — + redports.org</title> + + <contact> + <person> + <name> + <given>Bernhard</given> + <common>Froehlich</common> + </name> + <email>decke@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://redports.org/" /> + + <url href="irc://irc.freenode.net#redports">IRC: #redports on + Freenode</url> + + <url href="https://groups.google.com/group/redports">redports + mailing list</url> + + <url href="http://redports.org/wiki/UserGuide">Userguide (with + Screenshots)</url> + </links> + + <body> + <p>Redports is a free service for &os; port maintainers and port + committers to automatically buildtest ports on various &os; + versions and architectures. The motivation to do that was because + there are many people that do not have access to Ports Tinderboxes + and the existing Tinderboxes are usually dedicated to a single + team.</p> + + <p>The platform was designed with scalability in mind but building + capacity is currently very limited until more hardware is + available. I am already in contact with the usual suspects to + improve that.</p> + </body> + + <help> + <task>Get more Hardware for building.</task> + + <task>Port options support.</task> + + <task>ports-mgmt/portlint support.</task> + </help> + </project> + + <project cat='kern'> + <title>HDA Sound Driver (snd_hda) Improvements</title> + + <contact> + <person> + <name> + <given>Alexander</given> + <common>Motin</common> + </name> + <email>mav@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~mav/hda.rewrite2.patch"> + Latest patch</url> + </links> + + <body> + <p>snd_hda(4) driver took major rewrite:</p> + + <ul> + <li>Big old hdac driver was split into three independent pieces: + HDA controller driver (hdac), HDA CODEC driver (hdacc) and HDA + audio function driver (hdaa). All drivers are completely + independent and talk to each other only via NewBus interfaces. + Using more NewBus bells and whistles allows to properly see HDA + structure with standard system instruments, such as `devinfo -v`. + Biggest driver file size now is 150K, instead of 240K before, and + the code is much cleaner.</li> + + <li>Support for multichannel recording was added. While I have + never seen it configured by default, UAA specification tells that + it is possible. Now, as specification defines, driver checks + input associations for pins with sequence numbers 14 and 15, and + if found (usually) — works as before, mixing signals together. + If it does not, it configures input association as multichannel. + I have found some CODECs doing strange things when configured for + multichannel recording, but I have also found successfully working + examples.</li> + + <li>Signal tracer was improved to look for cases where several + DACs/ADCs in CODEC can work with the same audio signal. If such a + case is found, the driver registers additional playback/record stream + (channel) for the pcm device. Having more than one stream allows + to avoid vchans use and so avoid extra conversion to vchan's + pre-configured sample rate and format. Not many CODECs allow + this, especially on playback, but some do.</li> + + <li>New controller streams reservation mechanism was implemented. + That allows to have more pcm devices than streams supported by + the controller (usually 4 in each direction). Now it limits only + number of simultaneously transferred audio streams, that is + rarely reachable and properly reported if happens.</li> + + <li>Codec pins and GPIO signals configuration was exported via + set of writable sysctls. Another sysctl dev.hdaa.X.reconfig + allows to trigger driver reconfiguration in run-time. The only + requirement is that all pcm devices should be closed at the + moment, as they will be destroyed and recreated. This should + significantly simplify process of fixing CODEC configuration. It + should be possible now even to write GUI to do it with few mouse + clicks.</li> + + <li>Driver now decodes pins location and connector type names. In + some cases it gives a hint to the user where the connectors of + the pcm device are located on the system case. The number of + channels supported by pcm device, reported now (if it is not 2), + should also make finding them easier.</li> + </ul> + + <p>The code is in testing now and should be soon committed to the + HEAD branch.</p> + + <p>Project sponsored by iXsystems, Inc.</p> + </body> + + <help> + <task>Closer inspection of HDMI/DisplayPort audio is + planned.</task> + + <task>A number of hardware, mostly laptops, need workarounds to work + properly. Some statistics should be collected to implement some of + them avoiding excessive code bloat.</task> + </help> + </project> + + <project cat='kern'> + <title>SCSI Direct Access Driver (da) Improvements</title> + + <contact> + <person> + <name> + <given>Alexander</given> + <common>Motin</common> + </name> + <email>mav@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>BIO_DELETE support (aka TRIM) was added to the CAM SCSI Direct + Access device driver (da).</p> + + <p>Depending on device capabilities different methods are used to + implement it. Currently used method can be read/set via + kern.cam.da.X.delete_method sysctls. Possible values are:</p> + + <ul> + <li>NONE - no provisioning support reported by the device;</li> + + <li>DISABLE - provisioning support was disabled because of + errors;</li> + + <li>ZERO - use WRITE SAME (10) command to write zeroes;</li> + + <li>WS10 - use WRITE SAME (10) command with UNMAP bit set;</li> + + <li>WS16 - use WRITE SAME (16) command with UNMAP bit set;</li> + + <li>UNMAP - use UNMAP command (equivalent of the ATA DSM TRIM + command).</li> + </ul> + + <p>The last two methods (UNMAP and WS16) are defined by SBC + specification and the UNMAP method is the most advanced one. The + rest of the methods I have found supported in Linux, and as they + were trivial to implement, then why not? I hope they will be useful + in some cases.</p> + + <p>As side product of fetching logical block provisioning support + flag, da driver also got support for reporting device physical + sector size (aka Advanced Format) via stripesize/stripeoffset GEOM + fields. Some quirks were added for known 4K sector disks not + reporting it properly.</p> + + <p>The code was committed to the HEAD branch and is going to be merged + to 8/9-STABLE after some time.</p> + + <p>Project sponsored by iXsystems, Inc.</p> + </body> + + <help> + <task>To implement more effective selection of the best delete + method some more parameters need to be obtained from the device. + Unluckily none of devices I have report them.</task> + </help> + </project> + + <project cat='bin'> + <title>Replacing the Regular Expression Code</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Kövesdán</common> + </name> + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://svnweb.FreeBSD.org/base/user/gabor/tre-integration/"> + Project repo</url> + + <url href="http://laurikari.net/tre/">TRE homepage</url> + + <url href="http://www.tdk.aut.bme.hu/Files/TDK2011/POSIX-regularis-kifejezesek1.pdf"> + A paper on the topic</url> + </links> + + <body> + <p>The current regular expression code in libc has to be replaced + because it is old, unmaintained and does not support wide + characters. As it has been elaborated, TRE is the most suitable + replacement outside that has an acceptable license. However, the + development of BSD grep also brought some relevant observations. In + short, there are some possibilities to optimize pattern matching + but it is not possible with the POSIX API, because:</p> + + <ul> + <li>It uses NUL-terminated strings that requires processing each + character and makes longer jumps impossible.</li> + + <li>It matches for one pattern at a time. If more patterns are + searched, there are more efficient ways for pattern matching but + we have to know all of them and process them together.</li> + </ul> + + <p>This project intends to implement these shortcut and provide + efficient pattern matching for all programs that use regex + matching. It will also help avoiding the custom tricks that are + hardcoded into some programs, like GNU grep, to work around the + limiting POSIX API. Besides, GNU grep has some extensions over the + POSIX regular expression, which are necessary if we want to get rid + of GNU code in the end.</p> + </body> + + <help> + <task>Implement multi-pattern heuristic regex matching.</task> + + <task>Implement GNU-specific regex extensions.</task> + + <task>Adapt BSD grep to use the multi-pattern interface.</task> + + <task>Test standard-compliance and correct behavior.</task> + </help> + </project> + + <project cat='docs'> + <title>The &os; German Documentation Project</title> + + <contact> + <person> + <name> + <given>Benedict</given> + <common>Reuschling</common> + </name> + <email>bcr@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Johann</given> + <common>Kois</common> + </name> + <email>jkois@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="https://doc.bsdgroup.de/">Homepage of the &os; German + Documentation Project</url> + + <url href="http://www.FreeBSD.org/doc/de_DE.ISO8859-1/books/handbook/bsdinstall.html"> + The German translation of the bsdinstall handbook chapter</url> + </links> + + <body> + <p>The German Documentation Project is happy to report that two big + chapters have been translated in the past quarter. The first update + is in the firewall chapter and covering the complete IPFW section. + It was contributed by Christopher J. Ruwe. There were style and + language fixes to be done, but the biggest amount of work, the + actual translation, was done by him. We thank Christopher very + much.</p> + + <p>The other chapter that was translated is the new bsdinstall + chapter. Benedict Reuschling did the work on this chapter. He tried + to keep the same titles for sections that are mostly describing the + same things as in the sysinstall chapter (at least where this was + possible).</p> + + <p>German speaking users are encouraged to read both chapters and + report typos or grammar errors back to us so we can fix them.</p> + + <p>The German website is being updated on a regular basis.</p> + </body> + + <help> + <task>Catch up with the latest changes made to the + documentation.</task> + + <task>Translate more www pages into German.</task> + + <task>Find bugs in the German documentation and fix them.</task> + </help> + </project> + + <project cat='ports'> + <title>&os;/GNOME</title> + + <contact> + <person> + <name> + <given>GNOME &os; mailing list</given> + </name> + <email>freebsd-gnome@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/gnome" /> + + <url href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/" /> + </links> + + <body> + <p>It has been a while since we did a status report.</p> + + <p>This year we started work on GNOME 3.0. Due to time constrains + and lack of man power, this version did not make it into the ports. + Currently we have 3.2 in our development repo. See the development + FAQ on our website for details. The MC-UPDATING file contains + upgrade instructions.</p> + + <p>Currently the GNOME team is understaffed, help is welcome!</p> + </body> + + <help> + <task>Update the &os; gnome website with GNOME 3.x information, and + still supply the 2.32.x info.</task> + </help> + </project> + + <project cat='ports'> + <title>Up to Date X.Org Server</title> + + <contact> + <person> + <name> + <given>X11 &os; mailing list</given> + </name> + <email>freebsd-x11@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/Xorg" /> + </links> + + <body> + <p>The X11 team has started work on the next major update for the + X.Org ports. You might have noticed libraries and proto ports being + updated that belong to the X.Org stack. Currently in our development + repository we have the latest versions of many ports including mesa + and xf86-video-intel.</p> + + <p>We support versions 1.7.7 and 1.10.4 of the X.Org tree for users + with the appropriate hardware and patches.</p> + + <p>We need more testers for both the standard version from + xorg-devel and the WITH_NEW_XORG version. We also need testers for + updated input/video drivers, especially for the less mainstream + ones.</p> + + <p>In order to test check out our svn repository from <a + href="http://trillian.chruetertee.ch/ports/browser/branches/xorg-dev"> + http://trillian.chruetertee.ch/ports/browser/branches/xorg-dev</a> and + the merge script from <a + href="http://people.FreeBSD.org/~miwi/xorg/xorgmerge"> + http://people.FreeBSD.org/~miwi/xorg/xorgmerge</a>. See the wiki for + more details.</p> + </body> + + <help> + <task>Investigate xorg-server 1.12 which brings xinput 2.2.</task> + + <task>Merge development repository into the main repository, after + more testing.</task> + </help> + </project> + + <project cat='proj'> + <title>pfSense</title> + + <contact> + <person> + <name> + <given>Scott</given> + <common>Ullrich</common> + </name> + <email>sullrich@gmail.com</email> + </person> + + <person> + <name> + <given>Chris</given> + <common>Buechler</common> + </name> + <email>cbuechler@gmail.com</email> + </person> + + <person> + <name> + <given>Ermal</given> + <common>Luçi</common> + </name> + <email>ermal.luci@gmail.com</email> + </person> + </contact> + + <links> + <url href="http://www.pfsense.org/">pfSense homepage</url> + </links> + + <body> + <p>pfSense is a free and open source customized distribution of + &os; tailored for use as a firewall and router.</p> + + <p>2.0.1 was just released which corrected a number of issues + <a href="http://blog.pfsense.org/?p=633"> + http://blog.pfsense.org/?p=633</a>.</p> + </body> + + <help> + <task>6 month release cycle.</task> + + <task>Moving builds to &os; 9.</task> + + <task>Full IPV6 support.</task> + + <task>PBI Package binaries.</task> + + <task>Unbound integration.</task> + + <task>Multi-instance Captive Portal.</task> + + <task>Replacing Prototype with jQuery.</task> + </help> + </project> + + <project cat='team'> + <title>Release Engineering Team Status Report</title> + + <contact> + <person> + <name> + <given>Release Engineering Team</given> + </name> + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/" /> + </links> + + <body> + <p>The Release Engineering Team was pleased to announce the release + of &os;-9.0 on January 12th, 2012. To acknowledge his incredible + contributions to the world of computing and in particular the &os; + Project's corner of that world &os;-9.0 was dedicated to Dennis + Ritchie. May he rest in peace. The Release Engineering Team also + wishes to thank the &os; Developers and Community for all the work + they put into the release.</p> + + <p>With the &os;-9.0 release cycle completed our focus shifts to + preparing for the &os;-8.3 release. A schedule has not been set but + we expect to be shooting for release some time in March 2012.</p> + </body> + </project> + + <project cat='proj'> + <title>Auditdistd Project</title> + + <contact> + <person> + <name> + <given>Pawel Jakub</given> + <common>Dawidek</common> + </name> + <email>pjd@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Current weakness of &os;'s Security Event Audit facility is that + audit records are stored locally and can be modified or removed by + an attacker after a system compromise.</p> + + <p>The auditdistd will allow to reliably and securely distribute + audit trail files over TCP/IP network to remote system. In case of + system compromise it will enable administrators to analyze audit + records in trusted environment.</p> + + <p>This project is sponsored by the &os; Foundation and should be + completed by the end of February 2012.</p> + </body> + </project> + + <project cat='kern'> + <title>&os; No-IPv4 ("IPv6-Only") Support</title> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + <common>Zeeb</common> + </name> + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ipv6/ipv6only.html">FreeBSD + No-IPv4 Support</url> + </links> + + <body> + <p>The No-IPv4 (fka. "IPv6-Only") project initially + prototyped in p4 and merged into mainstream &os; with support from + the &os; Foundation and iXsystems earlier in 2011 for World IPv6 + Day continued as a free time project. Thanks to the help of an + anonymous source, dedicated i386 and amd64 build machines and a + distribution node were setup to allow continuous building of + snapshots and we hope to extend the support for the snapshots in + the future providing more services.</p> + + <p>During the 9.0 release cycle a BETA and an RC snapshot were + built and released. &os; 9.0-RELEASE will be the first official + release supporting a kernel to compile out IPv4 support. We will + provide (and given 9.0 is out at time of writing do provide) a + no-IPv4 snapshot accompanying the official release and hope for + your feedback.</p> + + <p>I would like to thank Hiroki Sato/allbsd.org for providing a mirror + in Japan for the Asian community in addition to mine in Europe.</p> + </body> + + <help> + <task>Commit/Submit upstream a few user space fixes.</task> + + <task>More user space cleanup and testing.</task> + + <task>Get rid of <tt>gethostby*()</tt> calls.</task> + </help> + </project> + + <project cat='arch'> + <title>&os;/powerpc on AppliedMicro APM86290</title> + + <contact> + <person> + <name> + <given>Grzegorz</given> + <common>Bernacki</common> + </name> + <email>gjb@semihalf.com</email> + </person> + + <person> + <name> + <given>Rafal</given> + <common>Jaworowski</common> + </name> + <email>raj@semihalf.com</email> + </person> + </contact> + + <body> + <p>The APM86290 system-on-chip device is a member of AppliedMicro's + PACKETpro family of embedded processors.</p> + + <p>The chip includes two Power Architecture PPC465 processor cores, + which are compliant with Book-E specification of the architecture, + and a number of integrated peripherals.</p> + + <p>This work is extending current Book-E support in &os; towards + PPC4xx processors variation along with device drivers for + integrated peripherals.</p> + + <p>The following drivers have been created since the last + report:</p> + + <ul> + <li>Ethernet controller driver</li> + + <li>Classifier driver</li> + + <li>Finished Queue Manager/Traffic Manager</li> + + <li>Improved performance and stability</li> + </ul> + + <p>Next steps:</p> + + <ul> + <li>L2 cache support</li> + + <li>Merge APM86290 support to -CURRENT</li> + </ul> + </body> + </project> + + <project cat='arch'> + <title>&os;/powerpc on Freescale QorIQ DPAA</title> + + <contact> + <person> + <name> + <given>Michal</given> + <common>Dubiel</common> + </name> + <email>md@semihalf.com</email> + </person> + + <person> + <name> + <given>Rafal</given> + <common>Jaworowski</common> + </name> + <email>raj@semihalf.com</email> + </person> + + <person> + <name> + <given>Piotr</given> + <common>Ziecik</common> + </name> + <email>kosmo@semihalf.com</email> + </person> + </contact> + + <links> + <url href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P2040"> + P2041 product page</url> + + <url href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P3041"> + P3041 product page</url> + + <url href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P5020"> + P5020 product page</url> + </links> + + <body> + <p>The QorIQ Data Path Acceleration Architecture (DPAA) from + Freescale is a comprehensive architecture, which integrates all + aspects of packet processing in the SoC, addressing issues and + requirements resulting from the nature of QorIQ multicore SoCs. It + includes:</p> + + <ul> + <li>Cores</li> + + <li>Network and packet I/O</li> + + <li>Hardware offload accelerators</li> + + <li>The infrastructure required to facilitate the flow of packets + between the above</li> + </ul> + + <p>The DPAA also addresses various performance related + requirements, especially those created by the high speed network + I/O found on multicore SoCs such as P2041, P3041, P5020, etc. This + work is bringing up &os; on these system-on-chip devices along with + device drivers for integrated peripherals.</p> + + <p>Current &os; QorIQ DPAA support includes:</p> + + <ul> + <li>QorIQ P2041 and P3041 devices</li> + + <li>E500mc core complex</li> + + <li>Adaptation of toolchain for the new core</li> + + <li>Booting via U-Boot bootloader</li> + + <li>CoreNet interconnect fabric</li> + + <li>L1, L2, L3 cache</li> + + <li>Serial console (UART)</li> + + <li>Interrupt controller</li> + + <li>DPAA infrastructure (BMAN, FMAN, QMAN)</li> + + <li>Ethernet (basic network functionality using Independent Mode + of DPAA infrastructure)</li> + + <li>EHCI controller</li> + + <li>PCI Express controller (host mode)</li> + + <li>SMP support (up to quad-core)</li> + + <li>I2C</li> + </ul> + + <p>Next steps:</p> + + <ul> + <li>QorIQ P5020 (32-bit mode) support</li> + + <li>Ethernet (full network functionality using Regular Mode of + DPAA infrastructure)</li> + + <li>Enhanced SDHC</li> + </ul> + </body> + </project> + + <project cat='arch'> + <title>&os;/arm on Marvell Armada XP</title> + + <contact> + <person> + <name> + <given>Grzegorz</given> + <common>Bernacki</common> + </name> + <email>gjb@semihalf.com</email> + </person> + + <person> + <name> + <given>Rafal</given> + <common>Jaworowski</common> + </name> + <email>raj@semihalf.com</email> + </person> + </contact> + + <links> + <url href="http://svnweb.FreeBSD.org/base/projects/armv6/">ARMv6 + branch</url> + </links> + + <body> + <p>Marvell Armada XP is a complete system-on-chip solution based on + Sheeva embedded CPU. These devices integrate up to four ARMv6/v7 + compliant Sheeva CPU cores with shared L2 cache.</p> + + <p>This work is extending the &os;/arm infrastructure towards support + for recent ARM architecture variations along with a basic set of + device drivers for integrated peripherals.</p> + + <p>The following code has been implemented since the last status + report:</p> + + <ul> + <li>SMP support</li> + + <ul> + <li>Implemented TLB broadcast and RFO</li> + + <li>Tested 2 and 4 cores setup in WT cache mode</li> + </ul> + + <li>SATA driver integrated and tested</li> + + <li>CESA driver integrated and tested</li> + </ul> + + <p>Next steps:</p> + + <ul> + <li>L2 cache support</li> + + <li>Full support for WB/WBA cache</li> + </ul> + </body> + </project> + + <project cat='team'> + <title>The &os; Foundation Status Report</title> + + <contact> + <person> + <name> + <given>Deb</given> + <common>Goodkin</common> + </name> + <email>deb@FreeBSDFoundation.org</email> + </person> + </contact> + + <links> + <url href="www.FreeBSDFoundation.org" /> + </links> + + <body> + <p>The most exciting news to report is that we raised $426,000 + through our fundraising efforts. We were overwhelmed by the + generosity of the &os; community. We would like to thank everyone + who made a contribution to &os; by either making a financial + donation to the foundation or volunteering on the Project.</p> + + <p>We published our <a + href="http://www.FreeBSDFoundation.org/press/2011Dec-newsletter.shtml"> + semi-annual newsletter</a> in December. If you have not + already done so, please take a moment to read this publication + to find out how we supported the &os; Project and community + during the second half of 2011. There are also two great + testimonials in the newsletter from TaxiMagic and the Apache + Software Foundation.</p> + + <p>The Foundation sponsored EuroBSDCon 2011 which was held in The + Netherlands, October 6-9. And, we sponsored six developers to + attend the conference. We sponsored the Bay Area Vendor Summit in + November. We were represented at LISA '11, Dec 7-8 in Boston + MA.</p> + + <p>We are a proud sponsor of AsiaBSDCon 2012, which will be held in + Tokyo, Japan, March 22-25.</p> + + <p>The Foundation funded project Feed-Forward Clock Synchronization + Algorithms Project by the University of Melbourne completed. We + approved two new projects for 2012, they are analyzing the + performance of &os;'s IPv6 stack by Bjoern Zeeb, and implementing + auditdistd daemon by Pawel Jakub Dawidek</p> + + <p>We purchased more servers and other hardware for the &os; + co-location centers at Sentex, NYI, and ISC.</p> + + <p>The work above, as well as many other tasks which we do for the + &os; Project, could not be done without donations. Please help us by + making a donation or asking your company to make a donation. We + would be happy to send marketing literature to you or your company. + Find out how to make a donation at <a + href="http://www.FreeBSDFoundation.org/donate/">our donate + page</a>.</p> + + <p>Find out more up-to-date Foundation news by reading our <a + href="http://FreeBSDFoundation.blogspot.com/">blog</a> and + <a href="http://www.facebook.com/FreeBSDFoundation">Facebook</a> + page.</p> + </body> + </project> + + <project cat='team'> + <title>&os; Ports Management Team Status Report</title> + + <contact> + <person> + <name> + <given>Thomas</given> + <common>Abthorpe</common> + </name> + <email>portmgr-secretary@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Port</given> + <common>Management Team</common> + </name> + <email>portmgr@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ports/" /> + + <url href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" /> + + <url href="http://portsmon.FreeBSD.org/index.html" /> + + <url href="http://www.FreeBSD.org/portmgr/index.html" /> + + <url href="http://blogs.FreeBSDish.org/portmgr/" /> + + <url href="http://www.twitter.com/freebsd_portmgr/" /> + + <url href="http://www.facebook.com/group.php?gid=135441496471197" /> + </links> + + <body> + <p>The ports tree finally surpassed 23,000 ports. The PR count + still remains at about 1100.</p> + + <p>In Q4 we added 4 new committers, took in 4 commit bit for safe + keeping, and had one committer return to ports work.</p> + + <p>The Ports Management team have been running -exp runs on an + ongoing basis, verifying how base system updates may affect the + ports tree, as well as providing QA runs for major ports updates. + Of note, -exp runs were done for:</p> + + <ul> + <li>KDE4 and cmake updates</li> + + <li>Multiple runs to test and fix breakages induced by the bump + in digits for &os; 10</li> + + <li>Verify the removal of X11BASE from ports</li> + + <li>Test ports after import of flex and m4 into src base</li> + + <li>Optimizations to bsd.ports.mk</li> + + <li>Test xcb update and split into multiple ports</li> + + <li>Estimate number of ports utilizing old interface ioctls</li> + + <li>Ongoing validation of infrastructure with pkgng</li> + + <li>testing ports with clang as default compiler</li> + </ul> + + <p>pkgng now has real safe binary upgrade, as well as real + integrity checking, work has been started to have the ports tree + be able to bootstrap pkgng. More info on the <a + href="http://lists.FreeBSD.org/pipermail/freebsd-ports/2011-November/071631.html"> + CFT email.</a>.</p> + + <p>The pointyhat-west build machine continues toward production + use, code updates have made it more versatile such as swapping out + information in make.conf for build slaves, assist in testing of + pkgng -exp runs and to properly build linux_base ports.</p> + + <p>It has been decided that the ports tree will be migrated from + CVS to Subversion, beat@ will be in charge of the project. More + information on the <a + href="http://wiki.FreeBSD.org/PortsSVN">wiki</a>.</p> + + <p>A moderated mailing list has been created for ports related + announcements, <a + href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-ports-announce"> + http://lists.FreeBSD.org/mailman/listinfo/freebsd-ports-announce</a>, + it is intended, but not limited, to be a means of communicating + portmgr@ announcements, Calls for Testing, plus other relevant + information to be used by our committers and ports maintainer + community.</p> + </body> + + <help> + <task>Looking for help getting <a + href="http://wiki.FreeBSD.org/PortsAndClang">ports to build + with clang</a>.</task> + + <task>Looking for help fixing <a + href="http://wiki.FreeBSD.org/PortsBrokenOnCurrent">ports broken + on CURRENT</a>. (List needs updating, too)</task> + + <task>Looking for help with <a + href="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures"> + Tier-2 architectures</a>.</task> + + <task><a + href="http://wiki.FreeBSD.org/PortsBrokenBySrcChanges">ports + broken by src changes</a>.</task> + + <task><a + href="http://wiki.FreeBSD.org/PortsFailingOnPointyhat">ports + failing on pointyhat</a>.</task> + + <task><a + href="http://wiki.FreeBSD.org/PortsFailingOnPointyhatWest">ports + failing on pointyhat-west</a>.</task> + + <task><a + href="http://wiki.FreeBSD.org/Trybroken">ports that are marked + as BROKEN</a>.</task> + + <task><a + href="http://wiki.FreeBSD.org/WhenDidThatPortBreak">When did + that port break</a>.</task> + + <task>Most ports PRs are assigned, we now need to focus on testing, + committing and closing.</task> + </help> + </project> + + <project cat='ports'> + <title>Multimedia — Watching/Recording Digital TV</title> + + <contact> + <person> + <name> + <given>Hans Petter</given> + <common>Selasky</common> + </name> + <email>hselasky@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Jason</given> + <common>Harmening</common> + </name> + <email>jason.harmening@gmail.com</email> + </person> + + <person> + <name> + <given>Juergen</given> + <common>Lock</common> + </name> + <email>nox@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/WebcamCompat">Tested DVB and + other hardware</url> + + <url href="http://wiki.FreeBSD.org/HTPC" /> + + <url href="http://wiki.FreeBSD.org/VDR" /> + </links> + + <body> + <p>Progress has been made when watching/recording live digital TV + using &os;:</p> + + <ul> + <li><a href="http://freshports.org/multimedia/webcamd"> + multimedia/webcamd</a> is continuously adding support for + more and more USB tuners using the Linux V4L/DVB drivers + (also including remotes via webcamd and <a + href="http://freshports.org/comms/lirc">comms/lirc</a>.)</li> + + <li><a href="http://freshports.org/multimedia/cx88"> + multimedia/cx88</a> recently added Linux DVB API support + for CX88-based PCI(-e) DVB-T tuners so "common" apps can now + also be used with that hardware.</li> + + <li><a href="http://freshports.org/multimedia/xbmc-pvr"> + multimedia/xbmc-pvr</a> was committed recently and the <a + href="http://wiki.FreeBSD.org/VDR">multimedia/vdr</a> + ports are working too for watching/recording live digital TV, and + also other apps like kaffeine, or mplayer, or vlc.</li> + </ul> + </body> + + <help> + <task>Continue updating the VDR ports to the latest versions and + fix remaining bugs.</task> + + <task>Update <a href="http://freshports.org/multimedia/libxine"> + multimedia/libxine</a> to 1.2.0 that recently was released + (which VDR uses.)</task> + + <task>Test more hardware?</task> + </help> + </project> + + <project cat='arch'> + <title>Improving Support for New Features in the Intel SandyBridge CPUs</title> + + <contact> + <person> + <name> + <given>Konstantin</given> + <common>Belousov</common> + </name> + <email>kib@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Support for new features in the Intel SandyBridge CPUs is + progressing.</p> + + <p>The patch to query and allow extended FPU states was committed, + which enabled the YMM registers and AVX instruction set on the + capable processors. Todo items include get wider testing of the + change before planned merge to stable/9 in a month, and start + using XSAVEOPT instruction to optimize context switch times.</p> + + <p>Patch to enable and use per-process TLB was developed. Latest + version is available at <a + href="http://people.freebsd.org/~kib/misc/pcid.2.patch"> + http://people.freebsd.org/~kib/misc/pcid.2.patch</a>. The facility, + referred in the documentation as PCID, allows to avoid TLB flush + on context switches by applying PID tag to each non-global TLB + entry. On SandyBridge, measurements did not prove any difference + between context switch latencies on patched and stock kernels.</p> + + <p>Forthcoming IvyBridge CPUs promised to provide optimizations in + the form of INVPCID instructions that allow to optimize TLB + shootdown handlers. The patch above uses the instruction on the + capable CPU. Todo items are to get access to IvyBridge and do the + benchmarks.</p> + + <p>Future work might provide SEP support, use hardware random + generator from IvyBridge for random(4), considering using faster + instructions to access %fs and %gs bases, and use improved AES-NI + instruction set for aesni(4).</p> + </body> + </project> + + <project cat='kern'> + <title>CAM Target Layer (CTL)</title> + + <contact> + <person> + <name> + <given>Ken</given> + <common>Merry</common> + </name> + <email>ken@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://lists.FreeBSD.org/pipermail/freebsd-current/2012-January/031007.html" /> + </links> + + <body> + <p>The CAM Target Layer (CTL) is now in &os;/head.</p> + + <p>CTL is a disk and processor device emulation subsystem originally + written for Copan Systems under Linux starting in 2003. It + has been shipping in Copan (now SGI) products since 2005.</p> + + <p>It was ported to &os; in 2008, and thanks to an agreement + between SGI (who acquired Copan's assets in 2010) and Spectra + Logic in 2010, CTL is available under a BSD-style license. The + intent behind the agreement was that Spectra would work to get + CTL into the &os; tree.</p> + + <p>It will likely be merged into the stable/9 tree in + mid-February.</p> + + <p>Some CTL features:</p> + + <ul> + <li>Disk and processor device emulation</li> + <li>Tagged queueing</li> + <li>SCSI task attribute support (ordered, head of queue, + simple tags)</li> + <li>SCSI implicit command ordering support. (e.g. if a read + follows a mode select, the read will be blocked until the + mode select completes.)</li> + <li>Full task management support (abort, LUN reset, target + reset, etc.)</li> + <li>Support for multiple ports</li> + <li>Support for multiple simultaneous initiators</li> + <li>Support for multiple simultaneous backing stores</li> + <li>Persistent reservation support</li> + <li>Mode sense/select support</li> + <li>Error injection support</li> + <li>High Availability support (1)</li> + <li>All I/O handled in-kernel, no userland context switch + overhead.</li> + </ul> + + <p>(1) HA Support is just an API stub, and needs much more to be fully + functional.</p> + + <p>For the basics on configuring and running CTL, see + src/sys/cam/ctl/README.ctl.txt in the &os;/head source + tree.</p> + </body> + </project> + + <project cat='kern'> + <title>LSI Supported mps(4) SAS driver</title> + + <contact> + <person> + <name> + <given>Ken</given> + <common>Merry</common> + </name> + <email>ken@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Kashyap</given> + <common>Desai</common> + </name> + <email>Kashyap.Desai@lsi.com</email> + </person> + </contact> + + <links> + <url href="http://lists.FreeBSD.org/pipermail/freebsd-current/2012-January/031358.html" /> + </links> + + <body> + <p>The LSI-supported version of the mps(4) driver, that supports + their 6Gb SAS controllers and WarpDrive solid state drives, is + available in &os;/head.</p> + + <p>In addition to WarpDrive support, the driver also has several + other new features:</p> + + <ul> + <li>Integrated RAID (IR) support</li> + <li>Improved error recovery code</li> + <li>Support for SCSI protection information (EEDP)</li> + <li>Support for TLR (Transport Level Retries), needed for tape + drives</li> + <li>ioctl interface compatible with LSI utilities</li> + </ul> + + <p>Thanks to LSI for doing the work on this driver, and the + testing.</p> + + <p>I plan to merge it into stable/9 and stable/8 in early + February.</p> + </body> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2012-01-2012-03.xml b/en_US.ISO8859-1/htdocs/news/status/report-2012-01-2012-03.xml new file mode 100644 index 0000000000..76f0b2786e --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2012-01-2012-03.xml @@ -0,0 +1,1490 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status +Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> +<!-- $FreeBSD: www/en/news/status/report-2012-01-2012-03.xml,v 1.5 2012/05/12 21:11:56 danger Exp $ --> +<report> + <date> + <month>January-March</month> + + <year>2012</year> + </date> + + <section> + <title>Introduction</title> + + <p>This report covers &os;-related projects between January and March + 2012. It is the first of the four reports planned for 2012. This + quarter was highlighted by releasing the next major version of &os;, + 9.0, which was finally released in the beginning of January + 2012. The FreeBSD Project dedicates the FreeBSD 9.0-RELEASE to + the memory of Dennis M. Ritchie, one of the founding fathers of + the &unix; operating system. Our release engineering team has + been also busy with preparation of the 8.3-RELEASE, which was + publicly announced in April.</p> + + <p>Thanks to all the reporters for the excellent work! This report + contains 27 entries and we hope you enjoy reading it.</p> + + <p>Please note that the deadline for submissions covering the period + between April and June 2012 is July 15th, 2012.</p> + </section> + + <category> + <name>proj</name> + + <description>Projects</description> + </category> + + <category> + <name>bin</name> + + <description>User-land Programs</description> + </category> + + <category> + <name>team</name> + + <description>&os; Team Reports</description> + </category> + + <category> + <name>kern</name> + + <description>Kernel</description> + </category> + + <category> + <name>net</name> + + <description>Network Infrastructure</description> + </category> + + <category> + <name>docs</name> + + <description>Documentation</description> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + </category> + + <project cat='docs'> + <title>The &os; Japanese Documentation Project</title> + + <contact> + <person> + <name> + <given>Hiroki</given> + <common>Sato</common> + </name> + <email>hrs@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ryusuke</given> + <common>Suzuki</common> + </name> + <email>ryusuke@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ja/">Japanese &os; Web Page</url> + <url href="http://www.jp.FreeBSD.org/doc-jp/">The &os; Japanese + Documentation Project Web Page</url> + </links> + + <body> + <p>The same as before, the outdated contents in the www/ja subtree + were updated to the latest versions in the English counterpart. The + updating work of the outdated translations in the www/ja subtree is + almost complete. Only the translations of the release documents + for old releases may be outdated.</p> + + <p>During this period, we translated the 9.0-RELEASE announcement and + published it in a timely manner. It seems that the Japanese version + of the release announcement is important for Japanese people as + this page has frequently been referenced.</p> + + <p>For &os; Handbook, translation work of the "cutting-edge" + section is still on-going. Some updates in the "printing" and the + "linuxemu" section were done.</p> + </body> + + <help> + <task>Further translation work of outdated documents in both + doc/ja_JP.eucJP and www/ja.</task> + </help> + </project> + + <project cat='ports'> + <title>The &os; Ports Collection</title> + + <contact> + <person> + <name> + <given>Thomas</given> + <common>Abthorpe</common> + </name> + <email>portmgr-secretary@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Port</given> + <common>Management Team</common> + </name> + <email>portmgr@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/ports/" /> + <url href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" /> + <url href="http://portsmon.FreeBSD.org/index.html" /> + <url href="http://www.FreeBSD.org/portmgr/index.html" /> + <url href="http://blogs.FreeBSDish.org/portmgr/" /> + <url href="http://www.twitter.com/freebsd_portmgr/" /> + <url href="http://www.facebook.com/portmgr" /> + </links> + + <body> + <p>The ports tree slowly climbs above 23,000 ports. The PR count + still remains at about 1100.</p> + + <p>In Q1 we added 2 new committers, took in 2 commit bits for safe + keeping, and had one committer return to ports work.</p> + + <p>The Ports Management team have been running -exp runs on an + ongoing basis, verifying how base system updates may affect the + ports tree, as well as providing QA runs for major ports updates. + Of note, -exp runs were done for:</p> + + <ul> + <li>Ports validation in the &os; 10 environment</li> + <li>Updates to bison, libtool and libiconv</li> + <li>Set java/opendjdk6 as default java</li> + <li>Tests with clang set as default</li> + <li>Update to devel/boost and friends</li> + <li>Update of audio/sdl and friends</li> + <li>Tests for changes in the ports licensing infrastructure</li> + <li>Update to devel/ruby1[8|9]</li> + <li>Update to postresql</li> + <li>Update to apr</li> + <li>Checks for new x11/xorg</li> + <li>Security update to security/gnutls</li> + <li>Ongoing validation of infrastructure with pkgng</li> + </ul> + + <p>A lot of focus during this period was put into getting the ports + tree into a ready state for &os; 8.3, including preparing packages + for the release.</p> + + <p>Beat Gaetzi has been doing ongoing tests with the ports tree to + ensure a smooth transition from CVS to Subversion.</p> + </body> + + <help> + <task>Looking for help getting <url + link="http://wiki.FreeBSD.org/PortsAndClang">ports to build + with clang</url>.</task> + + <task>Looking for help with <url + link="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures"> + Tier-2 architectures</url>.</task> + + <task><url + link="http://wiki.FreeBSD.org/PortsBrokenBySrcChanges">ports + broken by src changes</url>.</task> + + <task><url + link="http://wiki.FreeBSD.org/PortsFailingOnPointyhat">ports + failing on pointyhat</url>.</task> + + <task><url + link="http://wiki.FreeBSD.org/PortsFailingOnPointyhatWest"> + ports failing on pointyhat-west</url>.</task> + + <task><url + link="http://wiki.FreeBSD.org/Trybroken">ports that are marked + as BROKEN</url>.</task> + + <task><url + link="http://wiki.FreeBSD.org/WhenDidThatPortBreak">When did + that port break</url>?</task> + + <task>Most ports PRs are assigned, we now need to focus on testing, + committing and closing.</task> + </help> + </project> + + <project cat='ports'> + <title>The &os; Haskell Ports</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>PÁLI</common> + </name> + <email>pgj@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ashish</given> + <common>SHUKLA</common> + </name> + <email>ashish@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/Haskell">&os; Haskell wiki + page</url> + + <url href="https://github.com/freebsd-haskell/freebsd-haskell/"> + &os; Haskell ports repository</url> + + <url href="https://github.com/freebsd-haskell/hsporter/">hsporter + repository</url> + + <url href="https://github.com/freebsd-haskell/hsmtk/">hsmtk + repository</url> + </links> + + <body> + <p>We are proud announce that the &os; Haskell Team has committed + the Haskell Platform 2011.4.0.0 update, GHC 7.0.4 update, existing + port updates, as well new port additions to &os; ports repository, + which were pending due to freeze for 9.0-RELEASE. Some of the new + ports which were committed include Yesod, Happstack, wxHaskell, + gitit, Threadscope, etc. and the count of Haskell ports in &os; + Ports tree is now almost 300. All of these updates will be + available as part of upcoming 8.3-RELEASE.</p> + + <p>We started project hsporter to automate creation of new &os; + Haskell ports from .cabal file, as well as update existing ports. + We also published scripts which we were using in the &os; Haskell + project under the project hsmtk.</p> + </body> + + <help> + <task>Test GHC to work with clang/LLVM.</task> + + <task>Add an option to the <tt>lang/ghc</tt> + port to be able to build it with already installed GHC instead of + requiring a separate GHC boostrap tarball.</task> + + <task>Add more ports to the Ports Collection.</task> + </help> + </project> + + <project cat='net'> + <title>IPv6 Performance Analysis</title> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + <common>Zeeb</common> + </name> + <email>bz@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~bz/bench/">Benchmarking + results</url> + </links> + + <body> + <p>IPv6 performance numbers were often seen (significantly) lower + on &os; when compared to IPv4. Continuing last years IPv6-only + kernel efforts this project looked at various reasons for this and + started fixing some.</p> + + <p>As part of the project a benchmark framework was created that + could carry out various tests including reboots in between runs and + gather results reproducibly without user intervention. It + allows regular benchmarking with minimal configuration and easy + future extension for more benchmarks.</p> + + <p>As a result of the initial analysis, UDP locking and route + lookups were improved, and delayed checksumming, TSO6 and LRO + support for IPv6 were implemented. Following this checksum + "offload" for IPv6 on loopback was enabled and various + further individual improvements, both locking and general code + changes, as well as a reduction of the cache size footprint were + carried out. Some of the changes were equally applied to IPv4.</p> + + <p>Performance numbers on physical and loopback interfaces are + on par with IPv4 when using offload support with + TCP/IPv6, which is a huge improvement. UDP and non-offload numbers + on IPv6 have generally improved but are still lower than on IPv4 + and will need future work to catch up with a decade of IPv4 + benchmarking and code path optimizations. UDP IPv6 minimal size + send path packets per second (pps) numbers however have increased + beating IPv4 when sending to a local discard device.</p> + + <p>This gets us really close to being able to prefer IPv6 by default + without causing loopback performance regressions. For physical + interfaces, cxgb(4) in HEAD already supports IPv6 TCP offload and + LRO/v6 support was added. To be able to get more test results on + different hardware, both ixgbe(4) and cxgbe(4) were also updated to + support TSO6 and LRO with IPv6.</p> + + <p>Some of the insights gained from this work will help upcoming + discussions on both the lower/link-layer overhaul as well as for + the mbuf changes to prepare our stack for more, future improvements + (ahead of time).</p> + + <p>I once again want to thank the &os; Foundation and iXsystems for + their support of the project, as well as George Neville-Neil for + providing review.</p> + + <p>Having set the start to close one of the biggest feature parity + gaps left I will continue to improve IPv6 code paths and hope that + we will see more contributions and independent results from the + community as well soon.</p> + </body> + + <help> + <task>Carefully merge code changes to SVN.</task> + </help> + </project> + + <project cat='net'> + <title>Multi-FIB: IPv6 Support and Other Enhancements</title> + + <contact> + <person> + <name> + <given>Bjoern A.</given> + <common>Zeeb</common> + </name> + <email>bz@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Alexander V.</given> + <common>Chernikov</common> + </name> + <email>melifaro@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://svnweb.FreeBSD.org/base/projects/multi-fibv6/"> + SVN multi-FIB IPv6 project area</url> + </links> + + <body> + <p>In 2008 the multiple forwarding information base (FIB) feature + was introduced for IPv4 allowing up to 16 distinct forwarding + ("routing") tables in the kernel. Thanks to the sponsorship from + Cisco Systems, Inc. this feature is now also available for IPv6 and + one of the bigger IPv6 feature-parity gaps is closed. The changes + have been integrated to HEAD, were merged back to stable/9 and + stable/8 and will be part of future releases for these branches. A + backport to stable/7 is also available in the project branch. If + more than one FIB is requested, IPv6 FIBs will be added along the + extra IPv4 FIBs without any special configuration needed and + programs like netstat and setfib, as well as ipfw, etc. were + extended to seamlessly support the multi-FIB feature on both + address families.</p> + + <p>Thanks to the help of Alexander V. Chernikov all usage of the + multi-FIB feature is now using the boot-time variable rather than + depending on the compile time option. In HEAD this now allows us + you to use the multi-FIB feature with GENERIC kernels not needing + to recompile your own anymore. The former kernel option can still + be used to set a default value if desired. Otherwise the net.fibs + loader tunable can be used to request more than one IPv6 and IPv4 + FIB at boot time.</p> + + <p>Last, routing sockets are now aware of FIBs and will only show + the routing messages targeted at the FIB attached to. This allows + route monitor or routing daemons to get selective updates for just + a specific FIB.</p> + </body> + </project> + + <project cat='kern'> + <title>DTrace Probes for the linuxulator</title> + + <contact> + <person> + <name> + <given>Alexander</given> + <common>Leidinger</common> + </name> + <email>netchild@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Recently DTrace in the kernel was improved to be able to load + kernel modules with static dtrace providers after the dtrace + modules. This allows me to commit my linuxulator specific + static provider work to -CURRENT.</p> + + <p>Together with the linuxulator DTrace probes I developed some D + scripts to check various code paths in the linuxulator. Those + scripts check various error cases which may be interesting to + verify userland code, but also linuxulator internals like + locks.</p> + + <p>As of this writing I'm in the process of updating a test machine + to a more recent -current to prepare the commit.</p> + </body> + </project> + + <project cat='ports'> + <title>A New linux_base Port Based Upon CentOS</title> + + <contact> + <person> + <name> + <given>Alexander</given> + <common>Leidinger</common> + </name> + <email>netchild@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>We got a PR with a linux_based port which is based upon CentOS + 6. Currently this can only be used as a test environment, as it + depends upon a more recent linux kernel version, than the + linuxulator provides.</p> + + <p>As of this writing, I'm in the process of preparing a commit of + this port.</p> + </body> + + <help> + <task>Repocopy by portmgr.</task> + <task>Add conflicts in other linux_base ports.</task> + <task>Commit the CentOS based one.</task> + <task>Some cleanup.</task> + </help> + </project> + + <project cat='kern'> + <title>Improved hwpmc(9) Support for MIPS</title> + + <contact> + <person> + <name> + <given>Oleksandr</given> + <common>Tymoshenko</common> + </name> + <email>gonzo@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>hwpmc(9) for MIPS has been reworked. The changes include:</p> + + <ul> + <li>msip24k code was split to CPU-specific and arch-specific + parts to make adding support for new CPUs easier</li> + + <li>Added support for Octeon PMC</li> + + <li>Added sampling support for MIPS in general</li> + </ul> + </body> + </project> + + <project cat='arch'> + <title>Porting DTrace to MIPS and ARM</title> + + <contact> + <person> + <name> + <given>Oleksandr</given> + <common>Tymoshenko</common> + </name> + <email>gonzo@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The major part of DTrace has been ported to MIPS platform. + Supported ABIs: o32 and n64. n32 has not been tested yet. MIPS + implementation passes 853 of 927 tests from DTrace test suite.</p> + + <p>The fbt provider and userland DTrace are not supported yet.</p> + + <p>The port to ARM is in progress.</p> + </body> + + <help> + <task>Userland DTrace support for MIPS.</task> + + <task>Investigate amount of effort required for getting fbt + provider work at least partially.</task> + + <task>Find proper solution for cross-platform CTF data generation + (required for ARM).</task> + </help> + </project> + + <project cat='ports'> + <title>Perl Ports Testing</title> + + <contact> + <person> + <name> + <given>Steve</given> + <common>Wills</common> + </name> + <email>swills@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/Perl#Test_Dependencies" /> + </links> + + <body> + <p>Many Perl modules in ports come with test cases included with + their source. This project's goal is to ensure that all these tests + pass. Significant progress has been made on this project. The + change to build perl with -pthread was committed and no issues have + been reported. Many ports have had missing dependencies added + and/or other changes and approximately 90% of p5- ports pass tests. + Work is being done on bringing testing support out of ports + tinderbox.</p> + </body> + + <help> + <task>Finish work on patch to bring testing support to + ports.</task> + + <task>Add additional support for testing other types of ports such + as python and ruby.</task> + </help> + </project> + + <project cat='bin'> + <title>Replacing the Regular Expression Code</title> + + <contact> + <person> + <name> + <given>Gábor</given> + <common>Kövesdán</common> + </name> + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://svnweb.FreeBSD.org/base/user/gabor/tre-integration/"> + Project repo</url> + + <url href="http://laurikari.net/tre/">TRE homepage</url> + + <url href="http://www.tdk.aut.bme.hu/Files/TDK2011/POSIX-regularis-kifejezesek1.pdf"> + A paper on the topic</url> + </links> + + <body> + <p>Since the last status report, there has been a significant + progress in optimizing TRE. The multiple pattern heuristic code is + mostly finished and it distinguishes several different cases to + speed up pattern matching. It extracts literal fragments from the + original patterns and uses a multiple pattern matching algorithm to + find any occurrence. GNU grep uses the Commentz-Walter algorithm, + which is an automaton-based algorithm, while in this project, it + has been decided to use a Wu-Manber algorithm, which is more + efficient and also easier to implement. In the current state, it + does not work entirely yet and some cases, like the REG_ICASE flag + are not yet covered. This is the next major step to complete this + multiple pattern interface. In the development branch, BSD grep is + already modified to use this new interface so it can be used for + testing and debugging purposes.</p> + </body> + + <help> + <task>Finish multiple pattern heuristic regex matching.</task> + + <task>Implement GNU-specific regex extensions.</task> + + <task>Test standard-compliance and correct behavior.</task> + </help> + </project> + + <project cat='arch'> + <title>&os;/powerpc on Freescale QorIQ DPAA</title> + + <contact> + <person> + <name> + <given>Michal</given> + <common>Dubiel</common> + </name> + <email>md@semihalf.com</email> + </person> + + <person> + <name> + <given>Rafal</given> + <common>Jaworowski</common> + </name> + <email>raj@semihalf.com</email> + </person> + + <person> + <name> + <given>Piotr</given> + <common>Ziecik</common> + </name> + <email>kosmo@semihalf.com</email> + </person> + </contact> + + <links> + <url href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P2040"> + P2041 product page</url> + + <url href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P3041"> + P3041 product page</url> + + <url href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P5020"> + P5020 product page</url> + + <url href="http://www.freescale.com/webapp/sps/site/homepage.jsp?code=64BIT&fsrch=1&sr=1"> + e5500 core home page</url> + </links> + + <body> + <p>This work is bringing up the &os; on Freescale QorIQ Data Path + Acceleration Architecture (DPAA) system-on-chips along with device + drivers for integrated peripherals. Since the last status report, + the following support has been added:</p> + + <ul> + <li>Ethernet (full network functionality using Regular Mode of + DPAA infrastructure)</li> + + <li>QorIQ P5020 SoC (e5500 core in legacy 32-bit mode)</li> + + <li>P5020 QorIQ Development System support</li> + + <li>Initial support for Enhanced SDHC</li> + </ul> + + <p>The next step is:</p> + + <ul> + <li>e5500 core in native 64-bit mode</li> + </ul> + + <p>Related publications:</p> + + <ul> + <li>Michal Dubiel, Piotr Ziecik, "&os; on Freescale QorIQ Data + Path Acceleration Architecture Devices", AsiaBSDCon, March 2012, + Tokyo, Japan.</li> + </ul> + </body> + </project> + + <project cat='arch'> + <title>NAND File System, NAND Flash Framework, NAND Simulator</title> + + <contact> + <person> + <name> + <given>Grzegorz</given> + <common>Bernacki</common> + </name> + <email>gjb@semihalf.com</email> + </person> + + <person> + <name> + <given>Mateusz</given> + <common>Guzik</common> + </name> + <email>mjg@semihalf.com</email> + </person> + </contact> + + <links> + <url href="http://svnweb.FreeBSD.org/base/projects/nand/">NAND + branch</url> + </links> + + <body> + <p>The NAND Flash stack consists of a driver framework for NAND + controllers and memory chips, a NAND device simulator and a fault + tolerant, log-structured file system, accompanied by tools, + utilities and documentation.</p> + + <ul> + <li>NAND FS support merged into "nand" project branch</li> + + <ul> + <li>NAND FS filesystem</li> + + <li>NAND FS userland tools</li> + </ul> + + <li>NAND Framework and NAND simulator merged into "nand" project + branch</li> + + <ul> + <li>NAND framework: nandbus, generic nand chips drivers</li> + + <li>NAND Flash controllers (NFC) drivers for NAND Simulator and + Marvell MV-78100 (ARM)</li> + + <li>NAND tool (which allows to erase, write/read pages/oob, + etc.</li> + </ul> + </ul> + + <p>The next steps include:</p> + + <ul> + <li>Fix bugs</li> + <li>Merge into HEAD</li> + </ul> + + <p>Work on this project is supported by the &os; Foundation and + Juniper Networks.</p> + </body> + </project> + + <project cat="arch"> + <title>&os;/arm on Various TI Boards</title> + + <contact> + <person> + <name> + <given>Ben</given> + <common>Gray</common> + </name> + <email>bgray@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Olivier</given> + <common>Houchard</common> + </name> + <email>cognet@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Damjan</given> + <common>Marion</common> + </name> + <email>dmarion@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Oleksandr</given> + <common>Tymoshenko</common> + </name> + <email>gonzo@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://svnweb.FreeBSD.org/base/projects/armv6/sys/arm/ti/" /> + </links> + + <body> + <p>The goal of this project is to get &os; running on various + popular boards that use TI-based SoCs like OMAP3, OMAP4, AM335x. + Project covers some ARM generic Cortex-A components: GIC (Generic + Interrupt Controller), PL310 L2 Cache Controller and SCU.</p> + + <p>PandaBoard (TI OMAP4430) and PandaBoard ES (OMAP4460) Dual core + ARM Cortex-A9 board support includes: USB, onboard Ethernet over + USB, GPIO, I2C and MMC/SD card drivers. Board works in multiuser + mode over NFS root.</p> + + <p>BeagleBone (TI AM3358/AM3359) single core ARM Cortex-A8 based + board support currently includes: Ethernet, L2 cache, GPIO, I2C. + Board works in multiuser mode over NFS root.</p> + </body> + + <help> + <task>Completing missing peripherals: DMA, SPI, MMC/SD, Video, + Audio.</task> + + <task>Completing SMP support and testing.</task> + + <task>Importing BeagleBoard (OMAP3) code to SVN.</task> + + <task>Improving overall stability and performance.</task> + </help> + </project> + + <project cat='net'> + <title>Atheros 802.11n Support</title> + + <contact> + <person> + <name> + <given>Adrian</given> + <common>Chadd</common> + </name> + <email>adrian@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/AdrianChadd/AtherosTxAgg" /> + <url href="http://wiki.FreeBSD.org/dev/ath(4)" /> + </links> + + <body> + <p>802.11n station and hostap support is now fully functional, sans + correct hostap side power saving. TX aggregation and TX BAR + handling is implemented.</p> + + <p>Station chip power saving is not implemented at all yet, it's not + in the scope of this work.</p> + + <p>Testers should disable bgscan (-bgscan) as scan/bgscan will + simply drop any traffic in the TX/RX queues, causing potential + traffic stalls.</p> + </body> + + <help> + <task>Fix up hostap side power save handling.</task> + + <task>Implement filtered frames support in the driver.</task> + + <task>Fix scan/bgscan to correctly buffer and retransmit frames + when going off channel, so frames are not just "dropped" - this + causes issues in the aggregation sessions and may cause traffic + stalls.</task> + + <task>Test/fix any issues with adhoc 802.11n support.</task> + </help> + </project> + + <project cat='ports'> + <title>BSD-licensed sort Utility (GNU sort Replacement)</title> + + <contact> + <person> + <name> + <given>Oleg</given> + <common>Moskalenko</common> + </name> + <email>oleg.moskalenko@citrix.com</email> + </person> + + <person> + <name> + <given>Gábor</given> + <common>Kövesdán</common> + </name> + <email>gabor@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/textproc/bsdsort/"> + &os; port of BSD sort</url> + + <url href="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sort.html"> + IEEE Std 1003.1-2008 sort specification</url> + </links> + + <body> + <p>Currently the BSD sort reached usable stable stage. It is + stable, it is as fast as the GNU sort, and it supports multi-byte + locales (this is something that GNU sort does not do correctly). + BSD sort has all features of GNU sort 5.3.0 (version included into + &os;) with some extra features and bug fixes.</p> + </body> + + <help> + <task>Add BSD sort into HEAD as an alternative, installed as + bsdsort. If proven to work as expected, change it to the default + sort version and remove GNU sort.</task> + + <task>Investigate the possibility of a multi-threaded sort + implementation and implement it, if it proves more + efficient.</task> + + <task>Upgrade BSD sort features to include some obscure new + features in the latest GNU sort version 8.15.</task> + </help> + </project> + + <project cat='ports'> + <title>KDE/&os;</title> + + <contact> + <person> + <name> + <given>KDE</given> + <common>&os;</common> + </name> + <email>kde@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://FreeBSD.kde.org">KDE/&os; home page</url> + <url href="http://FreeBSD.kde.org/area51.php">area51</url> + </links> + + <body> + <p>The team has made many releases and upstreamed many fixes and + patches. The latest round of releases include:</p> + + <ul> + <li>KDE SC: 4.7.4 (in ports) and 4.8.0, 4.8.1, 4.8.2 (in + area51)</li> + <li>Qt: 4.8.0, 4.8.1 (in area51)</li> + <li>PyQt: 4.9.1; SIP: 4.13.2 (in area51)</li> + <li>KDevelop: 2.3.0; KDevPlatform: 1.3.0 (in area51)</li> + <li>Calligra: 2.3.87 (in area51)</li> + <li>Amarok: 2.5.0</li> + <li>CMake: 2.8.7</li> + </ul> + + <p>Due to the prolonged port freeze the KDE team has not been able + to update KDE in Ports as it is considered a intrusive change.</p> + + <p>The team is always looking for more testers and porters so + please contact us at kde@FreeBSD.org and visit our home page at + <a href="http://FreeBSD.kde.org">http://FreeBSD.kde.org</a>.</p> + </body> + + <help> + <task>Testing KDE SC 4.8.2.</task> + + <task>Testing KDE PIM 4.8.2.</task> + + <task>Testing phonon-gstreamer and phonon-vlc as the phonon-xine + backend was deprecated (but will remain in the ports for + now).</task> + + <task>Testing the Calligra beta releases (in the area51 + repository).</task> + </help> + </project> + + <project cat='team'> + <title>The &os; Foundation Team Report</title> + + <contact> + <person> + <name> + <given>Deb</given> + <common>Goodkin</common> + </name> + <email>deb@FreeBSDFoundation.org</email> + </person> + </contact> + + <links> + <url href="www.FreeBSDFoundation.org" /> + </links> + + <body> + <p>The Foundation sponsored AsiaBSDCon 2012 which was held in + Tokyo, Japan, March 22-25. We were represented at SCALE on Jan 21 + and NELF on March 17. This quarter we plan on being at ILF (Indiana + LinuxFest) April 14th, BSDCan May 11-12, and SELF (Southeast + LinuxFest) June 9.</p> + + <p>We are proud to be a gold sponsor of BSDCan 2012, which will be + held in Ottawa, Canada, May 11-12. We are sponsoring 14 developers + to attend the conference.</p> + + <p>We kicked off three foundation funded projects — Growing + Filesystems Online by Edward Tomasz Napierala, Implementing + auditdistd daemon by Pawel Jakub Dawidek, and NAND Flash Support by + Semihalf.</p> + + <p>We are pleased to <a + href="http://www.FreeBSDfoundation.org/announcements.shtml"> + announce</a> the addition of George Neville-Neil to our + board of directors. Deb Goodkin, our Director of + Operations, was <a + href="http://bsdtalk.blogspot.com/">interviewed by + bsdtalk</a>.</p> + + <p>We announced a call for project proposals. We will accept + proposals until April 30th. Please read <a + href="http://www.FreeBSDfoundation.org/documents /FreeBSD%20Foundation%20Proposals%20March%202012.pdf"> + Project Proposal Procedures</a> to find out more.</p> + + <p>&os; 9.0 was released and we are proud to say we funded 7 of the + new features!</p> + </body> + </project> + + <project cat='proj'> + <title>GNU-Free C++11 Stack</title> + + <contact> + <person> + <name> + <given>David</given> + <common>Chisnall</common> + </name> + <email>theraven@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Since the last status report, the combination of libc++ and + libcxxrt has received some additional testing and gained some new + features including support for ARM EABI. With clang 3.1, we now + pass all of the C++11 atomics tests.</p> + + <p>The xlocale implementation (required for libc++) has been tested + with a variety of ports that were originally written for the Darwin + implementation, and bugs that this testing uncovered have been + fixed. This should be released in 9.1.</p> + + <p>In -CURRENT, we are now building libsupc++ as a shared library. + This provides the ABI layer and building it as a shared library + means that we can replace it with libcxxrt easily. If you are + running -CURRENT, please try using libmap.conf to enable libcxxrt + instead of libsupc++.</p> + + <p>If libstdc++ is using libcxxrt, you can now link against both + libraries that are using libstdc++ and libc++, making the migration + slightly easier, although you cannot pass STL objects between + libraries using different STL versions.</p> + + <p>We still need a replacement for some parts of libgcc_s and for + the linker, but we're on track for a BSD licensed C++ stack in + 10.0.</p> + </body> + + <help> + <task>Test ports with libc++. Hopefully most will Just Work, but + others may need patches or have a hard dependency on + libstdc++.</task> + + <task>Enable building libc++ by default. This is dependent upon + building with clang, because the version of gcc in the base system + does not support C++11 and so can not be used to build + libc++.</task> + + <task>Removing libstdc++ from the base system and making it + available through ports for backwards compatibility.</task> + </help> + </project> + + <project cat='bin'> + <title>Clang Replacing GCC in the Base System</title> + + <contact> + <person> + <name> + <given>Brooks</given> + <common>Davis</common> + </name> + <email>brooks@FreeBSD.org</email> + </person> + + <person> + <name> + <given>David</given> + <common>Chisnall</common> + </name> + <email>theraven@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Dimitry</given> + <common>Andric</common> + </name> + <email>dim@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Ed</given> + <common>Schouten</common> + </name> + <email>ed@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Pawel</given> + <common>Worach</common> + </name> + <email>pawel.worach@gmail.com</email> + </person> + + <person> + <name> + <given>Roman</given> + <common>Divacky</common> + </name> + <email>rdivacky@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang"> + Building &os; with Clang</url> + </links> + + <body> + <p>Both &os; 10.0-CURRENT and 9.0-STABLE now have Clang 3.0 release + installed by default. At least on 10.0-CURRENT, both world and the + GENERIC kernel can be completely built without any -Werror + warnings. This may not be the case for all custom kernel + configurations yet.</p> + + <p>As of r231057, there is a WITH_CLANG_EXTRAS option for + src.conf(5), which will enable a number of additional LLVM and + Clang tools, such as 'llc' and 'opt'. These tools are mainly useful + for people that want to manipulate LLVM bitcode (.bc) and LLVM + assembly language (.ll) files, or want to tinker with LLVM and + Clang themselves.</p> + + <p>Also, as of r232322, there is a WITH_CLANG_IS_CC option for + src.conf(5), which will install Clang as /usr/bin/cc, /usr/bin/c++ + and /usr/bin/cpp, making it the default system compiler. Unless you + also use the WITHOUT_GCC option, gcc will still be available as + /usr/bin/gcc, /usr/bin/g++ and /usr/bin/gcpp.</p> + + <p>The intent is to switch on this option by default rather sooner + than later, so we can start preparing for shipping 10.0-RELEASE + with Clang as as the default system compiler, and deprecating + gcc.</p> + + <p>In other news, we will import a newer snapshot of Clang soon, + since upstream LLVM/Clang has already announced their 3.1 release + will be branched April 16, 2012. Most likely, the actual 3.1 + release will be follow a few weeks later, after which we will do + another import.</p> + + <p>Last but not least, there are many ports people working on + making our ports compile properly with Clang. Fixes are checked in + on a very regular basis now, and full exp-runs with Clang are also + done fairly regularly. Of course, there are always a few difficult + cases, especially with very old software that will not even compile + with newer versions of gcc, let alone clang.</p> + </body> + + <help> + <task>One of the most important tasks at the moment is to actually + build and run your entire &os; system with Clang, as much as + possible. Any compile-time or run-time problems should be reported + to the appropriate mailing list, or filed as a PR. If you have + patches and/or workarounds, that would be even better.</task> + + <task>Clang should have gotten better support for cross-compiling + after 3.0, so as soon as a 3.1 version is imported, we will need to + look at ways to get the &os; world and kernels to cross-compile. + This is mainly of use for ARM and MIPS, which are architectures you + usually do not want to build natively on.</task> + + <task>Help to make unwilling ports build with Clang is always + needed, and greatly appreciated. Please mail the maintainer of your + favorite port with patches, or file PRs.</task> + </help> + </project> + + <project cat='kern'> + <title>HDMI/DisplayPort Audio Support in HDA Sound Driver + (snd_hda)</title> + + <contact> + <person> + <name> + <given>Alexander</given> + <common>Motin</common> + </name> + <email>mav@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>snd_hda(4) driver got number of improvements to better support + HDMI/DisplayPort audio, such as:</p> + + <ul> + <li>Added fetching EDID-Like Data from the CODEC and video + driver, describing audio capabilities of the display device.</li> + + <li>Added setting HDMI/DP-specific CODEC options, such as number + of channels, speakers configuration and channels mapping.</li> + + <li>Added support for more multichannel formats. For HDMI and + DisplayPort device now supported: 2.0, 2.1, 3.0, 3.1, 4.0, 4.1, + 5.0, 5.1, 6.0, 6.1, 7.0 and 7.1 channels.</li> + + <li>Added support for compressed streams passthrough with data + rate 6.144 - 24Mbps, such as DTS-HD Master Audio or Dolby + TrueHD.</li> + + <li>Added support for HDA bus multiplexing to handle higher data + rates (up to 92, 184 or more Mbps, depending on hardware + capabilities). It allows to handle several 192/24/8 LPCM playback + streams simultaneously.</li> + </ul> + + <p>Above functionality was successfully tested on NVIDIA GT210 and + GT520 video cards with nvidia-driver-290.10 driver. HDMI audio on + older NVIDIA ION and Geforce 8300 boards still does not work for + unknown reason. There are also successful reports about Intel video + with latest KMS-based drivers. Support for ATI cards is limited to + older cards, because video driver supporting newer cards does + not support HDMI audio.</p> + + <p>The code was committed to HEAD and merged to 9-STABLE + branch.</p> + + <p>Project sponsored by iXsystems, Inc.</p> + </body> + + <help> + <task>Make better use of received EDID-Like Data.</task> + + <task>Identify and fix problem with older NVIDIA cards.</task> + </help> + </project> + + <project cat='proj'> + <title>The FreeNAS Project</title> + + <contact> + <person> + <name> + <given>Josh</given> + <common>Paetzel</common> + </name> + <email>jpaetzel@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Xin</given> + <common>Li</common> + </name> + <email>delphij@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeNAS.org" /> + </links> + + <body> + <p>FreeNAS 8.0.4 was released last month, which marks the end of + the 8.0.x branch in FreeNAS.</p> + + <p>FreeNAS 8.2.0 is in BETA currently, and will hopefully be + released by the end of April.</p> + + <p>It features a number of improvements over the 8.0.x line, + including plugin support, (the ability to run arbitrary software in + jails), as well as better integration between command line ZFS and + the GUI.</p> + + <p>Once 8.2.0 is out it will be quickly followed up with 8.3.0, + which will include a number of driver updates as well as the long + awaited ZFS v28.</p> + </body> + </project> + + <project cat='kern'> + <title>isci(4) SAS Driver</title> + + <contact> + <person> + <name> + <given>Jim</given> + <common>Harris</common> + </name> + <email>jimharris@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>An Intel-supported isci(4) driver, for the integrated SAS + controller in Intel's C600 chipsets, is now available in head, + stable/9, stable/8 and stable/7.</p> + + <p>The isci(4) driver will also be part of the &os; 8.3 + release.</p> + </body> + </project> + + <project cat='proj'> + <title>Growing filesystems online</title> + + <contact> + <person> + <name> + <given>Edward Tomasz</given> + <common>Napierala</common> + </name> + <email>trasz@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The goal of this project is to make it possible to grow a + filesystem, both UFS and ZFS, while it's mounted read-write. This + includes changes to both filesystems, GEOM infrastructure, and the + da(4) driver. For testing purposes, I've also added resizing to + mdconfig(8) and implemented LUN resizing in CAM Target Layer.</p> + + <p>From the system administrator point of view, this makes it + possible to resize mounted partition using gpart(8) and then resize + the filesystem on it using growfs(8) - all without unmounting it + first; especially useful if it's a root filesystem.</p> + + <p>All the functionality works and is in the process of being + refined, reviewed and merged to HEAD.</p> + + <p>This project is sponsored by The FreeBSD Foundation.</p> + </body> + + <help> + <task>The write suspension infrastructure (/dev/ufssuspend) + implemented to make resizing possible makes it also possible to + implement online tunefs(8) and fsck(8).</task> + + <task>Right now, there is no way for a GEOM class to veto resizing + — classes are notified about resize and they can either adapt, + or wither. Many classes store their metadata in the last sector, + though, so resizing a partition containing e.g. gmirror will make + it inoperable. It would be nice if geom_mirror(4) could veto + resizing, so the administrator attempting to shoot himself in the + foot would get a warning.</task> + </help> + </project> + + <project cat='team'> + <title>Release Engineering Team Status Report</title> + + <contact> + <person> + <name> + <given>Release Engineering Team</given> + </name> + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://www.FreeBSD.org/releng/" /> + </links> + + <body> + <p>On behalf of the FreeBSD Project the Release Engineering Team + was are pleased to announce the release of the &os; + 8.3-RELEASE on April 18th, 2012.</p> + + <p>With the &os; 8.3 release cycle completed our focus shifts to + preparing for the &os; 9.1-RELEASE. A schedule will be posted + shortly, with the release target date set for mid-July 2012.</p> + </body> + </project> + + <project cat='proj'> + <title>&os; Services Control</title> + + <contact> + <person> + <name> + <given>Tom</given> + <common>Rhodes</common> + </name> + <email>trhodes@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="http://people.FreeBSD.org/~trhodes/fsc/" /> + </links> + + <body> + <p>After a while of moving and getting a new job, I finally got + back to this project (also thanks to several submissions by + Julian Fagir), a new version has been uploaded along with a short + description page. The current version supports more options, a + configuration file, and updated rc.d script. It also includes + manual page updates and an optional debugging mode.</p> + </body> + </project> + + <project cat='bin'> + <title>The bsdconfig(8) utility</title> + + <contact> + <person> + <name> + <given>Devin</given> + <common>Teske</common> + </name> + <email>dteske@FreeBSD.org</email> + </person> + <person> + <name> + <given>Ron</given> + <common>McDowell</common> + </name> + <email>rcm@fuzzwad.org</email> + </person> + </contact> + + <links> + <url href="http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdconfig/"> + OpenSource Development Tree</url> + <url href="http://druidbsd.sf.net/download/bsdconfig/bsdconfig-20120512-1.svg"> + Menu Map w/ Includes</url> + <url href="http://druidbsd.sf.net/download/bsdconfig/bsdconfig-20120512-1i.svg"> + Menu Map w/o Includes</url> + </links> + + <body> + <p>Approaching 20,000 lines of sh(1) code, the bsdconfig(8) tool is + approximately 70% complete. Upon completion of this project, + bsdconfig(8) will represent (in conjunction with + already-existing bsdinstall(8)) a complete set of utilities + capable of purposefully deprecating sysinstall(8) in &os; 9 and + higher. This project has been a labor of love for Ron McDowell + and I for over 90 days now and we are approaching the completion + of this wonderful tool.</p> + </body> + + <help> + <task> + The "installer suite" modules for acquiring/installing binary + packages and additional distribution sets. Startup services module. + </task> + </help> + </project> +</report> diff --git a/en_US.ISO8859-1/htdocs/news/status/report-sample.xml b/en_US.ISO8859-1/htdocs/news/status/report-sample.xml new file mode 100644 index 0000000000..8269c77e14 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-sample.xml @@ -0,0 +1,51 @@ +<!-- $FreeBSD: www/en/news/status/report-sample.xml,v 1.6 2005/07/06 11:42:11 mlaier Exp $ --> + +<!-- Please send your reports to: monthly@FreeBSD.org --> + +<!-- Optional category tag. --> +<!-- Tags include: proj, doc, kern, bin, arch, ports, vendor, misc, soc --> +<project cat='proj'> + <title>Status Report Sample</title> + + <!-- Required section --> + <contact> + <person> + <name> + <given>John</given> + + <common>Smith</common> + </name> + + <email>test@FreeBSD.org</email> + </person> + </contact> + + <!-- Optional section but highly encouraged. --> + <links> + <!-- A hypertext link with a description... --> + <url href="http://www.example.com/project/url/here">Description + here.</url> + + <!-- And/or one without. --> + <url href="http://www.example.net/another/url" /> + </links> + + <!-- Required section. --> + <body> + <p>You can start your first paragraph here. Generally speaking, you + will only usually submit one paragraph per status report, as they + are intended to be somewhat brief. If, however, you find it + necessary to write one with multiple paragraphs, it's fairly + straightforward.</p> + + <p>Just start another `p' tag.</p> + </body> + + <!-- Optional section for listing tasks. --> + <help> + <task>Some work you need help with</task> + <task>More work</task> + <task>Keep these short and to the point</task> + </help> + +</project> diff --git a/en_US.ISO8859-1/htdocs/news/status/report.xsl b/en_US.ISO8859-1/htdocs/news/status/report.xsl new file mode 100644 index 0000000000..c07760825a --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report.xsl @@ -0,0 +1,178 @@ +<?xml version="1.0" encoding="ISO-8859-1" ?> +<!DOCTYPE xsl:stylesheet PUBLIC "-//FreeBSD//DTD FreeBSD XSLT 1.0 DTD//EN" + "http://www.FreeBSD.org/XML/www/share/sgml/xslt10-freebsd.dtd" [ +<!ENTITY base "../.."> +<!ENTITY title "FreeBSD Quarterly Status Report"> +<!ENTITY email "freebsd-www"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<!-- $FreeBSD: www/en/news/status/report.xsl,v 1.11 2007/04/10 03:35:31 brd Exp $ --> + +<!-- Standard header material --> +<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" + xmlns:cvs="http://www.FreeBSD.org/XML/CVS"> + + <xsl:import href="http://www.FreeBSD.org/XML/www/lang/share/sgml/libcommon.xsl"/> + + <xsl:variable name="date"> + <xsl:value-of select="//cvs:keyword[@name='freebsd']"/> + </xsl:variable> + + <xsl:variable name="ucletters" + select="'ABCDEFGHIJKLMNOPQRSTUVWXYZ'"/> + <xsl:variable name="lcletters" + select="'abcdefghijklmnopqrstuvwxyz'"/> + + <xsl:output type="html" encoding="iso-8859-1"/> + + <xsl:template match="report"> + <html> + &header1; + + <body> + + <div id="containerwrap"> + <div id="container"> + &header2; + + <div id="content"> + <div id="SIDEWRAP"> + &nav; + </div> <!-- SIDEWRAP --> + + <div id="contentwrap"> + &header3; + + <!-- Process all the <sections>, in order --> + <xsl:apply-templates select="section"/> + + <hr/> + + <!-- Generate a table of contents, sorted --> + <xsl:for-each select="category"> + <h3><xsl:value-of select="description"/></h3> + <xsl:variable name="cat-short" select="name"/> + <ul> + <xsl:for-each select="//project[@cat=$cat-short and @summary]"> + <xsl:sort select="translate(title, $lcletters, $ucletters)"/> + <li><a><xsl:attribute name="href">#<xsl:value-of + select="translate(title, ' ', + '-')"/></xsl:attribute><xsl:value-of select="title"/></a> + </li> + </xsl:for-each> + + <xsl:for-each select="//project[@cat=$cat-short and not(@summary)]"> + <xsl:sort select="translate(title, $lcletters, $ucletters)"/> + <li><a><xsl:attribute name="href">#<xsl:value-of + select="translate(title, ' ', + '-')"/></xsl:attribute><xsl:value-of select="title"/></a> + </li> + </xsl:for-each> + </ul> + </xsl:for-each> + <ul> + <xsl:for-each select="//project[not(@cat)]"> + <xsl:sort select="translate(title, $lcletters, $ucletters)"/> + <li><a><xsl:attribute name="href">#<xsl:value-of + select="translate(title, ' ', + '-')"/></xsl:attribute><xsl:value-of select="title"/></a> + </li> + </xsl:for-each> + </ul> + + <hr/> + + <!-- Process each project, sorted --> + <xsl:apply-templates select="project"> + <xsl:sort select="translate(title, $lcletters, $ucletters)"/> + </xsl:apply-templates> + + <!-- Standard footer --> + <a href="../news.html">News Home</a> | <a href="status.html">Status Home</a> + </div> <!-- contentwrap --> + + <br class="clearboth" /> + </div> <!-- content --> + <div id="FOOTER"> + ©right;<br /> + &date; + </div> <!-- FOOTER --> + </div> <!-- container --> + </div> <!-- containerwrap --> + </body> + </html> + </xsl:template> + + <!-- Everything that follows are templates for the rest of the content --> + + <!-- A section creates a header, and copies in all the <p> elements from + itself --> + <xsl:template match="section"> + <h1><xsl:value-of select="title"/></h1> + + <xsl:copy-of select="p"/> + </xsl:template> + + <!-- A project creates a header, and then process the three components of + a project report (links, contact details, project body) in turn --> + <xsl:template match="project"> + <h2><a> + <xsl:attribute name="name"><xsl:value-of + select="translate(title, ' ', '-')"/></xsl:attribute><xsl:value-of + select="title"/></a></h2> + + <xsl:apply-templates select="links"/> + + <xsl:apply-templates select="contact"/> + + <xsl:apply-templates select="body"/> + + <xsl:apply-templates select="help"/> + + <hr/> + </xsl:template> + + <!-- Create a paragraph to hold the contact information. Iterate over + each <person> element, copying their data in. All but the last + person has a terminating <br> in the output. --> + <xsl:template match="contact"> + <p> + <xsl:for-each select="person"> + Contact: <xsl:value-of select="name"/> <<a> + <xsl:attribute name="href">mailto:<xsl:value-of select="email"/></xsl:attribute><xsl:value-of select="email"/></a>> + <xsl:if test="position() != last()"><br/></xsl:if> + </xsl:for-each> + </p> + </xsl:template> + + <!-- Create a paragraph to hold the link information. Iterate over each + <url> element, copying their data in. All but the last link has a + terminating <br> in the output. --> + <xsl:template match="links"> + <p> + <xsl:for-each select="url"> + URL: + <a href="{@href}" title="{.}"> <!-- Copy in the href attribute --> + <xsl:value-of select="@href"/> + </a> + <xsl:if test="position() != last()"><br/></xsl:if> + </xsl:for-each> + </p> + </xsl:template> + + <!-- Body is a doddle. Since it contains HTML we just copy in all the + child elements. --> + <xsl:template match="body"> + <xsl:copy-of select="child::node()"/> + </xsl:template> + + <xsl:template match="help"> + <h3>Open tasks:</h3> + <ol> + <xsl:for-each select="task"> + <li><xsl:copy-of select="child::node()"/></li> + </xsl:for-each> + </ol> + </xsl:template> +</xsl:stylesheet> diff --git a/en_US.ISO8859-1/htdocs/news/status/status.sgml b/en_US.ISO8859-1/htdocs/news/status/status.sgml new file mode 100644 index 0000000000..c414a6aa8e --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/status.sgml @@ -0,0 +1,191 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA "../.."> +<!ENTITY date "$FreeBSD: www/en/news/status/status.sgml,v 1.67 2012/01/27 10:00:58 danger Exp $"> +<!ENTITY title "FreeBSD Quarterly Status Reports"> +<!ENTITY % navinclude.about "INCLUDE"> +]> + +<html> + &header; + + <h2>Next submissions due: July 15th, 2012</h2> + + <p>Use the <a href="http://www.FreeBSD.org/cgi/monthly.cgi">xml + generator</a> or download and edit the <a href="report-sample.xml"> + xml-template</a>. Submissions should be submitted by e-mail to + <a href="mailto:monthly@FreeBSD.org">monthly@FreeBSD.org</a>.</p> + + <hr> + + <p>One of the benefits of the FreeBSD development model is a focus on + centralized design and implementation, in which the operating system is + maintained in a central repository, and discussed on centrally maintained + lists. This allows for a high level of coordination between authors of + various components of the system, and allows policies to be enforced over + the entire system, covering issues ranging from architecture to style. + However, as the FreeBSD developer community has grown, and the rate of + both mailing list traffic and tree modifications has increased, making it + difficult even for the most dedicated developer to remain on top of all + the work going on in the tree.</p> + + <p>The FreeBSD Quarterly Development Status Report attempts to address this + problem by providing a vehicle that allows developers to make the broader + community aware of their on-going work on FreeBSD, both in and out of the + central source repository. For each project and sub-project, a one + paragraph summary is included, indicating progress since the last summary. + If it is a new project, or if a project has not submitted any prior status + reports, a short description may precede the status information.</p> + + <p>These status reports may be reproduced in whole or in part, as long as the + source is clearly identified and appropriate credit given.</p> + + <h2>2012</h2> + + <ul> + <li><a href="report-2012-01-2012-03.html">January, 2012 - + March, 2012</a></li> + </ul> + + <h2>2011</h2> + + <ul> + <li><a href="report-2011-10-2011-12.html">October, 2011 - + December, 2011</a></li> + <li><a href="report-2011-07-2011-09.html">July, 2011 - + September, 2011</a></li> + <li><a href="report-2011-04-2011-06.html">April, 2011 - + June, 2011</a></li> + <li><a href="report-2011-01-2011-03.html">January, 2011 - + March, 2011</a></li> + </ul> + + <h2>2010</h2> + + <ul> + <li><a href="report-2010-10-2010-12.html">October, 2010 - + December, 2010</a></li> + <li><a href="report-2010-07-2010-09.html">July, 2010 - + September, 2010</a></li> + <li><a href="report-2010-04-2010-06.html">April, 2010 - + June, 2010</a></li> + <li><a href="report-2010-01-2010-03.html">January, 2010 - + March, 2010</a></li> + </ul> + + <h2>2009</h2> + + <ul> + <li><a href="report-2009-10-2009-12.html">October, 2009 - + December, 2009</a></li> + <li><a href="report-2009-04-2009-09.html">April, 2009 - + September, 2009</a></li> + <li><a href="report-2009-01-2009-03.html">January, 2009 - + March, 2009</a></li> + </ul> + + <h2>2008</h2> + + <ul> + <li><a href="report-2008-10-2008-12.html">October, 2008 - + December, 2008</a></li> + <li><a href="report-2008-07-2008-09.html">July, 2008 - + September, 2008</a></li> + <li><a href="report-2008-04-2008-06.html">April, 2008 - + June, 2008</a></li> + <li><a href="report-2008-01-2008-03.html">January, 2008 - + March, 2008</a></li> + </ul> + + <h2>2007</h2> + + <ul> + <li><a href="report-2007-10-2007-12.html">October, 2007 - + December, 2007</a></li> + <li><a href="report-2007-07-2007-10.html">July, 2007 - + October, 2007</a></li> + <li><a href="report-2007-04-2007-06.html">April, 2007 - + June, 2007</a></li> + <li><a href="report-2007-01-2007-03.html">January, 2007 - + March, 2007</a></li> + </ul> + + <h2>2006</h2> + + <ul> + <li><a href="report-2006-10-2006-12.html">October, 2006 - + December, 2006</a></li> + <li><a href="report-2006-06-2006-10.html">June, 2006 - + October, 2006</a></li> + <li><a href="report-2006-04-2006-06.html">April, 2006 - + June, 2006</a></li> + <li><a href="report-2006-01-2006-03.html">January, 2006 - + March, 2006</a></li> + </ul> + + <h2>2005</h2> + + <ul> + <li><a href="report-2005-10-2005-12.html">October, 2005 - + December, 2005</a></li> + <li><a href="report-2005-07-2005-10.html">July, 2005 - + October, 2005</a></li> + <li><a href="report-2005-03-2005-06.html">March, 2005 - + June, 2005</a></li> + <li><a href="report-2005-01-2005-03.html">January, 2005 - + March, 2005</a></li> + </ul> + + <h2>2004</h2> + + <ul> + <li><a href="report-2004-07-2004-12.html">July, 2004 - + December, 2004</a></li> + <li><a href="report-2004-05-2004-06.html">May, 2004 - + June, 2004</a></li> + <li><a href="report-2004-03-2004-04.html">March, 2004 - + April, 2004</a></li> + <li><a href="report-2004-01-2004-02.html">January, 2004 - + February, 2004 </a></li> + </ul> + + <h2>2003</h2> + + <ul> + <li><a href="report-2003-10-2003-12.html">October, 2003 - + December, 2003 </a></li> + <li><a href="report-2003-03-2003-09.html">March, 2003 - + September, 2003 </a></li> + <li><a href="report-2003-01-2003-02.html">January, 2003 - + February, 2003 </a></li> + </ul> + + <h2>2002</h2> + + <ul> + <li><a href="report-2002-11-2002-12.html">November, 2002 - + December, 2002 </a></li> + <li><a href="report-2002-09-2002-10.html">September, 2002 - + October, 2002 </a></li> + <li><a href="report-2002-07-2002-08.html">July, 2002 - August, 2002 + </a></li> + <li><a href="report-2002-05-2002-06.html">May, 2002 - June, 2002 + </a></li> + <li><a href="report-2002-02-2002-04.html">February, 2002 - April, + 2002</a></li> + <li><a href="report-2001-12-2002-01.html">December, 2001 - January, + 2002</a></li> + </ul> + + <h2>2001</h2> + + <ul> + <li><a href="report-2001-11.html">November, 2001</a></li> + <li><a href="report-2001-09.html">September, 2001</a></li> + <li><a href="report-2001-08.html">August, 2001</a></li> + <li><a href="report-2001-07.html">July, 2001</a></li> + <li><a href="report-2001-06.html">June, 2001</a></li> + </ul> + + &footer; + </body> +</html> |