Spelling and grammar cleanup pass.
This commit is contained in:
Christian Brueffer
parent
ee339ce5fa
commit
5ed1945636
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=46194
1 changed files with 22 additions and 22 deletions
|
|
@ -105,7 +105,7 @@
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
<p>With funding from the &os; Foundation, the &os; forums
|
<p>With funding from the &os; Foundation, the &os; forums
|
||||||
were migrated to XenForo software. The new software is far more
|
were migrated to the XenForo software. The new software is far more
|
||||||
capable and easy to use. While the entire forum team
|
capable and easy to use. While the entire forum team
|
||||||
contributed, &a.danger; did an excellent job
|
contributed, &a.danger; did an excellent job
|
||||||
importing existing users and messages and bringing back the
|
importing existing users and messages and bringing back the
|
||||||
|
|
@ -166,15 +166,15 @@
|
||||||
<p>The Reaper facility, to allow a process to reliably track the
|
<p>The Reaper facility, to allow a process to reliably track the
|
||||||
running and exiting state of the whole subtree of the processes,
|
running and exiting state of the whole subtree of the processes,
|
||||||
was added. It is intended to improve tools like timeout(1) or
|
was added. It is intended to improve tools like timeout(1) or
|
||||||
poudriere, by making it impossible for the runaway granchild to
|
poudriere, by making it impossible for the runaway grandchild to
|
||||||
escape the controlling process. Feature was designed based on
|
escape the controlling process. The feature was designed based on
|
||||||
similar facility in the DragonFlyBSD and Linux, with some
|
similar facilities in DragonFlyBSD and Linux, with some
|
||||||
references to the Solaris contracts. Committed to HEAD in
|
references to Solaris contracts. Committed to HEAD in
|
||||||
r275800.</p>
|
r275800.</p>
|
||||||
|
|
||||||
<p>The FreeBSD suspension code does not
|
<p>The FreeBSD suspension code does not
|
||||||
ensure that the system, both software and hardware,
|
ensure that the system, both software and hardware,
|
||||||
is in the steady and consistent state. One aspect is
|
is in a steady and consistent state. One aspect is
|
||||||
usermode process activity, which is not yet stopped, continuing to
|
usermode process activity, which is not yet stopped, continuing to
|
||||||
making requests to the hardware. It is not realistic to expect
|
making requests to the hardware. It is not realistic to expect
|
||||||
drivers to be able to correctly handle the calls after
|
drivers to be able to correctly handle the calls after
|
||||||
|
|
@ -187,12 +187,12 @@
|
||||||
existing single-threading code, but extending it to allow external
|
existing single-threading code, but extending it to allow external
|
||||||
thread to put some processes into stopped state. Also, a facility
|
thread to put some processes into stopped state. Also, a facility
|
||||||
to sync filesystems before suspend was added, to ensure that
|
to sync filesystems before suspend was added, to ensure that
|
||||||
consistent metadata and as much as possilbe of the cached user
|
consistent metadata and as much as possible of the cached user
|
||||||
data are on stable storage, to minimize damage of failed
|
data are on stable storage, to minimize damage of failed
|
||||||
resume.</p>
|
resume.</p>
|
||||||
|
|
||||||
<p>The code stressed some parts of the system and has lead to
|
<p>The code stressed some parts of the system and has lead to
|
||||||
discovery of a numbers of bugs in the different areas,
|
discovery of a numbers of bugs in different areas,
|
||||||
including process management, buffer cache and syscall
|
including process management, buffer cache and syscall
|
||||||
handlers. The bugs were fixed, fixes and the features commmitted
|
handlers. The bugs were fixed, fixes and the features commmitted
|
||||||
by a series culminating in r275745.</p>
|
by a series culminating in r275745.</p>
|
||||||
|
|
@ -331,7 +331,7 @@
|
||||||
<p>Implement flexible dependencies.</p>
|
<p>Implement flexible dependencies.</p>
|
||||||
</task>
|
</task>
|
||||||
<task>
|
<task>
|
||||||
<p>Test the developement branch.</p>
|
<p>Test the development branch.</p>
|
||||||
</task>
|
</task>
|
||||||
<task>
|
<task>
|
||||||
<p>More developers are needed, check the Issues on Github.</p>
|
<p>More developers are needed, check the Issues on Github.</p>
|
||||||
|
|
@ -448,7 +448,7 @@
|
||||||
helpful to:
|
helpful to:
|
||||||
<ul>
|
<ul>
|
||||||
<li>Prepare a migration to a newer version of toolchain components.</li>
|
<li>Prepare a migration to a newer version of toolchain components.</li>
|
||||||
<li>Port &os; to newer architecture</li>
|
<li>Port &os; to a new architecture</li>
|
||||||
<li>Upgrade from a &os; that ships with GCC 4.2 to a version that ship with clang 3.5+ (which need a more modern toolchain than GCC 4.2 to bootstrap).</li>
|
<li>Upgrade from a &os; that ships with GCC 4.2 to a version that ship with clang 3.5+ (which need a more modern toolchain than GCC 4.2 to bootstrap).</li>
|
||||||
</ul>
|
</ul>
|
||||||
</p>
|
</p>
|
||||||
|
|
@ -478,7 +478,7 @@
|
||||||
</ul>
|
</ul>
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<p>Those packages will depend on special version of GCC
|
<p>Those packages will depend on special versions of GCC
|
||||||
(minimalistic cross-built ready GCC) and on binutils. To use
|
(minimalistic cross-built ready GCC) and on binutils. To use
|
||||||
them run: <tt>make CROSS_TOOLCHAIN=powerpc64-gcc TARGET=powerpc
|
them run: <tt>make CROSS_TOOLCHAIN=powerpc64-gcc TARGET=powerpc
|
||||||
TARGET_ARCH=powerpc64</tt></p>
|
TARGET_ARCH=powerpc64</tt></p>
|
||||||
|
|
@ -498,7 +498,7 @@
|
||||||
<p>Adapt and upstream the aarch64 patches for binutils 2.25.</p>
|
<p>Adapt and upstream the aarch64 patches for binutils 2.25.</p>
|
||||||
</task>
|
</task>
|
||||||
<task>
|
<task>
|
||||||
<p>Add more pre seeded configurations.</p>
|
<p>Add more pre-seeded configurations.</p>
|
||||||
</task>
|
</task>
|
||||||
</help>
|
</help>
|
||||||
</project>
|
</project>
|
||||||
|
|
@ -554,10 +554,10 @@
|
||||||
<p>The FreeBSD GNOME Team maintains the GNOME, MATE and CINNAMON desktop
|
<p>The FreeBSD GNOME Team maintains the GNOME, MATE and CINNAMON desktop
|
||||||
environments and graphical user interfaces for FreeBSD. GNOME 3 is part
|
environments and graphical user interfaces for FreeBSD. GNOME 3 is part
|
||||||
of the GNU Project. MATE is a fork of the GNOME 2 desktop. CINNAMON
|
of the GNU Project. MATE is a fork of the GNOME 2 desktop. CINNAMON
|
||||||
is desktop environment using GNOME 3 technologies but with a GNOME 2
|
is a desktop environment using GNOME 3 technologies but with a GNOME 2
|
||||||
look and feel.</p>
|
look and feel.</p>
|
||||||
|
|
||||||
<p>This quarter was exciting time for the GNOME Team. We imported
|
<p>This quarter was an exciting time for the GNOME Team. We imported
|
||||||
GNOME 3.14.0 and CINNAMON 2.2.16 into the ports tree. At the same
|
GNOME 3.14.0 and CINNAMON 2.2.16 into the ports tree. At the same
|
||||||
time we removed the old GNOME 2.32 desktop. And two weeks later
|
time we removed the old GNOME 2.32 desktop. And two weeks later
|
||||||
we updated GNOME to 3.14.2 and CINNAMON to 2.4.2, which was collected
|
we updated GNOME to 3.14.2 and CINNAMON to 2.4.2, which was collected
|
||||||
|
|
@ -847,7 +847,7 @@
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
<p>Since the last status report, many people have contributed
|
<p>Since the last status report, many people have contributed
|
||||||
help in various areas to help with with Continuous Integration
|
help in various areas to help with Continuous Integration
|
||||||
and Testing in FreeBSD. Some of the highlights include:</p>
|
and Testing in FreeBSD. Some of the highlights include:</p>
|
||||||
|
|
||||||
<ul>
|
<ul>
|
||||||
|
|
@ -862,7 +862,7 @@
|
||||||
<li>&a.rodrigc; gave a presentation "Kyua and Jenkins Testing
|
<li>&a.rodrigc; gave a presentation "Kyua and Jenkins Testing
|
||||||
Framework" for BSD at the Developer and Vendor summit on
|
Framework" for BSD at the Developer and Vendor summit on
|
||||||
November 3, 2014 in San Jose, California. In the presentation,
|
November 3, 2014 in San Jose, California. In the presentation,
|
||||||
&a.rodrigc;'s described how, for every commit to the FreeBSD source
|
&a.rodrigc; described how, for every commit to the FreeBSD source
|
||||||
tree, nearly 3000 tests are run using kyua inside a bhyve virtual
|
tree, nearly 3000 tests are run using kyua inside a bhyve virtual
|
||||||
machine. The kyua test results are exported to JUnit XML format,
|
machine. The kyua test results are exported to JUnit XML format,
|
||||||
which is then used by Jenkins to generate web-based test reports with
|
which is then used by Jenkins to generate web-based test reports with
|
||||||
|
|
@ -1121,7 +1121,7 @@
|
||||||
<p>We migrated our Ports development tree to Git and GitHub. Tracking
|
<p>We migrated our Ports development tree to Git and GitHub. Tracking
|
||||||
changes in the official Ports tree and preparing patches is way
|
changes in the official Ports tree and preparing patches is way
|
||||||
easier. Furthermore, we can accept pull requests. All reasons behind
|
easier. Furthermore, we can accept pull requests. All reasons behind
|
||||||
this change are detailed on the blog and the workf-low is described
|
this change are detailed on the blog and the workflow is described
|
||||||
on the wiki.</p>
|
on the wiki.</p>
|
||||||
|
|
||||||
<p>The XDC 2014 (X Developer's Conference) was a great conference.
|
<p>The XDC 2014 (X Developer's Conference) was a great conference.
|
||||||
|
|
@ -1328,7 +1328,7 @@
|
||||||
At this point, FreeBSD 10.0 and later provide that support, at least
|
At this point, FreeBSD 10.0 and later provide that support, at least
|
||||||
on x86.</p>
|
on x86.</p>
|
||||||
|
|
||||||
<p>In the near future, more components from the llvm.org will
|
<p>In the near future, more components from llvm.org will
|
||||||
be updated in base, with libc++ and libcompiler-rt most likely
|
be updated in base, with libc++ and libcompiler-rt most likely
|
||||||
being the first.</p>
|
being the first.</p>
|
||||||
|
|
||||||
|
|
@ -1339,7 +1339,7 @@
|
||||||
|
|
||||||
<help>
|
<help>
|
||||||
<task>
|
<task>
|
||||||
<p> While most ports that were impacted by this update have
|
<p>While most ports that were impacted by this update have
|
||||||
already been fixed, there are still a few that do not work with
|
already been fixed, there are still a few that do not work with
|
||||||
the clang 3.5.0 update.</p>
|
the clang 3.5.0 update.</p>
|
||||||
|
|
||||||
|
|
@ -1523,7 +1523,7 @@
|
||||||
objcopy, and accepts the same command-line arguments. For it to be
|
objcopy, and accepts the same command-line arguments. For it to be
|
||||||
a viable replacement for all uses of objcopy in the base system, it
|
a viable replacement for all uses of objcopy in the base system, it
|
||||||
must gain support for writing portable exectuable (PE)
|
must gain support for writing portable exectuable (PE)
|
||||||
format binaries, which are used in by UEFI boot code.</p>
|
format binaries, which are used by UEFI boot code.</p>
|
||||||
|
|
||||||
<p>The ELF Tool Chain project does not currently provide
|
<p>The ELF Tool Chain project does not currently provide
|
||||||
replacements for as, ld, and objdump. For &os; these tools will
|
replacements for as, ld, and objdump. For &os; these tools will
|
||||||
|
|
@ -1657,7 +1657,7 @@
|
||||||
|
|
||||||
<help>
|
<help>
|
||||||
<task>
|
<task>
|
||||||
<p> Improve documentation.</p>
|
<p>Improve documentation.</p>
|
||||||
</task>
|
</task>
|
||||||
|
|
||||||
<task>
|
<task>
|
||||||
|
|
@ -2114,7 +2114,7 @@
|
||||||
review. Currently it is planned to commit the PCI infrastructure to
|
review. Currently it is planned to commit the PCI infrastructure to
|
||||||
head by the end of January.</p>
|
head by the end of January.</p>
|
||||||
|
|
||||||
<p>In additional to the PCI infrastructure, individual PCI drivers
|
<p>In addition to the PCI infrastructure, individual PCI drivers
|
||||||
must be extended to implement SR-IOV. An SR-IOV implementation is in
|
must be extended to implement SR-IOV. An SR-IOV implementation is in
|
||||||
progress for the ixl(4) driver, which supports the Intel XL710 family
|
progress for the ixl(4) driver, which supports the Intel XL710 family
|
||||||
of 40G and 10G NICs. Currently it is planned to have this in review
|
of 40G and 10G NICs. Currently it is planned to have this in review
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue