os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Minor nits

Browse source
This commit is contained in:
Gabor Pali 2010-10-25 16:08:05 +00:00
parent 01627bb8b4
commit 408653f13f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=36524
1 changed files with 209 additions and 198 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

407
en/news/status/report-2010-07-2010-09.xml
View file

@ -1,7 +1,7 @@
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for
Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<!-- $FreeBSD: www/en/news/status/report-2010-07-2010-09.xml,v 1.5 2010/10/25 08:30:55 bcr Exp $ -->
<!-- $FreeBSD: www/en/news/status/report-2010-07-2010-09.xml,v 1.6 2010/10/25 15:31:39 danger Exp $ -->
<report>
<date>
@ -15,7 +15,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>This report covers &os;-related projects between July and
September 2010. It is the third of the four reports planned for
2010. During this period, we were victims of one
2010. During this period, we were victims of one
of the biggest BSD events of the year &mdash; EuroBSDCon.
We hope that the ones of you who have been able to attend it
have enjoyed your stay. Another good news is that work on the
@ -25,7 +25,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
the whole history and shows a good condition of the &os;
community.</p>
<p>Thanks to all the reporters for the excellent work! We hope you
<p>Thanks to all the reporters for the excellent work! We hope you
enjoy reading it.</p>
<p>Please note that the deadline for submissions covering the period
@ -93,7 +93,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</category>
<project cat='soc'>
<title>Atheros AR913x SoC support</title>
<title>Atheros AR913x SoC Support</title>
<contact>
<person>
@ -116,10 +116,10 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<body>
<p>&os;-CURRENT runs on the AR9132 SoC. Minor platform-specific
tweaks are needed to use it on a given piece of hardware (eg.,
where in flash the Ethernet MAC address is stored.) The AR910x
where in flash the Ethernet MAC address is stored.) The AR910x
wireless MAC/PHY is supported. The only available test platform
uses a 2.4GHz radio; 5GHz 11a mode has not been tested. As with
other atheros chipset support in &os;, 11n support is not yet
other Atheros chipset support in &os;, 11n support is not yet
finished. The current development platform is the TP-Link
TP-WN1043ND 802.11n wireless bridge/router. It is currently being
successfully used as a 11bg access point.</p>
@ -128,7 +128,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<help>
<task>USB support is currently not functional.</task>
<task>There is currently no support for the realtek gigabit
<task>There is currently no support for the Realtek Gigabit
switch/PHY chip. This is being worked on.</task>
</help>
</project>
@ -182,7 +182,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</contact>
<links>
<url href="http://wiki.FreeBSD.org/SOC2010ZhengLiu">project
<url href="http://wiki.FreeBSD.org/SOC2010ZhengLiu">Project
wiki</url>
<url href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2010/extfs/src/sys/fs/&amp;c=rFV@//depot/projects/soc2010/extfs/src/sys/fs/ext2fs/?ac=83">
@ -193,21 +193,21 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>This project has two goals: pre-allocation algorithm for
ext2fs and ext4 read-only mode. The aim of pre-allocation
algorithm is to implement a reservation window mechanism.
This mechanism has been implemented and I have submitted a patch
file to mailing list (fs@FreeBSD.org). The aim of ext4 read-only
mode is to make it possible to read ext4 file systems in read-only
mode when the disk is formatted with default features. Until now it
can read data from ext4 file systems with default features in
read-only mode. I have submitted a patch to mailing list
(fs@FreeBSD.org) and am building a new kernel module for it, which
is called ext4fs.</p>
<p>This project has two goals: pre-allocation algorithm for ext2fs
and ext4 read-only mode. Aim of the pre-allocation algorithm is
to implement a reservation window mechanism. This mechanism has
been implemented and a patch have been submitted. The aim of
ext4 read-only mode is to make it possible to read ext4 file
systems in read-only mode when the disk is formatted with
default features. Until now it can read data from ext4 file
systems with default features in read-only mode. A patch has
been submitted a patch to the freebsd-fs mailing list and there
is a new kernel module, called ext4fs, is under development for
it.</p>
</body>
<help>
<task>More testing of pre-allocation algorithm.</task>
<task>More testing of the pre-allocation algorithm.</task>
</help>
</project>
@ -312,10 +312,10 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>We recently imported the 2.8 release of Clang into CURRENT. This
release contains many new features and improvements. The
integrated assembler ships with this version, but it is not ready
for general use yet.</p>
<p>We recently imported the 2.8 release of Clang into -CURRENT.
This release contains many new features and improvements. The
integrated assembler ships with this version, but it is not
ready for general use yet.</p>
<p>Since r212979, all necessary changes have been committed to be
able to build world with Clang, at least on amd64 and i386. It
@ -349,8 +349,8 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='bin'>
<title>Updating base tools to accommodate ports
requirements</title>
<title>Updating Base Tools to Accommodate Ports
Requirements</title>
<contact>
<person>
@ -397,7 +397,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>All Octeon development is now ongoing in 9.0-CURRENT and most
<p>All Octeon development is now ongoing in -CURRENT and most
Octeon-specific and general MIPS changes from the old Octeon
branch have been checked in. The Simple Executive from the Cavium
Octeon SDK has been checked into Subversion and most of the
@ -427,7 +427,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='kern'>
<title>Kernel event timers infrastructure</title>
<title>Kernel Event Timers Infrastructure</title>
<contact>
<person>
@ -448,7 +448,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>Work on new event timers infrastructure continues. In CURRENT
<p>Work on new event timers infrastructure continues. In -CURRENT
amd64, arm (Marvell), i386, mips, pc98, powerpc, sparc64, sun4v
architectures were refactored to use new timers API.</p>
@ -494,7 +494,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='ports'>
<title>Ports distfile and WWW checker</title>
<title>Ports Distfile and WWW Checker</title>
<contact>
<person>
@ -524,7 +524,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</body>
<help>
<task>provide JavaScript to sort/filter/search tables.</task>
<task>Provide JavaScript to sort/filter/search tables.</task>
</help>
</project>
@ -691,7 +691,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
building.</p>
<p>The Ports Management team have been running -exp runs on an
ongoing basis, verifying how base system updates may affect the
on-going basis, verifying how base system updates may affect the
ports tree, as well as providing QA runs for major ports updates.
Of note, -exp runs were done for:</p>
@ -706,14 +706,14 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<li>ade: multiple runs autotools upgrade</li>
<li>gerald: setting USE_GCC=4.5 as default</li>
<li>ashish: changes to Mk/bsd.license.mk</li>
<li>kwm: test of clang in CURRENT</li>
<li>kwm: test of Clang in -CURRENT</li>
</ul>
</body>
<help>
<task>Looking for help fixing <a
href="http://wiki.FreeBSD.org/PortsBrokenOnCurrent">ports
broken on CURRENT</a>.</task>
broken on -CURRENT</a>.</task>
<task>Looking for help with <a
href="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures">
@ -778,10 +778,10 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>During the last two months the USB stack in &os;-CURRENT has
been enhanced to support USB 3.0 and the XHCI USB 3.0 chipset
from Intel. The XHCI chip will eventually replace the EHCI, OHCI
and UHCI chips.</p>
<p>During the last two months the USB stack in -CURRENT has been
enhanced to support USB 3.0 and the XHCI USB 3.0 chipset from
Intel. The XHCI chip will eventually replace the EHCI, OHCI and
UHCI chips.</p>
</body>
<help>
@ -818,19 +818,20 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>Drivers status:</p>
<ul>
<li>rt2860: Ralink RT2860 802.11n - Worked, but RT3022 2.4G
2T2R radio tuning required.</li>
<li>rt2860: Ralink RT2860 802.11n &mdash; Worked, but RT3022
2.4G 2T2R radio tuning required.</li>
<li>rt: Ralink RT3052F onChip Ethernet MAC - DONE</li>
<li>rt: Ralink RT3052F onChip Ethernet MAC &mdash; Done.</li>
<li>rtsw: OnChip Ethernet switch - not done (initialized by
UBoot)</li>
<li>rtsw: OnChip Ethernet switch &mdash; Not done (initialized
by UBoot).</li>
<li>usb-otg: DWC like USB OTG controller - Worked</li>
<li>usb-otg: DWC like USB OTG controller &mdash; Worked.</li>
<li>gpio: RT3052F onChip GPIO - Worked (LEDs, Buttons)</li>
<li>gpio: RT3052F onChip GPIO &mdash; Worked (LEDs,
Buttons).</li>
<li>cfi: CFI NOR Flash - Worked</li>
<li>cfi: CFI NOR Flash &mdash; Worked.</li>
</ul>
<p>&os;/mips D-Link DIR-320 project(BCM5354 SoC).</p>
@ -856,7 +857,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='docs'>
<title>Web feeds for UPDATING files</title>
<title>Web Feeds for UPDATING Files</title>
<contact>
<person>
@ -874,9 +875,9 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<body>
<p><a href="http://updating.versia.com/">updating.versia.com</a>
features web feeds for UPDATING files from ports, head, stable/7
and stable/8. These feeds provide an easy way to track important
changes in the ports tree and the base system.</p>
features web feeds for UPDATING files from ports, head, stable/7
and stable/8. These feeds provide an easy way to track
important changes in the ports tree and the base system.</p>
</body>
</project>
@ -900,8 +901,9 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
status report. The only noteworthy exception are some performance
optimizations which take advantage of features of Fujitsu SPARC64
CPUs. These were a bit too risky for putting them in shortly
before &os; 8.1-RELEASE but will be part of 7.4-RELEASE and
8.2-RELEASE now that they have received the necessary testing.</p>
before &os;&nbsp;8.1-RELEASE but will be part of 7.4-RELEASE and
8.2-RELEASE now that they have received the necessary
testing.</p>
<p>Part of reasons why not much has happened in this spot was some
lack of time on my side but also due to nobody showing up with a
@ -965,8 +967,8 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='docs'>
<title>mandoc/mdocml &mdash; groff replacement for rendering manpages
in &os;</title>
<title>mandoc/mdocml &mdash; groff Replacement for Rendering Manual
Pages in &os;</title>
<contact>
<person>
@ -985,19 +987,19 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>Kristaps' groff-replacement (for rendering manpages, only) is
already available in NetBSD and OpenBSD, and used to render the base
system manpages for the latter. This project aims to do similar
things for &os;.</p>
<p>Kristaps' groff-replacement (only for rendering manual pages)
is already available in NetBSD and OpenBSD, and used to render the
base system manpages for the latter. This project aims to do
similar things for &os;.</p>
<p>mandoc(1) is more strict in what it accepts as input and is still
lacking some features that are used by some selected few manpages.</p>
<p>Getting manpage fixes accepted by upstream vendors has been
challenging. Waiting for them to round-trip back into &os; will take
even longer. Future work will therefore result in direct commits to
our contrib/ and gnu/ repository areas, in the hope this will not
impact future vendor imports too much.</p>
<p>Getting manual page fixes accepted by upstream vendors has been
challenging. Waiting for them to round-trip back into &os; will
take even longer. Future work will therefore result in direct
commits to our contrib/ and gnu/ repository areas, in the hope
this will not impact future vendor imports too much.</p>
</body>
<help>
@ -1007,8 +1009,8 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<task>Import mandoc(1), switch to catpages for base.</task>
<task>Supply necessary ports infrastructure to opt-in to mandoc(1).
</task>
<task>Supply necessary ports infrastructure to opt-in to
mandoc(1).</task>
<task>Discuss future of groff(1) in base wrt. share/doc.</task>
</help>
@ -1032,7 +1034,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
bsdadminscripts SF project</url>
<url href="http://sf.net/projects/bsdadminscripts/files/publications/2010-10-eurobsdcon/">
EuroBSDCon2010 slides and paper</url>
EuroBSDCon&nbsp;2010 slides and paper</url>
</links>
<body>
@ -1042,12 +1044,12 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>Currently the tool is in the final stages of a recode, that
will greatly improve support for sharing packages over NFS or
nullfs mounts (e.g. for distributing packages into jails) and
nullfs mounts (e.g. for distributing packages into jails) and
also offers improved dependency tracking and performance, more in
line with how pointyhat and Tinderbox build packages.</p>
<p>I recently had the opportunity to present my work at the
EuroBSDCon2010.</p>
EuroBSDCon&nbsp;2010.</p>
</body>
<help>
@ -1061,7 +1063,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='soc'>
<title>Registration of optional kernel subsystems via
<title>Registration of Optional Kernel Subsystems via
sysctl</title>
<contact>
@ -1094,13 +1096,13 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<task>Presentation of feature set on the various mailing
lists.</task>
<task>Committing to CURRENT, possibly merging to stable branches
<task>Committing to -CURRENT, possibly merging to stable branches
(changes do not break ABI/KBI).</task>
</help>
</project>
<project cat='proj'>
<title>Kernel-level stacked cryptographic filesystem &mdash;
<title>Kernel-level Stacked Cryptographic File System &mdash;
PEFS</title>
<contact>
@ -1120,7 +1122,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>PEFS is a kernel level stacked cryptographic filesystem, i.e.
<p>PEFS is a kernel level stacked cryptographic file system, i.e.
it stacks on top of existing mounted filesystems. AES and
Camellia algorithms in XTS mode are supported. The project has
matured since Summer of Code 2009, most important improvements
@ -1128,7 +1130,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
implementation of sparse file support, fixing rename bugs
including race and livelock conditions, addition of ext2 support.
PEFS suite contains pam module facilitating user authentication
with filesystem key and adding keys to mounted filesystem on
with file system key and adding keys to mounted file system on
login. PEFS passes fsx, pjdfstest, blogbench and dbench tests
running on top of UFS and ZFS.</p>
</body>
@ -1166,12 +1168,12 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>Current Status:</p>
<ul>
<li>integrated with <b>lem</b> driver. Intel network controllers:
<li>Integrated with the lem driver. Intel network controllers:
8254X are supported.</li>
<li>packet filtering using BPF in both kernel and user-space</li>
<li>Packet filtering using BPF in both kernel and user space.</li>
<li>partly integrated with <b>ixgbe</b> driver for 10Gb capturing</li>
<li>Partly integrated with ixgbe driver for 10Gb capturing.</li>
</ul>
</body>
@ -1204,18 +1206,18 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>We were proud to be a sponsor for MeetBSD 2010 Poland and
KyivBSD 2010 in Kiev, Ukraine. We also committed to sponsoring
BSDDay Argentina 2010, MeetBSD California 2010, and NYBSDCon 2010
all in November. The Foundation was also represented at MeetBSD
Poland and Ohio LinuxFest.</p>
<p>We were proud to be a sponsor for MeetBSD&nbsp;2010 Poland and
KyivBSD&nbsp;2010 in Kiev, Ukraine. We also committed to
sponsoring BSDDay Argentina 2010, MeetBSD California 2010, and
NYBSDCon&nbsp;2010 all in November. The Foundation was also
represented at MeetBSD Poland and Ohio LinuxFest.</p>
<p>Completed the Foundation funded projects: &os; Jail Based
Virtualization by Bjoern Zeeb and DTrace Userland by Rui
<p>Completed the Foundation funded projects: "&os; Jail-Based
Virtualization" by Bjoern Zeeb and "DTrace Userland" by Rui
Paulo.</p>
<p>We kicked off a new project by Swinburne University called
Five New TCP Congestion Control Algorithms for &os;.</p>
"Five New TCP Congestion Control Algorithms for &os;".</p>
<p>We continued our work on infrastructure projects to beef up
hardware for package-building, network-testing, etc. This
@ -1235,7 +1237,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='ports'>
<title>Chromium web browser</title>
<title>Chromium Web Browser</title>
<contact>
<person>
@ -1371,8 +1373,8 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
administrators who operate &os; systems in atypical network
scenarios.</p>
<p>Keep an eye on the freebsd-net@FreeBSD.org mailing list for
project related announcements.</p>
<p>Keep an eye on the freebsd-net mailing list for project-related
announcements.</p>
</body>
</project>
@ -1400,11 +1402,11 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>All outstanding patches have been committed to the svn "head"
branch after a lengthy review process. I anticipate merging all
of the project's SIFTR and reassembly queue related patches from
head to the stable branches in time for the upcoming 7.4 and 8.2
releases.</p>
<p>All outstanding patches have been committed to -CURRENT after a
lengthy review process. It is anticpated to merge all of the
project's SIFTR and reassembly queue-related patches from
-CURRENT to the stable branches in time for the upcoming 7.4 and
8.2 releases.</p>
</body>
</project>
@ -1428,10 +1430,10 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
mechanisms, such as Hierarchical Resource Limits, for "Collective
Limits on Set of Processes (aka. Jobs)" Google Summer of Code
2010 project, for implementing mechanism similar to Linux
cgroups, and might be also used to e.g. provide precise resource
cgroups, and might be also used to e.g. provide precise resource
usage accounting for administrative or billing purposes. So far,
a generic resource usage framework has been developed, along with
limit enforcement for most resources. Work is ongoing on adding
limit enforcement for most resources. Work is on-going on adding
limits for remaining resources, debugging and generally improving
the implementation. This project is being sponsored by The &os;
Foundation.</p>
@ -1439,7 +1441,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='proj'>
<title>BSNMP enhancements</title>
<title>BSNMP Enhancements</title>
<contact>
<person>
@ -1460,8 +1462,8 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</contact>
<links>
<url href="http://wiki.FreeBSD.org/CategorySNMP">bsnmpd(1)
related pages on &os; wiki</url>
<url href="http://wiki.FreeBSD.org/CategorySNMP">bsnmpd(1)-related
pages on &os; wiki</url>
<url href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/syrinx/snmp_ieee80211&amp;HIDEDEL=NO">
snmp_wlan(3) P4 code tree</url>
@ -1472,31 +1474,39 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<body>
<p>During the previous few months several additions were
developed to &os;'s built-in SNMP daemon - bsnmpd(1). First a
snmp_wlan(3) module was developed that allows monitoring and
configuration of wlan(4) interfaces operating in various modes,
including statistics, attached/neighboring station information,
MAC access control entries and mesh routing information. The
module's code was submitted in SVN and is now a part of the &os;
base system. Next, SNMPv3 authentication and encryption support
were added to bsnmplib(3), bsnmpd(1) and bsnmptools (which are
available via the ports system currently). The message digest and
cipher calculation calls use the implementation of the relevant
developed to &os;'s built-in SNMP daemon &mdash; bsnmpd(1).</p>
<p>First a snmp_wlan(3) module was developed that allows
monitoring and configuration of wlan(4) interfaces operating in
various modes, including statistics, attached/neighboring
station information, MAC access control entries and mesh routing
information. The module's code was submitted in SVN and is now
a part of the &os; base system.</p>
<p>Next, SNMPv3 authentication and encryption support were added
to bsnmplib(3), bsnmpd(1) and bsnmptools (which are available
via the ports system currently). The message digest and cipher
calculation calls use the implementation of the relevant
cryptographic algorithm implementation in OpenSSL's crypto(3)
library. bsnmpd(1) may still optionally be compiled without the
crypto(3) library, in which case only unauthenticated plain-text
SNMPv3 PDUs may be processed. In addition, a snmp_usm(3) module
was developed that is used to configure SNMPv3 users parameters
(name, authentication &amp; encryption algorithms used and relevant
keys, etc.) into bsnmpd(1) as per RFC 3414. Finally, a
snmp_vacm(3) module was developed that allows configuration of
view-based access control as per RFC 3415, and relevant checks
are made by bsnmpd(1) that allow or restrict access to specific
SNMPv1/SNMPv2 communities or SNMPv3 users to certain MIB subtrees
as per the configuration in the snmp_vacm(3) module. If none of
the SNMPv3-related modules is loaded, bsnmpd(1) preserves its
current behavior with SNMPv1/SNMPv2c PDUs. This work is being
funded by the &os; Foundation.</p>
SNMPv3 PDUs may be processed.</p>
<p>In addition, a snmp_usm(3) module was developed that is used to
configure SNMPv3 users parameters (name, authentication &amp;
encryption algorithms used and relevant keys, etc.) into
bsnmpd(1) as per RFC 3414.</p>
<p>Finally, a snmp_vacm(3) module was developed that allows
configuration of view-based access control as per RFC 3415, and
relevant checks are made by bsnmpd(1) that allow or restrict
access to specific SNMPv1/SNMPv2 communities or SNMPv3 users to
certain MIB subtrees as per the configuration in the
snmp_vacm(3) module. If none of the SNMPv3-related modules is
loaded, bsnmpd(1) preserves its current behavior with
SNMPv1/SNMPv2c PDUs.</p>
<p>This work is being funded by the &os; Foundation.</p>
</body>
<help>
@ -1542,9 +1552,9 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
utility may be used to inquire about what services are
monitored, their pidfile location, and current process id.</p>
<p>FSC provides several advantages over the third party
<p>FSC provides several advantages over the third-party
daemontools package. For example, fscd uses push notifications
instead of polling; fscd is an internal, &os; maintained
instead of polling; fscd is an internal, &os;-maintained
software package accessible to all developers where daemontools
would have to be a port and require us to maintain patches;
fscd could be easily integrated with the current rc.d
@ -1566,7 +1576,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='kern'>
<title>Netdump support</title>
<title>Netdump Support</title>
<contact>
<person>
@ -1666,7 +1676,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='bin'>
<title>xz compression for packages and logfiles</title>
<title>xz Compression for Packages and Log Files</title>
<contact>
<person>
@ -1679,10 +1689,10 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</contact>
<body>
<p>Support for xz compression has been enabled in bsdtar (CURRENT
8-STABLE) and added to pkg_create(1) and pkg_add(1) (CURRRENT).
<p>Support for xz compression has been enabled in bsdtar (-CURRENT
8-STABLE) and added to pkg_create(1) and pkg_add(1) (-CURRRENT).
Packages with the .txz suffix can be created and installed.
Logfile compression using xz in newsyslog(8) will be integrated
Log file compression using xz in newsyslog(8) will be integrated
soon. Benchmarks show 15-30% better compression ratios and up to
halved decompression times when compared to bzip2. A switch from
the default package format from .tbz to .txz is to be
@ -1695,7 +1705,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='misc'>
<title>meetBSD California 2010 DevSummit</title>
<title>&os; Developer Summit, meetBSD California 2010</title>
<contact>
<person>
@ -1715,18 +1725,18 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<body>
<p>We will be having a developers summit meeting at meetBSD
California 2010 on November 4th, the day before the conference.
Based on who is in attendance, we will be talking about the status
of pressing issues; working on pressing problems and using the
opportunity for face to face meetings to work out issues that are
difficult in email. This is an invitation only event, but any
developer can invite people they think would help drive this
meeting forward. An agenda will be published closer to the date.
For more information, please contact Warner Losh.</p>
Based on who is in attendance, we will be talking about the
status of pressing issues; working on pressing problems and
using the opportunity for face to face meetings to work out
issues that are difficult in email. This is an invitation-only
event, but any developer can invite people they think would help
drive this meeting forward. An agenda will be published closer
to the date.</p>
</body>
</project>
<project cat='proj'>
<title>External toolchain support</title>
<title>External Toolchain Support</title>
<contact>
<person>
@ -1745,16 +1755,17 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
generically, but often times silicon vendors produce specialized
toolchains to wring the most performance out of their silicon.
Right now, it is difficult to compile &os; with these tools, as
many manual steps are required to make things 'just so'. The
external toolchain project will leverage some of the work done by
the clang team to support clang in the base system (breaking the
strict dependency on CC=cc (except for the broken intel CC
support)). In addition, the orchestration of the build (make
buildworld) will change to avoid bootstrapping certain tools, or
compiling the compilers at all. In addition, support for using
alternate assemblers, linkers, etc., will be added. The work will
be done in subversion in projects/xtc (for eXternal Tool
Chain).</p>
many manual steps are required to make things 'just so'.</p>
<p>The external toolchain project will leverage some of the work
done by the Clang team to support Clang in the base system
(breaking the strict dependency on CC=cc (except for the broken
intel CC support)). In addition, the orchestration of the build
(make buildworld) will change to avoid bootstrapping certain
tools, or compiling the compilers at all. In addition, support
for using alternate assemblers, linkers, etc., will be added.
The work will be done in subversion in projects/xtc (for
eXternal Tool Chain).</p>
</body>
</project>
@ -1922,7 +1933,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
need wider testing and use to expose potential weaknesses, bugs,
and additional features it may require.</task>
<task>Related tasks include getting a text front end to
<task>Related tasks include getting a text front-end to
pc-sysinstall working and hooking up pc-sysinstall to the build
so install media is generated that runs pc-sysinstall.</task>
</help>
@ -1957,7 +1968,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>DAHDI (Digium/Asterisk Hardware Device Interface) is an
open-source device driver framework and a set of hardware drivers
for E1/T1, ISDN digital, and FXO/FXS analog cards [<a
ref="http://www.asterisk.org/dahdi/">1</a>].
href="http://www.asterisk.org/dahdi/">1</a>].
Asterisk is one of the most popular open-source software PBX
solutions [<a href="http://www.asterisk.org/">2</a>].</p>
@ -1980,17 +1991,17 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
soon:</p>
<ul>
<li>add ability to run asterisk+dahdi under non-root user
account</li>
<li>Add ability to run asterisk+dahdi under non-root user
account.</li>
<li>add support for bri_net_ptmp ISDN signalling to asterisk
<li>Add support for bri_net_ptmp ISDN signalling to asterisk
port and drop old and outdated zaptel+asterisk-bristuff
ports</li>
ports.</li>
</ul>
<p>I will continue periodic merges from DAHDI/Linux SVN on a
regular basis and roll out new DAHDI/&os; releases (most likely
synchronized with DAHDI/Linux releases).</p>
<p>Periodic merges from DAHDI/Linux SVN will be continued on a
regular basis with rolling out new DAHDI/&os; releases (most
likely synchronized with DAHDI/Linux releases).</p>
</body>
</project>
@ -2012,17 +2023,17 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>The V4L support in the Linux emulator has been MFC'd to
8-STABLE allowing use of video in skype calls using a camera
<p>The V4L support in the Linux emulator has been merged to
8-STABLE allowing use of video in Skype calls using a camera
supported by the pwcbsd or video4bsd drivers. A known issue for
skype is that your camera must support YUV420 mode which is what
skype uses. Note that V4L2 support is not included in the current
Skype is that your camera must support YUV420 mode which is what
Skype uses. Note that V4L2 support is not included in the current
work, and remains as a project for anyone interested.</p>
</body>
</project>
<project cat='net'>
<title>Syncing pf(4) with OpenBSD 4.5</title>
<title>Syncing pf(4) with OpenBSD&nbsp;4.5</title>
<contact>
<person>
@ -2046,7 +2057,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>This work is based on OpenBSD 4.5 state of pf(4). It includes
<p>This work is based on OpenBSD&nbsp;4.5 state of pf(4). It includes
many improvements over the code currently present in &os;. The
actual new feature present in pf45 repository is support for
divert(4), which should allow tools like snort_inline to work
@ -2054,9 +2065,9 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
a module as well.</p>
<p>Currently, this work is considered stable and a patch against
CURRENT has been released on freebsd-pf@ mailing list.</p>
-CURRENT has been released on freebsd-pf mailing list.</p>
<p>The reason why this work is based off of OpenBSD 4.5 is that
<p>The reason why this work is based off of OpenBSD&nbsp;4.5 is that
after this release they have changed the syntax which is not
backwards compatible.</p>
@ -2072,7 +2083,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='ports'>
<title>OpenAFS port</title>
<title>OpenAFS Port</title>
<contact>
<person>
@ -2100,19 +2111,20 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>AFS is a distributed network filesystem that originated from
<p>AFS is a distributed network file system that originated from
the Andrew Project at Carnegie-Mellon University; the OpenAFS
client implementation has not been particularly useful on &os;
since the &os; 4.X releases. The previous status report
brought the OpenAFS client to a useful form on 9.0-CURRENT,
since the &os;&nbsp;4.X releases. The previous status report
brought the OpenAFS client to a useful form on -CURRENT,
though with many rough edges. Only a couple of those edges have
been smoothed out during the past few months, as developer time
was scarce. A mismatch between file size and vmobject size
tracking was resolved (allowing executables to be run from AFS),
and our system call entry has been updated on CURRENT and 8-STABLE
to match reality. Thanks to kib@ for both of those! The code is
useful enough that we plan to submit an openafs-devel port to the
Ports Collection in the coming cycle.</p>
and our system call entry has been updated on -CURRENT and 8-STABLE
to match reality. Thanks to Kostik Belusov for both of those!
The code is useful enough that we plan to submit an
openafs-devel port to the Ports Collection in the coming
cycle.</p>
<p>There are several known outstanding issues that are being
worked on, but detailed bug reports are welcome at
@ -2136,7 +2148,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='proj'>
<title>gptboot improvements</title>
<title>gptboot Improvements</title>
<contact>
<person>
@ -2166,7 +2178,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='proj'>
<title>HAST (Highly Available Storage) improvements</title>
<title>HAST (Highly Available Storage) Improvements</title>
<contact>
<person>
@ -2179,12 +2191,12 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</contact>
<body>
<p>HAST is now better than ever!:) Some recent improvements
<p>HAST is now better than ever! Some recent improvements
include:</p>
<ul>
<li>Hooks supports - HAST will execute the given command on
various events (connect, disconnect, synchronization start,
<li>Hooks supports &mdash; HAST will execute the given command
on various events (connect, disconnect, synchronization start,
synchronization completed, synchronization interrupted,
split-brain condition, role change).</li>
@ -2200,7 +2212,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='proj'>
<title>ZFSv28 is ready for wider testing</title>
<title>ZFSv28 is Ready for Wider Testing</title>
<contact>
<person>
@ -2224,7 +2236,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='proj'>
<title>GELI additions</title>
<title>GELI Additions</title>
<contact>
<person>
@ -2238,7 +2250,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<body>
<p>There are three new GELI (a disk encryption GEOM class)
features available in &os;-CURRENT:</p>
features available in -CURRENT:</p>
<ul>
<li>AES-XTS encryption. XTS mode is a standard that is
@ -2259,7 +2271,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='ports'>
<title>Valgrind port</title>
<title>Valgrind Port</title>
<contact>
<person>
@ -2294,11 +2306,11 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
threading bugs, and profiling. Version 3.6.0 has recently been
released and the &os; port has now been updated.</p>
<p>Development of the Valgrind port has moved from perforce to
<p>Development of the Valgrind port has moved from Perforce to
bitbucket.org, in order to make it easier for others to track
changes as we progress towards getting the port into shape to
commit upstream. You can access the repository at the bitbucket
URL at the beginning of this report.</p>
commit upstream. The repository's Bitbucket address is at the
beginning of the report.</p>
<p>A bugzilla entry has been submitted to track the &os; Valgrind
port. You can see the status and vote for the bug to express your
@ -2319,7 +2331,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='proj'>
<title>Capsicum: practical capabilities for UNIX</title>
<title>Capsicum: Practical Capabilities for UNIX</title>
<contact>
<person>
@ -2375,7 +2387,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
sandboxed capability mode for processes, anonymous shared memory
objects, process descriptors, and a modified C runtime able to
support distributed applications within sandboxes. Capsicum
has been prototyped on &os; 9-CURRENT, with a 8-STABLE
has been prototyped on &os; -CURRENT, with a 8-STABLE
backport.</p>
<p>Capsicum is intended to supplement existing system-centric
@ -2389,16 +2401,16 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
rendering.</p>
<p>We plan to begin merging the core Capsicum kernel features
to &os; 9-CURRENT in November/December 2010 once a number of
to &os; -CURRENT in November/December 2010 once a number of
known problems have been resolved. Following a KBI analysis, we
will consider merging our 8-STABLE backport to Subversion. For
the time being, and while APIs stabilise, we plan to distribute
the Capsicum libraries via ports. However, simply having the
the Capsicum libraries via ports. However, simply having the
kernel features in place is sufficient to support sandboxing in
tcpdump and Chromium.</p>
<p>The Capsicum paper by Robert Watson / Jonathan Anderson
(Cambridge) and Ben Laurie/ Kris Kennaway (Google) won a best
(Cambridge) and Ben Laurie / Kris Kennaway (Google) won a best
paper award at the 2010 USENIX Security Symposium!</p>
</body>
@ -2409,7 +2421,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<task>Using results of our recent model checking analysis of the
namei() sandboxing approach, make robustness improvements.</task>
<task>Merge to &os; 9-CURRENT in November/December.</task>
<task>Merge to &os; -CURRENT in November/December.</task>
<task>KBI analysis for possible 8-STABLE merge.</task>
@ -2483,10 +2495,10 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>August saw us host another bugathon, with an aim of
investigating and getting into a committable state several of the
PRs with patches. Turnout was not as great as in the past -
mainly believed to be die to the short notice, but still several
PRs were progressed, with several commits made and several PRs
closed.</p>
PRs with patches. Turnout was not as great as in the past
&mdash; mainly believed to be die to the short notice, but still
several PRs were progressed, with several commits made and
several PRs closed.</p>
<p>The number of PRs has held steady over the last three months,
with improvements in numbers in some categories (especially usb
@ -2495,8 +2507,8 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>Reports continue to be produced from the PR database, all of
which can be found from the links above. Committers interested
in custom reports are encouraged to discuss requirements with
bugmeister@ - we are happy to create new reports where needs are
identified.</p>
bugmeister@ &mdash; we are happy to create new reports where
needs are identified.</p>
<p>As always, anybody interested in helping out with the PR queue is
welcome to join us in #freebsd-bugbusters on EFnet. We are
@ -2537,7 +2549,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<body>
<p>The Release Engineering Team has announced the schedule for the
upcoming joint release of &os; 7.4 and 8.2. The schedules
are available on the Web site:</p>
are available on the web site:</p>
<ul>
<li><a href="http://www.freebsd.org/releases/7.4R/schedule.html">
@ -2632,8 +2644,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
latest ARM processors, and pc-sysinstall. The event was opened by
a keynote speech from Poul-Henning Kamp on software tools and
their future, and it was closed by short status reports on
different BSD flavors. Next year's event in 2011 will take place
in the Netherlands from 6th to 9th October 2011.</p>
different BSD flavors.</p>
</body>
</project>
@ -2664,7 +2675,7 @@ Status Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>The EuroBSDCon conference is inviting developers and users of
BSD based systems to submit innovative and original papers not
submitted to other European conferences on BSD related topics.</p>
submitted to other European conferences on BSD-related topics.</p>
<p>Please see the EuroBSDCon 2011 website for more details.</p>
</body>