From ccd8108540d5a2eebd6375b1ed686a588f9de0f1 Mon Sep 17 00:00:00 2001 From: Gabor Pali Date: Tue, 20 Jul 2010 00:08:47 +0000 Subject: [PATCH] - A few minor nits to the upcoming status report --- en/news/status/report-2010-04-2010-06.xml | 413 ++++++++++++---------- 1 file changed, 217 insertions(+), 196 deletions(-) diff --git a/en/news/status/report-2010-04-2010-06.xml b/en/news/status/report-2010-04-2010-06.xml index 3b6a02357d..1c01162c63 100644 --- a/en/news/status/report-2010-04-2010-06.xml +++ b/en/news/status/report-2010-04-2010-06.xml @@ -1,7 +1,7 @@ - + April-June @@ -11,13 +11,13 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
Introduction -

This report covers &os; related projects between April and June +

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 + contains 44 entries. During this period, a lot of work has gone into the development of new minor version of &os;, 8.1-RELEASE, which should be released within days.

-

Thanks to all the reporters for the excellent work! We hope you +

Thanks to all the reporters for the excellent work! We hope you enjoy reading.

Please note that the deadline for submissions covering the @@ -75,7 +75,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> - &os; German Documentation Project + The &os; German Documentation Project @@ -99,7 +99,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> Website of the &os; German Documentation Project - Mailinglists + Mailing lists for the coordination of our work and the place where you can report bugs back to us @@ -136,7 +136,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> - Binary package patch infrastructure — pkg_patch + Binary Package Patch Infrastructure — pkg_patch @@ -168,8 +168,8 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> Get some testing for it. - Convince portmgr it is actually a Good Thing to have even as - an experimental feature. + Convince the Port Management Team it is actually a Good + Thing to have even as an experimental feature. 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"> - BSDL iconv in base system + BSD-Licensed iconv in Base System @@ -245,7 +245,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> - BSDL grep in base system + BSD-Licensed grep in Base System @@ -264,7 +264,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">

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.

@@ -275,7 +275,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> - Collective resource limits (aka jobs) + Collective Resource Limits (aka. Jobs) @@ -369,7 +369,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> - Kernel event timers infrastructure + Kernel Event Timers Infrastructure @@ -383,11 +383,11 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">

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.

+ at the same time limited and hard-coded.

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">

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 — it will be + replaced. If there is no second timer — it will be emulated. The administrator may affect that choice using loader tunables during - boot and sysctls in run-time (kern.eventtimer, ...).

+ boot and sysctl variables in run-time (kern.eventtimer.*, and so on).

Most of the code was recently committed to HEAD. Now it is used by i386 and amd64 architectures.

@@ -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.

@@ -525,8 +525,8 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">

