Fix a few wording, grammar, spelling, and a few style nits in the Status
Report.
This commit is contained in:
parent
d0d3990c51
commit
ed1567f887
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=37689
1 changed files with 20 additions and 20 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: www/en/news/status/report-2011-04-2011-06.xml,v 1.1 2011/09/12 15:23:25 danger Exp $ -->
|
||||
<!-- $FreeBSD: www/en/news/status/report-2011-04-2011-06.xml,v 1.2 2011/09/12 22:44:57 gjb Exp $ -->
|
||||
|
||||
<report>
|
||||
<date>
|
||||
|
|
@ -143,7 +143,7 @@ Status Report//EN"
|
|||
<body>
|
||||
<p>On June 6, the &os; documentation project held a doc sprint
|
||||
where a number of documentation issues were discussed. The sprint
|
||||
took place primarily on efnet's IRC channel #bsddocs. Notes were
|
||||
took place primarily in IRC channel #bsddocs on EFNet. Notes were
|
||||
taken in an Etherpad document where all participants could
|
||||
concurrently edit them in an easy to use interface. Parallel to the
|
||||
discussion, a number of doc problem reports have been closed. There
|
||||
|
|
@ -213,7 +213,7 @@ Status Report//EN"
|
|||
and does not support wide characters. There are various open
|
||||
source regular expression libraries but replacing the code is
|
||||
not a simple task because there are quite many considerations
|
||||
and requirements. The best candidate is TRE, which is
|
||||
and requirements. The best candidate is TRE, which is a
|
||||
BSD-licensed, supports wide and multibyte characters, conforms
|
||||
to POSIX and it performs well compared to another available
|
||||
alternatives, so the work has been started with TRE. Apart
|
||||
|
|
@ -522,7 +522,7 @@ Status Report//EN"
|
|||
MAKE_JOBS), it cannot build multiple ports concurrently. This tool
|
||||
accomplishes just that.</p>
|
||||
|
||||
<p>Some of it's key features:</p>
|
||||
<p>Some of its key features:</p>
|
||||
|
||||
<ul>
|
||||
<li>Concurrent port building</li>
|
||||
|
|
@ -585,7 +585,7 @@ Status Report//EN"
|
|||
in a per-interface basis. The traditional "host" and "router"
|
||||
node model in IPv6 RFCs is translated into a concept of
|
||||
"RA-receiving interfaces" and "RA-sending interfaces" in
|
||||
&os; 9.0 or later, not depending only on system-wide IP
|
||||
&os; 9.0 or later, not depending only on system-wide IP
|
||||
forwarding capability. This is useful for a system with
|
||||
multiple IPv6-capable interfaces (such as a customer-edge
|
||||
router) which require SLAAC (Stateless Address
|
||||
|
|
@ -664,7 +664,7 @@ Status Report//EN"
|
|||
also contains a more comprehensive introduction, as well as links
|
||||
to related work and documentation.</p>
|
||||
|
||||
<p>In July 2011 we released DIFFUSE v0.4. This release contains a
|
||||
<p>In July 2011, we released DIFFUSE v0.4. This release contains a
|
||||
number of bug fixes and new features. Most notably we improved the
|
||||
functionality of the tools used for training classification models,
|
||||
and performing offline analysis.</p>
|
||||
|
|
@ -690,19 +690,19 @@ Status Report//EN"
|
|||
|
||||
<body>
|
||||
<p>The new NFS client and server are no longer considered
|
||||
experimental and will most likely be the default for &os;9.0.
|
||||
experimental and will most likely be the default for &os; 9.0.
|
||||
Included is support for NFSv4.0 as well as NFSv3 and NFSV2. The
|
||||
NFSv4.0 support was tested at a recent NFSv4 Interoperability
|
||||
Bakeathon held at CITI of the University of Michigan. Also tested
|
||||
at the Bakeathon was a basic client implementation of NFSv4.1 which
|
||||
will soon be available as a test patch against the &os;9.0
|
||||
will soon be available as a test patch against the &os; 9.0
|
||||
kernel sources. If you are interested in testing NFSv4,1, stay
|
||||
tuned to the freebsd-fs@FreeBSD.org mailing list.
|
||||
zkirsch@FreeBSD.org and friends will be taking on a majority of the
|
||||
NFSv4 server work while I concentrate on the client, with hopes
|
||||
that the NFSv4.1 support will mature over the next year or so.</p>
|
||||
|
||||
<p>I will also be making a patch for an experimental agressive
|
||||
<p>I will also be making a patch for an experimental aggressive
|
||||
client side on-disk caching mechanism for NFSv4 I call Packrats
|
||||
available. An announcement about this will be made on
|
||||
freebsd-fs@FreeBSD.org as well.</p>
|
||||
|
|
@ -732,8 +732,8 @@ Status Report//EN"
|
|||
|
||||
<body>
|
||||
<p>ZFS pool version 28 has been merged into 8-STABLE as of
|
||||
2011-06-06. In addition, several bugfixes and improvements from the
|
||||
Illumos project have been imported.</p>
|
||||
June 6, 2011. In addition, several bugfixes and improvements
|
||||
from the Illumos project have been imported.</p>
|
||||
</body>
|
||||
|
||||
<help>
|
||||
|
|
@ -1050,7 +1050,7 @@ Status Report//EN"
|
|||
are already synchronized with www/en at this moment, and this
|
||||
updating work will be finished within this year.</p>
|
||||
|
||||
<p>For &os; Handbook, translation work for kernelconfig section
|
||||
<p>For &os; Handbook, translation work for the kernelconfig section
|
||||
was just started. In addition, we are planning to translate the
|
||||
upcoming release announcement because it is also important for
|
||||
Japanese people.</p>
|
||||
|
|
@ -1101,8 +1101,8 @@ Status Report//EN"
|
|||
<p>The ports tree slowly moves up closer to 23,000. The PR count
|
||||
still remains at about 1100.</p>
|
||||
|
||||
<p>In Q2 we added 3 new committers, took in 2 commit bit for safe
|
||||
keeping and added a new member to portmgr.</p>
|
||||
<p>In Q2 we added 3 new committers, took in 2 commit bits for safe
|
||||
keeping, and added a new member to portmgr.</p>
|
||||
|
||||
<p>The Ports Management team have been running -exp runs on an
|
||||
ongoing basis, verifying how base system updates may affect the
|
||||
|
|
@ -1154,7 +1154,7 @@ Status Report//EN"
|
|||
Tier-2 architectures</a>. (List needs updating, too)</task>
|
||||
|
||||
<task>Most ports PRs are assigned, we now need to focus on testing,
|
||||
committing and closing.</task>
|
||||
committing, and closing.</task>
|
||||
</help>
|
||||
</project>
|
||||
|
||||
|
|
@ -1179,7 +1179,7 @@ Status Report//EN"
|
|||
<body>
|
||||
<p>Some applications from the base system received sandboxing
|
||||
support, current task is to adapt lightweight resolver daemon for
|
||||
using it in sandboxes -- this fixes problems with applications that
|
||||
using it in sandboxes — this fixes problems with applications that
|
||||
need to convert IP addresses into domain names while in
|
||||
sandbox.</p>
|
||||
</body>
|
||||
|
|
@ -1312,7 +1312,7 @@ Status Report//EN"
|
|||
</links>
|
||||
|
||||
<body>
|
||||
<p>The &os; Foundation sponsored project to port Linux
|
||||
<p>The &os; Foundation sponsored project to port the Linux
|
||||
kernel-mode driver for Intel GPU progressed to the point where some
|
||||
machines can use Xorg with ddx driver from the git head and latest
|
||||
Mesa. On my test machine I was able to run uhexen2 and
|
||||
|
|
@ -1360,13 +1360,13 @@ Status Report//EN"
|
|||
<p>During the last period most work went into keeping the Handbook
|
||||
up to date; it is currently up-to-date except for a section on
|
||||
network servers. Other areas being worked on are the FAQ and the
|
||||
web site. The latter two are still work-in-progress.</p>
|
||||
web site. The latter two are still a work-in-progress.</p>
|
||||
</body>
|
||||
|
||||
<help>
|
||||
<task>Volunteers! The best part is that you do not need to be an
|
||||
expert on &os; nor the Dutch language to join, just some
|
||||
enthousiasm and spare time.</task>
|
||||
enthusiasm and spare time.</task>
|
||||
</help>
|
||||
</project>
|
||||
|
||||
|
|
@ -1444,7 +1444,7 @@ Status Report//EN"
|
|||
but backward jumps are allowed). If later a rule with
|
||||
<tt>return</tt> action is encountered, the processing returns to
|
||||
the first rule with number greater than the number saved in the
|
||||
internal stack. This makes possible to organize "subroutines"
|
||||
internal stack. This makes it possible to organize "subroutines"
|
||||
with rules, e.g. to call one subroutine several times from
|
||||
different places in the ruleset. For more details, see <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=8&manpath=FreeBSD+9.0-RELEASE&format=html">
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue