aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rwxr-xr-xen/cgi/man-wrapper.cgi8
-rwxr-xr-xen/cgi/man.cgi1229
-rw-r--r--en/news/status/report-2001-06.xml826
-rw-r--r--en/news/status/report-2001-07.xml1204
-rw-r--r--en/news/status/report-2001-08.xml1519
-rw-r--r--en/news/status/report-2001-09.xml944
-rw-r--r--en/news/status/report-2001-11.xml1025
-rw-r--r--en/news/status/report-2001-12-2002-01.xml717
-rw-r--r--en/news/status/report-2002-02-2002-04.xml1297
-rw-r--r--en/news/status/report-2002-05-2002-06.xml1446
-rw-r--r--en/news/status/report-2002-07-2002-08.xml1057
-rw-r--r--en/news/status/report-2002-09-2002-10.xml1021
-rw-r--r--en/news/status/report-2002-11-2002-12.xml877
-rw-r--r--en/news/status/report-2003-01-2003-02.xml700
-rw-r--r--en/news/status/report-2003-03-2003-09.xml970
-rw-r--r--en/news/status/report-2003-10-2003-12.xml1361
-rw-r--r--en/news/status/report-2004-01-2004-02.xml865
-rw-r--r--en/news/status/report-2004-03-2004-04.xml1151
-rw-r--r--en/news/status/report-2004-05-2004-06.xml1103
-rw-r--r--en/news/status/report-2004-07-2004-12.xml2337
-rw-r--r--en/news/status/report-2005-01-2005-03.xml2143
-rw-r--r--en/news/status/report-2005-03-2005-06.xml2169
22 files changed, 0 insertions, 25969 deletions
diff --git a/en/cgi/man-wrapper.cgi b/en/cgi/man-wrapper.cgi
deleted file mode 100755
index f05975c292..0000000000
--- a/en/cgi/man-wrapper.cgi
+++ /dev/null
@@ -1,8 +0,0 @@
-#!/usr/bin/perl -T
-# Copyright (c) Wolfram Schneider, Berlin. Sep 1997.
-#
-# FreeBSD man script
-#
-# $FreeBSD: www/en/cgi/man.cgi,v 1.4 2000/01/05 15:47:44 phantom Exp $
-
-require '/usr/local/www/bsddoc/bin/man.cgi';
diff --git a/en/cgi/man.cgi b/en/cgi/man.cgi
deleted file mode 100755
index 1db02f1c53..0000000000
--- a/en/cgi/man.cgi
+++ /dev/null
@@ -1,1229 +0,0 @@
-#!/usr/bin/perl -T
-#
-# Copyright (c) 1996-2004 Wolfram Schneider <wosch@FreeBSD.org>
-# All rights reserved.
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions
-# are met:
-# 1. Redistributions of source code must retain the above copyright
-# notice, this list of conditions and the following disclaimer.
-# 2. Redistributions in binary form must reproduce the above copyright
-# notice, this list of conditions and the following disclaimer in the
-# documentation and/or other materials provided with the distribution.
-#
-# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
-# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
-# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-# SUCH DAMAGE.
-#
-# man.cgi - HTML hypertext FreeBSD man page interface
-#
-# based on bsdi-man.pl,v 2.17 1995/10/05 16:48:58 sanders Exp
-# bsdi-man -- HTML hypertext BSDI man page interface
-# based on bsdi-man.pl,v 2.10 1993/10/02 06:13:23 sanders Exp
-# by polk@BSDI.COM 1/10/95
-# BSDI Id: bsdi-man,v 1.2 1995/01/11 02:30:01 polk Exp
-# Dual CGI/Plexus mode and new interface by sanders@bsdi.com 9/22/1995
-#
-# $Id: man.cgi,v 1.149 2005-06-27 09:55:49 wosch Exp $
-
-#use Data::Dumper;
-#use Carp;
-
-
-$www{'title'} = 'FreeBSD Hypertext Man Pages';
-$www{'home'} = 'http://www.FreeBSD.org';
-$www{'head'} = qq[<A HREF="$www{'home'}">$www{'title'}</a> ] .
- qq[<IMG SRC="/gifs/littlelogo.gif">] .
- "";
-
-$command{'man'} = 'man'; # 8Bit clean man
-$command{'man'} = '/home/wosch/bin/cgi-man'; # 8Bit clean man
-$command{'man'} = '/usr/bin/man'; # 8Bit clean man
-
-
-# Config Options
-# map sections to their man command argument(s)
-%sections = (
- '', '',
- 'All', '',
- '0', '',
-
- '1', '-S1',
- '1c', '-S1',
- '1C', '-S1',
- '1g', '-S1',
- '1m', '-S1',
- '2', '-S2',
- '2j', '-S2',
- '3', '-S3',
- '3S', '-S3',
- '3f', '-S3',
- '3j', '-S3',
- '3m', '-S3',
- '3n', '-S3',
- '3r', '-S3',
- '3s', '-S3',
- '3x', '-S3',
- '4', '-S4',
- '5', '-S5',
- '6', '-S6',
- '7', '-S7',
- '8', '-S8',
- '8c', '-S8',
- '9', '-S9',
- 'l', '-Sl',
- 'n', '-Sn',
-);
-
-$sectionpath = {
- 'HP-UX 11.22' => { 'path' => '1:1m:2:3:4:5:7:9' },
- 'HP-UX 11.20' => { 'path' => '1:1m:2:3:4:5:7:9' },
- 'HP-UX 11.11' => { 'path' => '1:1m:2:3:4:5:7:9' },
- 'HP-UX 11.00' => { 'path' => '1:1m:2:3:4:5:7:9' },
- 'HP-UX 10.20' => { 'path' => '1:1m:2:3:4:5:7:9' },
- 'HP-UX 10.10' => { 'path' => '1:1m:2:3:4:5:7:9' },
- 'HP-UX 10.01' => { 'path' => '1:1m:2:3:4:5:7:9' },
- 'SunOS 5.9' => {
- 'path' => '1:1m:1s:2:3:3c:3malloc:3dl:3nsl:3socket:3ldap:3nisdb:3rac:3resolv:3rpc:3slp:3xfn:3proc:3rt:3thr:3elf:3kvm:3kstat:3m:3mp:3pam:3sched:3aio:3bsm:3cpc:3sec:3secdb:3cfgadm:3crypt:3devid:3devinfo:3door:3lib:3libucb:3head:3nvpair:3rsm:7:7d:7fs:7i:7m:7p:9:9e:9f:9p:9s:4:5:4b:3gen:3exacct:3sysevent:3wsreg:3dmi:3snmp:3tnf:3volmgt:3mail:3layout:3ext:3picl:3picltree:3pool:3project:1b:1c:1f:3ucb:3xnet:3curses:3plot:3xcurses:3gss:6:l:n',
- },
- 'SunOS 5.8' => {
- 'path' => '1:1m:1s:2:3:3c:3malloc:3dl:3nsl:3socket:3ldap:3krb:3nisdb:3rac:3resolv:3rpc:3slp:3xfn:3proc:3rt:3thr:3elf:3kvm:3kstat:3m:3mp:3pam:3sched:3aio:3bsm:3cpc:3sec:3secdb:3cfgadm:3crypt:3devid:3devinfo:3door:3lib:3libucb:3head:7:7d:7fs:7i:7m:7p:9:9e:9f:9s:4:5:4b:3gen:3dmi:3snmp:3tnf:3volmgt:3mail:3layout:3ext:1b:1c:1f:3ucb:3xnet:3curses:3plot:3xcurses:6:l:n',
- },
- 'SunOS 5.7' => {
- 'path' => '1:1m:1c:1f:1s:1b:2:3:3c:3s:3x:3xc:3n:3r:3t:3xn:3m:3k:3g:3e:3b:9f:9s:9e:9:4:5:7:7d:7i:7m:7p:7fs:4b:6:l:n',
- },
- 'SunOS 5.6' => {
- 'path' => '1:1m:1c:1f:1s:1b:2:3:3c:3s:3x:3xc:3xn:3r:3t:3n:3m:3k:3g:3e:3b:9f:9s:9e:9:4:5:7:7d:7i:7m:7p:7fs:4b:6:l:n',
- },
- 'SunOS 5.5.1' => {
- 'path' => '1:1m:1c:1f:1s:1b:2:3:3c:3s:3x:3xc:3xn:3r:3t:3n:3m:3k:3g:3e:3b:9f:9s:9e:9:4:5:7:7d:7i:7m:7p:7fs:4b:6:l:n',
- },
- 'OpenBSD 3.0' => {
- 'path' => '1:2:3:3p:4:5:6:7:8:9',
- },
- 'OpenBSD 3.1' => {
- 'path' => '1:2:3:3p:4:5:6:7:8:9',
- },
- 'OpenBSD 3.2' => { 'path' => '1:2:3:3p:4:5:6:7:8:9', },
- 'OpenBSD 3.3' => { 'path' => '1:2:3:3p:4:5:6:7:8:9', },
- 'OpenBSD 3.4' => { 'path' => '1:2:3:3p:4:5:6:7:8:9', },
- 'OpenBSD 3.5' => { 'path' => '1:2:3:3p:4:5:6:7:8:9', },
- 'OpenBSD 3.6' => { 'path' => '1:2:3:3p:4:5:6:7:8:9', },
-};
-
-foreach my $os (keys %$sectionpath) {
- foreach my $section (split(/:/, $sectionpath->{$os}{'path'})) {
- $section =~ /(.)(.*)/;
- $sectionpath->{$os}{$1} .=
- ($sectionpath->{$os}{$1} ? ':' : '') . $section;
- }
-}
-
-
-%sectionName =
- (
- '0', 'All Sections',
- '1', '1 - General Commands',
- '2', '2 - System Calls',
- '3', '3 - Subroutines',
- '4', '4 - Special Files',
- '5', '5 - File Formats',
- '6', '6 - Games',
- '7', '7 - Macros and Conventions',
- '8', '8 - Maintenance Commands',
- '9', '9 - Kernel Interface',
- 'n', 'n - New Commands',
- );
-
-$manLocalDir = '/usr/local/www/bsddoc/man';
-$manPathDefault = 'FreeBSD 5.4-RELEASE and Ports';
-#$manPathDefault = 'FreeBSD 5.1-RELEASE';
-
-%manPath =
- (
- 'FreeBSD 5.4-RELEASE and Ports', "$manLocalDir/FreeBSD-5.4-RELEASE/man:$manLocalDir/FreeBSD-5.4-RELEASE/openssl/man:$manLocalDir/FreeBSD-ports-5.3-RELEASE",
-
- 'FreeBSD 6.0-current', "$manLocalDir/FreeBSD-6-current",
- 'FreeBSD 5.4-stable', "$manLocalDir/FreeBSD-5.4-stable",
- 'FreeBSD 4.11-stable', "$manLocalDir/FreeBSD-4.11-stable",
-
- 'FreeBSD 5.4-RELEASE', "$manLocalDir/FreeBSD-5.4-RELEASE/man:$manLocalDir/FreeBSD-5.4-RELEASE/openssl/man",
- 'FreeBSD 5.3-RELEASE', "$manLocalDir/FreeBSD-5.3-RELEASE/man:$manLocalDir/FreeBSD-5.3-RELEASE/openssl/man",
- 'FreeBSD 5.2.1-RELEASE', "$manLocalDir/FreeBSD-5.2-RELEASE/man:$manLocalDir/FreeBSD-5.2-RELEASE/openssl/man",
- 'FreeBSD 5.2-RELEASE', "$manLocalDir/FreeBSD-5.2-RELEASE/man:$manLocalDir/FreeBSD-5.2-RELEASE/openssl/man",
- 'FreeBSD 5.1-RELEASE', "$manLocalDir/FreeBSD-5.1-RELEASE/man:$manLocalDir/FreeBSD-5.1-RELEASE/openssl/man",
- 'FreeBSD 5.0-RELEASE', "$manLocalDir/FreeBSD-5.0-RELEASE",
- 'FreeBSD 4.11-RELEASE', "$manLocalDir/FreeBSD-4.11-RELEASE/man:$manLocalDir/FreeBSD-4.11-RELEASE/openssl/man:$manLocalDir/FreeBSD-4.11-RELEASE/perl/man",
- 'FreeBSD 4.10-RELEASE', "$manLocalDir/FreeBSD-4.10-RELEASE/man:$manLocalDir/FreeBSD-4.10-RELEASE/openssl/man:$manLocalDir/FreeBSD-4.10-RELEASE/perl/man",
- 'FreeBSD 4.9-RELEASE', "$manLocalDir/FreeBSD-4.9-RELEASE",
- 'FreeBSD 4.8-RELEASE', "$manLocalDir/FreeBSD-4.8-RELEASE",
- 'FreeBSD 4.7-RELEASE', "$manLocalDir/FreeBSD-4.7-RELEASE",
- 'FreeBSD 4.6.2-RELEASE', "$manLocalDir/FreeBSD-4.6.2-RELEASE",
- 'FreeBSD 4.6-RELEASE', "$manLocalDir/FreeBSD-4.6-RELEASE",
- 'FreeBSD 4.5-RELEASE', "$manLocalDir/FreeBSD-4.5-RELEASE",
- 'FreeBSD 4.4-RELEASE', "$manLocalDir/FreeBSD-4.4-RELEASE",
- 'FreeBSD 4.3-RELEASE', "$manLocalDir/FreeBSD-4.3-RELEASE",
- 'FreeBSD 4.2-RELEASE', "$manLocalDir/FreeBSD-4.2-RELEASE",
- 'FreeBSD 4.1.1-RELEASE', "$manLocalDir/FreeBSD-4.1.1-RELEASE",
- 'FreeBSD 4.1-RELEASE', "$manLocalDir/FreeBSD-4.1-RELEASE",
- 'FreeBSD 4.0-RELEASE', "$manLocalDir/FreeBSD-4.0-RELEASE",
- 'FreeBSD 3.5.1-RELEASE', "$manLocalDir/FreeBSD-3.5.1-RELEASE",
- 'FreeBSD 3.4-RELEASE', "$manLocalDir/FreeBSD-3.4-RELEASE",
- 'FreeBSD 3.3-RELEASE', "$manLocalDir/FreeBSD-3.3-RELEASE",
- 'FreeBSD 3.2-RELEASE', "$manLocalDir/FreeBSD-3.2-RELEASE",
- 'FreeBSD 3.1-RELEASE', "$manLocalDir/FreeBSD-3.1-RELEASE",
- 'FreeBSD 3.0-RELEASE', "$manLocalDir/FreeBSD-3.0-RELEASE",
- 'FreeBSD 2.2.5-RELEASE', "$manLocalDir/FreeBSD-2.2.5-RELEASE",
- 'FreeBSD 2.2.6-RELEASE', "$manLocalDir/FreeBSD-2.2.6-RELEASE",
- 'FreeBSD 2.2.7-RELEASE', "$manLocalDir/FreeBSD-2.2.7-RELEASE",
- 'FreeBSD 2.2.8-RELEASE', "$manLocalDir/FreeBSD-2.2.8-RELEASE",
- 'FreeBSD 2.2.2-RELEASE', "$manLocalDir/FreeBSD-2.2.2-RELEASE",
- 'FreeBSD 2.2.1-RELEASE', "$manLocalDir/FreeBSD-2.2.1-RELEASE",
- 'FreeBSD 2.1.7.1-RELEASE', "$manLocalDir/FreeBSD-2.1.7.1-RELEASE",
- 'FreeBSD 2.1.6.1-RELEASE', "$manLocalDir/FreeBSD-2.1.6.1-RELEASE",
- 'FreeBSD 2.1.5-RELEASE', "$manLocalDir/FreeBSD-2.1.5-RELEASE",
- 'FreeBSD 2.1.0-RELEASE', "$manLocalDir/FreeBSD-2.1.0-RELEASE",
- 'FreeBSD 2.0.5-RELEASE', "$manLocalDir/FreeBSD-2.0.5-RELEASE",
- 'FreeBSD 2.0-RELEASE', "$manLocalDir/FreeBSD-2.0-RELEASE",
- 'FreeBSD 1.1.5.1-RELEASE', "$manLocalDir/FreeBSD-1.1.5.1-RELEASE",
- 'FreeBSD 1.1-RELEASE', "$manLocalDir/FreeBSD-1.1-RELEASE",
- 'FreeBSD 1.0-RELEASE', "$manLocalDir/FreeBSD-1.0-RELEASE",
-
- 'FreeBSD Ports 5.3-RELEASE', "$manLocalDir/FreeBSD-ports-5.3-RELEASE",
- 'FreeBSD Ports 5.1-RELEASE', "$manLocalDir/FreeBSD-ports-5.1-RELEASE",
- 'FreeBSD Ports 5.0-RELEASE', "$manLocalDir/FreeBSD-ports-5.0-RELEASE",
- 'FreeBSD Ports 4.7-RELEASE', "$manLocalDir/FreeBSD-ports-4.7-RELEASE",
-
- 'OpenBSD 2.0', "$manLocalDir/OpenBSD-2.0",
- 'OpenBSD 2.1', "$manLocalDir/OpenBSD-2.1",
- 'OpenBSD 2.2', "$manLocalDir/OpenBSD-2.2",
- 'OpenBSD 2.3', "$manLocalDir/OpenBSD-2.3",
- 'OpenBSD 2.4', "$manLocalDir/OpenBSD-2.4",
- 'OpenBSD 2.5', "$manLocalDir/OpenBSD-2.5",
- 'OpenBSD 2.6', "$manLocalDir/OpenBSD-2.6",
- 'OpenBSD 2.7', "$manLocalDir/OpenBSD-2.7",
- 'OpenBSD 2.8', "$manLocalDir/OpenBSD-2.8",
- 'OpenBSD 2.9', "$manLocalDir/OpenBSD-2.9",
- 'OpenBSD 3.0', "$manLocalDir/OpenBSD-3.0",
- 'OpenBSD 3.1', "$manLocalDir/OpenBSD-3.1",
- 'OpenBSD 3.2', "$manLocalDir/OpenBSD-3.2",
- 'OpenBSD 3.3', "$manLocalDir/OpenBSD-3.3",
- 'OpenBSD 3.4', "$manLocalDir/OpenBSD-3.4/share/man:$manLocalDir/OpenBSD-3.4/X11R6/man",
- 'OpenBSD 3.5', "$manLocalDir/OpenBSD-3.5/share/man:$manLocalDir/OpenBSD-3.5/X11R6/man",
- 'OpenBSD 3.6', "$manLocalDir/OpenBSD-3.6/share/man:$manLocalDir/OpenBSD-3.6/X11R6/man",
-
- #'NetBSD 0.9', "$manLocalDir/NetBSD-0.9",
- 'NetBSD 1.0', "$manLocalDir/NetBSD-1.0",
- 'NetBSD 1.1', "$manLocalDir/NetBSD-1.1",
- 'NetBSD 1.2', "$manLocalDir/NetBSD-1.2",
- 'NetBSD 1.2.1', "$manLocalDir/NetBSD-1.2.1",
- 'NetBSD 1.3', "$manLocalDir/NetBSD-1.3",
- 'NetBSD 1.3.1', "$manLocalDir/NetBSD-1.3.1",
- 'NetBSD 1.3.2', "$manLocalDir/NetBSD-1.3.2",
- 'NetBSD 1.3.3', "$manLocalDir/NetBSD-1.3.3",
- 'NetBSD 1.4', "$manLocalDir/NetBSD-1.4",
- 'NetBSD 1.4.1', "$manLocalDir/NetBSD-1.4.1",
- 'NetBSD 1.4.2', "$manLocalDir/NetBSD-1.4.2",
- 'NetBSD 1.4.3', "$manLocalDir/NetBSD-1.4.3",
- 'NetBSD 1.5', "$manLocalDir/NetBSD-1.5",
- 'NetBSD 1.5.1', "$manLocalDir/NetBSD-1.5.1",
- 'NetBSD 1.5.2', "$manLocalDir/NetBSD-1.5.2",
- 'NetBSD 1.5.3', "$manLocalDir/NetBSD-1.5.3",
- 'NetBSD 1.6', "$manLocalDir/NetBSD-1.6",
- 'NetBSD 1.6.1', "$manLocalDir/NetBSD-1.6.1",
- 'NetBSD 1.6.2', "$manLocalDir/NetBSD-1.6.2",
- 'NetBSD 2.0', "$manLocalDir/NetBSD-2.0",
-
- '2.8 BSD', "$manLocalDir/2.8BSD",
- '2.9.1 BSD', "$manLocalDir/2.9.1BSD",
- '2.10 BSD', "$manLocalDir/2.10BSD",
- '2.11 BSD', "$manLocalDir/2.11BSD",
- '386BSD 0.0', "$manLocalDir/386BSD-0.0",
- '386BSD 0.1', "$manLocalDir/386BSD-0.1",
- '4.3BSD Reno', "$manLocalDir/4.3BSD-Reno",
- '4.3BSD NET/2', "$manLocalDir/net2",
- '4.4BSD Lite2', "$manLocalDir/4.4BSD-Lite2",
-
- 'Linux Slackware 3.1', "$manLocalDir/Slackware-3.1",
- 'Red Hat Linux/i386 4.2', "$manLocalDir/RedHat-4.2",
- 'Red Hat Linux/i386 5.0', "$manLocalDir/RedHat-5.0",
- 'Red Hat Linux/i386 5.2', "$manLocalDir/RedHat-5.2-i386",
- 'Red Hat Linux/i386 6.1', "$manLocalDir/RedHat-6.1-i386",
- 'Red Hat Linux/i386 6.2', "$manLocalDir/RedHat-6.2-i386",
- 'Red Hat Linux/i386 7.0', "$manLocalDir/RedHat-7.0-i386",
- 'Red Hat Linux/i386 7.1', "$manLocalDir/RedHat-7.1-i386",
- 'Red Hat Linux/i386 7.2', "$manLocalDir/RedHat-7.2-i386",
- 'Red Hat Linux/i386 7.3', "$manLocalDir/RedHat-7.3-i386",
- 'Red Hat Linux/i386 8.0', "$manLocalDir/RedHat-8.0-i386",
- 'Red Hat Linux/i386 9', "$manLocalDir/RedHat-9-i386",
-
- 'SuSE Linux/i386 4.3', "$manLocalDir/SuSE-4.3-i386",
- 'SuSE Linux/i386 5.0', "$manLocalDir/SuSE-5.0-i386",
- 'SuSE Linux/i386 5.2', "$manLocalDir/SuSE-5.2-i386",
- 'SuSE Linux/i386 5.3', "$manLocalDir/SuSE-5.3-i386",
- 'SuSE Linux/i386 6.0', "$manLocalDir/SuSE-6.0-i386",
- 'SuSE Linux/i386 6.1', "$manLocalDir/SuSE-6.1-i386",
- 'SuSE Linux/i386 6.3', "$manLocalDir/SuSE-6.3-i386",
- 'SuSE Linux/i386 6.4', "$manLocalDir/SuSE-6.4-i386",
- 'SuSE Linux/i386 7.0', "$manLocalDir/SuSE-7.0-i386",
- 'SuSE Linux/i386 7.1', "$manLocalDir/SuSE-7.1-i386",
- 'SuSE Linux/i386 7.2', "$manLocalDir/SuSE-7.2-i386",
- 'SuSE Linux/i386 7.3', "$manLocalDir/SuSE-7.3-i386",
- 'SuSE Linux/i386 8.0', "$manLocalDir/SuSE-8.0-i386",
- 'SuSE Linux/i386 8.1', "$manLocalDir/SuSE-8.1-i386",
- 'SuSE Linux/i386 8.2', "$manLocalDir/SuSE-8.2-i386",
-
- 'HP-UX 11.22', "$manLocalDir/HP-UX-11.22",
- 'HP-UX 11.20', "$manLocalDir/HP-UX-11.20",
- 'HP-UX 11.11', "$manLocalDir/HP-UX-11.11",
- 'HP-UX 11.00', "$manLocalDir/HP-UX-11.00",
- 'HP-UX 10.20', "$manLocalDir/HP-UX-10.20",
- 'HP-UX 10.10', "$manLocalDir/HP-UX-10.10",
- 'HP-UX 10.01', "$manLocalDir/HP-UX-10.01",
-
- 'SunOS 5.9', "$manLocalDir/SunOS-5.9",
- 'SunOS 5.8', "$manLocalDir/SunOS-5.8",
- 'SunOS 5.7', "$manLocalDir/SunOS-5.7",
- 'SunOS 5.6', "$manLocalDir/SunOS-5.6",
- 'SunOS 5.5.1', "$manLocalDir/SunOS-5.5.1",
- 'SunOS 4.1.3', "$manLocalDir/SunOS-4.1.3",
-
- 'XFree86 3.2', "$manLocalDir/XFree86-3.2",
- 'XFree86 3.3', "$manLocalDir/XFree86-3.3",
- 'XFree86 3.3.6', "$manLocalDir/XFree86-3.3.6",
- 'XFree86 4.0', "$manLocalDir/XFree86-4.0",
- 'XFree86 4.0.1', "$manLocalDir/XFree86-4.0.1",
- 'XFree86 4.0.2', "$manLocalDir/XFree86-4.0.2",
- 'XFree86 4.1.0', "$manLocalDir/XFree86-4.1.0",
- 'XFree86 4.2.0', "$manLocalDir/XFree86-4.2.0",
- 'XFree86 4.2.99.3', "$manLocalDir/XFree86-4.2.99.3",
- 'XFree86 4.3.0', "$manLocalDir/XFree86-4.3.0",
- 'XFree86 4.4.0', "$manLocalDir/XFree86-4.4.0",
-
- 'X11R6.7.0', "$manLocalDir/X11R6.7.0",
-
- 'ULTRIX 4.2', "$manLocalDir/ULTRIX-4.2",
- 'OSF1 V4.0/alpha', "$manLocalDir/OSF1-V4.0-alpha",
- 'OSF1 V5.1/alpha', "$manLocalDir/OSF1-V5.1-alpha",
-
- 'Plan 9', "$manLocalDir/plan9",
- 'Minix 2.0', "$manLocalDir/Minix-2.0",
- 'Unix Seventh Edition', "$manLocalDir/v7man",
- 'deutsch - Linux/GNU', "$manLocalDir/linux-de-0.4",
- 'Darwin 1.3 PPC', "$manLocalDir/Darwin-1.3-ppc",
- 'Darwin 7.0.1 PPC', "$manLocalDir/Darwin-7.0.1-ppc",
-);
-
-# delete not existing releases
-while (($key,$val) = each %manPath) {
- my $counter = 0;
-
- # if the manpath contains colons, at least one directory must exists
- foreach (split(/:/, $val)) {
- $counter++ if -d;
- }
-
- # give up and delete release
- delete $manPath{"$key"} if !$counter && $key ne $manPathDefault;
-}
-
-# keywords must be in lower cases.
-%manPathAliases =
- (
- 'freebsd', 'FreeBSD 5.3-RELEASE',
- 'freebsd-stable', 'FreeBSD 4.11-stable',
- 'freebsd-stable5', 'FreeBSD 5.4-stable',
- 'freebsd-current', 'FreeBSD 6-current',
- 'slackware', 'Linux Slackware 3.1',
- 'linux-de', 'deutsch - Linux/GNU',
- 'redhat', 'Red Hat Linux/i386 9',
- 'suse', 'SuSE Linux/i386 8.2',
- 'linux', 'Red Hat Linux/i386 9',
- 'darwin', 'Darwin 7.0.1 PPC',
- 'macosx', 'Darwin 7.0.1 PPC',
-
- 'netbsd', 'NetBSD 2.0',
- 'openbsd', 'OpenBSD 3.6',
- 'v7', 'Unix Seventh Edition',
- 'v7man', 'Unix Seventh Edition',
- 'x11', 'X11R6.7.0',
- 'xfree86', 'XFree86 4.4.0',
- 'ultrix', 'ULTRIX 4.2',
- 'hpux', 'HP-UX 11.22',
- 'solaris', 'SunOS 5.9',
- 'sunos5', 'SunOS 5.9',
- 'sunos4', 'SunOS 4.1.3',
- 'sunos', 'SunOS 4.1.3',
- 'freebsd ports', 'FreeBSD Ports 5.3-RELEASE',
- 'ports', 'FreeBSD Ports 5.3-RELEASE',
- 'plan9', 'Plan 9',
- 'osf1', 'OSF1 V5.1/alpha',
- 'true64', 'OSF1 V5.1/alpha',
-);
-
-foreach (sort keys %manPathAliases) {
- # delete non-existing aliases
- if (!defined($manPath{$manPathAliases{$_}})) {
- undef $manPathAliases{$_};
- next;
- }
-
- # add aliases, replases spaces with dashes
- if (/\s/) {
- local($key) = $_;
- $key =~ s/\s+/-/g;
- $manPathAliases{$key} = $manPathAliases{$_};
- }
-}
-
-@sections = keys %sections; shift @sections; # all but the "" entry
-$sections = join("|", @sections); # sections regexp
-
-
-# mailto - Author
-# webmaster - who run this service
-$mailto = 'wosch@FreeBSD.org';
-$mailtoURL = 'http://wolfram.schneider.org';
-$mailtoURL = "mailto:$mailto" if !$mailtoURL;
-$webmaster = $mailto;
-$webmasterURL = $mailtoURL;
-$manstat = 'http://www.de.freebsd.org/de/stat/man';
-
-&secure_env;
-# CGI Interface -- runs at load time
-&do_man(&env('SCRIPT_NAME'), &env('PATH_INFO'), &env('QUERY_STRING'))
- unless defined($main'plexus_configured);
-
-$enable_include_links = 0;
-
-# Plexus Native Interface
-sub do_man {
- local($BASE, $path, $form) = @_;
- local($_, %form, $query, $proto, $name, $section, $apropos);
-
- # spinner is buggy, shit
- local($u) = 'http://user.cs.tu-berlin.de/~wosch/man.cgi';
- local($u)= $BASE;
-
- return &faq_output($u) if ($path =~ /faq.html$/);
- return &copyright_output($u) if ($path =~ /copyright.html$/);
- return &get_the_sources if ($path =~ /source$/);
-
- return &include_output($path)
- if ($enable_include_links && $path =~ m%^/usr/include/% && -f $path);
-
- return &indexpage if ($form eq "");
-
- &decode_form($form, *form, 0);
-
- $format = $form{'format'};
- $format = 'html' if $format !~ /^(ps|pdf|ascii|latin1|dvi|troff)$/;
-
- local($fform) = &dec($form);
- if ($fform =~ m%^([a-zA-Z_\-]+)$%) {
- return &man($1, '');
- } elsif ($fform =~ m%^([a-zA-Z_\-]+)\(([0-9a-zA-Z]+)\)$%) {
- return &man($1, $2);
- }
-
- # remove trailing spaces for dumb users
- $form{'query'} =~ s/\s+$//;
- $form{'query'} =~ s/^\s+//;
-
- $name = $query = $form{'query'};
- $section = $form{'sektion'};
- $apropos = $form{'apropos'};
- $alttitle = $form{'title'};
- $manpath = $form{'manpath'};
- if (!$manpath) {
- $manpath = $manPathDefault;
- } elsif (!$manPath{$manpath}) {
- local($m) = ($manpath =~ y/A-Z/a-z/);
- if ($manPath{$manPathAliases{$manpath}}) {
- $manpath = $manPathAliases{$manpath};
- } else {
- $manpath = $manPathDefault;
- }
- }
-
- # download a man hierarchie as gzip'd tar file
- return &download if ($apropos > 1);
-
- # empty query
- return &indexpage if ($manpath && $form !~ /query=/);
-
- $section = "" if $section eq "ALL" || $section eq '';
-
- if (!$apropos && $query =~ m/^(.*)\(([^\)]*)\)/) {
- $name = $1; $section = $2;
- }
-
- $apropos ? &apropos($query) : &man($name, $section);
-}
-
-# --------------------- support routines ------------------------
-
-sub debug {
- &http_header("text/plain");
- print @_,"\n----------\n\n\n";
-}
-
-sub get_the_sources {
- local($file) = '/usr/local/www/bsddoc/bin/man.cgi';
- $file = $0 if ! -f $file;
-
- open(R, $file) || &mydie("open $file: $!\n");
- print "Content-type: text/plain\n\n";
- while(<R>) { print }
- close R;
- exit;
-}
-
-# download a manual directory as gzip'd tar archive
-sub download {
-
- $| = 1;
- my $filename = $manpath;
- $filename =~ s/\s+/_/;
- $filename = &encode_url($filename);
- $filename .= '.tar.gz';
-
- print qq{Content-type: application/x-tar\n} .
- qq{Content-encoding: x-gzip\n} .
- qq{Content-disposition: inline; filename="$filename"\n} .
- "\n";
-
- local(@m);
- local($m) = $manPath{"$manpath"};
- foreach (split(/:/, $m)) {
- push(@m, $_) if s%^$manLocalDir/?%%;
- }
-
- chdir($manLocalDir) || do {
- print "chdir: $!\n"; exit(0);
- };
-
- $m = join(" ", @m);
- #warn "find $m -print | cpio -o -H tar 2>/dev/null | gzip -cqf";
-
- sleep 1;
- system("find $m -print | cpio -o -H tar 2>/dev/null | gzip -cqf");
- exit(0);
-}
-
-sub http_header {
- local($content_type) = @_;
- if (defined($main'plexus_configured)) {
- &main'MIME_header('ok', $content_type);
- } else {
- print "Content-type: $content_type\n\n";
- }
-}
-
-sub env { defined($main'ENV{$_[0]}) ? $main'ENV{$_[0]} : undef; }
-
-sub apropos {
- local($query) = @_;
- local($_, $title, $head, *APROPOS);
- local($names, $section, $msg, $key);
- local($prefix);
-
- $prefix = "Apropos ";
- if ($alttitle) {
- $prefix = "";
- $title = &encode_title($alttitle);
- $head = &encode_data($alttitle);
- } else {
- $title = &encode_title($query);
- $head = &encode_data($query);
- }
-
- &http_header("text/html");
- print &html_header("Apropos $title");
- print "<H1>$www{'head'}</H1>\n\n";
- &formquery;
-
- local($mpath) = $manPath{$manpath};
-
- open(APROPOS, "env MANPATH=$mpath $command{'man'} -k . |") || do {
- warn "$0: Cannot open whatis database for `$mpath'\n";
- print "Cannot open whatis database for `$mpath'\n";
- print "</DL>\n</BODY>\n</HTML>\n";
- return;
- };
-
- local($q) = $query;
- $q =~ s/(\W)/\\W/g;
- local($acounter) = 0;
-
- while (<APROPOS>) {
- next if !/$q/oi;
- $acounter++;
-
- # matches whatis.db lines: name[, name ...] (sect) - msg
- $names = $section = $msg = $key = undef;
- ($key, $section) = m/^([^()]+)\(([^)]*)\)/;
- $key =~ s/\s+$//;
- $key =~ s/.*\s+//;
- ($names, $msg) = m/^(.*\))\s+-\s+(.*)/;
- print "<DT><A HREF=\"$BASE?query=", &encode_url($key),
- "&sektion=", &encode_url($section), "&apropos=0",
- "&manpath=", &encode_url($manpath), "\">",
- &encode_data("$names"), "</A>\n<DD>",
- &encode_data($msg), "\n";
- }
- close(APROPOS);
-
- if (!$acounter) {
- print "Sorry, no data found for `$query'.\n";
- print qq{You may look for other } .
- qq{<a href="../../search/">FreeBSD Search Services</a>.\n};
- }
- print "</DL>\n</BODY>\n</HTML>\n";
-}
-
-sub man {
- local($name, $section) = @_;
- local($_, $title, $head, *MAN);
- local($html_name, $html_section, $prefix);
- local(@manargs);
- local($query) = $name;
-
- # $section =~ s/^([0-9ln]).*$/$1/;
- $section =~ tr/A-Z/a-z/;
-
- $prefix = "Man ";
- if ($alttitle) {
- $prefix = "";
- $title = &encode_title($alttitle);
- $head = &encode_data($alttitle);
- } elsif ($section) {
- $title = &encode_title("${name}($section)");
- $head = &encode_data("${name}($section)");
- } else {
- $title = &encode_title("${name}");
- $head = &encode_data("${name}");
- }
-
- if ($format eq "html") {
- &http_header("text/html");
- print &html_header("$title");
- print "<H1>$www{'head'}</H1>\n\n";
- &formquery;
- print "<PRE>\n";
- } else {
- #$format =~ /^(ps|ascii|latin1|dvi|troff)$/')
- $ENV{'NROFF_FORMAT'} = $format;
-
- # Content-encoding: x-gzip
- if ($format eq "ps") {
- &http_header("application/postscript");
- } elsif ($format eq "pdf") {
- &http_header("application/pdf");
- } elsif ($format eq "dvi") {
- &http_header("application/x-dvi");
- } elsif ($format eq "troff") {
- &http_header("application/x-troff-mandoc");
- } else {
- &http_header("text/plain");
- }
- }
-
- $html_name = &encode_data($name);
- $html_section = &encode_data($section);
-
- #print Dumper($sectionpath);
- #print "yy $section yy $manpath\n";
- if ($name =~ /^\s*$/) {
- print "Empty input, no man page given.\n";
- return;
- }
-
- if (index($name, '*') != -1) {
- print "Invalid character input '*': $name\n";
- return;
- }
-
- if ($section !~ /^[0-9ln]\w*$/ && $section ne '') {
- print "Sorry, section `$section' is not valid\n";
- return;
- }
-
- if (!$section) {
- if ($sectionpath->{$manpath}) {
- $section = "-S " . $sectionpath->{$manpath}{'path'};
- } else {
- $section = '';
- }
- } else {
- if ($sectionpath->{$manpath}{$section}) {
- $section = "-S " . $sectionpath->{$manpath}{$section};
- } else {
- $section = "-S $section";
- }
- }
-
- @manargs = split(/ /, $section);
- if ($manpath) {
- if ($manPath{$manpath}) {
- unshift(@manargs, ('-M', $manPath{$manpath}));
- } elsif ($manpath{&dec($manpath)}) {
- unshift(@manargs, ('-M', $manPath{&dec($manpath)}));
- } else {
- # unset invalid manpath
- print "x $manpath x\n";
- print "x " . &dec($manpath) . "x\n";
- undef $manpath;
- }
- }
-
- if ($format =~ /^(ps|pdf)$/) {
- push(@manargs, '-t');
- }
-
- # print "X $command{'man'} @manargs -- x $name x\n";
- &proc(*MAN, $command{'man'}, @manargs, "--", $name) ||
- &mydie ("$0: open of $command{'man'} command failed: $!\n");
- if (eof(MAN)) {
- # print "X $command{'man'} @manargs -- x $name x\n";
- print "Sorry, no data found for `$html_name" .
- ($html_section ? "($html_section)": '') . "'.\n";
- print qq{You may look for other } .
- qq{<a href="../../search/">FreeBSD Search Services</a>.\n};
- return;
- }
-
- if ($format ne "html") {
- if ($format eq "latin1" || $format eq "ascii") {
- while(<MAN>) { s/.//g; print; }
- } elsif ($format eq "pdf") {
- #
- # run a PostScript to PDF converter
- #
- local(@args) = ('mktemp', '/tmp/_man.cgi-ps2pdf-XXXXXXXXXXXX');
- open(TMP, "-|") or
- exec(@args) or die "open @args: $!\n";
- local($tempfile) = <TMP>;
- close TMP;
-
- # chomp, avoid security warnings using -T switch
- #chop($tempfile);
- if ($tempfile =~ /(\S+)/) {
- $tempfile = $1;
- }
-
- if (!$tempfile || ! -f $tempfile) {
- die "Cannot create tempfile: $tempfile\n";
- }
- #warn $tempfile;
-
- #$tempfile = '/tmp/bla2';
- open(TMP, "> $tempfile") or die "open $tempfile: $!\n";
- while(<MAN>) {
- print TMP $_;
- }
- close TMP;
- local($ENV{'PATH'}) = '/bin:/usr/bin:/usr/local/bin';
- open(PDF, "-|") or
- exec('/usr/local/bin/ps2pdf', $tempfile, '/dev/stdout') or
- die "open ps2pdf: $!\n";
-
- # sleep and delete the temp file
- #select(undef, undef, undef, 0.8);
- #unlink($tempfile);
-
- while(<PDF>) {
- print;
- }
- close PDF;
- unlink($tempfile);
-
- } else {
- while(<MAN>) { print; }
- }
- close(MAN);
- exit(0);
- }
-
- local($space) = 1;
- local(@sect);
- local($i, $j);
- while(<MAN>) {
- # remove tailing white space
- if (/^\s+$/) {
- next if $space;
- $space = 1;
- } else {
- $space = 0;
- }
-
- $_ = &encode_data($_);
- if($enable_include_links &&
- m,(<B>)?\#include(</B>)?\s+(<B>)?\&lt\;(.*\.h)\&gt\;(</B>)?,) {
- $match = $4; ($regexp = $match) =~ s/\./\\\./;
- s,$regexp,\<A HREF=\"$BASE/usr/include/$match\"\>$match\</A\>,;
- }
- /^\s/ && # skip headers
- s,((<[IB]>)?[\w\_\.\-]+\s*(</[IB]>)?\s*\(([1-9ln][a-zA-Z]*)\)),&mlnk($1),oige;
-
- # detect E-Mail Addreses in manpages
- if (/\@/) {
- s/([a-z0-9_\-\.]+\@[a-z0-9\-\.]+\.[a-z]+)/<A HREF="mailto:$1">$1<\/A>/gi;
- }
-
- # detect URLs in manpages
- if (m%tp://%) {
- s,((ftp|http)://[^\s<>\)]+),<A HREF="$1">$1</A>,gi;
- }
-
- if (/^<B>\S+/ && m%^<B>([^<]+)%) {
- $i = $1; $j = &encode_url($i);
- s%^<B>([^<]+)</B>%<a name="$j" href="#end"><B>$i</B></a>%;
- push(@sect, $1);
- }
- print;
- }
- close(MAN);
- print qq{</PRE>\n<a name="end">\n<hr noshade>\n};
-
- for ($i = 0; $i <= $#sect; $i++) {
- print qq{<a href="#} . &encode_url($sect[$i]) .
- qq{">$sect[$i]</a>} . ($i < $#sect ? " |\n" : "\n");
- }
-
- print "</BODY>\n";
- print "</HTML>\n";
-
- # Sleep 0.35 seconds to avoid DoS attacs
- select undef, undef, undef, 0.35;
-}
-
-sub mlnk {
- local($matched) = @_;
- local($link, $section);
- ($link = $matched) =~ s/[\s]+//g;
- $link =~ s/<\/?[IB]>//g;
- ($link, $section) = ($link =~ m/^([^\(]*)\((.*)\)/);
- $link = &encode_url($link);
- $section = &encode_url($section);
- local($manpath) = &encode_url($manpath);
- return qq{<A HREF="$BASE?query=$link} .
- qq{&sektion=$section&apropos=0&manpath=$manpath">$matched</A>};
-}
-
-sub proc {
- local(*FH, $prog, @args) = @_;
- local($pid) = open(FH, "-|");
- return undef unless defined($pid);
- if ($pid == 0) {
- exec $prog, @args;
- &mydie("exec $prog failed\n");
- }
- 1;
-}
-
-# $indent is a bit of optional data processing I put in for
-# formatting the data nicely when you are emailing it.
-# This is derived from code by Denis Howe <dbh@doc.ic.ac.uk>
-# and Thomas A Fine <fine@cis.ohio-state.edu>
-sub decode_form {
- local($form, *data, $indent, $key, $_) = @_;
- foreach $_ (split(/&/, $form)) {
- ($key, $_) = split(/=/, $_, 2);
- $_ =~ s/\+/ /g; # + -> space
- $key =~ s/\+/ /g; # + -> space
- $_ =~ s/%([\da-f]{1,2})/pack(C,hex($1))/eig; # undo % escapes
- $key =~ s/%([\da-f]{1,2})/pack(C,hex($1))/eig; # undo % escapes
- $_ =~ s/[\r\n]+/\n\t/g if defined($indent); # indent data after \n
- $data{$key} = &escape($_);
- }
-}
-
-# block cross-site scripting attacks (css)
-sub escape($) { $_ = $_[0]; s/&/&amp;/g; s/</&lt;/g; s/>/&gt;/g; $_; }
-
-sub dec {
- local($_) = @_;
-
- s/\+/ /g; # '+' -> space
- s/%(..)/pack("c",hex($1))/ge; # '%ab' -> char ab
-
- return($_);
-}
-
-#
-# Splits up a query request, returns an array of items.
-# usage: @items = &main'splitquery($query);
-#
-sub splitquery {
- local($query) = @_;
- grep((s/%([\da-f]{1,2})/pack(C,hex($1))/eig, 1), split(/\+/, $query));
-}
-
-# encode unknown data for use in a URL <A HREF="...">
-sub encode_url {
- local($_) = @_;
- # rfc1738 says that ";"|"/"|"?"|":"|"@"|"&"|"=" may be reserved.
- # And % is the escape character so we escape it along with
- # single-quote('), double-quote("), grave accent(`), less than(<),
- # greater than(>), and non-US-ASCII characters (binary data),
- # and white space. Whew.
- s/([\000-\032\;\/\?\:\@\&\=\%\'\"\`\<\>\177-\377 ])/sprintf('%%%02x',ord($1))/eg;
- s/%20/+/g;
- $_;
-}
-# encode unknown data for use in <TITLE>...</TITILE>
-sub encode_title {
- # like encode_url but less strict (I couldn't find docs on this)
- local($_) = @_;
- s/([\000-\031\%\&\<\>\177-\377])/sprintf('%%%02x',ord($1))/eg;
- $_;
-}
-# encode unknown data for use inside markup attributes <MARKUP ATTR="...">
-sub encode_attribute {
- # rfc1738 says to use entity references here
- local($_) = @_;
- s/([\000-\031\"\'\`\%\&\<\>\177-\377])/sprintf('\&#%03d;',ord($1))/eg;
- $_;
-}
-# encode unknown text data for using as HTML,
-# treats ^H as overstrike ala nroff.
-sub encode_data {
- local($_) = @_;
- local($str);
-
- # Escape &, < and >
- s,\010[><&],,g;
- s/\&/\&amp\;/g;
- s/\</\&lt\;/g;
- s/\>/\&gt\;/g;
-
- s,((_\010.)+),($str = $1) =~ s/.\010//g; "<I>$str</I>";,ge;
- s,(.\010)+,$1,g;
-
- if (!s,((.\010.)+\s+(.\010.)+),($str = $1) =~ s/.\010//g; "<B>$str</B>";,ge) {
- s,((.\010.)+),($str = $1) =~ s/.\010//g; "<B>$str</B>";,ge;
- }
-
-
- # Escape binary data except for ^H which we process below
- # \375 gets turned into the & for the entity reference
- #s/([^\010\012\015\032-\176])/sprintf('\375#%03d;',ord($1))/eg;
- # Process ^H sequences, we use \376 and \377 (already escaped
- # above) to stand in for < and > until those characters can
- # be properly escaped below.
- #s,\376[IB]\377_\376/[IB]\377,,g;
- #s/.[\b]//g; # just do an erase for anything else
- # Now convert our magic chars into our tag markers
- #s/\375/\&/g; s/\376/</g; s/\377/>/g;
-
- s,.\010,,g;
-
- $_;
-}
-
-sub indexpage {
- &http_header("text/html");
- print &html_header("$www{'title'}: Index Page") .
- "<H1>$www{'head'}</H1>\n\n" . &intro;
- &formquery;
-
- local($m) = ($manpath ? $manpath : $manPathDefault);
- $m = &encode_url($m);
-
- print "<B><I>Section Indexes</I></B>: ";
- foreach ('1', '2', '3', '4', '5', '6', '7', '8', '9', 'n') {
- print qq{&#164; <A HREF="$BASE?query=($_)&sektion=&apropos=1&manpath=$m&title=Section%20$_Index">$_</A>\n};
- }
-
- print "<BR><B><I>Explanations of Man Sections:</I></B>";
- foreach ('1', '2', '3', '4', '5', '6', '7', '8', '9') {
- print qq{&#164; <A HREF="$BASE?query=intro&sektion=$_&apropos=0&manpath=$m&title=Introduction%20Section%20$_">intro($_)</A>\n};
- }
-
- print "<BR>\n<B><I>Quick Reference Categories:</I></B>\n";
- foreach ('database', 'disk', 'driver', 'ethernet', 'mail', 'net', 'nfs',
- 'nis', 'protocol', 'ppp', 'roff', 'string', 'scsi',
- 'statistic', 'tcl', 'tcp', 'time')
- {
- print qq{&#164; <A HREF="$BASE?query=$_&sektion=&apropos=1&manpath=$m&title=Quick%20Ref%20$_">$_</A>\n};
- }
-
- print <<ETX if $mailto;
-<HR noshade>
-<img ALIGN="RIGHT" src="/gifs/powerlogo.gif">
-Please direct questions about this server to
-<I><A HREF="$webmasterURL">$webmaster</A></I><br>
-URL: <A HREF="$BASE" target=_parent>$www{'home'}$BASE</a><br>
-ETX
-
- print "<br>\n";
- print "</BODY>\n</HTML>\n";
- 0;
-}
-
-sub formquery {
- local($astring, $bstring);
- if (!$apropos) {
- $astring = " CHECKED";
- } else {
- $bstring = " CHECKED";
- }
-
- print <<ETX;
-<FORM METHOD="GET" ACTION="$BASE">
-<B><I>Man Page or Keyword Search:</I></B>
-<INPUT VALUE="$query" NAME="query">
-<INPUT TYPE="submit" VALUE="Submit">
-<INPUT TYPE="reset" VALUE="Reset">
-<BR>
-<INPUT NAME="apropos" VALUE="0" TYPE="RADIO"$astring> <A HREF="$BASE?query=man&sektion=1&apropos=0">Man</A>
-<SELECT NAME="sektion">
-ETX
-
-
- foreach $key (sort keys %sectionName) {
- print "<OPTION" . (($key eq $section) ? ' SELECTED ' : ' ') .
- qq{VALUE="$key">$sectionName{$key}</OPTION>\n};
- };
-
-
- print qq{</SELECT>\n<SELECT NAME="manpath">\n};
-
- local($l) = ($manpath ? $manpath : $manPathDefault);
- foreach (sort keys %manPath) {
- $key = $_;
- print "<OPTION" . (($key eq $l) ? ' SELECTED ' : ' ') .
- qq{VALUE="$key">$key</OPTION>\n};
- }
-
- local($m) = &encode_url($l);
- print <<ETX;
-</SELECT>
-<BR>
-<INPUT NAME="apropos" VALUE="1" TYPE="RADIO"$bstring> <A HREF="$BASE?query=apropos&sektion=1&apropos=0">Apropos</A> Keyword Search (all sections)
-<SELECT NAME="format">
-ETX
-
- foreach ('html', 'ps', 'pdf',
- # 'dvi', # you need a 8 bit clean man, e.g. jp-man
- 'ascii', 'latin1') {
- print qq{<OPTION VALUE="$_">$_</OPTION>\n};
- };
-
- print <<ETX;
-</SELECT>
-Output format
-</FORM>
-
-<A HREF="$BASE?manpath=$m">Index Page and Help</A> |
-<A HREF="$BASE/faq.html">FAQ</A> |
-<A HREF="$BASE/copyright.html">Copyright</A>
-<HR>
-ETX
- 0;
-}
-
-sub copyright {
- $id = '$Id: man.cgi,v 1.149 2005-06-27 09:55:49 wosch Exp $';
-
- return qq{\
-<PRE>
-Copyright (c) 1996-2004 Wolfram Schneider <A HREF="$mailtoURL">&lt;$mailto&gt;</A>
-Copyright (c) 1993-1995 Berkeley Software Design, Inc.
-
-This data is part of a licensed program from BERKELEY SOFTWARE
-DESIGN, INC. Portions are copyrighted by BSDI, The Regents of
-the University of California, Massachusetts Institute of
-Technology, Free Software Foundation, FreeBSD Inc., and others.
-
-</PRE>\n
-This script has the revsion: $id
-<p>
-
-Copyright (c) for man pages by OS vendors.
-<p>
-<a href="ftp://ftp.2bsd.com">2.11 BSD</a>,
-<a href="http://www.hp.com">HP</a>,
-<a href="http://www.freebsd.org">FreeBSD</a>,
-<a href="http://www.cs.vu.nl/~ast/minix.html">Minix</a>,
-<a href="http://slackware.com">Linux Slackware</a>,
-<a href="http://www.linux.de">Linux/de</a>,
-<a href="http://www.netbsd.org">NetBSD</a>,
-<a href="http://www.openbsd.org">OpenBSD</a>,
-<a href="http://plan9.bell-labs.com/plan9/">Plan 9</a>,
-<a href="http://www.sun.com">SunOS</a>,
-<a href="http://www.digital.com">ULTRIX</a>,
-<a href="ftp://elib.zib.de/pub/netlib/att/cs/v7man">Unix Seventh Edition</a>,
-<a href="http://www.xfree86.org">XFree86</a>,
-<a href="http://www.x.org">X11R6</a>
-};
-}
-
-sub faq {
-
- local(@list, @list2);
- local($url);
- foreach (sort keys %manPath) {
- $url = &encode_url($_);
- push(@list,
- qq{<li><a href="$BASE?apropos=2&manpath=$url">[download]} .
- qq{</a> "$_" -> $BASE?manpath=$url});
- }
-
- foreach (sort keys %manPathAliases) {
- push(@list2, qq[<li>"$_" -> "$manPathAliases{$_}" -> ] .
- "$BASE?manpath=" .
- &encode_url($_) . "\n") if $manPathAliases{$_};
- }
-
- return qq{\
-<PRE>
-Copyright (c) 1996-2004 Wolfram Schneider <a href="$mailtoURL">&lt;$mailto&gt;</a>
-</PRE>
-
-<h2>FAQ</h2>
-<UL>
-<li>Get the <a href="$BASE/source">source</a> of the man.cgi script
-<li>Troff macros works only if defined in FreeBSD/groff. OS specific
-macros like `appeared in NetBSD version 1.2' are not supported.
-<li>Netscape is buggy, you may press twice the link 'Index Page and Help'
-<li>Some OSs provide only formated manual pages (catpages), e.g. NetBSD
-and OpenBSD. In this case it is not possible to create Postscript
-and troff output.
-<li>The <a href="http://cvsweb.freebsd.org/src/share/misc/bsd-family-tree">
-Unix family tree, BSD part</a>.
-<li>The <a href="http://www.freebsd.org/cgi/ports.cgi">
-FreeBSD Ports Changes</a> script.
-<li>Copyright (c) and download for man pages by <a href="$BASE/copyright.html">
-OS vendors</a>
-</UL>
-
-<h2>Releases</h2>
-
-Releases and Releases Aliases are information how
-to make a link to this script to the right OS version.
-<p>
-You may download the manpages as gzip'd tar archive
-for private use. A tarball is usually 5MB big.
-<p>
-<ul>
-@list
-</ul>
-
-<h2>Releases Aliases</h2>
-Release aliases are for lazy people. Plus, they have a longer
-lifetime, eg. 'openbsd' points always to the latest OpenBSD release.
-<ul>
-@list2
-</ul>
-};
-}
-
-
-sub intro {
- return qq{\
-<P>
-<I>Man Page Lookup</I> searches for man pages name and section as
-given in the selection menu and the query dialog. <I>Apropos
-Keyword Search</I> searches the database for the string given in
-the query dialog. There are also several hypertext links provided
-as short-cuts to various queries: <I>Section Indexes</I> is apropos
-listings of all man pages by section. <I>Explanations of Man
-Sections</I> contains pointers to the intro pages for various man
-sections. Or you can select a category from <I>Quick Reference
-Categories</I> and see man pages relevant to the selected topic.
-<P>
-};
-}
-
-sub copyright_output {
- &http_header("text/html");
- print &html_header("HTML hypertext FreeBSD man page interface") .
- "<H1>$www{'head'}</H1>\n" . &copyright . qq{\
-<HR>
-
-<A HREF="$_[0]">Index Page and Help</A>
-</BODY>
-</HTML>
-};
-}
-
-sub faq_output {
- &http_header("text/html");
- print &html_header("HTML hypertext FreeBSD man page interface") .
- "<H1>$www{'head'}</H1>\n" . &faq . qq{\
-<HR>
-
-<A HREF="$_[0]">Index Page and Help</A>
-</BODY>
-</HTML>
-};
-}
-
-sub html_header {
- return qq{<HTML>
-<HEAD>
-<TITLE>$_[0]</TITLE>
-<link rev="made" href="mailto:wosch\@FreeBSD.ORG">
-<META name="robots" content="nofollow">
-<meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type">
-<style type="text/css">
-<!--
-body {color:#000000;background-color:#EEEEEE}
-b {color:#996600;background-color:#EEEEEE}
-i {color:#008000;background-color:#EEEEEE}
-//-->
-</style>
-</HEAD>
-<BODY BGCOLOR="#FFFFFF" TEXT="#000000">\n\n};
-}
-
-sub secure_env {
- $main'ENV{'PATH'} = '/bin:/usr/bin';
- $main'ENV{'MANPATH'} = $manPath{$manPathDefault};
- $main'ENV{'IFS'} = " \t\n";
- $main'ENV{'PAGER'} = 'cat';
- $main'ENV{'SHELL'} = '/bin/sh';
- $main'ENV{'LANG'} = 'en_US.ISO_8859-1';
- undef $main'ENV{'DISPLAY'};
-}
-
-sub include_output {
- local($inc) = @_;
-
- &http_header("text/plain");
- open(I, "$inc") || do { print "open $inc: $!\n"; exit(1) };
- while(<I>) { print }
- close(I);
-}
-
-# CGI script must die with error status 0
-sub mydie {
- local($message) = @_;
- &http_header("text/html");
- print &html_header("Error");
- print $message;
-
-print qq{
-<p>
-<A HREF="$BASE">Index Page and Help</A>
-</BODY>
-</HTML>
-};
-
- exit(0);
-}
-
-1;
-
-
diff --git a/en/news/status/report-2001-06.xml b/en/news/status/report-2001-06.xml
deleted file mode 100644
index 4904ce5fa2..0000000000
--- a/en/news/status/report-2001-06.xml
+++ /dev/null
@@ -1,826 +0,0 @@
-<!-- $FreeBSD: www/en/news/status/report-june-2001.xml,v 1.6 2003/04/13 16:31:52 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-june-2001.xml,v 1.6 2003/04/13 16:31:52 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 &lt;
- <a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>
-
- &gt;</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
- &lt;johnp@knight-trosoft.com&gt;, 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/&lt;pid&gt;/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/&lt;pid&gt;/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 &amp; 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/news/status/report-2001-07.xml b/en/news/status/report-2001-07.xml
deleted file mode 100644
index c935c8c05b..0000000000
--- a/en/news/status/report-2001-07.xml
+++ /dev/null
@@ -1,1204 +0,0 @@
-<?xml version="1.0"?>
-
-<!-- $FreeBSD: www/en/news/status/report-july-2001.xml,v 1.6 2003/04/13 16:31:52 hrs 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-july-2001.xml,v 1.6 2003/04/13 16:31:52 hrs 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 &lt;
- <a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>
-
- &gt;</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 todays -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&gt;</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 &amp; 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/news/status/report-2001-08.xml b/en/news/status/report-2001-08.xml
deleted file mode 100644
index bd3b02e072..0000000000
--- a/en/news/status/report-2001-08.xml
+++ /dev/null
@@ -1,1519 +0,0 @@
-<!-- $FreeBSD: www/en/news/status/report-august-2001.xml,v 1.5 2003/04/13 16:31:52 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-august-2001.xml,v 1.5 2003/04/13 16:31:52 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 &gt; 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
- &lt;abc@FreeBSD.org&gt; 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 &amp; 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 &amp; 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 &amp;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 &lt;dd@FreeBSD.org&gt;
- and Nik Clayton &lt;nik@FreeBSD.org&gt; 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
- &lt;jyliu@163.net&gt; 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 &#163;150 for individuals and &#163;250 for
- corporations. The individual pricing is valid only until the end
- of September, the price will rise to &#163;200 for October and
- late registrations in November will be &#163;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/news/status/report-2001-09.xml b/en/news/status/report-2001-09.xml
deleted file mode 100644
index 3716ceb880..0000000000
--- a/en/news/status/report-2001-09.xml
+++ /dev/null
@@ -1,944 +0,0 @@
-<!-- $FreeBSD: www/en/news/status/report-september-2001.xml,v 1.2 2003/04/13 16:31:52 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-september-2001.xml,v 1.2 2003/04/13 16:31:52 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 &amp; 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 &amp; 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&gt; 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.&lt;ifindex&gt;.dev="devname"
- hint.net.&lt;ifindex&gt;.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 &lt;stdint.h&gt; and
- &lt;inttypes.h&gt; 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/news/status/report-2001-11.xml b/en/news/status/report-2001-11.xml
deleted file mode 100644
index c4f07c642e..0000000000
--- a/en/news/status/report-2001-11.xml
+++ /dev/null
@@ -1,1025 +0,0 @@
-<!-- $FreeBSD: www/en/news/status/report-november-2001.xml,v 1.2 2003/04/13 16:31:52 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&#248;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&#8212;particularly the
- <tt>passwd(1)</tt>
-
- ,
- <tt>chpass(1)</tt>
-
- etc. utilities&#8212;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
- &lt;--&gt; 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&#248;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 &amp; 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 &amp; POSIX Conformance Project is
- progressing nicely. Since the last status report, two new headers
- have been added [&lt;stdint.h&gt; and &lt;inttypes.h&gt;],
- 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>&lt;-- from http://groups.yahoo.com/group/FreeBSD-rc/ --&gt;
- <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>
-
- &lt;-- from Gordon Tetlow's ranting --&gt;
- <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/news/status/report-2001-12-2002-01.xml b/en/news/status/report-2001-12-2002-01.xml
deleted file mode 100644
index f3bd52140c..0000000000
--- a/en/news/status/report-2001-12-2002-01.xml
+++ /dev/null
@@ -1,717 +0,0 @@
-<!-- $FreeBSD: www/en/news/status/report-dec-2001-jan-2002.xml,v 1.6 2004/04/04 21:46:14 phantom 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-dec-2001-jan-2002.xml,v 1.6 2004/04/04 21:46:14 phantom 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 &amp; 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&#248;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/news/status/report-2002-02-2002-04.xml b/en/news/status/report-2002-02-2002-04.xml
deleted file mode 100644
index 560b29600f..0000000000
--- a/en/news/status/report-2002-02-2002-04.xml
+++ /dev/null
@@ -1,1297 +0,0 @@
-<!-- $FreeBSD: www/en/news/status/report-feb-2002-apr-2002.xml,v 1.10 2003/04/13 16:31:52 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 &amp; 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
- &lt;sys/cdefs.h&gt;. Some work has been completed on renovating the
- way types are defined. This has lead to the creation of
- &lt;sys/_types.h&gt;. Further improvements such as the merger of
- &lt;machine/ansi.h&gt; and &lt;machine/types.h&gt; are planned.
- Additionally, the headers: &lt;strings.h&gt;, &lt;string.h&gt;, and
- &lt;sys/un.h&gt; 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&#351;</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&#370;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&#370;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/news/status/report-2002-05-2002-06.xml b/en/news/status/report-2002-05-2002-06.xml
deleted file mode 100644
index 25248f14b7..0000000000
--- a/en/news/status/report-2002-05-2002-06.xml
+++ /dev/null
@@ -1,1446 +0,0 @@
-<!-- $FreeBSD: www/en/news/status/report-may-2002-june-2002.xml,v 1.5 2003/04/13 16:31:52 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 &amp; 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:
- &lt;netinet/in.h&gt;, &lt;pwd.h&gt;, &lt;sys/statvfs.h&gt;, and
- &lt;sys/wait.h&gt;.</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 &amp; 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 &lt;Jean-Luc.Richier@imag.fr&gt; 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/news/status/report-2002-07-2002-08.xml b/en/news/status/report-2002-07-2002-08.xml
deleted file mode 100644
index fb53d369a4..0000000000
--- a/en/news/status/report-2002-07-2002-08.xml
+++ /dev/null
@@ -1,1057 +0,0 @@
-<!-- $FreeBSD: www/en/news/status/report-july-2002-aug-2002.xml,v 1.4 2003/04/13 16:31:52 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 &lt;if&gt;_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 &amp; 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: &lt;fmtmsg.h&gt;, &lt;poll.h&gt;, &lt;sys/mman.h&gt;, and
- &lt;ulimit.h&gt;. The header &lt;cpio.h&gt; was implemented. The
- headers &lt;machine/ansi.h&gt; and &lt;machine/types.h&gt; 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&#225;rio S&#233;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&#237;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&#225;rio S&#233;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&#225;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&#233;</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/news/status/report-2002-09-2002-10.xml b/en/news/status/report-2002-09-2002-10.xml
deleted file mode 100644
index 30d061ab59..0000000000
--- a/en/news/status/report-2002-09-2002-10.xml
+++ /dev/null
@@ -1,1021 +0,0 @@
-<!-- $FreeBSD: www/en/news/status/report-sept-2002-oct-2002.xml,v 1.7 2004/04/05 14:46:17 phantom 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 &amp; 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&#233;</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/news/status/report-2002-11-2002-12.xml b/en/news/status/report-2002-11-2002-12.xml
deleted file mode 100644
index 7cf255898c..0000000000
--- a/en/news/status/report-2002-11-2002-12.xml
+++ /dev/null
@@ -1,877 +0,0 @@
-<!-- $FreeBSD: www/en/news/status/report-nov-2002-dec-2002.xml,v 1.4 2004/04/05 14:46:17 phantom 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 &amp; 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
- &lt;wordexp.h&gt; 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&#233;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&#233;phane has began the
- integration of our French localization web site in the US CVS Tree.
- S&#233;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&#35; 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&#35;).</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
- Millenium 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/news/status/report-2003-01-2003-02.xml b/en/news/status/report-2003-01-2003-02.xml
deleted file mode 100644
index a21d51f12e..0000000000
--- a/en/news/status/report-2003-01-2003-02.xml
+++ /dev/null
@@ -1,700 +0,0 @@
-<!-- $FreeBSD: www/en/news/status/report-jan-2003-feb-2003.xml,v 1.4 2003/04/13 16:31:52 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 &amp; 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/news/status/report-2003-03-2003-09.xml b/en/news/status/report-2003-03-2003-09.xml
deleted file mode 100644
index cf42d8744f..0000000000
--- a/en/news/status/report-2003-03-2003-09.xml
+++ /dev/null
@@ -1,970 +0,0 @@
-<!-- $FreeBSD: www/en/news/status/report-mar-2003-sep-2003.xml,v 1.2 2004/04/04 21:46:14 phantom 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 completly (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> Volonteers 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/news/status/report-2003-10-2003-12.xml b/en/news/status/report-2003-10-2003-12.xml
deleted file mode 100644
index c55f64dbab..0000000000
--- a/en/news/status/report-2003-10-2003-12.xml
+++ /dev/null
@@ -1,1361 +0,0 @@
-<!-- $FreeBSD: www/en/news/status/report-oct-2003-dec-2003.xml,v 1.3 2004/02/01 00:45:05 ale 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, &quot;syn-proxy&quot;
- 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 &lt;matt at peterson dot org&gt; I now have
- Bluetooth keyboard and mouse for development. I'm currently
- working on Bluetooth HID profile implementation.</p>
-
- <p>Dave Sainty &lt;dave at dtsp dot co dot nz&gt; 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/news/status/report-2004-01-2004-02.xml b/en/news/status/report-2004-01-2004-02.xml
deleted file mode 100644
index 325b7971f5..0000000000
--- a/en/news/status/report-2004-01-2004-02.xml
+++ /dev/null
@@ -1,865 +0,0 @@
-<!-- $FreeBSD: www/en/news/status/report-jan-2004-feb-2004.xml,v 1.4 2004/04/07 11:27:47 phantom 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 &lt;if&gt; name &lt;newname&gt;".</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 &lt; matt at peterson dot org &gt; 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/news/status/report-2004-03-2004-04.xml b/en/news/status/report-2004-03-2004-04.xml
deleted file mode 100644
index 0b2be2ad69..0000000000
--- a/en/news/status/report-2004-03-2004-04.xml
+++ /dev/null
@@ -1,1151 +0,0 @@
-<!-- $FreeBSD: www/en/news/status/report-mar-2004-apr-2004.xml,v 1.2 2004/05/16 09:08:28 blackend 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 enha