Our efforts on porting the generalized, general-purpose purely functional programming language, Haskell has rallied, since - two new committers, Giuseppe Pilichi and Ashish - Shukla joined recently, forming the &os; Haskell Team. + 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

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 @@ -603,7 +603,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> extracting information via kvm(3). This library implements abstractions over the gathered data. -

  • Adapt sources of the existing applications, i.e. netstat(1) +
  • Adapt sources of the existing applications, i.e. netstat(1) and bsnmpd(1) to use the abstractions offered by the library, resulting in a cleaner and simpler code.
    • @@ -662,19 +662,19 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> -

    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 +

    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.

    - Fix bugs, unresolved issues and #TODO's in perforce. + Fix bugs, unresolved issues and to-dos in Perforce.     - Flattened Device Tree for embedded &os; + Flattened Device Tree for Embedded &os; @@ -730,7 +730,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
  • MPC8572DS
    • -
  • The FDT infrastructure (bus drivers, helper libraries and +
  • 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"> - Improve howto and guidelines for new adopters (how to convert + Improve how-to and guidelines for new adopters (how to convert to FDT and so on). 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">

    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 mailing list or on the - Jail based virtualization + Jail-Based Virtualization @@ -865,7 +865,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">

    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.

    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">

    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 7.5, KDE 4, GNOME 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.

    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">

    Since the last report, we added four new committers, and had two old committers rejoin us.

    -

    The Ports Management team is very grateful to the &os; +

    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.

    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.

    + 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:

    -

    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.

    +
      +
    • ale: Update of math/gmp.
      • +
    • delphij: Changes to Mk/bsd.ldap.mk.
      • +
    • gahr: Inclusion of USE_GL=glew.
      • +
    • pgollucci: Changes to Mk/bsd.*apache.mk plus updates to devel/apr + and www/apache*.
      • +
    • Testing of x11/xorg, x11/gnome2, x11/kde4, and + lang/mono
      • +
    • A test run make fetch run.
      • +
    • A test run for devel/gettext.
      • +
    • mm: Inclusion of USE_XZ.
      • +
    • ale: Request to switch default mysql from 5.0-EOL to + 5.1-GA.
      • +
    + +

    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.

    Looking for help fixing     ports - broken on CURRENT. + broken on 9-CURRENT. Looking for help with Tier-2 architectures. Most ports PRs are assigned, we now need to focus on testing, - committing and closing. + committing, and closing. @@ -1017,7 +1027,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> -

    On July 13, &os;/powerpc64 was integrated into -CURRENT. This +

    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.

    + be possible to boot the console multi-user.

    - OpenAFS port + OpenAFS Port @@ -1097,23 +1107,23 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">

    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.

    + unsuccessful, though, as mmap() is not always reliable.

    -

    There are several known outstanding issues that are being worked - on, but detailed bug reports are welcome at - port-freebsd@openafs.org.

    +

    There are several known outstanding issues that are being + worked on, but detailed bug reports are welcome at port-freebsd@openafs.org.

    Fix the {get,put}pages vnode operations for more reliable - mmap operation. + mmap() operation. Update VFS locking to allow the use of disk-based client caches as well as memory-based caches. @@ -1127,7 +1137,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">     - Package management library - libpkg + Package Management Library — libpkg @@ -1147,8 +1157,8 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> -

    Libpkg will allow for fairly fine grained control over package - management.

    +

    The libpkg library will allow for fairly fine grained control + over package management.

    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"> - General Purpose DMA Framework + General-Purpose DMA Framework @@ -1180,7 +1190,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> description on &os; wiki - Project branch on P4 + Project branch on Perforce @@ -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.

    -

    This project is a part of Google Summer of Code 2010 and is a +

    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.

    @@ -1198,12 +1208,12 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> Add support for more DMA engines. - Complete, clean up and merge with HEAD. + Complete, clean up, and merge with HEAD.     - Making ports work with clang + Making Ports Work with Clang @@ -1228,22 +1238,22 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> -

    First part of the project is mostly complete. It added support +

    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.

    -

    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.

    +

    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.

    - Fix broken ports that do not work with clang. + Fix broken ports that do not work with Clang. - Test patched ports with clang, report clang bugs. + Test patched ports with Clang, report Clang bugs.     @@ -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.

    -

    The Foundation and Core Team held a summit on BSD licensed +

    The Foundation and Core Team held a summit on BSD-licensed toolchains at BSDCan 2010.

    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.

    + Edward Tomasz Napierała.

    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.

    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"> - GEOM-based pseudo-RAID implementation — + <title>GEOM-Based Pseudo-RAID Implementation — geom_pseudoraid @@ -1371,18 +1381,18 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> -

    &os;/avr32 project was started by Arnar Mar Sing and actively +

    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.

    + pmap and bringing port back to single-user stage.

    - GPIO framework + GPIO Framework @@ -1409,23 +1419,23 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">

    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:

      -
    • gpioled provides simple led(4) functionality
      • +
    • gpioled provides simple led(4) functionality.
      • -
    • gpioiic implements I2C over GPIO
      • +
    • gpioiic implements I2C over GPIO.

    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.

     - Chromium web browser + Chromium Web Browser @@ -1445,8 +1455,8 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> -

    Chromium is a Webkit-based web browser that is largely BSD - licensed. It works very well on &os; and supports new features like +

    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"> -

    This project has two goals: preallocation algorithm and ext4 +

    This project has two goals: pre-allocation algorithm and ext4 read-only mode.

    -

    The aim of preallocation algorithm is to implement a reservation +

    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 wiki.

    -

    The aim of ext4 read-only mode is to make it can read ext4 file +

    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"> Implement SSL in network communication. - Perform security improvements/bug fixing, strlxxx functions, - memcpy instead of strcpy when using non char variables. + Perform security improvements and bug fixing, strlxxx() functions, + memcpy() instead of strcpy() when using non-char variables. - Integrate with current Audit subsystem. + Integrate with the current Audit subsystem. - File system changes notification + File System Changes Notification @@ -1548,17 +1558,17 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> -

    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.

    +

    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.

    Add access permissions checks. Port inotify test cases. - + Fix compatibility issues. Add linuxulator support. @@ -1579,28 +1589,29 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">     -

    As of now, &os; only offers very rudimentary resource controls - +

    As of now, &os; only offers very rudimentary resource controls — 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.

    - +

    The goal of this project is to implement resource containers - and a simple per-jail resource limits mechanism. Resource + 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.

    - + "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.

    +

    This project is being sponsored by The &os; Foundation.

     - Namecache improvements — dircache + Namecache Improvements — dircache @@ -1618,7 +1629,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">

    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">

    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.

    + and current process ID.

    -

    FSC provides several advantages over the third party +

    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.

    @@ -1668,15 +1679,18 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">

    Partially based on the ideas of daemontools and Solaris Service Service Mangement Facility (SMF), this could be an extremely useful tool for &os; systems.

    - - - Testing. I would like to hear how it works in various - environments. - Code review. - Other ideas on the rc.d integration.Update the manual pages. - + + + Testing. Get feedback on how it works in various + environments. + + Code review. + + Other ideas on the rc.d integration. + + Update the manual pages. +     @@ -1703,24 +1717,25 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> -

    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.

    +

    SIFTR was recently imported into HEAD and will be backported to + 8-STABLE in time to be included in 8.2-RELEASE.

    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.

    + be backported to 8-STABLE after an appropriate burn in period.

    + Try SIFTR out and let me know if you run into any + problems. + Solicit external testing for and commit the reassembly queue autotuning patch.     - Packet capturing stack — ringmap + Packet-Capturing Stack — ringmap @@ -1741,20 +1756,21 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> -

    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.

    +

    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.

    -

    In the context of GSOC-2010:

    +

    In the context of Google Summer of Code 2010:

      -
    • The ringmap software was ported to -CURRENT.
      • +
    • The ringmap software was ported to 9-CURRENT.
    • Ringmap was redesigned to make it easier to port to other adapters and to integrate it with other network drivers.
      • @@ -1767,7 +1783,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> Porting ringmap to 10GbE (integrating with ixgbe driver). - Porting the entire ringmap code from -CURRENT to + Porting the entire ringmap code from 9-CURRENT to -STABLE. Evaluation tests. @@ -1797,11 +1813,11 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> B1600 platform).

      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.

      + place, but they need testing as well.

      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"> - Someone adding support for 64-bit SPARC V9 to Clang/LLVM and - getting it on par with GCC would be appreciated. + Access to machines based on SPARC64 VI and VII CPUs, like + the Fujitsu/Sun SPARC Enterprise Mx000 series would be + appreciated. + + Someone adding support for 64-bit SPARC V9 to Clang/LLVM, + and getting it on par with GCC would be appreciated. - New system installer — pc-sysinstall + New System Installer — pc-sysinstall @@ -1858,13 +1878,13 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">

      • ZFS (Including support for raidz/mirror/multiple device pool - setups)
        • + setups). -
      • Disk encryption via GELI
        • +
      • Disk encryption via GELI(8).
        • -
      • Auto labeling of file-systems with glabel
        • +
      • Auto labeling of file systems with glabel(8).
        • -
      • Big disk support using GPT/EFI
        • +
      • Big disk support using GPT/EFI.
      • Full Installation Logging, which is saved to disk for post-install inspection.
        • @@ -1872,8 +1892,8 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">

        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.

        While pc-sysinstall is still relatively new, it is already in - use as the default backend for PC-BSD 8.0 & 8.1, and has been + use as the default backend for PC-BSD 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.

        @@ -1890,7 +1910,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> - DAHDI/&os; project + DAHDI/&os; Project @@ -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.

        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 + [1]. Asterisk is one of the most popular open-source software PBX solutions - (http://www.asterisk.org/).

        + [2].

        -

        The project includes porting DAHDI framework and HW drivers for - E1/T1, FXO/FXS analog and ISDN digital cards to &os;. This also +

        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.

        -

        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.

        +

        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.

         - V4L support in Linux emulator + V4L Support in Linux Emulator @@ -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.

        -

        The code is still only in -current. We were going to MFC it to +

        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.

         - Clang replacing GCC in the base system + Clang Replacing GCC in the Base System @@ -2005,30 +2026,30 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> -

        In the past quarter we imported clang into &os; and it is being +

        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.

        + the necessary changes to let world compile with Clang.

        -

        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.).

        +

        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).

        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".

        - Import of newer LLVM/clang into HEAD. + Import of newer Clang/LLVM into HEAD. - Help with ARM/Mips/Sparc64. + Help with ARM/MIPS/SPARC64. Start pushing src patches into HEAD. - More testing of clang on 3rd party apps (ports). + More testing of Clang on third-party applications (ports). More work on the ELF writer. @@ -2097,7 +2118,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">

        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 - 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 @@ -2105,9 +2126,9 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> information.

        Mark Linimon and Gavin Atkinson held a session on the State of - Bugbusting at BSDCan, which was well attended and led to some + 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.

        + several committers to discuss long-standing PRs.

        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.

        + "subcategories" of kernel PRs.

        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".

        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"> -

        meetBSD 2010 took place on July 2-3 in Krakow, Poland at the +

        meetBSD 2010 took place on July 2 - 3 in Krakow, Poland at the Faculty of Mathematics and Computer Science building of the Jagiellonian University.

        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.