- add a new entry covering MeetBSD 2010 in Poland [1]

- various language and grammar fixes [2]
- add Misc category and move there BSDCan together with MeetBSD entries
- some style fixes

Submitted by:	rafal@ [1]
Submitted by:	linimon@ [2]
This commit is contained in:
Daniel Gerzo 2010-07-19 18:33:57 +00:00
parent d1eb953631
commit eaeaf19ca0
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=36057

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.2 2010/07/17 16:50:30 danger Exp $ -->
<!-- $FreeBSD: www/en/news/status/report-2010-04-2010-06.xml,v 1.3 2010/07/17 16:52:27 danger Exp $ -->
<report>
<date>
<month>April-June</month>
@ -12,11 +12,10 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<title>Introduction</title>
<p>This report covers &os; related projects between April and June
2010. It is the second of the four reports planned for 2010,
containing 42 entries. The progress of the &os; Project is keeping
up with the latest trends. During this period, a lot of work has
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,
which should be released real soon now.</p>
which should be released within days.</p>
<p>Thanks to all the reporters for the excellent work! We hope you
enjoy reading.</p>
@ -70,7 +69,12 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<description>Ports</description>
</category>
<project cat='doc'>
<category>
<name>misc</name>
<description>Miscellaneous</description>
</category>
<project cat='docs'>
<title>&os; German Documentation Project</title>
<contact>
@ -260,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 number of failures that seems 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>
@ -321,7 +325,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</help>
</project>
<project cat='doc'>
<project cat='docs'>
<title>The &os; Spanish Documentation Project</title>
<contact>
@ -350,7 +354,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<body>
<p>We need manpower. Existing documentation set has not been
updated for quite some time because of lack of volunteers. Current
members are busy with another projects and real life at the moment
members are busy with other projects and real life at the moment
and we have not received anything from outside contributors. It is
a shame because there are lots of users in Spain and Latin-America,
as well. Besides, the world's first Free Software Street has been
@ -382,8 +386,8 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
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 same
time limited and hardcoded.</p>
kernel. That code has a long history, that made it tangled and
at the same time limited and hardcoded.</p>
<p>New kernel event timers infrastructure was started to allow
different event timer hardware to be operated in uniform way and to
@ -395,16 +399,16 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<p>The new driver API provides unified support for both per-CPU
(independent for every CPU core) and global timers in periodic and
one-shot modes. Management code at this moment uses only periodic
mode, while one-shot mode use planned by later tickless kernel
mode, while one-shot mode use is planned by later tickless kernel
work.</p>
<p>Different kinds of timers have different capabilities and could
be present in hardware in different combinations. In every
situation infrastructure automatically chooses two best event
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.
Administrator may affect that choice using loader tunables during
The administrator may affect that choice using loader tunables during
boot and sysctls in run-time (kern.eventtimer. ...).</p>
<p>Most of the code was recently committed to HEAD. Now it is used
@ -459,7 +463,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<body>
<p>Thanks to Katalin Konkoly, the first few chapters of the &os;
Handbook translation have been reviewed, therefore many typos,
Handbook translation have been reviewed, therefore many typos and
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
@ -659,8 +663,8 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<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. Ongoing work
is undergoing on porting the recent ZFS version 26 with
will be MFCed to 8-STABLE around September 13th, 2010. Wwork
is ongoing on porting the recent ZFS version 26 with
deduplication functionality.</p>
</body>
@ -692,7 +696,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
the Flattened Device Tree (FDT) technology, a mechanism for
describing computer hardware resources, which cannot be probed or
self enumerated, in a uniform and portable way. The primary
consumer of this technology are embedded &os; platforms (ARM, MIPS,
consumers of this technology are embedded &os; platforms (ARM, MIPS,
PowerPC), where a lot of designs are based on similar chips, but
have different assignment of pins, memory layout, addresses ranges,
interrupts routing and other resources.</p>
@ -862,9 +866,9 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
and to stable/8 and will be included in the upcoming 8.1
release.</p>
<p>A first major task was to generalize the virtualization
<p>The first major task was to generalize the virtualization
framework, so that virtualization of further subsystems would be
easier and could be achieved with lesles duplication.</p>
easier and could be achieved with less duplication.</p>
<p>In addition some documentation on the virtual network stack
programming was written to help developers virtualizing their code.
@ -935,7 +939,7 @@ 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 os Xorg 7.5, KDE4, Gnome2, plus preparation of ports
for inclusion of Xorg 7.5, KDE4, Gnome2, 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
for the recent src/ freeze.</p>
@ -944,7 +948,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
currently floats at about 1200 entries.</p>
<p>Since the last report, we added four new committers, and had two
old committer rejoin us.</p>
old committers rejoin us.</p>
<p>The Ports Management team is very grateful to the &os;
Foundation for sponsoring two new head nodes for the ports building
@ -959,8 +963,8 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
infrastructure improvements, the cluster scheduling code, and &os;
itself. Over the last few weeks, Mark Linimon has been working hard
to get the first of the two new nodes online and has already
produced its first package. This has involved a substantial rework
of our custom codebase.</p>
completed its first package build. This has involved a substantial
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
@ -1059,7 +1063,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</body>
</project>
<project cat='vendor'>
<project cat='proj'>
<title>OpenAFS port</title>
<contact>
@ -1227,8 +1231,8 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
of CC to change ports compiler. This allows user to change ports
compiler easily, while still respecting USE_GCC.</p>
<p>Sime patches were written to get ports to work with clang, and a
lot of old patches written prior to GSoC project were updated.
<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>
@ -1375,7 +1379,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
moment I am trying to get it back into shape. So far some problems
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 singe user stage.</p>
pmap and bringing port back to single user stage.</p>
</body>
</project>
@ -1487,7 +1491,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
page.</p>
<p>The aim of ext4 read-only mode is to make it can read ext4 file
system in read-only mode when hard disk is formatted with default
system in read-only mode when the hard disk is formatted with default
features. Now it can support some features, such as extents,
huge_file. Others features will be supported, such as dir_index,
uninit_bg, dir_nlink, flex_bg and extra_isize. My work resides in
@ -1527,7 +1531,7 @@ 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 strcpy when using non char variables.</task>
memcpy instead of strcpy when using non char variables.</task>
<task>Integrate with current Audit subsystem.</task>
</help>
@ -1640,7 +1644,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<body>
<p>&os; Services Control is a mix of binaries which integrate into
the rc.d system and provide for service (daemon) monitoring. It
knows about signals, pidfiles, and uses very little resources.</p>
knows about signals, pidfiles, and uses very few resources.</p>
<p>The fsc daemon (fscd) runs in the background once the system has
started. Services are then added to this daemon via the fscadm
@ -1780,7 +1784,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</contact>
<body>
<p>Since the last status report some issue with cas(4) have been
<p>Since the last status report some issues with cas(4) have been
fixed, allowing it to work with Sun GigaSwift Ethernet 1.0 MMF
cards (Cassini Kuheen, part no. 501-5524) as well as the on-board
interfaces of Sun Fire B100s server blades (for the Sun Fire
@ -1916,9 +1920,9 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
with DAHDI folks at Digium.</p>
<p>The project is nearing its completion: DAHDI framework and HW
drivers telephony cards has been ported and tested. There is a
number of success stories from early adopters who use E1/T1 and
FXO/FXS cards on &os; for several months.</p>
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>
@ -2146,7 +2150,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</help>
</project>
<project cat='proj'>
<project cat='misc'>
<title>BSDCan</title>
<contact>
@ -2160,7 +2164,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
</contact>
<links>
<url href="http://www.bsdcan.org/2010/">BSDCan 2010</url>
<url href="http://www.BSDCan.org/2010/">BSDCan 2010</url>
</links>
<body>
@ -2173,7 +2177,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
projects.</p>
<p>The talks during the Dev Summit are beginning to attract a wider
audience, and we've been talking about opening this up to the
audience, and we have been talking about opening this up to the
general audience by creating a fourth track at BSDCan 2011.</p>
<p>As impossible as it sounds, each year has seen an increase in
@ -2185,4 +2189,48 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
website updates, booking travel, etc.</task>
</help>
</project>
<project cat='misc'>
<title>meetBSD 2010 -- The BSD Conference</title>
<contact>
<person>
<name>
<given>meetBSD</given>
<common>Information</common>
</name>
<email>info@meetbsd.org</email>
</person>
</contact>
<links>
<url href="http://www.meetbsd.org" />
<url href="http://picasaweb.google.com/meetbsd/MeetBSD2010Day1#" />
<url href="http://picasaweb.google.com/meetbsd/MeetBSD2010Day2#" />
<url href="http://picasaweb.google.com/meetbsd/MeetBSD2010SocialEvent#" />
</links>
<body>
<p>meetBSD 2010 took place on July 2-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
world. We had many interesting presentations, of various character and
appeal for the diversified audience.</p>
<p>Attendees had a chance for taking the BSD Certification exam during
the conference, as well as the advantage of face to face side
conversations and discussions, which continued long during the social
event on Friday night!</p>
<p>The conference presentation slides are already available for
download. Video recordings edition is being finalized, and their
publication is expected shortly.</p>
<p>We hope you enjoyed the event and had great time in Krakow. See you
again soon!</p>
</body>
</project>
</report>