diff --git a/en/news/status/Makefile b/en/news/status/Makefile
index 4f90462383..77c1447d09 100644
--- a/en/news/status/Makefile
+++ b/en/news/status/Makefile
@@ -1,53 +1,54 @@
-# $FreeBSD: www/en/news/status/Makefile,v 1.43 2008/08/19 23:04:12 brd Exp $
+# $FreeBSD: www/en/news/status/Makefile,v 1.44 2008/11/11 03:52:54 brd 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
XSLT.DEFAULT= report.xsl
# Install a sample This quarter included some very exciting work including the
+ the release of FreeBSD 6.4 and the much anticipated release of
+ FreeBSD 7.1. We also launched our own official FreeBSD Forums.
+ The first Bugathon of the year will be held this weekend, see
+ below for more information and how to participate. Thanks to all the reporters for the excellent work! We hope you
+ enjoy reading. A new channel
+ has been setup on YouTube
+ 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. We are currently looking for more videos from
+ BSDCan,
+ EuroBSDCon,
+ AsiaBSDCon,
+ 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. 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. Last year, we didn't have many Bugathons - this year is planned
+ to be different! 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. 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. 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. 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. Join us on IRC: EFnet #FreeBSD-bugbusters from Friday 2009-01-30
+ to Sunday 2009-02-01. Don't miss this event! The next Bugathon (TBA) will have topics in different special
+ interest areas. We will be having our next Bugathon on 2009-01-30 to 2009-02-01
+ (see separate entry). 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. 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
+ In addition, another new report, oriented towards PR submitters,
+ summarizes the
+ 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. One of those volunteers, Bruce Cran (brucec@), has now been
+ released from mentorship. Mark Linimon (linimon@) continues to work on more new prototype
+ reports, including: The
+ The overall PR count jumped to over 5600 during the 6.4/7.1
+ release cycle, but has come down a bit. Hungarian translation of the
+ FreeBSD Documentation Project Primer for New Contributors
+
+ has been finished and now it is available both
+ online
+
+ and
+
+ for download. 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. Beside the continuous maintenance of the Hungarian documentation
+ and web pages, a new article translation has been added to the
+ Hungarian Documentation Set,
+ CUPS. The FreeBSD forums were publicly launched on November 16th, 2008
+ as a complementary support channel to our great mailing lists. 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. 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. 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.
+
+ Click here
+
+ to find out more about the projects. 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. Read our
+
+ end-of-year newsletter, to find out what else we've done to
+ help The FreeBSD Project and community. 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 chapter, with many new translated chapters. At this
+ pace, we hope to have a complete Greek Handbook by 8.0-RELEASE. More volunteers are always welcome of course, as there is still
+ plenty of work to be done. The multi-IPv4/v6/no-IP jails project patch has finally been
+ committed to FreeBSD-CURRENT at the end of November. 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. 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. The BSD# Project is devoted to porting the Mono .NET framework
+ and applications to the FreeBSD operating system. 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 is
+ 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. 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. 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. 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. 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. GNOME has been updated to 2.24.3. KDE has been updated to 4.1.4. X.Org version 7.4 The following large changes are in the pipeline:
+
+
+
+
+
+
+
+
+
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.
+ +We have added 5 new committers since the last report, and 2 + older ones have rejoined.
+ + +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:
+ +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).
+ ++
Since last status report both 7.1-RELEASE (5 January 2009) and + 6.4-RELEASE (28 November 2008) have been released. Starting with + the 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.
+ +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:
+ +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 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.
+ +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.
+ + + ++
FreeBSD mmc(4)/mmcsd(4) stack was improved to support all + MMC/SD card types existing now. Was added support for SD High + Capacity (SDHC) cards and MultiMediaCards (MMC) memory cards of + normal (up to 2GB) and high capacity. Added support 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 + used card and controller.
+ +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.
+ + + ++
snd_hda(4) audio driver was significantly improved to provide + better functionality according to High Definition Audio (HDA) and + Universal Audio Architecture (UAA) specifications.
+ +According to HDA specification, driver now supports multiple + codecs per HDA bus and multiple audio functional groups per + codec.
+ +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 provided + as separate pcm device and can be used independently.
+ +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.
+ +Also new driver implements SPDIF/HDMI digital audio, + suspend/resume and initial parts of multichannel support.
+ + + +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:
+ +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
+ + +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.
+ +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.
+ +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.
+ +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.
+ +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.
+ + +Use the xml generator or download and edit the xml-template. Submissions should be submitted by e-mail to monthly@FreeBSD.org.
One of the benefits of the FreeBSD development model is a focus on centralized design and implementation, in which the operating system is maintained in a central repository, and discussed on centrally maintained lists. This allows for a high level of coordination between authors of various components of the system, and allows policies to be enforced over the entire system, covering issues ranging from architecture to style. However, as the FreeBSD developer community has grown, and the rate of both mailing list traffic and tree modifications has increased, making it difficult even for the most dedicated developer to remain on top of all the work going on in the tree.
The FreeBSD 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.
These status reports may be reproduced in whole or in part, as long as the source is clearly identified and appropriate credit given.