svn commit: r45345 - head/en_US.ISO8859-1/htdocs/news/status
Benjamin Kaduk
bjk at FreeBSD.org
Sun Jul 20 23:49:47 UTC 2014
Author: bjk
Date: Sun Jul 20 23:49:46 2014
New Revision: 45345
URL: http://svnweb.freebsd.org/changeset/doc/45345
Log:
General edits for style, grammar, and clarity for the 2014Q2 report
Standardize on "toolchain" and "safekeeping", as these seem to be
the more-commonly used forms.
Approved by: gjb (implicit)
Modified:
head/en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml
Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml Sun Jul 20 18:08:19 2014 (r45344)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml Sun Jul 20 23:49:46 2014 (r45345)
@@ -118,9 +118,9 @@
</links>
<body>
- <p>The so-called "CUSE4BSD" has been imported into the base
- system of &os;-11. CUSE is short for character device in
- userspace. The CUSE library is a wrapper for the
+ <p>The so-called <quote>CUSE4BSD</quote> has been imported into the base
+ system of &os;-11. CUSE is short for <quote>character device in
+ userspace</quote>. The CUSE library is a wrapper for the
<tt>devfs(8)</tt> kernel functionality which is exposed
through /dev/cuse. In order to function, the CUSE kernel code
must either be enabled in the kernel configuration file or
@@ -153,7 +153,7 @@
request rate increased by many times, reaching up to 600K
requests per second on modern hardware.</p>
- <p>The CAM Target Layer (CTL), used as base for new kernel iSCSI
+ <p>The CAM Target Layer (CTL), used as the base for the new kernel iSCSI
server, also received a series of locking optimizations which
allowed its peak request rate to increase from ~200K to ~600K
IOPS with the potential of reaching a rate of 1M requests per
@@ -278,7 +278,7 @@
<tt>vt(4)</tt> gained the ability to make early driver
selection. <tt>vt(4)</tt> selects the best
successfully-probed driver before most other kernel
- subsystems. Also, to make easy migration from
+ subsystems are initialized. Also, to facilitate migration from
<tt>syscons(4)</tt> to <tt>vt(4)</tt>, multiple virtual
terminal subsystems in the kernel are now supported. It is
controlled by a small module with just one kernel environment
@@ -288,8 +288,7 @@
<p>The GENERIC kernel configuration for the amd64 and i386
platforms now includes both <tt>syscons(4)</tt> and
<tt>vt(4)</tt> by default. This configuration is also planned
- to be in the next 10-STABLE release and
- &os; 10.1-RELEASE.</p>
+ to be in &os; 10.1-RELEASE.</p>
<p>The project finally received a man page, so now
<tt>vt(4)</tt> is not only the project name, but also a link
@@ -350,7 +349,7 @@
<tt>vidcontrol(1)</tt>.</task>
<task>Write manual pages for <tt>vt(4)</tt> drivers and kernel
- interface.</task>
+ interfaces.</task>
<task>Support direct handling of keyboard by the <tt>kbd</tt>
device (without <tt>kbdmux(4)</tt>).</task>
@@ -404,8 +403,8 @@
</links>
<body>
- <p>The <tt>ports-mgmt/poudriere-devel</tt> port is aware of how
- to build ports via an emulator. Configuration of the
+ <p>The <tt>ports-mgmt/poudriere-devel</tt> port is capable of
+ building ports via an emulator. Configuration of the
miscellaneous binary image activator is required prior to a
poudriere-devel run.</p>
@@ -414,7 +413,8 @@
of builds. They can be viewed on the "Status of ports
building" link.</p>
- <p>On current or latest stable/10:</p>
+ <p>To build packages via emulation, on current or latest
+ stable/10:</p>
<p>Clone the github repository, and switch to the bsd-user
branch. Then run:</p>
@@ -439,7 +439,7 @@
<p>Install poudriere-devel from ports. It knows how to set up
things.</p>
- <p>Build poudriere jail to do all the magic:</p>
+ <p>Create a poudriere jail to do all the magic:</p>
<p><tt>poudriere jail -c -j 11armv632 -m svn -a armv6 \<br/>
-v head</tt></p>
@@ -463,27 +463,28 @@
<help>
<task>PPC on AMD64 emulation. This is a work in progress as
there appear to be some serious issues running the bsd-user
- binary on big-endian hardware. Justin Hibbits working on
+ binary on big-endian hardware. Justin Hibbits is working on
this.</task>
<task>SPARC64 on AMD64 emulation is non-functional and instantly
- segfaults. Looking for someone to poke at the bits
+ segfaults. We are looking for someone to poke at the bits
here.</task>
- <task>External Tool Chain, XDEV support. Partial support for
- using an AMD64 tool chain that can output other architecture
- (use AMD64 toolchain to build MIPS64 packages). Currently
- tracking a linking issue with <tt>ports-mgmt/pkg</tt>. Thanks
- to Warner Losh, Baptiste Daroussin, Dimitry Andric for poking
- at bits in here to make the XDEV target useful.</task>
+ <task>External Toolchain, XDEV support. There is partial
+ support for using an AMD64 toolchain that can output binaries
+ for other architecture (e.g., using an AMD64 toolchain to
+ build MIPS64 packages). We are currently tracking a linking
+ issue with <tt>ports-mgmt/pkg</tt>. Thanks to Warner Losh,
+ Baptiste Daroussin, Dimitry Andric for poking at bits in here
+ to make the XDEV target useful.</task>
- <task>Signal handling, MIPS/ARMV6 target still displays a
+ <task>Signal handling. The MIPS/ARMV6 target stills display a
failure that manifests itself when building
<tt>devel/p5-Sys-SigAction</tt>.</task>
<task>Massive documentation update needed. These modifications
actually allow chrooting into a MIPS or ARMv6 environment
- and using native tool chains and libraries to prototype
+ and using native toolchains and libraries to prototype
software for a target platform.</task>
</help>
</project>
@@ -514,8 +515,8 @@
and installable in parallel for different Python versions at
the same time on the same host. The package building tools,
however, do not support this feature yet and the Python team
- will work closely with portmgr and pkg developers to enable
- support on a global ports and package scale.</p>
+ will work closely with portmgr and the pkg developers to enable
+ support on a global ports and packages scale.</p>
<p>In May and June a huge clean-up operation took place to
remove the last bits and pieces targeting easy_install. In
@@ -609,7 +610,7 @@
<tt>vt(4)</tt> selection to the UEFI boot path.</p>
<p>Snapshots are now built as dual-mode images, and should boot
- via BIOS and UEFI. Our plan is to merge the UEFI and
+ via both BIOS and UEFI. Our plan is to merge the UEFI and
<tt>vt(4)</tt> work to stable/10 to appear in &os;
10.1-RELEASE.</p>
</body>
@@ -754,18 +755,18 @@
<ul>
<li>Libvirt hypervisor driver for bhyve.</li>
- <li>Support for bhyve (via libvirt compute driver) and &os;
- platform in overall in nova-compute.</li>
+ <li>Support for bhyve (via libvirt compute driver) and the
+ overall &os; platform in nova-compute.</li>
<li>OpenContrail vRouter (forwarding plane kernel module) port
to &os;.</li>
<li>OpenContrail Agent (network controller node) port to
&os;.</li>
- <li>Integration, performance optimizations.</li>
+ <li>Integration and performance optimizations.</li>
</ul>
<p>Since the last report the following items have been
- completed, which allow for a working demo of OpenStack compute
- node on a &os; host using OpenContrail solution for network
+ completed, which allow for a working demo of an OpenStack compute
+ node on a &os; host using OpenContrail for network
virtualization:</p>
<ul>
@@ -823,9 +824,9 @@
Project.</p>
<p>The annual board meeting was held in Ottawa, Canada, in May.
- Directors and officers were elected, and did some long term
+ Directors and officers were elected, and we did some long-term
planning. We worked on our vision, core values, project road
- mapping, and our near term goals. We also met with the core
+ mapping, and our near-term goals. We also met with the core
team to discuss roles and responsibilities, project
roadmapping, and what we can do to help the Project more.</p>
@@ -849,7 +850,7 @@
(southeastlinuxfest.org).</p>
<p>Hardware was purchased to support an upgrade at Sentex. A
- new high capacity 1Gbps switch was deployed to allow for more
+ new high-capacity 1Gbps switch was deployed to allow for more
systems to be added to the test lab. The main file server and
development box was upgraded to allow more users in the lab
simultaneously.</p>
@@ -921,17 +922,17 @@
<body>
<p>SDIO is an interface designed as an extension of the existing
SD card standard, which allows the connecting of different
- peripherals to the host with a standard SD controller.
+ peripherals to a host with a standard SD controller.
Peripherals currently sold on the general market include
WLAN/BT modules, cameras, fingerprint readers, and barcode
scanners. Additionally, SDIO is used to connect some
- peripherals in products like Chromebooks and Wandboard. A
+ peripherals in products like Chromebooks and Wandboards. A
prototype of the driver for the Marvell SDIO WLAN/BT (Avastar
88W8787) module is also being developed, using the existing
Linux driver as the reference.</p>
- <p>SDIO card detection and initialization already work, most
- needed bus methods are implemented and tested.</p>
+ <p>SDIO card detection and initialization already work. Most
+ necessary bus methods are implemented and tested.</p>
<p>The WiFi driver is able to load firmware onto the card and
initialize it. A rewrite of the MMC stack as a transport
@@ -942,11 +943,11 @@
<help>
<task>SDIO stack: finish CAM migration. The initialization of
- MMC/SD card is implemented in the XPT layer, but cannot be
+ the MMC/SD card is implemented in the XPT layer, but cannot be
tested with real hardware because of the lack of any device
drivers that implement peripheral drivers and SIMs for CAM
- MMC. The plan is to use a modified version of BeagleBone
- Black SDHCI controller driver for SIM and a modified version
+ MMC. The plan is to use a modified version of the BeagleBone
+ Black SDHCI controller driver for the SIM and a modified version
of <tt>mmcsd(4)</tt> as a peripheral driver.</task>
<task>Marvell SDIO WiFi: connect to the &os; network stack,
@@ -1000,7 +1001,6 @@
The FreeBSD Foundation
</sponsor>
- <help></help>
</project>
<project cat='kern'>
@@ -1165,9 +1165,9 @@
cycle is becoming an imperative.</task>
<task>We need testers who can run development versions of pkg in
- as many distinct types of use-case as possible, and feedback
- their experiences via the freebsd-pkg at freebsd.org mailing list
- or our issues list on github.</task>
+ as many distinct types of use-cases as possible, and report
+ feedback from their experiences to the freebsd-pkg at freebsd.org
+ mailing list or our issues list on github.</task>
</help>
</project>
@@ -1204,8 +1204,8 @@
This required modifications to
<tt>emulators/i386-wine-devel</tt> so that it works with
WITH_NEW_XORG, and the creation of a new port,
- <tt>libtxc_dxtn</tt>, to support texture compression required
- by StarCraft II. We haven't yet had the time to polish
+ <tt>libtxc_dxtn</tt>, to support the texture compression used
+ by StarCraft II. We have not yet had the time to polish
everything, so this still requires manual steps.</p>
<p>The DRM generic code update is ready, but it breaks the
@@ -1214,7 +1214,7 @@
<p>Compared to the previous status report, OpenCL test programs
are running fine now, thanks to upgrades and fixes to libc++
- and Clang. Relevant ports are still not ready to hit the
+ and Clang. The relevant ports are still not ready to hit the
ports tree, unfortunately.</p>
</body>
@@ -1291,8 +1291,8 @@
kernel test suite was done. The issues found were debugged
and fixed.</p>
- <p>Most of the problems are related to the bugs in the
- interaction of vnode and node lifetime, culminating in e.g.,
+ <p>Most of the problems are related to bugs in the
+ interaction of the vnode and node lifetime, culminating in e.g.,
unmount races and dotdot lookup bugs.</p>
</body>
@@ -1319,12 +1319,12 @@
<body>
<p>Analysis of the performance of the latest 9.3 version of
PostgreSQL on &os;-CURRENT has been performed. The issues
- which prevented the good scalability on a 40-core machine were
+ which prevented good scalability on a 40-core machine were
determined, and changes prototyped which solve the
bottlenecks.</p>
<p>The URL above provides a paper which contains a detailed
- explanation of the issues and solutions, together with the
+ explanation of the issues and solutions, together with a
graph demonstrating the effects on scalability.</p>
</body>
@@ -1376,18 +1376,18 @@
frequency of system releases but also frees much developer
time to be spent on different areas of the project.</p>
- <p>Furthermore, a new website and forum is being worked at,
+ <p>Furthermore, a new website and forum is being worked on,
replacing the old-fashioned website that offers only limited
functionality. The new website will be linked to the server
database, providing real-time updates about the project.</p>
- <p>In addition, a new platform for collaborated development is
+ <p>In addition, a new platform for collaborative development is
in the works. A service addon has been created for the GitLab
project, which is a drop-in replacement of the popular GitHub
website. The choice was made to host our own solution and not
rely on GitHub itself. In retrospect this appears to be a
good decision. The recent development where GitHub removed
- projects after DCMA-takedowns being sent is incompatible with
+ projects after DCMA takedowns being sent is incompatible with
the philosophy of free-flow-of-information, which the ZFSguru
project is a strong proponent of. By hosting our own
solution, we have avoided any dependency on third party
@@ -1402,12 +1402,12 @@
web-interface. This functionality provides an easy way to
upgrade the current system by performing a new clean
installation, but migrate all relevant configuration to the
- new installation. It also allows to 'backup' all system
+ new installation. It also allows to backup all system
configuration in a single file to be stored on a different
machine should things go awry.</p>
<p>A longer version of this status report giving a wider
- perspective on the project, can be found at the
+ perspective on the project can be found at the
<quote>stateoftheproject</quote> link.</p>
</body>
</project>
@@ -1453,13 +1453,13 @@
been allocated, a total of 16 projects were selected to
participate in Google Summer of Code 2014 with &os;.</p>
- <p>Projects selected cover a wide range of areas within &os;,
+ <p>The projects selected span a wide range of areas within &os;,
covering both the base system and ports infrastructure,
userland and kernel. We have students working on firewall
optimisation, ports packaging tools, embedded systems,
debugging infrastructure, improved Unicode support,
enhancements to the loader and to the installer, and several
- other areas of work. We are just over half way through the
+ other areas of work. We are just over halfway through the
allocated time this year, and are very much looking forward to
integrating code produced by these projects into &os;.</p>
@@ -1503,7 +1503,7 @@
while the PR count is slightly below 1800.</p>
<p>In Q2 we added three new committers, took in one commit bit
- for safe keeping, and reinstated one commit bit.</p>
+ for safekeeping, and reinstated one commit bit.</p>
<p>In May, &a.tabthorpe; was replaced by &a.culot; as portmgr
secretary, and &a.swills; became a member of the portmgr
@@ -1592,7 +1592,7 @@
integrate with the Lightweight Directory Access Protocol
(LDAP) service.</p>
- <p>The project is at early testing stage. A patch will be
+ <p>The project is at the early testing stage. A patch will be
released as part of a broader call for testing after
additional review on some critical components (in particular,
the autofs filesystem). After fixing reported problems, the
More information about the svn-doc-all
mailing list