svn commit: r44528 - head/en_US.ISO8859-1/htdocs/news/status
Warren Block
wblock at FreeBSD.org
Fri Apr 11 02:10:57 UTC 2014
Author: wblock
Date: Fri Apr 11 02:10:56 2014
New Revision: 44528
URL: http://svnweb.freebsd.org/changeset/doc/44528
Log:
Whitespace-only fixes, translators please ignore.
Modified:
head/en_US.ISO8859-1/htdocs/news/status/report-2014-01-2014-03.xml
Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2014-01-2014-03.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2014-01-2014-03.xml Fri Apr 11 01:25:22 2014 (r44527)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2014-01-2014-03.xml Fri Apr 11 02:10:56 2014 (r44528)
@@ -12,13 +12,15 @@
<title>Introduction</title>
<p>This report covers &os;-related projects between January and
- March 2014. This is the first of four reports planned for 2014.</p>
+ March 2014. This is the first of four reports planned for
+ 2014.</p>
<!-- XXX: Add introduction -->
<!-- XXX: Keep the number of entries updated -->
- <p>Thanks to all the reporters for the excellent work! This report
- contains 38 entries and we hope you enjoy reading it.</p>
+
+ <p>Thanks to all the reporters for the excellent work! This
+ report contains 38 entries and we hope you enjoy reading it.</p>
<p>The deadline for submissions covering between April and
June 2014 is July 7th, 2014.</p>
@@ -92,11 +94,11 @@
<p>Chromium is the open source web browser project from which
Google Chrome draws its source code. The browsers share the
majority of code and features, though there are some minor
- differences in features and they have different licensing. Over
- the last four years, the Chromium team has been busy with
- porting Chromium to &os;. This involves patching the browser so
- that it runs on &os;, tracking and documenting security updates,
- and merging patches back upstream.</p>
+ differences in features and they have different licensing.
+ Over the last four years, the Chromium team has been busy with
+ porting Chromium to &os;. This involves patching the browser
+ so that it runs on &os;, tracking and documenting security
+ updates, and merging patches back upstream.</p>
<p>While there are already several browsers available for &os;,
advantages of Chromium are:</p>
@@ -112,27 +114,28 @@
within a single weekend.</li>
</ul>
- <p>George Liaskos and &a.rene; are currently busy with submitting
- the remaining patches specific to &os; back upstream. Apart from
- making future updates easier, it sometimes also improves the
- overall code quality.</p>
+ <p>George Liaskos and &a.rene; are currently busy with
+ submitting the remaining patches specific to &os; back
+ upstream. Apart from making future updates easier, it
+ sometimes also improves the overall code quality.</p>
- <p>&a.jonathan; recently updated the Capsicum patches for Chromium
- and is talking to upstream about them.</p>
+ <p>&a.jonathan; recently updated the Capsicum patches for
+ Chromium and is talking to upstream about them.</p>
</body>
<help>
<task>Advocate &os;. While patches are getting accepted by both
- humans and bots, it is not an official platform so attitude varies
- from developer to developer. While &a.rene; thinks it is a bit
- early, it might be fruitful to investigate what is required to
- make &os; (and possibly OpenBSD) an official platform in terms
- of both hardware and procedures.</task>
-
- <task>If you feel comfortable with large source trees, you can try
- to build the Git version of Chromium on &os;. If you are also
- comfortable with signing Google's Contributor License Agreement,
- you can join in testing and submitting patches upstream.</task>
+ humans and bots, it is not an official platform so attitude
+ varies from developer to developer. While &a.rene; thinks it
+ is a bit early, it might be fruitful to investigate what is
+ required to make &os; (and possibly OpenBSD) an official
+ platform in terms of both hardware and procedures.</task>
+
+ <task>If you feel comfortable with large source trees, you can
+ try to build the Git version of Chromium on &os;. If you are
+ also comfortable with signing Google's Contributor License
+ Agreement, you can join in testing and submitting patches
+ upstream.</task>
</help>
</project>
@@ -173,16 +176,16 @@
<body>
<p>ZFS is one of the premier features of &os;. The current
documentation in the Handbook and elsewhere online is severely
- lacking. Much of the original documentation from Sun and Oracle
- has disappeared, moved, or is about the proprietary version of
- ZFS.</p>
-
- <p>New users have many questions about ZFS and yet there exists a
- great deal more bad advice about ZFS than proper documentation.
- The current ZFS chapter of the &os; Handbook starts off with the
- required steps to configure an i386 machine to run ZFS. This is
- more likely to scare off a new user than to educate them about
- how to properly use ZFS.</p>
+ lacking. Much of the original documentation from Sun and
+ Oracle has disappeared, moved, or is about the proprietary
+ version of ZFS.</p>
+
+ <p>New users have many questions about ZFS and yet there exists
+ a great deal more bad advice about ZFS than proper
+ documentation. The current ZFS chapter of the &os; Handbook
+ starts off with the required steps to configure an i386
+ machine to run ZFS. This is more likely to scare off a new
+ user than to educate them about how to properly use ZFS.</p>
<p>At BSDCan 2013, the process of writing an entirely new
chapter of the Handbook on ZFS was started. Currently this
@@ -193,12 +196,12 @@
ZFS.</p>
<p>The remaining section is the FAQ. To help users address the
- most common problems they might run into with ZFS. It would be
- useful to hear experiences, questions, misconceptions, gotchas,
- stumbling blocks, and suggestions for the FAQ section from other
- users. Also, a use cases section that highlights some of the
- cases where ZFS provides advantages over traditional file
- systems.</p>
+ most common problems they might run into with ZFS. It would
+ be useful to hear experiences, questions, misconceptions,
+ gotchas, stumbling blocks, and suggestions for the FAQ section
+ from other users. Also, a use cases section that highlights
+ some of the cases where ZFS provides advantages over
+ traditional file systems.</p>
<p>Please send suggestions to the <tt>freebsd-doc</tt> mailing
list.</p>
@@ -207,7 +210,8 @@
<sponsor>ScaleEngine, Inc</sponsor>
<help>
- <task>Technical review by Matt Ahrens (co-creator of ZFS).</task>
+ <task>Technical review by Matt Ahrens (co-creator of
+ ZFS).</task>
<task>Improve delegation section.</task>
<task>Improve tuning section, add new sysctls added in
<tt>head</tt>.</task>
@@ -236,15 +240,15 @@
<body>
<p>The &os; Release Engineering Team is responsible for setting
- and publishing release schedules for official project releases of
- &os;, announcing code freezes and maintaining the respective
- branches, among other things.</p>
-
- <p>In early January, the team became aware of several last-minute
- showstopper issues in &os; 10.0, which lead to an extension
- in the final release builds. &os; 10.0-RELEASE was
- announced on January 20, two months behind the original
- schedule.</p>
+ and publishing release schedules for official project releases
+ of &os;, announcing code freezes and maintaining the
+ respective branches, among other things.</p>
+
+ <p>In early January, the team became aware of several
+ last-minute showstopper issues in &os; 10.0, which lead
+ to an extension in the final release builds.
+ &os; 10.0-RELEASE was announced on January 20, two months
+ behind the original schedule.</p>
<p>The schedule for the &os; 9.3-RELEASE cycle has been
written and posted to the website, and the release cycle will
@@ -252,8 +256,8 @@
<p>There is ongoing work to integrate support for embedded
architectures as part of the release build process. At this
- time, support exists for a number of ARM kernels, in particular
- the Raspberry Pi, BeagleBone, and WandBoard.</p>
+ time, support exists for a number of ARM kernels, in
+ particular the Raspberry Pi, BeagleBone, and WandBoard.</p>
</body>
<sponsor>The &os; Foundation</sponsor>
@@ -275,11 +279,11 @@
<body>
<p>The &os; Documentation Engineering Team is responsible for
- defining and following up documentation goals for the committers
- in the Documentation project. The team is pleased to announce a
- new member — &a.wblock;. In early March, the &os;
- Documentation Engineering Team members assumed responsibility
- for the &os; Webmaster Team.</p>
+ defining and following up documentation goals for the
+ committers in the Documentation project. The team is pleased
+ to announce a new member — &a.wblock;. In early March,
+ the &os; Documentation Engineering Team members assumed
+ responsibility for the &os; Webmaster Team.</p>
</body>
</project>
@@ -304,34 +308,35 @@
<body>
<p>Ada is a structured, statically typed, imperative,
wide-spectrum, and object-oriented high-level computer
- programming language, extended from Pascal and other languages,
- originally targeted at embedded and real-time systems. The
- number of Ada ports in the collection has grown significantly
- since the last report six months ago. There are almost 50
- Ada-related ports now, with new ones getting added all the time.</p>
+ programming language, extended from Pascal and other
+ languages, originally targeted at embedded and real-time
+ systems. The number of Ada ports in the collection has grown
+ significantly since the last report six months ago. There are
+ almost 50 Ada-related ports now, with new ones getting added
+ all the time.</p>
<p>The previous plan was to move from the GCC 4.7-based GNAT
- compiler to a GCC 4.8-based one, but finally GCC 4.8 was skipped
- and now a GCC 4.9-based GNAT is the standard Ada compiler, which
- fully supports the new ISO standard, Ada 2012. Moving to a
- newer compiler allowed several important ports like PolyOrb and
- GPRBuild to be upgraded to the latest available versions. In
- fact, almost every Ada port is currently at its most recent
- upstream version.</p>
+ compiler to a GCC 4.8-based one, but finally GCC 4.8 was
+ skipped and now a GCC 4.9-based GNAT is the standard Ada
+ compiler, which fully supports the new ISO standard, Ada 2012.
+ Moving to a newer compiler allowed several important ports
+ like PolyOrb and GPRBuild to be upgraded to the latest
+ available versions. In fact, almost every Ada port is
+ currently at its most recent upstream version.</p>
<p>For non-Windows-based Ada development, &os; and DragonFly are
- now undisputed as the go-to platforms. The other candidates are
- Debian and Fedora, but there are few Ada software on those
- platforms that are not also in the &os; ports tree, but the versions are
- much older. The Ports Collection also features software not found
- anywhere else such as the USAFA's Ironsides DNS server,
- libsparkcrypto, matreshka, GNATDroid (Android cross-compiler) and
- several developer libraries.</p>
+ now undisputed as the go-to platforms. The other candidates
+ are Debian and Fedora, but there are few Ada software on those
+ platforms that are not also in the &os; ports tree, but the
+ versions are much older. The Ports Collection also features
+ software not found anywhere else such as the USAFA's Ironsides
+ DNS server, libsparkcrypto, matreshka, GNATDroid (Android
+ cross-compiler) and several developer libraries.</p>
<p>A desired addition to the Ada ports will be SPARK 2014 (see
- links), which should cement &os; as an option for professional,
- safety-critical application development. This package should
- have its first release by early summer.</p>
+ links), which should cement &os; as an option for
+ professional, safety-critical application development. This
+ package should have its first release by early summer.</p>
</body>
</project>
@@ -385,8 +390,8 @@
</ul>
<p>We also follow development of core components (available in
- your repository). See link for documentation on how to upgrade
- those libraries.</p>
+ your repository). See link for documentation on how to
+ upgrade those libraries.</p>
<ul>
<li>garcon (0.3.0)</li>
@@ -431,13 +436,13 @@
</links>
<body>
- <p>PCI Single Root I/O Virtualization (SR-IOV) is an optional part
- of the PCIe standard that provides hardware acceleration for the
- virtualization of PCIe devices. When SR-IOV is in use, a
- function in a PCI device (known as a Physical Function, or PF)
- will present multiple Virtual PCI Functions (VF) on the PCI bus.
- These VFs are fully independent PCI devices that have
- access to the resources of the PF. For example, on a network
+ <p>PCI Single Root I/O Virtualization (SR-IOV) is an optional
+ part of the PCIe standard that provides hardware acceleration
+ for the virtualization of PCIe devices. When SR-IOV is in
+ use, a function in a PCI device (known as a Physical Function,
+ or PF) will present multiple Virtual PCI Functions (VF) on the
+ PCI bus. These VFs are fully independent PCI devices that have
+ access to the resources of the PF. For example, on a network
interface card, VFs could transmit and receive packets
independent of the PF.</p>
@@ -446,16 +451,17 @@
use PCI passthrough to assign the VFs to the VMs. This would
allow multiple VMs to share access to the PCI device without
having to do any expensive communication with the hypervisor,
- greatly increasing performance of performing I/O from a VM.</p>
+ greatly increasing performance of performing I/O from a
+ VM.</p>
- <p>There are two parts to this project. The first is implementing
- an API in the PCI subsystem for creating VFs and configuring
- standard PCI features like BARs. The second part is updating
- individual drivers for PCI devices that support SR-IOV to
- configure their VFs. For example, a network interface driver
- will typically have to assign a MAC address to a VF and
- configure the interface to route packets destined for that MAC
- address to the VF.</p>
+ <p>There are two parts to this project. The first is
+ implementing an API in the PCI subsystem for creating VFs and
+ configuring standard PCI features like BARs. The second part
+ is updating individual drivers for PCI devices that support
+ SR-IOV to configure their VFs. For example, a network
+ interface driver will typically have to assign a MAC address
+ to a VF and configure the interface to route packets destined
+ for that MAC address to the VF.</p>
<p>At this point only SR-IOV support for the <tt>ixgbe(4)</tt>
driver is planned. The PCI subsystem API is designed to be
@@ -464,12 +470,12 @@
currently not planned due to lack of time and hardware.</p>
<p>At present, <tt>ixgbe(4)</tt> is able to create VFs and the
- <tt>ixgbevf</tt> driver is able to pass traffic. There is still
- a fair amount of work to support VLAN tags, multicast addresses,
- and other features on the VFs. Also, the VF configuration needs
- to be better integrated with the PF initialization path to
- ensure that resets of the PF do not interrupt operation of the
- VFs.</p>
+ <tt>ixgbevf</tt> driver is able to pass traffic. There is
+ still a fair amount of work to support VLAN tags, multicast
+ addresses, and other features on the VFs. Also, the VF
+ configuration needs to be better integrated with the PF
+ initialization path to ensure that resets of the PF do not
+ interrupt operation of the VFs.</p>
</body>
<sponsor>Sandvine, Inc</sponsor>
@@ -501,32 +507,32 @@
the box and during the development of the system. The test
suite is installed into <tt>/usr/tests/</tt> and the
<tt>kyua(1)</tt> command-line tool (<tt>devel/kyua</tt> in the
- Ports Collection) is used to run them. See the project page for
- more details.</p>
+ Ports Collection) is used to run them. See the project page
+ for more details.</p>
<p>Since the last status report, we have been hard at work
- polishing the framework in many different areas. The highlights
- are:</p>
+ polishing the framework in many different areas. The
+ highlights are:</p>
<ul>
<li>A roadmap for the project has been prepared and published,
see links.</li>
<li>Many tests have been added to the test suite thanks to the
- work of various developers and, in particular, a good bunch of
- old tests from <tt>src/tools/regression/</tt> have been
+ work of various developers and, in particular, a good bunch
+ of old tests from <tt>src/tools/regression/</tt> have been
incorporated into the new test suite. As of this writing,
there are 509 test cases continuously running.</li>
- <li>The testing infrastructure in the <tt>stable/10</tt> branch has
- been synced to <tt>head</tt>. It should now be possible to
- seamlessly MFC changes to the stable branch along with their
- tests, if any.</li>
+ <li>The testing infrastructure in the <tt>stable/10</tt>
+ branch has been synced to <tt>head</tt>. It should now be
+ possible to seamlessly MFC changes to the stable branch
+ along with their tests, if any.</li>
<li>The testing cluster, which only issued <tt>amd64</tt>
builds, has been extended to perform <tt>i386</tt> builds as
- well. Additionally, a canary machine has been put in place so
- that changes to the cluster configuration can be properly
+ well. Additionally, a canary machine has been put in place
+ so that changes to the cluster configuration can be properly
validated before deployment.</li>
<li>A tutorial on Kyua and the &os; Test Suite was given at
@@ -534,8 +540,8 @@
public consumption, please consult the links.</li>
<li>Both Kyua's and ATF's upstream sites have been moved to
- GitHub, mostly due to the discontinuation of file downloads in
- Google Code.</li>
+ GitHub, mostly due to the discontinuation of file downloads
+ in Google Code.</li>
</ul>
</body>
@@ -556,8 +562,8 @@
packages, to mention a few examples.</task>
<task>Add JUnit XML output to Kyua for better integration with
- Jenkins. This work is actively ongoing and should be ready for
- prime time at BSDCan 2014.</task>
+ Jenkins. This work is actively ongoing and should be ready
+ for prime time at BSDCan 2014.</task>
</help>
</project>
@@ -580,28 +586,29 @@
<body>
<p>AFS is a distributed network filesystem that originated from
- the Andrew Project at Carnegie-Mellon University. OpenAFS is an
- open-source implementation of the AFS protocol derived from IBM
- AFS, which was released under the IBM Public License. OpenAFS
- on &os; (the <tt>net/openafs</tt> port) is suitable for light
- use, but is not yet production ready.</p>
+ the Andrew Project at Carnegie-Mellon University. OpenAFS is
+ an open-source implementation of the AFS protocol derived from
+ IBM AFS, which was released under the IBM Public License.
+ OpenAFS on &os; (the <tt>net/openafs</tt> port) is suitable
+ for light use, but is not yet production ready.</p>
<p>We got a chance to pick up this porting project after some
- hiatus. Recent work focused on investigating the bugs preventing
- the use of a disk cache for caching file data. An internal
- "lookupname" abstraction was intended to return an unlocked,
- referenced vnode, but instead returned a locked, referenced
- vnode, leading to various failure modes depending on the number
- of kernel debugging options enabled.</p>
+ hiatus. Recent work focused on investigating the bugs
+ preventing the use of a disk cache for caching file data. An
+ internal "lookupname" abstraction was intended to return an
+ unlocked, referenced vnode, but instead returned a locked,
+ referenced vnode, leading to various failure modes depending
+ on the number of kernel debugging options enabled.</p>
</body>
<help>
- <task>Track down an issue involving incorrect reference counts on
- the AFS root vnode that cause warnings on shutdown.</task>
+ <task>Track down an issue involving incorrect reference counts
+ on the AFS root vnode that cause warnings on shutdown.</task>
<task>Audit the locking in all the vnode operations code —
- it is expected that there remain some incorrectly locked areas,
- though none that present visible issues under light load.</task>
+ it is expected that there remain some incorrectly locked
+ areas, though none that present visible issues under light
+ load.</task>
</help>
</project>
@@ -625,18 +632,19 @@
</links>
<body>
- <p>Libvirt is a virtualization library providing a common API for
- various hypervisors (Qemu/KVM, Xen, LXC, and others), and also a
- popular library used by a number of projects. Libvirt 1.2.2,
- released on March, 2014, was the first release to include bhyve
- support. Enabling bhyve support allows consumers to use bhyve
- in libvirt-ready applications without major efforts.</p>
+ <p>Libvirt is a virtualization library providing a common API
+ for various hypervisors (Qemu/KVM, Xen, LXC, and others), and
+ also a popular library used by a number of projects. Libvirt
+ 1.2.2, released on March, 2014, was the first release to
+ include bhyve support. Enabling bhyve support allows
+ consumers to use bhyve in libvirt-ready applications without
+ major efforts.</p>
<p>Currently, libvirt supports almost all essential features of
- bhyve, such as Virtual Machine lifecycle (start, stop), bridged
- networking, and virtio/SATA driver support. The work continues
- to implement more API calls and to cover more of features
- offered by bhyve.</p>
+ bhyve, such as Virtual Machine lifecycle (start, stop),
+ bridged networking, and virtio/SATA driver support. The work
+ continues to implement more API calls and to cover more of
+ features offered by bhyve.</p>
</body>
<help>
@@ -664,28 +672,28 @@
</links>
<body>
- <p>Arm64 is the name of the in-progress port of &os; to the ARMv8
- CPU when it is in AArch64 mode. Until recently, all ARM CPU
- designs were 32-bit only. With the introduction of the ARMv8,
- architecture ARM has added a new 64-bit mode. This new mode has
- been named AArch64.</p>
+ <p>Arm64 is the name of the in-progress port of &os; to the
+ ARMv8 CPU when it is in AArch64 mode. Until recently, all ARM
+ CPU designs were 32-bit only. With the introduction of the
+ ARMv8, architecture ARM has added a new 64-bit mode. This new
+ mode has been named AArch64.</p>
- <p>Progress has been good on getting &os; to build and run on the
- ARM Foundation model. &os; is able to be built for this
+ <p>Progress has been good on getting &os; to build and run on
+ the ARM Foundation model. &os; is able to be built for this
architecture, however it requires a number of external tools
including <tt>objdump(1)</tt> and <tt>ld(1)</tt>. These tools
- are provided by an external copy of binutils until replacements
- can be written.</p>
+ are provided by an external copy of binutils until
+ replacements can be written.</p>
<p>&os; will run the early boot on the Foundation model. The
loader has been ported to the AArch64 UEFI environment and can
load and run the kernel. The kernel is able to create the
initial page tables to be able to run from virtual memory. It
- can then execute C code to parse the memory map provided by the
- loader. This is as far as the kernel currently boots.</p>
+ can then execute C code to parse the memory map provided by
+ the loader. This is as far as the kernel currently boots.</p>
- <p>This work is now happening in the &os; Subversion repository in
- a project branch, see the links.</p>
+ <p>This work is now happening in the &os; Subversion repository
+ in a project branch, see the links.</p>
</body>
<help>
@@ -709,27 +717,26 @@
</contact>
<body>
- <p>&os; has been updated to allow it to use the VFP variant of the
- ARM EABI ABI. The VFP unit is the ARM hardware to perform
- floating-point operations. This changes the ABI to improve the
- performance of code that uses floating-point operations. By
- default, &os; already uses the ARM EABI on all releases from
- 10.0.</p>
+ <p>&os; has been updated to allow it to use the VFP variant of
+ the ARM EABI ABI. The VFP unit is the ARM hardware to perform
+ floating-point operations. This changes the ABI to improve
+ the performance of code that uses floating-point operations.
+ By default, &os; already uses the ARM EABI on all releases
+ from 10.0.</p>
<p>This is important for &os;/arm users running code with
- floating-point operations on ARMv6 or ARMv7 SoC systems.
- It removes the need for the slow software
- floating-point support in <tt>libc</tt>. This is mostly
- compatible with the existing ABI, with the exception of how
- floating-point values are passed into functions. Because no
- floating-point values are passed to the kernel, the
- <tt>armv6</tt> and <tt>armv6hf</tt> kernels will work with
- either userland.</p>
-
- <p>As part of this change, some support functions have been updated to
- use the VFP unit when available. The existing
- <tt>armv6</tt> target architecture will be kept for cases where
- the SoC lacks a VFP unit, or existing binaries that are
+ floating-point operations on ARMv6 or ARMv7 SoC systems. It
+ removes the need for the slow software floating-point support
+ in <tt>libc</tt>. This is mostly compatible with the existing
+ ABI, with the exception of how floating-point values are
+ passed into functions. Because no floating-point values are
+ passed to the kernel, the <tt>armv6</tt> and <tt>armv6hf</tt>
+ kernels will work with either userland.</p>
+
+ <p>As part of this change, some support functions have been
+ updated to use the VFP unit when available. The existing
+ <tt>armv6</tt> target architecture will be kept for cases
+ where the SoC lacks a VFP unit, or existing binaries that are
incompatible with the new ABI.</p>
</body>
@@ -758,31 +765,34 @@
</links>
<body>
- <p>The Linux emulation layer relies on a Linux base
- distribution along with Linux ports of relevant non-base
- software. Fedora 10 was imported in 2006, and it shows
- — current Linux software like Skype 4, Sublime Text 2, or
- even modern games fail to run with the provided libraries.</p>
+ <p>The Linux emulation layer relies on a Linux base distribution
+ along with Linux ports of relevant non-base software. Fedora
+ 10 was imported in 2006, and it shows — current Linux
+ software like Skype 4, Sublime Text 2, or even modern games
+ fail to run with the provided libraries.</p>
<p>CentOS 6.5 was released in December 2013 and will be
- supported until 2017, making it an ideal basis for an
- update to the ports infrastructure. Built upon the work of
- Carlos Jacobo Puga Medina, all ports using Linux have been
- updated to work with either Fedora 10 or CentOS 6.5.</p>
+ supported until 2017, making it an ideal basis for an update
+ to the ports infrastructure. Built upon the work of Carlos
+ Jacobo Puga Medina, all ports using Linux have been updated to
+ work with either Fedora 10 or CentOS 6.5.</p>
<p>The goal of this project is to make CentOS 6.5 the default
- Linux distribution, so that &os; users can enjoy running modern
- Linux binaries without having to resort to virtualization
- à la VirtualBox, or even dual-booting.</p>
+ Linux distribution, so that &os; users can enjoy running
+ modern Linux binaries without having to resort to
+ virtualization à la VirtualBox, or even
+ dual-booting.</p>
</body>
<sponsor>Goldener Grund OÜ</sponsor>
<help>
- <task>Clean up <tt>Mk/bsd.linux-*.mk</tt> and fix errors detected
- in <tt>ports/187786</tt>.</task>
+ <task>Clean up <tt>Mk/bsd.linux-*.mk</tt> and fix errors
+ detected in <tt>ports/187786</tt>.</task>
+
+ <task>Revert making c6 the default (in the git
+ repository).</task>
- <task>Revert making c6 the default (in the git repository).</task>
<task>Testing.</task>
<task>Review patches and import into the ports tree (any help
@@ -823,38 +833,40 @@
<body>
<p>Address space layout randomization (ASLR) is a computer
security technique involved in protection from buffer overflow
- attacks. In order to prevent an attacker from reliably jumping
- to a particular exploited function in memory, ASLR involves
- randomly arranging the positions of key data areas of a program,
- including the base of the executable and the positions of the
- stack, heap, and libraries, in a process' address space.</p>
+ attacks. In order to prevent an attacker from reliably
+ jumping to a particular exploited function in memory, ASLR
+ involves randomly arranging the positions of key data areas of
+ a program, including the base of the executable and the
+ positions of the stack, heap, and libraries, in a process'
+ address space.</p>
<p>We have added ASLR support to all architectures. As the
primary developers behind this feature have the most access to
<tt>amd64</tt>, the focus of development is on the
- <tt>amd64</tt> architecture. Other architectures, such as ARM,
- have known bugs with our current ASLR implementation and we are
- working hard to fix them. We added support for
+ <tt>amd64</tt> architecture. Other architectures, such as
+ ARM, have known bugs with our current ASLR implementation and
+ we are working hard to fix them. We added support for
Position-Independent Executables (PIEs) in a number of
applications in base.</p>
</body>
<help>
<task>Shawn has access to a Raspberry Pi (RPI). PIE is 90%
- broken. Debug and fix major issues on the RPI. The existing NX
- stack protections are not obeyed on RPI. Properly implemented
- ASLR requires NX stack.</task>
+ broken. Debug and fix major issues on the RPI. The existing
+ NX stack protections are not obeyed on RPI. Properly
+ implemented ASLR requires NX stack.</task>
<task>Shawn will be receiving a <tt>sparc64</tt> box on April 6,
2014. He will test ASLR on <tt>sparc64</tt>, identifying and
fixing any bugs that pop up.</task>
- <task>Olivér has identified one or more bugs with the Linuxulator.
- He will be looking into that and fixing those.</task>
-
- <task>Shawn will be cleaning up code and adding more applications
- in base to support PIE. He will also add PIE support to the
- ports framework for general consumption.</task>
+ <task>Olivér has identified one or more bugs with the
+ Linuxulator. He will be looking into that and fixing
+ those.</task>
+
+ <task>Shawn will be cleaning up code and adding more
+ applications in base to support PIE. He will also add PIE
+ support to the ports framework for general consumption.</task>
<task>Shawn will be giving a presentation regarding ASLR at
BSDCan 2014.</task>
@@ -879,24 +891,25 @@
</links>
<body>
- <p>The Unified Extensible Firmware Interface (UEFI) provides boot-
- and run-time services for x86 computers, and is a replacement
- for the legacy BIOS. This project will adapt the &os; loader
- and kernel boot process for compatibility with UEFI firmware,
- found on contemporary servers, desktops, and laptops.</p>
-
- <p>Starting with &a.rpaulo;'s <tt>i386</tt> EFI loader, &a.benno;
- developed a working proof-of-concept <tt>amd64</tt> loader in 2013
- under sponsorship from the &os; Foundation. After refinement,
- that work has now been merged from the <tt>projects/uefi</tt>
- Subversion branch into &os; <tt>head</tt>. The project includes
- the infrastructure to build a UEFI-enabled loader, and the
- kernel-side changes to parse metadata provided by the
- loader.</p>
-
- <p>A number of integration tasks remain, with a plan to have UEFI
- installation and boot support merged to <tt>stable/10</tt> in
- time for &os; 10.1-RELEASE.</p>
+ <p>The Unified Extensible Firmware Interface (UEFI) provides
+ boot- and run-time services for x86 computers, and is a
+ replacement for the legacy BIOS. This project will adapt the
+ &os; loader and kernel boot process for compatibility with
+ UEFI firmware, found on contemporary servers, desktops, and
+ laptops.</p>
+
+ <p>Starting with &a.rpaulo;'s <tt>i386</tt> EFI loader,
+ &a.benno; developed a working proof-of-concept <tt>amd64</tt>
+ loader in 2013 under sponsorship from the &os; Foundation.
+ After refinement, that work has now been merged from the
+ <tt>projects/uefi</tt> Subversion branch into &os;
+ <tt>head</tt>. The project includes the infrastructure to
+ build a UEFI-enabled loader, and the kernel-side changes to
+ parse metadata provided by the loader.</p>
+
+ <p>A number of integration tasks remain, with a plan to have
+ UEFI installation and boot support merged to
+ <tt>stable/10</tt> in time for &os; 10.1-RELEASE.</p>
</body>
<sponsor>The &os; Foundation</sponsor>
@@ -906,7 +919,8 @@
configurations.</task>
<task>Implement chain-loading from UFS/ZFS file systems.</task>
- <task>Integrate UEFI configuration with the &os; installer.</task>
+ <task>Integrate UEFI configuration with the &os;
+ installer.</task>
<task>Support secure boot.</task>
</help>
</project>
@@ -930,8 +944,8 @@
following:</p>
<ul>
- <li>Assimilated master email configurations into a single source
- control repository.</li>
+ <li>Assimilated master email configurations into a single
+ source control repository.</li>
<li>Moved the &os; web server CGI services to a new location
(sponsored).</li>
@@ -942,8 +956,8 @@
<li>Added a Russian <tt>pkg(8)</tt> mirror, hosted by
Yandex.</li>
- <li>Moved the &os; Foundation web services to a new server
- (sponsored).</li>
+ <li>Moved the &os; Foundation web services to a new
+ server (sponsored).</li>
</ul>
</body>
@@ -968,10 +982,10 @@
<body>
<p>KDE is an international free software community producing an
- integrated set of cross-platform applications designed to run on
- Linux, &os;, Solaris, Microsoft Windows, and OS X systems. The
- KDE/&os; Team have continued to improve the experience of KDE
- software and Qt under &os;.</p>
+ integrated set of cross-platform applications designed to run
+ on Linux, &os;, Solaris, Microsoft Windows, and OS X systems.
+ The KDE/&os; Team have continued to improve the experience of
+ KDE software and Qt under &os;.</p>
<p>During this quarter, the team has kept most of the KDE and Qt
ports up-to-date, working on the following releases:</p>
@@ -994,9 +1008,9 @@
<p>A major change has been the deprecation of the KDE3 ports and
the move of the <tt>KDE4_PREFIX</tt> to <tt>LOCALBASE</tt>.
Also, work on Qt5 continues to maturity. &a.rakuco; has been
- working with upstream to ensure Baloo (Nepomuk successor in KDE
- SC 4.13) compiles and runs on non-Linux systems. His work not
- only benefits &os; but other BSDs and OS X.</p>
+ working with upstream to ensure Baloo (Nepomuk successor in
+ KDE SC 4.13) compiles and runs on non-Linux systems. His work
+ not only benefits &os; but other BSDs and OS X.</p>
<p>As usual, the team is always looking for more testers and
porters, so please contact us and visit our home page (see
@@ -1048,9 +1062,9 @@
<body>
<p>Wine is a free and open source software application that aims
to allow applications designed for Microsoft Windows to run on
- Unix-like operating systems, such as &os;. The Wine project has
- been in maintenance mode this quarter and has updated the ports
- for the following versions:</p>
+ Unix-like operating systems, such as &os;. The Wine project
+ has been in maintenance mode this quarter and has updated the
+ ports for the following versions:</p>
<ul>
<li>Stable releases: 1.6.2</li>
@@ -1063,11 +1077,11 @@
</body>
<help>
- <task>See the <q>Open Tasks</q> and <q>Known Problems</q> sections
- on the Wine wiki page.</task>
+ <task>See the <q>Open Tasks</q> and <q>Known Problems</q>
+ sections on the Wine wiki page.</task>
- <task>&os;/<tt>amd64</tt> integration, consult the i386-Wine wiki
- page for the details.</task>
+ <task>&os;/<tt>amd64</tt> integration, consult the i386-Wine
+ wiki page for the details.</task>
<task>Port WoW64 (supporting Windows 32-bit and 64-bit from the
same port) and Wine64.</task>
@@ -1092,11 +1106,12 @@
</links>
<body>
- <p>Chromebook is an ARMv7 Cortex-A15 personal computer powered by
- Samsung Exynos 5 Dual System-on-Chip. As of the current status
- of this project, such laptops can be booted with &os; from USB
- flash — it works stably (including SMP) and it can build
- third-party applications. The display and keyboard work.</p>
+ <p>Chromebook is an ARMv7 Cortex-A15 personal computer powered
+ by Samsung Exynos 5 Dual System-on-Chip. As of the current
+ status of this project, such laptops can be booted with &os;
+ from USB flash — it works stably (including SMP) and it
+ can build third-party applications. The display and keyboard
+ work.</p>
<p>Thanks to &a.grehan; for providing hardware.</p>
</body>
@@ -1148,49 +1163,52 @@
source projects for Continuous Integration (CI). CI allows
developers to commit code to a Source Code Management (SCM)
system such as Subversion, and then have automated programs
- check out, build, and test the code. Jenkins is implemented in
- the Java language.</p>
+ check out, build, and test the code. Jenkins is implemented
+ in the Java language.</p>
- <p>&a.emaste; reviewed some CI work that &a.rodrigc; had done for
- the FreeNAS project with Jenkins, and encouraged him to set up
- something similar for the &os; Project. With the help of the
- &os; Cluster Administration Team, he set up a &os; machine
- running two bhyve virtual machines,
+ <p>&a.emaste; reviewed some CI work that &a.rodrigc; had done
+ for the FreeNAS project with Jenkins, and encouraged him to
+ set up something similar for the &os; Project. With the help
+ of the &os; Cluster Administration Team, he set up a &os;
+ machine running two bhyve virtual machines,
<tt>jenkins-9.FreeBSD.org</tt> and
<tt>jenkins-10.FreeBSD.org</tt>. He set up software builds of
<tt>head</tt> and several <tt>stable</tt> branches on these
machines. The status of these builds is visible on a web
- interface accessible at <tt>jenkins.FreeBSD.org</tt>.
- When any of the builds fail, emails are sent to
- <tt>freebsd-current</tt> or <tt>freebsd-stable</tt>. Emails are
- also sent directly to the list of people who recently committed
- code to Subversion since the last successful build.</p>
-
- <p>As part of the Jenkins setup, &a.rodrigc; encountered problems
- with running Java &os; 9.2 and &os; 10.0. Both problems
- stemmed from changes to the &os; Virtual Memory (VM) subsystem.
- On &os; 9.2-RELEASE, running Jenkins under Java would cause the
- kernel to panic. This was a known problem, and fixed in
- 9.2.-RELEASE-p3. On &os; 10.0-RELEASE, Java processes would
- randomly crash. Disabling the <tt>vm.pmap.pcid_enabled</tt>
- <tt>sysctl(3)</tt> variable seemed to fix the problem. In
- <tt>kern/187238</tt>, Henrik Gulbrandsen submitted fixes to the
- &os; VM to address this problem. &a.kib; committed the fixes
- to <tt>head</tt>, where they are being tested now.</p>
-
- <p>During the setup of the bhyve VMs which run Jenkins processes,
- &a.rodrigc; wrote scripts to start bhyve VMs from the
- <tt>rc.d</tt> bootup scripts, which were then published at
+ interface accessible at <tt>jenkins.FreeBSD.org</tt>. When
+ any of the builds fail, emails are sent to
+ <tt>freebsd-current</tt> or <tt>freebsd-stable</tt>. Emails
+ are also sent directly to the list of people who recently
+ committed code to Subversion since the last successful
+ build.</p>
+
+ <p>As part of the Jenkins setup, &a.rodrigc; encountered
+ problems with running Java &os; 9.2 and &os; 10.0.
+ Both problems stemmed from changes to the &os; Virtual Memory
+ (VM) subsystem. On &os; 9.2-RELEASE, running Jenkins under
+ Java would cause the kernel to panic. This was a known
+ problem, and fixed in 9.2.-RELEASE-p3. On &os; 10.0-RELEASE,
+ Java processes would randomly crash. Disabling the
+ <tt>vm.pmap.pcid_enabled</tt> <tt>sysctl(3)</tt> variable
+ seemed to fix the problem. In <tt>kern/187238</tt>, Henrik
+ Gulbrandsen submitted fixes to the &os; VM to address this
+ problem. &a.kib; committed the fixes to <tt>head</tt>, where
+ they are being tested now.</p>
+
+ <p>During the setup of the bhyve VMs which run Jenkins
+ processes, &a.rodrigc; wrote scripts to start bhyve VMs from
+ the <tt>rc.d</tt> bootup scripts, which were then published at
GitHub.</p>
- <p>On February 19, 2014, &a.rodrigc; notified the &os; developers
- that Jenkins was running in the &os; cluster, and that they
- could look at the web interface to see the status of builds.</p>
+ <p>On February 19, 2014, &a.rodrigc; notified the &os;
+ developers that Jenkins was running in the &os; cluster, and
+ that they could look at the web interface to see the status of
+ builds.</p>
<p>On March 13, 2014, &a.rodrigc; gave a presentation of the
- Jenkins work at the Bay Area &os; User Group (BAFUG) in Mountain
- View, California, USA. Video of the presentation was recorded
- and put online by iXsystems.</p>
+ Jenkins work at the Bay Area &os; User Group (BAFUG) in
+ Mountain View, California, USA. Video of the presentation was
+ recorded and put online by iXsystems.</p>
<p>&a.rodrigc; assembled a team of volunteers,
<tt>jenkins-admin</tt>, to help maintain
@@ -1201,39 +1219,40 @@
<ul>
<li>R. Tyler Croy is both a &os; developer and a Jenkins
developer. He will be working on fixing bugs in Jenkins
- specific to &os;. He is first looking at fixing the libpam4j
- library which is used by Jenkins to interface with the PAM
- system for user authentication. The released version of
- libpam4j does not currently work on &os;.</li>
-
- <li>&a.lwhsu; maintains the <tt>devel/jenkins</tt> port. He set
- up a Jenkins build which runs the scan-build static analyzer
- which is part of LLVM.</li>
+ specific to &os;. He is first looking at fixing the
+ libpam4j library which is used by Jenkins to interface with
+ the PAM system for user authentication. The released
+ version of libpam4j does not currently work on &os;.</li>
+
+ <li>&a.lwhsu; maintains the <tt>devel/jenkins</tt> port. He
+ set up a Jenkins build which runs the scan-build static
+ analyzer which is part of LLVM.</li>
<li>&a.skreuzer; has experience administering Jenkins systems.
He set up several builds on <tt>jenkins.FreeBSD.org</tt>,
including a Jenkins build of the &os; documentation. He is
- looking into using Ansible for automatic provisioning of VMs running Jenkins in
- the &os; cluster.</li>
+ looking into using Ansible for automatic provisioning of VMs
+ running Jenkins in the &os; cluster.</li>
<li>&a.rodrigc; will be running a Continuous Testing working
- group at the &os; Devsummit in Ottawa on May 15, 2014.
- He will also give a Jenkins presentation on May 17, 2014.
- He is interested in working with &a.jmmv; to
- integrate Jenkins and Kyua. They have exchanged
- some emails about this on the <tt>freebsd-testing</tt> list.</li>
+ group at the &os; Devsummit in Ottawa on May 15, 2014. He
+ will also give a Jenkins presentation on May 17, 2014. He
+ is interested in working with &a.jmmv; to integrate Jenkins
+ and Kyua. They have exchanged some emails about this on the
+ <tt>freebsd-testing</tt> list.</li>
<li>&a.swills; maintains the <tt>devel/jenkins-lts</tt> port.
- He has implemented several builds at <tt>jenkins.FreeBSD.org</tt>
- which detect commits to the &os; ports repository, and then
- build the ports tree using Poudrière.</li>
+ He has implemented several builds at
+ <tt>jenkins.FreeBSD.org</tt> which detect commits to the
+ &os; ports repository, and then build the ports tree using
+ Poudrière.</li>
</ul>
<p>At the end of March, &a.novel; reported to
- <tt>jenkins-admin</tt> that he has successfully run the Jenkins
- libvirt plugin with his libvirt modifications to integrate with
- bhyve. He provided a link to a blog posting where he described
- his experience.</p>
+ <tt>jenkins-admin</tt> that he has successfully run the
+ Jenkins libvirt plugin with his libvirt modifications to
+ integrate with bhyve. He provided a link to a blog posting
+ where he described his experience.</p>
</body>
<sponsor>iXsystems, Inc</sponsor>
@@ -1248,16 +1267,19 @@
<task>Set up more Jenkins builds of the &os; ports repository on
different &os; versions.</task>
- <task>Integrate with Kyua, so that Jenkins can run Kyua tests and
- report the results directly in the native Jenkins web UI where
- test results are reported.</task>
+ <task>Integrate with Kyua, so that Jenkins can run Kyua tests
+ and report the results directly in the native Jenkins web UI
+ where test results are reported.</task>
<task>Write scripts which can take a Jenkins build of &os;, and
boot the results in a bhyve VM or on real hardware.</task>
<task>Fix libpam4j on &os;.</task>
- <task>Continuous Testing working group at Devsummit on May 15, 2014</task>
- <task>Jenkins presentation at BSDCan on May 17, 2014</task>
+
+ <task>Continuous Testing working group at Devsummit on May 15,
+ 2014</task>
+
+ <task>Jenkins presentation at BSDCan on May 17, 2014</task>
</help>
</project>
@@ -1279,21 +1301,22 @@
</links>
<body>
- <p>The new &os; in-kernel iSCSI stack was functionally complete in
- &os; 10.0-RELEASE, but ongoing enhancements and bug fixes are
- being committed to &os; <tt>head</tt>, with a plan to merge them
- back to <tt>stable/10</tt> in time for &os; 10.1-RELEASE.</p>
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
More information about the svn-doc-all
mailing list