diff --git a/en/news/status/Makefile b/en/news/status/Makefile
index 77c1447d09..bb3bcad392 100644
--- a/en/news/status/Makefile
+++ b/en/news/status/Makefile
@@ -1,54 +1,55 @@
-# $FreeBSD: www/en/news/status/Makefile,v 1.44 2008/11/11 03:52:54 brd Exp $
+# $FreeBSD: www/en/news/status/Makefile,v 1.45 2009/01/29 06:50:26 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
+XMLDOCS+= report-2009-01-2009-03
XSLT.DEFAULT= report.xsl
# Install a sample 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
+ BSDCan Website
+
+ for more information. Thanks to all the reporters for the excellent work! We hope you
+ enjoy reading. We continue to classify PRs as they arrive, with 'tags'
+ corresponding to the kernel subsystem, or man page referencesfor
+ userland PRs. These tags, in turn, produce lists of PRs sorted both
+
+
+ by tag
+
+ and
+
+ by manpage
+
+ . Mark Linimon (linimon@) has created
+
+ special reports for the Release Engineering Team
+
+ 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
+
+ 'customised reports for developers'
+
+ announced in the last status report. A full list of all the
+
+ automatically generated reports
+
+ is also available. Any recommendations for reports which do not
+ currently exist but which would be beneficial are welcomed. Mark
+ Linimon also continues attempting to define the general problem and
+ investigating possible new workflow models, and will be presenting
+ on the subject at BSDCan. 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. Since the last status report, the number of open bugs has
+ continued to hover around the 5600 mark, although has began to rise
+ with the 7.2 ports freeze. 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. 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. 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. 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. We are proud to announce that the FreeBSD Hungarian web pages
+ have been extended by the following items: We are still hoping that having the
+ FDP
+ Primer
+
+ 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
+
+ introduction
+
+ (in Hungarian).
+ In Februay 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. The website (at least the areas we see as relevant for a
+ translation) is translated and updated constantly. More volunteers are always welcome of course, as there is
+ still plenty of work to be done.
+
+
+
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.
+ +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.
+ + +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: +
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.
+ + +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 targetted at early September 2009.
+ +The &os; Dutch Documentation Project is an ongoing project + to translate &os; Documentation into the Dutch language.
+ +The translation of the Handbook was completed last January. It
+ is kept up-to-date with the English version. Furthermore five
+ articles and the
+
Some initial work has been done to translate the website, but + most likely more translators are needed to fully realize it.
+ + ++ Sysinfo + + a shell script which purpose is to automatically gather system + information and document 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.
+ +It consists of several modules (also shell scripts), thus is + easily extensible and provides an easy way to inspect overall + system configuration.
+ +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 + + forums + + , or alternatively you can send me a private email.
+ +The tool itself can now be installed using the Ports tree from + the + + sysutils/sysinfo + + port.
+ + +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: +
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.
+ +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: +
After the first mail from Alexander Eichner on the vbox-dev + mailinglist, we are 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 vbox developers, Gustau + Perez and Ulf Lilleengen. If you like to play with the current port + you can checkout the port + + here + + . Please do not ping us about any problems we know about a lot and + still working to get all solved befor we officel call for + testing.
+ + +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.
+ +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).
+ +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.
+ +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.
+ +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.
+