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

- Some more language improvements

Browse source
This commit is contained in:
Gabor Kovesdan 2010-01-17 11:06:43 +00:00
parent 4afdd2beff
commit 08b4a1556b
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=35206
1 changed files with 64 additions and 61 deletions
Download patch file Download diff file Expand all files Collapse all files

125
en/news/status/report-2009-10-2009-12.xml
View file

@ -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: www/en/news/status/report-2009-10-2009-12.xml,v 1.11 2010/01/16 16:56:52 gabor Exp $ -->
<!-- $FreeBSD: www/en/news/status/report-2009-10-2009-12.xml,v 1.12 2010/01/16 17:57:54 gabor Exp $ -->
<report>
<date>
<month>October-December</month>
@ -769,10 +769,10 @@ Report//EN"
<p>This work allows Linux applications using V4L video calls to
work with existing &os; video drivers that provide V4L interfaces.
It is tested and working with the net/skype port and also with
browser-based Flash applications that access webcams. It is tested on
&os;-8.0/amd64 and &os;-7.2/i386. An early version has been
browser-based Flash applications that access webcams. An early version has been
committed to 9.0-CURRENT and work is in progress to commit the latest
version and then MFC.</p>
version and then MFC. It is also tested on &os;-8.0/amd64 and
&os;-7.2/i386.</p>
<p>Note: to be clear, this does not add V4L support to all webcams.
The &os; camera driver must already offer V4L support itself in
@ -1098,7 +1098,7 @@ Report//EN"
<p>The purpose of this project is to provide &os; with support for the
Flattened Device Tree (FDT) technology, the 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
a uniform and portable way. The primary consumers of this technology are
embedded &os; platforms (ARM, AVR32, MIPS, PowerPC), where a lot of
designs are based on similar chips but have different assignment of pins,
memory layout, addresses bindings, interrupts routing and other resources.</p>
@ -1264,8 +1264,8 @@ Report//EN"
</contact>
<body>
<p>Important changes regarding &os; TDM Framework since last Status
Report:</p>
<p>Important changes regarding &os; TDM Framework since the last status
report:</p>
<ul>
<li>Fully functional TDM controller driver for Marvell Kirkwood and
@ -1316,13 +1316,13 @@ Report//EN"
<url href="http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/lib/libc/gen/utmpx.c">NetBSD's implementation</url>
<url href="http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/gen/getutx.c">OpenSolaris's implementation</url>
<url href="http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/gen/getutx.c">OpenSolaris' implementation</url>
</links>
<body>
<p>On January 13, I removed the utmp user accounting database and
replaced it with POSIX utmpx. Unfortunately, the upgrade path is a bit
bumpy, because the utmp interface provided almost no library
replaced it with a new POSIX utmpx implementation. Unfortunately, the upgrade path is a bit
complex, because the utmp interface provided almost no library
interface to interact with the database files.</p>
<p>This change may have caused some regressions. Some ports may fail
@ -1358,8 +1358,8 @@ Report//EN"
<body>
<p>Good compatibility has been ensured and there are only few pending
items which have to be reviewed/enhanced. Recently, an enhancement
has been completed which makes it possible to accomplish better
items that have to be reviewed/enhanced. Recently, an enhancement
has been completed, which makes it possible to accomplish better
transliteration, just like in the GNU version. An initial testing
patch is expected at the beginning of February.</p>
</body>
@ -1426,7 +1426,7 @@ Report//EN"
<body>
<p>NVIDIA has released the first BETA version of its graphics
drivers for &os;/amd64. Note that this driver will work on &os;
versions 7.3 or 8.0 and later. It also works on very recent
versions 7.3-RELEASE or 8.0-RELEASE and later. It also works on very recent
versions of 7.2-STABLE. More details are provided in the
official release announcement.</p>
</body>
@ -1488,7 +1488,7 @@ Report//EN"
<p>The list of PRs recommended for committer evaluation by the
Bugbusting Team continues to receive new additions; however, it
has not yet achieved high visibility. (This list contains PRs,
mostly with patches, that the Bugbusting Team feel are probably
mostly with patches, that the Bugbusting Team consider potentially
ready to be committed as-is, or are probably trivially resolved
in the hands of a committer with knowledge of the particular
subsystem.) One of the suggestions at the Cambridge devsummit
@ -1505,9 +1505,9 @@ Report//EN"
been converted, and we are keeping up as new ones come in. We
hope that this is making it easier to browse the PR database.</p>
<p>The overall PR count jumped to over 6200 during the 8.0 release
cycle, but seems to have stabilized at around 6100. As in the
past, we have a fairly good clearance rate for ports PRs, but
<p>The overall PR count jumped to over 6,200 during the 8.0-RELEASE release
cycle but seems to have stabilized at around 6,100. As in the
past, we have a fairly good clearance rate for ports PRs but
much less so for other PRs. (Partly this is due to the concept
of individual ports having 'maintainers'.)</p>
</body>
@ -1533,10 +1533,10 @@ Report//EN"
<body>
<p>Work continues on our ia64 port. Many recent commits to
help improve stability have been made to -CURRENT and MFCed
help improve stability have been made to 9.0-CURRENT and MFCed
to 8-STABLE.</p>
<p>Due to interest from one very motivated user, package builds
<p>Due to interest from a very motivated user, package builds
have been restarted for ia64-8. This is primarily intended as
a QA step to discover and fix bugs on ia64, rather than to
create packages for upload.</p>
@ -1563,7 +1563,7 @@ Report//EN"
<task>Configure a fourth machine that has been made available
to us.</task>
<task>Figure out the problems with the latest gcc port on
<task>Figure out the problems with the latest GCC port on
ia64.</task>
<task>We can use some help with reviewing the ia64 platform pages
@ -1594,28 +1594,31 @@ Report//EN"
reasons:</p>
<ul>
<li>Uses latest v4 firmware image instead of using v3 which is
enough old one so we could have benefits supporting N-PHYs or
fixes various firmware bugs.</li>
<li>Uses latest v4 firmware image instead of using v3, which is
old enough. In this way, we have some great benefits, such as the
supportos N-PHYs or the fixes of various earlier firmware bugs.</li>
<li>Supports PIO mode that as you might Broadcom Wireless Driver
is created by reverse-engineering so AFAIK some H/W does not
<li>Supports PIO mode. This is importanta because &mdash; as you might
know &mdash; the Broadcom Wireless Driver is created by
reverse-engineering so some pieces of hardware might not
work with DMA operations.</li>
<li>Supports 64 bit DMA operations.</li>
<li>Separates bwi(4) driver into two parts; siba(4) driver and
bwn(4) driver. AFAIK many Broadcom wirelesses or NIC devices
are based on Silicon Sonics Backplane and bwi(4) was one of
them but in a case of bwi(4) it had implemented siba(4)
driver internally so other drivers which were willing to use
the SIBA APIs had to implement their own routines. In bwn(4)
I wanted to avoid it.</li>
bwn(4) driver. Many Broadcom wireless and NIC devices
are based on Silicon Sonics Backplane, such as bwi(4), which
implemented the SIBA operations internally. This resulted in
code duplication as other drivers had to implement their
own routines to deal with SIBA. In the case of bwn(4),
these two parts have been separated and implemented in their
own kernel modules to avoid this problem and help further
development by providing a standalone siba(4) driver.</li>
</ul>
<p>Currently it is tested on big/little endian machines and 32/64
bits DMA operation with STA mode. A major patch for siba(4)
is being reviewed before committing into HEAD.</p>
<p>Currently, it is tested on big/little endian machines and 32/64-bit
DMA operation with STA mode. A major patch for siba(4)
is being reviewed before committing into 9.0-CURRENT.</p>
</body>
<help>
@ -1650,7 +1653,7 @@ Report//EN"
<p>The Release Engineering Team would like to thank George
Neville-Neil (gnn@) for his service on the team. George
continues to work with the &os; Project but has stepped down
from the Release Engineering Team to focus on those other
from the Release Engineering Team to focus on other
activities.</p>
</body>
</project>
@ -1677,25 +1680,25 @@ Report//EN"
identified:</p>
<ul>
<li>problems with the IPcomp packet handling in IPsec.</li>
<li>Problems with the IPcomp packet handling in IPsec.</li>
<li>opencrypto compression handling and deflate implementation
limitations. These were debugged using DTrace SDT
probes.</li>
<li>problems due to an outdated version of zlib used in some
<li>Problems due to an outdated version of zlib used in some
parts of the network stack and by the opencrypto
framework</li>
framework.</li>
</ul>
<p>Patches for all but the zlib support have been committed to
HEAD and merged to all supported stable branches including
RELENG_6. Special thanks to Eugene Grosbein for helping with
9.0-RELEASE and merged to all supported stable branches including
6-STABLE. Special thanks to Eugene Grosbein for helping with
testing.</p>
</body>
<help>
<task>Fix ng_deflate so that we could make use of Kip Macy's work
<task>Fix ng_deflate so that we can make use of Kip Macy's work
on an up-to-date unified zlib version in the kernel, which
would also fix the last occasional IPcomp hiccups.</task>
</help>
@ -1721,10 +1724,10 @@ Report//EN"
<body>
<p>Despite a difficult economy, we more than doubled our number
of donors, we raised $269k towards our goal of $300k, and with
of donors, we raised $269K towards our goal of $300K, and with
an improved economy hope to surpass that this year.</p>
<p>We funded two new projects. One is the Flattened Device Tree by
<p>We have funded two new projects. One is the Flattened Device Tree by
Rafal Jaworowski. And, the second one is Highly Available Storage
by Pawel Jakub Dawidek. We continued supporting the New Console
Driver by Ed Schouten and Improvements to the &os; TCP Stack by
@ -1790,10 +1793,10 @@ Report//EN"
</links>
<body>
<p>VirtualBox 3.1.2 has been committed to the Ports tree.</p>
<p>VirtualBox 3.1.2 has been committed to the ports tree.</p>
<p>Several changes to the port have been performed with this
update which include:</p>
update including:</p>
<ul>
<li>Port has been renamed to virtualbox-ose to reflect that we
@ -1810,22 +1813,22 @@ Report//EN"
<li>Procfs is not required anymore because vbox uses sysctl(3)
now.</li>
<li>Nox@'s &os; host networking patches have been added. They
<li>Juergen Lock's &os; host networking patches have been added. They
are now also in the upstream vbox SVN (modulo vbox variable
naming style adjustments).</li>
<li>Allow direct tap networking again (for users that need the
best network performance and/or need more complex network
setups, like when they want to use routing instead of bridging
to e.g. protect guests from messing with the lan's arp tables;
to e.g. protect guests from messing with the lan's ARP tables;
a tap + routing + proxy arp example is in the above
freebsd-emulation@ posting.)</li>
<li>Enable vbox' shared mac feature when using bridged mode on
a wifi interface, together with the virtualbox-ose-kmod
change this should fix bridged mode for wifi users.</li>
<li>Enable vbox's shared MAC feature when using bridged mode on
a Wifi interface, together with the virtualbox-ose-kmod
change this should fix bridged mode for Wifi users.</li>
<li>We would like to say thanks to all the people who helped us
<li>We would like to say thanks to all the people that helped us
by reporting bugs and submitting fixes. We also thank the
VirtualBox developers for their help with the ongoing effort
to port VirtualBox to &os;</li>
@ -1857,7 +1860,7 @@ Report//EN"
appeals to a wide range of people from extreme novices to
advanced developers.</p>
<p>BSDCan 2010 will be held on 13-14 May 2010 at University of
<p>BSDCan 2010 will be held on 13-14 May 2010 at the University of
Ottawa, and will be preceded by two days of Tutorials on 11-12
May 2010.</p>
@ -1894,7 +1897,7 @@ Report//EN"
systems based on FreeBSD, NetBSD, OpenBSD, DragonFlyBSD, Darwin
and MacOS X.</p>
<p>The next conference will be held at Tokyo University of
<p>The next conference will be held at the Tokyo University of
Science, Tokyo, Japan, on 11th to 14th March, 2010.</p>
<p>For more detailed information, please check the conference
@ -1903,7 +1906,7 @@ Report//EN"
</project>
<project cat='misc'>
<title>meetBSD 2010 -- The BSD Conference</title>
<title>meetBSD 2010 &mdash; The BSD Conference</title>
<contact>
<person>
@ -1926,7 +1929,7 @@ Report//EN"
meetBSD Wintercamp in Livigno, this year we are back to
Krakow, Poland.</p>
<p>In 2010, meetBSD will be held on 2-3 July at Jagiellonian
<p>In 2010, meetBSD will be held on 2-3 July at the Jagiellonian
University.</p>
<p>See the conference main web site for more details.</p>
@ -1978,24 +1981,24 @@ Report//EN"
<body>
<p>We are again able to build bootable i386/amd64 kernel. Nathan
Whitehorn commited a fix to &os; which enabled LLVM/clang to
Whitehorn committed a fix to &os;, which enabled LLVM/clang to
work mostly fine on PowerPC. There is some preliminary testing
of LLVM/clang on ARM and MIPS being done. We have some ideas
about sparc64 support which are currently being investigated.
You are welcome to contact us if you want to help.</p>
<p>Since the last report a lot has happened mostly in the area of
C++, clang is currently able to build working groff, gperf and
devd, ie. all of the C++ apps we have in base. Unfortunatelly,
<p>Since the last report, a lot has happened mostly in the area of
C++; clang is currently able to build working groff, gperf and
devd, i.e. all of the C++ apps we have in base. Unfortunately,
it still cannot build any of the C++ libraries &mdash; two of
them are missing builtins and libstdc++ is broken for other
reasons.</p>
<p>Not much happened in the clangbsd branch as we cannot upgrade
<p>Not much happened in the clangbsd branch as we cannot
upgrade the clang/llvm there because we are blocked by a bug
that requires using newer assembler than we can ship. This
might be solved by either fixing this (short term) or using
llvm-mc instead of gnu as for assembling (longer term).</p>
llvm-mc instead of GNU as for assembling (longer term).</p>
</body>
<help>