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

- A few minor nits to the upcoming status report

Browse source
This commit is contained in:
Gabor Pali 2010-07-20 00:08:47 +00:00
parent 8e5ae11400
commit ccd8108540
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=36059
1 changed files with 217 additions and 196 deletions
Download patch file Download diff file Expand all files Collapse all files

387
en/news/status/report-2010-04-2010-06.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-04-2010-06.xml,v 1.4 2010/07/19 18:33:57 danger Exp $ -->
<!-- $FreeBSD: www/en/news/status/report-2010-04-2010-06.xml,v 1.5 2010/07/19 21:36:37 brd Exp $ -->
<report>
<date>
<month>April-June</month>
@ -11,7 +11,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<section>
<title>Introduction</title>
<p>This report covers &os; related projects between April and June
<p>This report covers &os;-related projects between April and June
2010. It is the second of the four reports planned for 2010, and
contains 44 entries. During this period, a lot of work has
gone into the development of new minor version of &os;, 8.1-RELEASE,
@ -75,7 +75,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</category>
<project cat='docs'>
<title>&os; German Documentation Project</title>
<title>The &os; German Documentation Project</title>
<contact>
<person>
@ -99,7 +99,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<url href="http://doc.bsdgroup.de">Website of the &os; German
Documentation Project</url>
<url href="http://www.FreeBSD.de/mailinglists.html">Mailinglists
<url href="http://www.FreeBSD.de/mailinglists.html">Mailing lists
for the coordination of our work and the place where you can report
bugs back to us</url>
</links>
@ -136,7 +136,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='soc'>
<title>Binary package patch infrastructure &mdash; pkg_patch</title>
<title>Binary Package Patch Infrastructure &mdash; pkg_patch</title>
<contact>
<person>
@ -168,8 +168,8 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<task>Get some testing for it.</task>
<task>Convince portmgr it is actually a Good Thing to have even as
an experimental feature.</task>
<task>Convince the Port Management Team it is actually a Good
Thing to have even as an experimental feature.</task>
<task>Agree upon the policy on which package patches will be
created (i.e. from which point in time to which point in time),
@ -212,7 +212,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='bin'>
<title>BSDL iconv in base system</title>
<title>BSD-Licensed iconv in Base System</title>
<contact>
<person>
@ -245,7 +245,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='bin'>
<title>BSDL grep in base system</title>
<title>BSD-Licensed grep in Base System</title>
<contact>
<person>
@ -264,7 +264,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<body>
<p>A portbuild test showed that grep is basically ready to enter
-HEAD, but there were a few failures that seem to be
HEAD, but there were a few failures that seem to be
related. These have to be investigated and fixed before
committing grep to 9-CURRENT.</p>
</body>
@ -275,7 +275,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='soc'>
<title>Collective resource limits (aka jobs)</title>
<title>Collective Resource Limits (aka. Jobs)</title>
<contact>
<person>
@ -369,7 +369,7 @@ 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>
@ -383,11 +383,11 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<body>
<p>Modern x86 systems include four different types of event timers:
i8254, RTC, LAPIC and HPET. First three are already supported by
i8254, RTC, LAPIC, and HPET. First three are already supported by
&os;. Depending on hardware and loader tunables, periodic
interrupts from them are used to trigger all time-based events in
kernel. That code has a long history, that made it tangled and
at the same time limited and hardcoded.</p>
at the same time limited and hard-coded.</p>
<p>New kernel event timers infrastructure was started to allow
different event timer hardware to be operated in uniform way and to
@ -405,11 +405,11 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>Different kinds of timers have different capabilities and could
be present in hardware in different combinations. In every
situation the infrastructure automatically chooses two best event
timers to supply system with hardclock(), statclock() and
profclock() events. If some timer is not functioning - it will be
replaced. If there is no second timer - it will be emulated.
timers to supply system with hardclock(), statclock(), and
profclock() events. If some timer is not functioning &mdash; it will be
replaced. If there is no second timer &mdash; it will be emulated.
The administrator may affect that choice using loader tunables during
boot and sysctls in run-time (kern.eventtimer, ...).</p>
boot and sysctl variables in run-time (kern.eventtimer.*, and so on).</p>
<p>Most of the code was recently committed to HEAD. Now it is used
by i386 and amd64 architectures.</p>
@ -467,7 +467,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
mistranslations were spotted and fixed. Apart from this, we are
still keeping the existing documentation and web page translations
up to date, currently without plans on further work. If you are
interested in helping us, or you have any comments or requests
interested in helping us, or you have any comments, or requests
regarding the translations, do not hesitate to contact the project
via the email addresses mentioned in the entry.</p>
</body>
@ -525,8 +525,8 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>Our efforts on porting the generalized, general-purpose purely
functional programming language, <a
href="http://www.haskell.org/">Haskell</a> has rallied, since
two new committers, <em>Giuseppe Pilichi</em> and <em>Ashish
Shukla</em> joined recently, forming the <em>&os; Haskell Team</em>.
two new committers, Giuseppe Pilichi and Ashish
Shukla joined recently, forming the &os; Haskell Team.
Over the last months, &os;/i386 and &os;/amd64 have become Tier-1
platforms, featuring officially supported vanilla binary
distributions for the <a
@ -584,7 +584,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<body>
<p>This project is about creating a wrapper library to support
monitoring and management networking with avoiding direct use of
monitoring and management of networking with avoiding direct use of
the &os; kvm(3) and sysctl(3) interfaces. This approach would allow
the kernel implementation to change and monitoring applications to
be extended without breaking applications and requiring them to be
@ -662,19 +662,19 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>The ZFS file system has been updated to version 15 on -HEAD and
will be MFCed to 8-STABLE around September 13th, 2010. Wwork
is ongoing on porting the recent ZFS version 26 with
<p>The ZFS file system has been updated to version 15 on HEAD and
it will be MFC'ed to 8-STABLE around September 13th, 2010. Work
is in progress on porting the recent ZFS version 26 with
deduplication functionality.</p>
</body>
<help>
<task>Fix bugs, unresolved issues and #TODO's in perforce.</task>
<task>Fix bugs, unresolved issues and to-dos in Perforce.</task>
</help>
</project>
<project cat='arch'>
<title>Flattened Device Tree for embedded &os;</title>
<title>Flattened Device Tree for Embedded &os;</title>
<contact>
<person>
@ -730,7 +730,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<li>MPC8572DS</li>
</ul>
<li>The FDT infrastructure (bus drivers, helper libraries and
<li>The FDT infrastructure (bus drivers, helper libraries, and
routines shared across architectures and platforms) allows for
easier porting to new platforms or variations. The initially
supported systems offer a working example of how to migrate
@ -741,7 +741,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</body>
<help>
<task>Improve howto and guidelines for new adopters (how to convert
<task>Improve how-to and guidelines for new adopters (how to convert
to FDT and so on).</task>
<task>Migrate more existing embedded &os; platforms (ARM, MIPS) to
@ -832,7 +832,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>We are once again participating in the Google Summer of Code.
This is our 6th year of participation and we hope to once again see
great results from our 18 students. Coding officially began May
24th and we are in the middle of the mid-term evaluation period.
24th, and we are in the middle of the mid-term evaluation period.
You can see and comment on weekly status reports on the <a
href="http://lists.freebsd.org/mailman/listinfo/soc-status">mailing
list</a> or on the <a
@ -841,7 +841,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='kern'>
<title>Jail based virtualization</title>
<title>Jail-Based Virtualization</title>
<contact>
<person>
@ -865,7 +865,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>The project started with some cleanup on the network stack after
all the import work and adjustments for virtualization to minimize
changes to earlier branches. These made it into the tree already
and to stable/8 and will be included in the upcoming 8.1
and to 8-STABLE, and it will be included in the upcoming 8.1
release.</p>
<p>The first major task was to generalize the virtualization
@ -941,9 +941,9 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<body>
<p>A significant part of quarter two was spent coordinating efforts
for inclusion of Xorg 7.5, KDE4, Gnome2, plus preparation of ports
for inclusion of Xorg&nbsp;7.5, KDE&nbsp;4, GNOME&nbsp;2, plus preparation of ports
for the 8.1 release process. Due to the success of enforcing
Feature Safe ports commits during the 7.3-RELEASE, it was continued
Feature Safe ports commits during 7.3-RELEASE, it was continued
for the recent src/ freeze.</p>
<p>The port count is approaching 22,000 ports. The open PR count
@ -952,7 +952,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>Since the last report, we added four new committers, and had two
old committers rejoin us.</p>
<p>The Ports Management team is very grateful to the &os;
<p>The Ports Management Team is very grateful to the &os;
Foundation for sponsoring two new head nodes for the ports building
cluster, pointyhat. Each of the new head nodes has a larger
capacity, both with regard to performance but also in amount of
@ -969,32 +969,42 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
rework of our custom codebase.</p>
<p>The Ports Management team have been running -exp runs on an
ongoing basis, verifying how src code updates may affect the ports
tree, as well as providing QA runs for major ports updates. Of note
-exp runs were done for; ale's update of math/gmp; delphij's
changes to Mk/bsd.ldap.mk; gahr's inclusion of USE_GL=glew;
pgollucci's changes to Mk/bsd.*apache.mk plus updates to devel/apr
and www/apache*; testing of x11/xorg, x11/gnome, x11/kde4 and
lang/mono; a test run make fetch run; a test run for deve/gettext;
mm's inclusion of USE_XZ; and ale's request to switch default mysql
from 5.0-EOL to 5.1-GA.</p>
ongoing basis, verifying how base system updates may affect the
ports tree, as well as providing QA runs for major ports
updates. Of note, -exp runs were done for:</p>
<p>alepulver's SoC Licensing Framework project has made it into the
tree and portmgr is currently assessing the fallout and will come
up with guidelines and documentation in due time.</p>
<ul>
<li>ale: Update of math/gmp.</li>
<li>delphij: Changes to Mk/bsd.ldap.mk.</li>
<li>gahr: Inclusion of USE_GL=glew.</li>
<li>pgollucci: Changes to Mk/bsd.*apache.mk plus updates to devel/apr
and www/apache*.</li>
<li>Testing of x11/xorg, x11/gnome2, x11/kde4, and
lang/mono</li>
<li>A test run make fetch run.</li>
<li>A test run for devel/gettext.</li>
<li>mm: Inclusion of USE_XZ.</li>
<li>ale: Request to switch default mysql from 5.0-EOL to
5.1-GA.</li>
</ul>
<p>alepulver's Licensing Framework Summer of Code project has made
it into the tree and the Port Management Team is currently
assessing the fallout and it will come up with guidelines and
documentation in due time.</p>
</body>
<help>
<task>Looking for help fixing <a
href="http://wiki.FreeBSD.org/PortsBrokenOnCurrent">ports
broken on CURRENT</a>.</task>
broken on 9-CURRENT</a>.</task>
<task>Looking for help with <a
href="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures">
Tier-2 architectures</a>.</task>
<task>Most ports PRs are assigned, we now need to focus on testing,
committing and closing.</task>
committing, and closing.</task>
</help>
</project>
@ -1017,7 +1027,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>On July 13, &os;/powerpc64 was integrated into -CURRENT. This
<p>On July 13, &os;/powerpc64 was integrated into HEAD. This
provides support for fully 64-bit operation on 64-bit PowerPC
machines conforming to the Book-S specification, including the
PowerPC 970, Cell, and POWER4-7. Hardware support is currently
@ -1061,12 +1071,12 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
is possible to netboot a kernel, which has support for the
framebuffer, MMU, and device discovery. Once work on drivers for
the network interface and interrupt controller is complete, it will
be possible to boot the console multiuser.</p>
be possible to boot the console multi-user.</p>
</body>
</project>
<project cat='proj'>
<title>OpenAFS port</title>
<title>OpenAFS Port</title>
<contact>
<person>
@ -1097,23 +1107,23 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>AFS is a distributed network filesystem that originated from the
Andrew Project at Carnegie-Mellon University; the OpenAFS client
implementation has not been particularly useful on &os; since the
&os; 4.X releases. Recent work on the OpenAFS codebase has updated
4.X releases. Recent work on the OpenAFS codebase has updated
it to be consistent with current versions of &os;, and the client,
though still considered experimental, is now relatively stable for
light (single-threaded) use on 9.0-CURRENT. The auxiliary utilities
light (single-threaded) use on 9-CURRENT. The auxiliary utilities
for managing and examining the filesystem are functional, and
reading and writing files works sufficiently well to copy /usr/src
into and out of AFS. Compiling and running executables in AFS is
unsuccessful, though, as mmap is not always reliable.</p>
unsuccessful, though, as mmap() is not always reliable.</p>
<p>There are several known outstanding issues that are being worked
on, but detailed bug reports are welcome at
port-freebsd@openafs.org.</p>
<p>There are several known outstanding issues that are being
worked on, but detailed bug reports are welcome at <a
href="mailto:port-freebsd@openafs.org">port-freebsd@openafs.org</a>.</p>
</body>
<help>
<task>Fix the {get,put}pages vnode operations for more reliable
mmap operation.</task>
mmap() operation.</task>
<task>Update VFS locking to allow the use of disk-based client
caches as well as memory-based caches.</task>
@ -1127,7 +1137,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='soc'>
<title>Package management library - libpkg</title>
<title>Package Management Library &mdash; libpkg</title>
<contact>
<person>
@ -1147,8 +1157,8 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>Libpkg will allow for fairly fine grained control over package
management.</p>
<p>The libpkg library will allow for fairly fine grained control
over package management.</p>
<p>Presently libpkg has complete read functionality. Info and
delete tools that have most of the current package tool features
@ -1163,7 +1173,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='proj'>
<title>General Purpose DMA Framework</title>
<title>General-Purpose DMA Framework</title>
<contact>
<person>
@ -1180,7 +1190,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
description on &os; wiki</url>
<url href="http://p4web.FreeBSD.org/@md=d&amp;cd=//&amp;c=eCv@//depot/projects/soc2010/jceel_dma/?ac=83">
Project branch on P4</url>
Project branch on Perforce</url>
</links>
<body>
@ -1190,7 +1200,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
programming interface to use direct memory transfers in kernel and
userspace applications.</p>
<p>This project is a part of Google Summer of Code 2010 and is a
<p>This project is a part of Google Summer of Code 2010 and it is a
work in progress. Current status can be observed on the wiki
page.</p>
</body>
@ -1198,12 +1208,12 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<help>
<task>Add support for more DMA engines.</task>
<task>Complete, clean up and merge with HEAD.</task>
<task>Complete, clean up, and merge with HEAD.</task>
</help>
</project>
<project cat='soc'>
<title>Making ports work with clang</title>
<title>Making Ports Work with Clang</title>
<contact>
<person>
@ -1228,22 +1238,22 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>First part of the project is mostly complete. It added support
<p>First part of the project is mostly complete. I added support
for new PORTS_CC variable which should be used in make.conf instead
of CC to change ports compiler. This allows user to change ports
compiler easily, while still respecting USE_GCC.</p>
<p>Some patches were written to get ports to work with clang, and a
lot of old patches written prior to the GSoC project were updated.
There are still a lot of broken ports and some that cannot be built
because of clang/llvm bugs, but at this point, clang can build most
ports.</p>
<p>Some patches were written to get ports to work with Clang, and
a lot of old patches written prior to the Google Summer of Code
project were updated. There are still a lot of broken ports, and
some that cannot be built because of Clang/LLVM bugs, but at
this point, Clang can build most ports.</p>
</body>
<help>
<task>Fix broken ports that do not work with clang.</task>
<task>Fix broken ports that do not work with Clang.</task>
<task>Test patched ports with clang, report clang bugs.</task>
<task>Test patched ports with Clang, report Clang bugs.</task>
</help>
</project>
@ -1269,17 +1279,17 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
committed to sponsoring MeetBSD 2010 Poland and California. We
provided 12 travel grants for BSDCan.</p>
<p>The Foundation and Core Team held a summit on BSD licensed
<p>The Foundation and Core Team held a summit on BSD-licensed
toolchains at BSDCan 2010.</p>
<p>We officially kicked off five new projects that we are funding.
They are BSNMP Improvements by Shteryana Shopova, Userland Dtrace
by Rui Paulo, &os; jail based virtualization by Bjoern Zeeb, DAHDI
They are BSNMP Improvements by Shteryana Shopova, Userland DTrace
by Rui Paulo, &os; jail-based virtualization by Bjoern Zeeb, DAHDI
&os; driver port by Max Khon, and Resource Containers project by
Edward Napierala.</p>
Edward Tomasz Napiera&#322;a.</p>
<p>We continued our work on infrastructure projects to beef up
hardware for package-building, network-testing, etc. This includes
hardware for package building, network testing, etc. This includes
purchasing equipment as well as managing equipment donations.</p>
<p>We are half way through the year and we have raised around
@ -1295,7 +1305,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='proj'>
<title>GEOM-based pseudo-RAID implementation &mdash;
<title>GEOM-Based Pseudo-RAID Implementation &mdash;
geom_pseudoraid</title>
<contact>
@ -1371,18 +1381,18 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>&os;/avr32 project was started by Arnar Mar Sing and actively
<p>The &os;/avr32 project was started by Arnar Mar Sing, and actively
developed by him and Ulf Lilleengen. It successfully reached
single-user stage but since then has not progressed much. At the
moment I am trying to get it back into shape. So far some problems
with toolchain on i386 host have been fixed. buildkernel succeeds,
with toolchain on i386 host have been fixed, buildkernel succeeds,
buildworld succeeds with some exceptions. Next step would be fixing
pmap and bringing port back to single user stage.</p>
pmap and bringing port back to single-user stage.</p>
</body>
</project>
<project cat='proj'>
<title>GPIO framework</title>
<title>GPIO Framework</title>
<contact>
<person>
@ -1409,23 +1419,23 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<body>
<p>Implementation of General Purpose Input/Output interface for
&os;. Current GPIO bus implementation allows user to control pins
from userland and could be expanded to support various type of
from userland and it could be expanded to support various type of
peripheral devices. So far there are two drivers:</p>
<ul>
<li><b>gpioled</b> provides simple led(4) functionality</li>
<li><b>gpioled</b> provides simple led(4) functionality.</li>
<li><b>gpioiic</b> implements I2C over GPIO</li>
<li><b>gpioiic</b> implements I2C over GPIO.</li>
</ul>
<p>Framework is used in Alexandr Rybalko's port of &os; to D-Link
DIR-320 and in Luis Ottavio O Souza's work of bringing &os; to
DIR-320 and in Luis Otavio O Souza's work of bringing &os; to
RouterBoard.</p>
</body>
</project>
<project cat='proj'>
<title>Chromium web browser</title>
<title>Chromium Web Browser</title>
<contact>
<person>
@ -1445,8 +1455,8 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>Chromium is a Webkit-based web browser that is largely BSD
licensed. It works very well on &os; and supports new features like
<p>Chromium is a Webkit-based web browser that is largely
BSD-licensed. It works very well on &os; and supports new features like
HTML 5 video. I have been offering subscriptions to fund the
porting effort to &os;: we are up to 20+ paying subscribers after 3
months, I would like to get that up to 100. This effort uses a new
@ -1479,15 +1489,15 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>This project has two goals: preallocation algorithm and ext4
<p>This project has two goals: pre-allocation algorithm and ext4
read-only mode.</p>
<p>The aim of preallocation algorithm is to implement a reservation
<p>The aim of pre-allocation algorithm is to implement a reservation
window mechanism. Now this mechanism has been introduced. The
performance comparison can be found on the <a
href="http://wiki.FreeBSD.org/SOC2010ZhengLiu">wiki</a>.</p>
<p>The aim of ext4 read-only mode is to make it can read ext4 file
<p>The aim of ext4 read-only mode is to make it possible to read ext4 file
system in read-only mode when the hard disk is formatted with default
features. Currently it only supports a few features, such as extents,
huge_file. Others features will be added, such as dir_index,
@ -1527,15 +1537,15 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<task>Implement SSL in network communication.</task>
<task>Perform security improvements/bug fixing, strlxxx functions,
memcpy instead of strcpy when using non char variables.</task>
<task>Perform security improvements and bug fixing, strlxxx() functions,
memcpy() instead of strcpy() when using non-char variables.</task>
<task>Integrate with current Audit subsystem.</task>
<task>Integrate with the current Audit subsystem.</task>
</help>
</project>
<project cat='soc'>
<title>File system changes notification</title>
<title>File System Changes Notification</title>
<contact>
<person>
@ -1548,10 +1558,10 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</contact>
<body>
<p>The aim of the project is to implement an inotify compatible file system
change notification mechanism for &os; and later add inotify
support to linuxulator. fsnotify is already functional but not yet
compatible with inotify in some details.</p>
<p>The aim of the project is to implement an inotify-compatible file system
change notification mechanism for &os; and later, and add inotify
support to linuxulator. The result, fsnotify is already functional
but not yet compatible with inotify in some details.</p>
</body>
<help>
@ -1579,28 +1589,29 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</contact>
<body>
<p>As of now, &os; only offers very rudimentary resource controls -
<p>As of now, &os; only offers very rudimentary resource controls &mdash;
resource limits for many resources (e.g. SysV IPC) are missing, and
there is no way to set resource limits for Jails. As a result,
there is no way to set resource limits for jails. As a result,
users who want to run many different workloads on a single physical
machine often have to replace Jails with several &os; instances
machine often have to replace jails with several &os; instances
running in virtual machines.</p>
<p>The goal of this project is to implement resource containers
and a simple per-jail resource limits mechanism. Resource
containers are also a prerequisite for other resource management
mechanisms, such as Hierarchical Resource Limits, for
"Collective limits on set of processes (a.k.a. jobs)" GSoC 2010
project, for implementing mechanism similar to Linux cgroups,
and might be also used to e.g. provide precise resource usage
accounting for administrative or billing purposes.</p>
"Collective Limits on Set of Processes (aka. Jobs)" Google
Summer of Code 2010 project, for implementing mechanism similar
to Linux cgroups, and might be also used to e.g. provide
precise resource usage accounting for administrative or billing
purposes.</p>
<p>This project is being sponsored by The &os; Foundation.</p>
</body>
</project>
<project cat='soc'>
<title>Namecache improvements &mdash; dircache</title>
<title>Namecache Improvements &mdash; dircache</title>
<contact>
<person>
@ -1618,7 +1629,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<body>
<p>I have been reimplementing VFS namecache to make it granularly
locked and supporting reliable full path lookup without calling
locked and supporting reliable full-path lookup without calling
underlying file system routines. I have successfully implemented
directory cache that works in idealized environment with tmpfs. I am
currently working on adding support for entries without associated
@ -1650,17 +1661,17 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>The fsc daemon (fscd) runs in the background once the system has
started. Services are then added to this daemon via the fscadm
control utility and from there they will be monitored. When they
control utility, and from there they will be monitored. When they
die, depending on the reason, they will be restarted. Certain
signals may be ignored (list not decided) and fscd will remove that
service from monitoring. Every action is logged to the system
logging daemon. Additionally, the fscadm utility may be used to
inquire about what services are monitored, their pidfile location,
and current process id.</p>
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 software
instead of polling; fscd is an internal, &os;-maintained software
package accessible to all developers, where daemontools would have
to be a port and require us to maintain patches; fscd could be
easily integrated with the current rc.d infrastructure.</p>
@ -1668,15 +1679,18 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>Partially based on the ideas of daemontools and Solaris Service
Service Mangement Facility (SMF), this could be an extremely
useful tool for &os; systems.</p>
</body>
<help>
<task>Testing. I would like to hear how it works in various
<task>Testing. Get feedback on how it works in various
environments.</task>
<task>Code review.</task>
<task>Other ideas on the rc.d integration.</task
<task>Other ideas on the rc.d integration.</task>
<task>Update the manual pages.</task>
</help>
</body>
</project>
<project cat='net'>
@ -1703,24 +1717,25 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>SIFTR was recently imported into the &os; "head" svn branch
(a.k.a. 9-CURRENT) and will be back-ported to 8-STABLE in time to
be included in 8.2-RELEASE. Please try it out and let me know if
you run into any problems.</p>
<p>SIFTR was recently imported into HEAD and will be backported to
8-STABLE in time to be included in 8.2-RELEASE.</p>
<p>TCP reassembly queue autotuning will be ready for public testing
within the next week and will be committed soon after. It too will
be back-ported to 8-STABLE after an appropriate burn in period.</p>
be backported to 8-STABLE after an appropriate burn in period.</p>
</body>
<help>
<task>Try SIFTR out and let me know if you run into any
problems.</task>
<task>Solicit external testing for and commit the reassembly queue
autotuning patch.</task>
</help>
</project>
<project cat='soc'>
<title>Packet capturing stack &mdash; ringmap</title>
<title>Packet-Capturing Stack &mdash; ringmap</title>
<contact>
<person>
@ -1741,20 +1756,21 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>Ringmap is a complete &os; packet capturing stack specialized
for very high-speed networks. Similar to the "zero-copy BPF"
implementation, the idea of ringmap is to eliminate packet copy
operations by using shared memory buffers. However, unlike the
"zero-copy BPF" model, ringmap eliminates ALL packet copies during
capturing: the network adapter's DMA buffer is mapped directly into
user-space. Ringmap also adapts libpcap accordingly to provide
user-space applications with access to the captured packets without
any additional overhead.</p>
<p>The ringmap stack is a complete &os; packet-capturing
mplementation specialized for very high-speed networks. Similar
to the "zero-copy BPF" implementation, the idea of ringmap is to
eliminate packet copy operations by using shared memory buffers.
However, unlike the "zero-copy BPF" model, ringmap eliminates
ALL packet copies during capturing: the network adapter's DMA
buffer is mapped directly into user-space. The ringmap stack
also adapts libpcap accordingly to provide userspace
applications with access to the captured packets without any
additional overhead.</p>
<p>In the context of GSOC-2010:</p>
<p>In the context of Google Summer of Code 2010:</p>
<ul>
<li>The ringmap software was ported to -CURRENT.</li>
<li>The ringmap software was ported to 9-CURRENT.</li>
<li>Ringmap was redesigned to make it easier to port to other
adapters and to integrate it with other network drivers.</li>
@ -1767,7 +1783,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<task>Porting ringmap to 10GbE (integrating with ixgbe
driver).</task>
<task>Porting the entire ringmap code from -CURRENT to
<task>Porting the entire ringmap code from 9-CURRENT to
-STABLE.</task>
<task>Evaluation tests.</task>
@ -1797,11 +1813,11 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
B1600 platform).</p>
<p>Support for Fujitsu (Siemens) PRIMEPOWER 250 based on SPARC64
V CPUs has been added. PRIMEPOWER 450, 650 and 850 likely also
V CPUs has been added. PRIMEPOWER 450, 650, and 850 likely also
work but have not been tested. This also means that the building
blocks for support of machines based on SPARC64 VI and VII CPUs
like the Fujitsu/Sun SPARC Enterprise Mx000 series are now in
place. Access to such machines would be appreciated.</p>
place, but they need testing as well.</p>
<p>The problems with Schizo version 7 bridges (actually the
firmware of these machines) triggering panics during boot finally
@ -1815,13 +1831,17 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</body>
<help>
<task>Someone adding support for 64-bit SPARC V9 to Clang/LLVM and
getting it on par with GCC would be appreciated.</task>
<task>Access to machines based on SPARC64 VI and VII CPUs, like
the Fujitsu/Sun SPARC Enterprise Mx000 series would be
appreciated.</task>
<task>Someone adding support for 64-bit SPARC V9 to Clang/LLVM,
and getting it on par with GCC would be appreciated.</task>
</help>
</project>
<project cat='proj'>
<title>New system installer &mdash; pc-sysinstall</title>
<title>New System Installer &mdash; pc-sysinstall</title>
<contact>
<person>
@ -1858,13 +1878,13 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<ul>
<li>ZFS (Including support for raidz/mirror/multiple device pool
setups)</li>
setups).</li>
<li>Disk encryption via GELI</li>
<li>Disk encryption via GELI(8).</li>
<li>Auto labeling of file-systems with glabel</li>
<li>Auto labeling of file systems with glabel(8).</li>
<li>Big disk support using GPT/EFI</li>
<li>Big disk support using GPT/EFI.</li>
<li>Full Installation Logging, which is saved to disk for
post-install inspection.</li>
@ -1872,8 +1892,8 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>In addition to the features above, pc-sysinstall is unique, in
that every install ends up being a scripted install. Front-ends, be
it GUI or text based, simply generate the appropriate system
configuration file, and pc-sysinstall does the grunt-work of the
it GUI- or text-based, simply generate the appropriate system
configuration file, and pc-sysinstall does the grunt work of the
actual installation. This is important for a couple of reasons.
First, it makes the task of front-end development much easier by
not needing to worry about a backend-driven program flow. Second it
@ -1882,7 +1902,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
automated installs.</p>
<p>While pc-sysinstall is still relatively new, it is already in
use as the default backend for PC-BSD 8.0 &amp; 8.1, and has been
use as the default backend for PC-BSD&nbsp;8.0 and 8.1, and has been
getting a very good reception and any bugs found are fixed quickly.
A text-based front-end is already in the works which will allow
installation media to be created without X11 support.</p>
@ -1890,7 +1910,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</project>
<project cat='proj'>
<title>DAHDI/&os; project</title>
<title>DAHDI/&os; Project</title>
<contact>
<person>
@ -1914,28 +1934,29 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
&os; as a base system for software PBX solutions.</p>
<p>DAHDI (Digium/Asterisk Hardware Device Interface) is an
open-source device driver framework and a set of HW drivers for
E1/T1, ISDN digital and FXO/FXS analog cards
(http://www.asterisk.org/dahdi/). Asterisk is one of the most
open-source device driver framework and a set of hardware drivers for
E1/T1, ISDN digital, and FXO/FXS analog cards
[<a href="http://www.asterisk.org/dahdi/">1</a>]. Asterisk is one of the most
popular open-source software PBX solutions
(http://www.asterisk.org/).</p>
[<a href="http://www.asterisk.org/">2</a>].</p>
<p>The project includes porting DAHDI framework and HW drivers for
E1/T1, FXO/FXS analog and ISDN digital cards to &os;. This also
<p>The project includes porting DAHDI framework and hardware drivers for
E1/T1, FXO/FXS analog, and ISDN digital cards to &os;. This also
includes TDMoE support, software and HW echo cancellation (Octasic,
VPMADT032) and HW transcoding support (TC400B). The work is ongoing
VPMADT032), and hardware transcoding support (TC400B). The work is ongoing
in the official DAHDI SVN repository with the close collaboration
with DAHDI folks at Digium.</p>
<p>The project is nearing completion. The DAHDI framework and HW
drivers telephony cards have been ported and tested. There are a
number of success stories from early adopters who have been using
E1/T1 and FXO/FXS cards on &os; for several months.</p>
<p>The project is nearing completion. The DAHDI framework and
hardware drivers telephony cards have been ported and tested.
There are a number of success stories from early adopters who
have been using E1/T1 and FXO/FXS cards on &os; for several
months.</p>
</body>
</project>
<project cat='proj'>
<title>V4L support in Linux emulator</title>
<title>V4L Support in Linux Emulator</title>
<contact>
<person>
@ -1956,15 +1977,15 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
made to work with the cuse4bsd webcam driver, which supports a
great many camera chipsets.</p>
<p>The code is still only in -current. We were going to MFC it to
<p>The code is still only in 9-CURRENT. We were going to MFC it to
8.x but ran into the code freeze for 8.1, so missed that. However,
the code does work on 8-stable. We will try to get it MFC'd for
the code does work on 8-STABLE. We will try to get it MFC'd for
8.2.</p>
</body>
</project>
<project cat='proj'>
<title>Clang replacing GCC in the base system</title>
<title>Clang Replacing GCC in the Base System</title>
<contact>
<person>
@ -2005,30 +2026,30 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>In the past quarter we imported clang into &os; and it is being
<p>In the past quarter we imported Clang into &os; and it is being
built by default on i386/amd64/powerpc. We have not yet commited
the necessary changes to let world compile with clang.</p>
the necessary changes to let world compile with Clang.</p>
<p>Some bugs/warnings were fixed in HEAD as a result of the clang
import and people are exploring more and more areas (dtrace, etc.).
There are some bug fixes in clang/LLVM as well that stem from the
import (unknown pragmas, warnings, etc.).</p>
<p>Some bugs and warnings were fixed in HEAD as a result of the Clang
import and people are exploring more and more areas (DTrace, etc).
There are some bug fixes in Clang/LLVM as well that stem from the
import (unknown pragmas warnings, etc).</p>
<p>Roman Divacky and Matthew Fleming are working on ELF writer in
LLVM. This is meant as a replacement for assembler (currently we
use an outdated GNU as). This work is progressing nicely, currently it
is able to produce working variants of hello world in C and C++ and
use an outdated GNU as(1)). This work is progressing nice, currently it
is able to produce working variants of hello world in C and C++, and
some other small programs from "configure run".</p>
</body>
<help>
<task>Import of newer LLVM/clang into HEAD.</task>
<task>Import of newer Clang/LLVM into HEAD.</task>
<task>Help with ARM/Mips/Sparc64.</task>
<task>Help with ARM/MIPS/SPARC64.</task>
<task>Start pushing src patches into HEAD.</task>
<task>More testing of clang on 3rd party apps (ports).</task>
<task>More testing of Clang on third-party applications (ports).</task>
<task>More work on the ELF writer.</task>
</help>
@ -2097,7 +2118,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<body>
<p>After a long hiatus, we aim to hold a bugathon on the weekend of
the 6th-9th August. Everybody is welcome to help resolve or
the 6th&nbsp;-&nbsp;9th August. Everybody is welcome to help resolve or
progress PRs from the database. We appreciate the help of
committers and non-committers alike, please join us on IRC in
#freebsd-bugbusters on EFnet if you are free at any time over
@ -2107,7 +2128,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>Mark Linimon and Gavin Atkinson held a session on the State of
Bugbusting at BSDCan, which was well attended and led to some
interesting discussions. Time was also found to sit down with
several committers to discuss long standing PRs.</p>
several committers to discuss long-standing PRs.</p>
<p>The bugbusting team continue work on trying to make the GNATS PR
database more accessible and easier for committers to find and
@ -2119,17 +2140,17 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
Reports are generated from these nightly, grouping related PRs in
one place, sorted by tag or man page. Mark Linimon continues work
on producing a new report, Summary Chart of PRs with Tags, which
sorts tagged PRs into logical groups such as filesystem, network
sorts tagged PRs into logical groups such as file system, network
drivers, libraries, and so forth. The slice labels are clickable
and may further subdivide the groups. The chart is updated once
a day. You can consider it as a prototype for browsing
"sub-categories" of kernel PRs.</p>
"subcategories" of kernel PRs.</p>
<p>The "recommended list" has been split up into "non-trivial PRs
which need committer evaluation" and the "easy list" of trivial
PRs, to try to focus some attention on the latter. Various new
reports exist, including "PRs containing code for new device
drivers", "PRs which are from &os; vendors or OEMs" and
drivers", "PRs which are from &os; vendors or OEMs", and
"PRs referencing other BSDs".</p>
<p>It is now possible for interested parties to be emailed a weekly,
@ -2219,12 +2240,12 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</links>
<body>
<p>meetBSD 2010 took place on July 2-3 in Krakow, Poland at the
<p>meetBSD 2010 took place on July 2&nbsp;-&nbsp;3 in Krakow, Poland at the
Faculty of Mathematics and Computer Science building of the
Jagiellonian University.</p>
<p>The gathering was a much successful event which brought together
developers, contributors and users of the BSD systems from around the
developers, contributors, and users of the BSD systems from around the
world. We had many interesting presentations, of various character and
appeal for the diversified audience.</p>