- grammar and language fixes [1]
- add re@ status report [2] Submitted by: bjk@, wblock@, manolis@ [1] Submitted by: kensmith@ [2]
This commit is contained in:
parent
a7b3506354
commit
4b7fc1cc14
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=37901
1 changed files with 97 additions and 68 deletions
|
@ -2,7 +2,7 @@
|
|||
<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for
|
||||
Status Report//EN"
|
||||
"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
|
||||
<!-- $FreeBSD$ -->
|
||||
<!-- $FreeBSD: www/en/news/status/report-2011-07-2011-09.xml,v 1.1 2011/11/05 14:59:08 danger Exp $ -->
|
||||
<report>
|
||||
<date>
|
||||
<month>July-September</month>
|
||||
|
@ -15,11 +15,12 @@ Status Report//EN"
|
|||
|
||||
<p>This report covers &os;-related projects between July and
|
||||
September 2011. It is the third of the four reports planned for 2011.
|
||||
This quarter was mainly devoted to polishing the stuff for the next
|
||||
major version of &os;, 9.0, which is to be released in September.</p>
|
||||
This quarter was mainly devoted to polishing the bits for the next
|
||||
major version of &os;, 9.0, which is to be released by then end
|
||||
of this year.</p>
|
||||
|
||||
<p>Thanks to all the reporters for the excellent work! This report
|
||||
contains 27 entries and we hope you enjoy reading it.</p>
|
||||
contains 28 entries and we hope you enjoy reading it.</p>
|
||||
|
||||
<p>Please note that the deadline for submissions covering the period
|
||||
between October and December 2011 is January 15th, 2012.</p>
|
||||
|
@ -105,13 +106,13 @@ Status Report//EN"
|
|||
<p>We tried to re-activate committers who did not contribute for
|
||||
some time but most of them are currently unable to free up enough
|
||||
time. We hope to gain fresh contributor blood as we are getting
|
||||
occasional reports about bugs and grammar in the german
|
||||
occasional reports about bugs and grammar in the German
|
||||
translation.</p>
|
||||
</body>
|
||||
|
||||
<help>
|
||||
<task>Submit grammar, spelling or other errors you find in the
|
||||
german documents and the website</task>
|
||||
German documents and the website</task>
|
||||
|
||||
<task>Translate more articles and other open handbook sections
|
||||
(especially the new chapter about the new &os;
|
||||
|
@ -151,13 +152,13 @@ Status Report//EN"
|
|||
<p>The www/ja and doc/ja_JP.eucJP/books/handbook subtrees have
|
||||
constantly been updated since the last report.</p>
|
||||
|
||||
<p>www/ja: During this period, many part of outdated contents in
|
||||
<p>www/ja: During this period, many areas of outdated content in
|
||||
the www/ja subtree were updated to the latest versions in the
|
||||
English counterpart. The Japanese version of 8.2R release
|
||||
English counterparts. The Japanese version of 8.2R release
|
||||
announcement was added and the upcoming 9.0R announcement will be
|
||||
translated in a timely manner.</p>
|
||||
|
||||
<p>Handbook: Japanese "kernelconfig" section finally caught up with
|
||||
<p>Handbook: The Japanese "kernelconfig" section finally caught up with
|
||||
the original English version. The next targets are "cutting-edge"
|
||||
and new installer section.</p>
|
||||
</body>
|
||||
|
@ -200,10 +201,10 @@ Status Report//EN"
|
|||
</links>
|
||||
|
||||
<body>
|
||||
<p>The ports tree slowly moves up closer to 23,000. The PR count
|
||||
<p>The ports tree slowly moves up closer to the 23,000 mark. The PR count
|
||||
still remains at about 1000.</p>
|
||||
|
||||
<p>In Q2 we added 4 new committers, took in 6 commit bit for safe
|
||||
<p>In Q2 we added 4 new committers, but took in 6 commit bits for safe
|
||||
keeping.</p>
|
||||
|
||||
<p>The Ports Management team have been running -exp runs on an
|
||||
|
@ -215,12 +216,12 @@ Status Report//EN"
|
|||
<li>Python update</li>
|
||||
<li>Boost updates</li>
|
||||
<li>Gtk3 updates</li>
|
||||
<li>Clang testing</li>
|
||||
<li>clang testing</li>
|
||||
<li>pkgng testing</li>
|
||||
<li>testing ruby19</li>
|
||||
<li>set default fortran to lang/gcc46</li>
|
||||
<li>setting the default fortran to lang/gcc46</li>
|
||||
<li>setting apache22 as default</li>
|
||||
<li>set default LDFLAGS in CONFIGURE_ENV</li>
|
||||
<li>setting the default LDFLAGS in CONFIGURE_ENV</li>
|
||||
</ul>
|
||||
|
||||
<p>Work continues to refine the new build master pointyhat-west. An
|
||||
|
@ -248,7 +249,7 @@ Status Report//EN"
|
|||
<p>linimon is working on a set of scripts to more quickly produce
|
||||
pre-configured PXEboot images for package build nodes.</p>
|
||||
|
||||
<p>The update of FreeBSD_version in param.h to 1000000 proved very
|
||||
<p>The update of __FreeBSD_version in param.h to 1000000 proved very
|
||||
disruptive to the ports tree, triggering lots of bad assumption in
|
||||
code that interpreted it as &os; 1. A great deal of work has
|
||||
gone into identifying the instances of broken code and fixing and
|
||||
|
@ -357,15 +358,15 @@ Status Report//EN"
|
|||
|
||||
<body>
|
||||
<p>ZFSguru is a newly designed Network Attached Storage operating
|
||||
system, much like FreeNAS is. The difference is that ZFSguru
|
||||
system, much like FreeNAS. The difference is that ZFSguru
|
||||
focuses heavily on ZFS and user friendly operation, and uses a full
|
||||
&os; distribution with no elements stripped down. This allows
|
||||
for people new to &os; and UNIX in general to access the power
|
||||
people new to &os; and UNIX in general to access the power
|
||||
of ZFS, while still allowing more advanced users to tweak their NAS
|
||||
with additional functionality and use it as normal &os;
|
||||
with additional functionality and use it as a normal &os;
|
||||
distribution.</p>
|
||||
|
||||
<p>Started little over a year ago, the ZFSguru project is making
|
||||
<p>Started a little over a year ago, the ZFSguru project is making
|
||||
good progress. It should already be one of the most user friendly
|
||||
distributions focused on ZFS, and sports some very unique features.
|
||||
The advanced ZFS benchmarking and convenient Root-on-ZFS
|
||||
|
@ -417,7 +418,7 @@ Status Report//EN"
|
|||
immediately allocating and deallocating kernel virtual memory. This
|
||||
results in a gain in terms of performances (there is a relatively
|
||||
high cost in the approach adopted until now), and also in terms of
|
||||
reduction of fragmentation (VM system uses a first-fit policy of
|
||||
reduction of fragmentation (the VM system uses a first-fit policy of
|
||||
allocation so there is room for improvements).</p>
|
||||
</body>
|
||||
</project>
|
||||
|
@ -507,7 +508,7 @@ Status Report//EN"
|
|||
|
||||
<links>
|
||||
<url href="http://wiki.FreeBSD.org/ZhihaoSoC2011">&os;
|
||||
Wiki</url>
|
||||
Wiki</url>
|
||||
<url href="https://github.com/lichray/nvi2">Github page</url>
|
||||
</links>
|
||||
|
||||
|
@ -529,10 +530,10 @@ Status Report//EN"
|
|||
never change the actual encoding, and the detection failbacks to
|
||||
locale.</li>
|
||||
<li>Pavel Timofeev provided a full Russian translation of the
|
||||
catalog. Thanks him.</li>
|
||||
catalog. Thanks to him.</li>
|
||||
<li>Now nvi-iconv is able to be compiled with widechar only and
|
||||
without iconv (inspired by a user on FreeBSDChina.org). In such
|
||||
case, it only supports your locale.</li>
|
||||
without iconv (inspired by a user on FreeBSDChina.org). In
|
||||
that case, it only supports your locale.</li>
|
||||
</ul>
|
||||
</body>
|
||||
|
||||
|
@ -570,14 +571,14 @@ Status Report//EN"
|
|||
PACKETpro family of embedded processors.</p>
|
||||
|
||||
<p>The chip includes two Power Architecture PPC465 processor cores,
|
||||
which are compliant with Book-E specification of the architecture,
|
||||
which are compliant with the Book-E specification of the architecture,
|
||||
and a number of integrated peripherals.</p>
|
||||
|
||||
<p>This work is extending current Book-E support in &os; towards
|
||||
PPC4xx processors variation along with device drivers for
|
||||
PPC4xx processor variants along with device drivers for
|
||||
integrated peripherials.</p>
|
||||
|
||||
<p>Following drivers has been created since last report:</p>
|
||||
<p>The following drivers have been created since the last report:</p>
|
||||
|
||||
<ul>
|
||||
<li>Interrupt controller</li>
|
||||
|
@ -619,14 +620,14 @@ Status Report//EN"
|
|||
|
||||
<body>
|
||||
<p>Marvell Armada XP is a complete system-on-chip solution based on
|
||||
Sheeva embedded CPU. These devices integrate up to four ARMv6/v7
|
||||
the Sheeva embedded CPUs. These devices integrate up to four ARMv6/v7
|
||||
compliant Sheeva CPU cores with shared L2 cache.</p>
|
||||
|
||||
<p>This work is extending &os;/arm infrastructure towards
|
||||
support for recent ARM architecture variations along with a basic
|
||||
set of device drivers for integrated peripherials.</p>
|
||||
set of device drivers for integrated peripherals.</p>
|
||||
|
||||
<p>The following code has been implemented since last status
|
||||
<p>The following code has been implemented since the last status
|
||||
report:</p>
|
||||
|
||||
<ul>
|
||||
|
@ -672,8 +673,8 @@ Status Report//EN"
|
|||
</contact>
|
||||
|
||||
<body>
|
||||
<p>We updated existing ports to their latest versions, hunted down
|
||||
a bug in 9-CURRENT rtld which was causing GHC to crash
|
||||
<p>We updated existing ports to their latest versions and hunted down
|
||||
a bug in the 9-CURRENT rtld which was causing GHC to crash
|
||||
intermittently. We also started work on Haskell Platform 2011.3.0.0
|
||||
(development version) in a <a
|
||||
href="https://github.com/freebsd-haskell/freebsd-haskell/tree/haskell-platform-2011.3.0.0">
|
||||
|
@ -683,7 +684,7 @@ Status Report//EN"
|
|||
<help>
|
||||
<task>Test GHC to work with clang/LLVM.</task>
|
||||
|
||||
<task>Add an option to GHC port to be able to build it with already
|
||||
<task>Add an option to the GHC port to be able to build it with already
|
||||
installed GHC instead of requiring a separate GHC boostrap
|
||||
tarball.</task>
|
||||
|
||||
|
@ -695,7 +696,7 @@ Status Report//EN"
|
|||
</project>
|
||||
|
||||
<project cat='kern'>
|
||||
<title>new CARP</title>
|
||||
<title>The new CARP</title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
|
@ -714,17 +715,17 @@ Status Report//EN"
|
|||
<body>
|
||||
<p>I am now working on significant rewrite of CARP in &os;.</p>
|
||||
|
||||
<p>The reason for this work is that CARP protocol actually does
|
||||
<p>The reason for this work is that the CARP protocol actually does
|
||||
not bring a new interface, but is a property of interface address.
|
||||
Rewriting it in this way helps to remove several hacks from
|
||||
incoming packet processing, simplifies some code, makes CARP
|
||||
addresses more sane from viewpoint of routing daemons such as
|
||||
addresses more sane from the viewpoint of routing daemons such as
|
||||
quagga/zebra and closes many CARP-related PRs in GNATS. It also
|
||||
brings support for a single redundant address on the subnet, the
|
||||
thing that is called "carpdev feature" in OpenBSD, long awaited in
|
||||
&os;.</p>
|
||||
|
||||
<p>For this moment I have got a patch against head/ that compiles and
|
||||
<p>For this moment I have a patch against head/ that compiles and
|
||||
works in my test environment that I am going to deploy soon on some
|
||||
of servers under my control.</p>
|
||||
|
||||
|
@ -734,7 +735,7 @@ Status Report//EN"
|
|||
<help>
|
||||
<task>More testing requested!</task>
|
||||
|
||||
<task>Implement arpbalance & ipbalance features. This require a
|
||||
<task>Implement arpbalance and ipbalance features. This requires a
|
||||
next step of rewriting, probably borrowing some ideas from
|
||||
OpenBSD.</task>
|
||||
|
||||
|
@ -944,7 +945,7 @@ Status Report//EN"
|
|||
developers of today's open-source BSD systems to popularize their
|
||||
work and their organizations, and to meet each other in the real
|
||||
life. We wanted to motivate potential future developers
|
||||
and users, especially undergraduate university students to work
|
||||
and users, especially undergraduate university students, to work
|
||||
with BSD systems.</p>
|
||||
|
||||
<p>This year's BSD-Day was be held in Bratislava, Slovakia at
|
||||
|
@ -982,8 +983,8 @@ Status Report//EN"
|
|||
<body>
|
||||
<p>The 10th anniversary European BSD Conference was organized in
|
||||
Maarssen, The Netherlands with more than 250 registered visitors.
|
||||
There were many interesting tutorials, including introduction to
|
||||
DTrace or working with Netgraph. It featured 26 high-quality talks
|
||||
There were many interesting tutorials, including introductions to
|
||||
DTrace and working with Netgraph. It featured 26 high-quality talks
|
||||
and 2 keynote speakers on various topics related to &os;,
|
||||
OpenBSD, NetBSD, or even MINIX: OpenBSD PF, NetBSD NPF, IPv6
|
||||
support in &os;, virtualization in the BSD domain, recent
|
||||
|
@ -1024,11 +1025,11 @@ Status Report//EN"
|
|||
&os; Developer Summit organized as part of EuroBSDcon 2011 in
|
||||
Maarssen, The Netherlands. This year EuroBSDcon organizers offered
|
||||
us their generous support in handling the details, like
|
||||
registrations, renting the venue, or providing food for keeping
|
||||
registrations, renting the venue, and providing food for keeping
|
||||
attendees happy.</p>
|
||||
|
||||
<p>The Maarssen developer summit spanned over 3 days. It is
|
||||
generally a workshop-style event that has now adapted the layout of
|
||||
generally a workshop-style event that has now adopted the layout of
|
||||
the developer summit organized successfully in Canada earlier in
|
||||
May. On the first day, there were working groups on various topics,
|
||||
e.g. Capsicum, toolchain issues, ports, and documentation. On the
|
||||
|
@ -1106,7 +1107,7 @@ Status Report//EN"
|
|||
</project>
|
||||
|
||||
<project cat='proj'>
|
||||
<title>ZRouter.org project - a &os; based firmware for embedded
|
||||
<title>ZRouter.org project — a &os;-based firmware for embedded
|
||||
devices</title>
|
||||
|
||||
<contact>
|
||||
|
@ -1129,9 +1130,10 @@ Status Report//EN"
|
|||
</links>
|
||||
|
||||
<body>
|
||||
<p>ZRouter.org is a young project that targeting to produce &os;
|
||||
based firmware for small boxes such a SOHO router, APs, etc. At
|
||||
present time ZRouter.org able to build working firmware for:</p>
|
||||
<p>ZRouter.org is a young project that aims to produce
|
||||
&os;-based firmware for small boxes such as SOHO router, APs, etc.
|
||||
At the present time ZRouter.org is able to build working firmware
|
||||
for:</p>
|
||||
|
||||
<ul>
|
||||
<li>D-Link DAP-1350</li>
|
||||
|
@ -1150,16 +1152,16 @@ Status Report//EN"
|
|||
|
||||
<p>Currently we are working on most parts of the core system but we
|
||||
are also in the planning phase for implementing a simple web-based
|
||||
GUI which we hope will have taken form before next &os; status
|
||||
GUI which we hope will have taken form before the next &os; status
|
||||
report.</p>
|
||||
|
||||
<p>We still have many items not done, so any devices in that list
|
||||
cannot be called as "Production Ready" yet. But we work on that.</p>
|
||||
<p>We still have many items not done, so devices in that list
|
||||
cannot be called "Production Ready" yet. But we work on that.</p>
|
||||
|
||||
<p>It is easy to add new devices, because we have separate
|
||||
definition of board and SoC(System on Chip), so if you have "Asus
|
||||
WL-500g Premium v2" for example, you can copy D-Link/DIR-320
|
||||
directory and tweak to work for you device. We already have basic
|
||||
directory and tweak to work for your device. We already have basic
|
||||
support for:</p>
|
||||
|
||||
<ul>
|
||||
|
@ -1209,11 +1211,12 @@ Status Report//EN"
|
|||
</links>
|
||||
|
||||
<body>
|
||||
<p>Many embedded devices have Ethernet switch on board, same take a
|
||||
place on some multiports NICs, switch framework designed to give
|
||||
ability to user easily control basic futures that management
|
||||
switches have, such a VLANs, QOS, port mirroring, etc. Currently we
|
||||
able to control only VLANs on:</p>
|
||||
<p>Many embedded devices have an Ethernet switch on board; such
|
||||
switches are even embedded on some multiport NICs. This
|
||||
embedded switch framework is designed to give users the
|
||||
ability to easily control basic features present in managed
|
||||
switches, such as VLANs, QoS, port mirroring, etc. Currently
|
||||
we are able to control only VLANs on:</p>
|
||||
|
||||
<ul>
|
||||
<li>Atheros AR8216/AR8316 (standalone and embedded in
|
||||
|
@ -1230,7 +1233,7 @@ Status Report//EN"
|
|||
<help>
|
||||
<task>Fix AR8216/AR8316 driver</task>
|
||||
<task>Fix BCM5325 driver, not all ports pass data</task>
|
||||
<task>Add tick handler for RTL8309 to auto unisolate ports</task>
|
||||
<task>Add tick handler for RTL8309 to automatically unisolate ports</task>
|
||||
<task>Unify MIB statistic counters access</task>
|
||||
<task>Add mii read/write bus methods</task>
|
||||
<task>Implement pseudo interfaces for switch PHYs</task>
|
||||
|
@ -1256,21 +1259,21 @@ Status Report//EN"
|
|||
</links>
|
||||
|
||||
<body>
|
||||
<p>A set of scripts, to make easy of building &os; VM
|
||||
images.</p>
|
||||
<p>A set of scripts to make building &os; VM images easy.</p>
|
||||
|
||||
<p>Providing a way to make regular build images of latest version
|
||||
from SVN. Images currently can be `dd` to USB flash (to make real
|
||||
hardware testing), VirtualBox (.vdi).</p>
|
||||
<p>Providing a way to make regular build images of the latest version
|
||||
from SVN. Images currently can be copied with `dd` to USB
|
||||
flash (for testing on real hardware) and VirtualBox
|
||||
(.vdi).</p>
|
||||
</body>
|
||||
|
||||
<help>
|
||||
<task>Build images with ports-set from main port-tree</task>
|
||||
|
||||
<task>Build images with ports-set from main port-tree plus
|
||||
overrides form area51 (Like expeerimental images)</task>
|
||||
overrides form area51 (like experimental images)</task>
|
||||
|
||||
<task>Build images with special development branches included (Like
|
||||
<task>Build images with special development branches included (like
|
||||
for testing drivers)</task>
|
||||
</help>
|
||||
</project>
|
||||
|
@ -1292,7 +1295,7 @@ Status Report//EN"
|
|||
<given>Giorgos</given>
|
||||
<common>Keramidas</common>
|
||||
</name>
|
||||
<email>keramids@FreeBSD.org</email>
|
||||
<email>keramida@FreeBSD.org</email>
|
||||
</person>
|
||||
</contact>
|
||||
|
||||
|
@ -1305,7 +1308,7 @@ Status Report//EN"
|
|||
|
||||
<body>
|
||||
<p>After a few rather quiet months, the &os; Greek Documentation
|
||||
Project is back in track, translating and improving the Handbook,
|
||||
Project is back on track, translating and improving the Handbook,
|
||||
FAQ and &os; articles. The new bsdinstall chapter has been
|
||||
translated and is now present in the Handbook. Our <a
|
||||
href="http://www.FreeBSDgr.org/handbook">experimental Handbook
|
||||
|
@ -1401,13 +1404,13 @@ Status Report//EN"
|
|||
</links>
|
||||
|
||||
<body>
|
||||
<p>AR5416, AR9160, AR9280 functions in both station and hostap
|
||||
<p>AR5416, AR9160, and AR9280 functions in both station and hostap
|
||||
mode. Performance is good.</p>
|
||||
|
||||
<p>Software retry of frames is implemented. Aggregation is
|
||||
implemented.</p>
|
||||
|
||||
<p>BAR TX is not yet handled. HT protection is not implemented, neither
|
||||
<p>BAR TX is not yet handled. HT protection is not implemented; neither
|
||||
is MIMO powersave.</p>
|
||||
</body>
|
||||
|
||||
|
@ -1472,4 +1475,30 @@ Status Report//EN"
|
|||
page.</p>
|
||||
</body>
|
||||
</project>
|
||||
|
||||
<project cat='team'>
|
||||
<title>The &os; Release Engineering Team</title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
<name>
|
||||
<given>Release Engineering Team</given>
|
||||
</name>
|
||||
<email>re@FreeBSD.org</email>
|
||||
</person>
|
||||
</contact>
|
||||
|
||||
<links>
|
||||
<url href="http://www.FreeBSD.org/releng/" />
|
||||
</links>
|
||||
|
||||
<body>
|
||||
<p>The Release Engineering Team has been coordinating the upcoming
|
||||
&os; 9.0-RELEASE. Thanks to work done by many of the
|
||||
developers. The release, though delayed, is taking the shape
|
||||
nicely. We have reached the stage of doing the second
|
||||
Release Candidate. At this time we expect to have one more
|
||||
Release Candidate, to be followed by the final release itself.</p>
|
||||
</body>
|
||||
</project>
|
||||
</report>
|
||||
|
|
Loading…
Reference in a new issue