1022 lines
31 KiB
XML
1022 lines
31 KiB
XML
<?xml version="1.0" encoding="utf-8" ?>
|
|
<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for
|
|
Status Report//EN"
|
|
"http://www.FreeBSD.org/XML/share/xml/statusreport.dtd" >
|
|
|
|
<!-- $FreeBSD$ -->
|
|
|
|
<report>
|
|
<date>
|
|
<month>July-September</month>
|
|
|
|
<year>2014</year>
|
|
</date>
|
|
|
|
<section>
|
|
<title>Introduction</title>
|
|
|
|
<!-- <?ignore -->
|
|
<p><strong>This is a draft of the July-September 2014 status
|
|
report. Please check back after it is finalized, and an
|
|
announcement email is sent to the &os;-Announce mailing
|
|
list.</strong></p>
|
|
<!-- ?> -->
|
|
|
|
<p>This report covers &os;-related projects between July and
|
|
September 2014. This is the third of four reports planned for
|
|
2014.</p>
|
|
|
|
<p>The third quarter of 2014... was a very busy and productive
|
|
time</p>
|
|
|
|
<p>Thanks to all the reporters for the excellent work! This
|
|
report contains 0 entries and we hope you enjoy reading it.</p>
|
|
|
|
<p>The deadline for submissions covering the period from October
|
|
to December 2014 is January 7th, 2015.</p>
|
|
</section>
|
|
|
|
<category>
|
|
<name>team</name>
|
|
|
|
<description>&os; Team Reports</description>
|
|
</category>
|
|
|
|
<category>
|
|
<name>proj</name>
|
|
|
|
<description>Projects</description>
|
|
</category>
|
|
|
|
<category>
|
|
<name>kern</name>
|
|
|
|
<description>Kernel</description>
|
|
</category>
|
|
|
|
<category>
|
|
<name>arch</name>
|
|
|
|
<description>Architectures</description>
|
|
</category>
|
|
|
|
<?ignore
|
|
<category>
|
|
<name>bin</name>
|
|
|
|
<description>Userland Programs</description>
|
|
</category>
|
|
?>
|
|
|
|
<category>
|
|
<name>ports</name>
|
|
|
|
<description>Ports</description>
|
|
</category>
|
|
|
|
<category>
|
|
<name>doc</name>
|
|
|
|
<description>Documentation</description>
|
|
</category>
|
|
|
|
<category>
|
|
<name>misc</name>
|
|
|
|
<description>Miscellaneous</description>
|
|
</category>
|
|
|
|
<project cat='proj'>
|
|
<title>New Automounter</title>
|
|
|
|
<contact>
|
|
<person>
|
|
<name>
|
|
<given>Edward Tomasz</given>
|
|
<common>Napierała</common>
|
|
</name>
|
|
<email>trasz@FreeBSD.org</email>
|
|
</person>
|
|
</contact>
|
|
|
|
<links>
|
|
<url href="https://wiki.freebsd.org/Automounter" />
|
|
<url href="http://people.freebsd.org/~trasz/autofs.pdf" />
|
|
</links>
|
|
|
|
<body>
|
|
<p>Deficiencies in the current automounter, <tt>amd(8)</tt>, are a
|
|
recurring problem reported by many &os; users. A new
|
|
automounter is being developed to address these concerns.</p>
|
|
|
|
<p>The automounter is a cleanroom implementation of
|
|
functionality available in most other Unix systems, using
|
|
proper kernel support implemented via an autofs filesystem.
|
|
The automounter supports a standard map format, and will
|
|
integrate with the Lightweight Directory Access Protocol
|
|
(LDAP) service.</p>
|
|
|
|
<p>The code is ready to use - it has been committed to 11-CURRENT
|
|
and 10-STABLE, and will ship as part of 10.1-RELEASE. There
|
|
is ongoing work on improving performance and fixing possible
|
|
bugs.</p>
|
|
</body>
|
|
|
|
<sponsor>
|
|
The &os; Foundation
|
|
</sponsor>
|
|
|
|
<help></help>
|
|
</project>
|
|
|
|
<project cat='proj'>
|
|
<title>Chelsio iSCSI Offload Support</title>
|
|
|
|
<contact>
|
|
<person>
|
|
<name>
|
|
<given>Sreenivasa</given>
|
|
<common>Honnur</common>
|
|
</name>
|
|
<email>shonnur@chelsio.com</email>
|
|
</person>
|
|
|
|
<person>
|
|
<name>
|
|
<given>Edward Tomasz</given>
|
|
<common>Napierała</common>
|
|
</name>
|
|
<email>trasz@FreeBSD.org</email>
|
|
</person>
|
|
</contact>
|
|
|
|
<links></links>
|
|
|
|
<body>
|
|
<p>
|
|
Building on the new in-kernel iSCSI target and initiator stack
|
|
released in &os; 10.0, Chelsio Communications has begun
|
|
developing an offload interface to take advantage of the
|
|
hardware offload capabilities of Chelsio T4 and T5 10 and 40
|
|
gigabit Ethernet adapters.</p>
|
|
|
|
<p>The code implements hardware PDU offload for both target and
|
|
initiator. The iSCSI stack has been modified to provide
|
|
hardware-independent offload API, allowing offload drivers to
|
|
be loaded as kernel modules, and to provide mechanisms for the
|
|
system administrator to configure this feature. The project
|
|
is entering a testing phase. The code will be released under
|
|
the BSD license and is expected to be completed later in the
|
|
year and ship in &os; 10.2-RELEASE.</p>
|
|
</body>
|
|
|
|
<sponsor>
|
|
Chelsio Communications
|
|
</sponsor>
|
|
|
|
<sponsor>
|
|
The &os; Foundation
|
|
</sponsor>
|
|
|
|
<help>
|
|
<task>
|
|
<p>Complete testing</p>
|
|
</task>
|
|
</help>
|
|
</project>
|
|
|
|
<project cat='docs'>
|
|
<contact>
|
|
<person>
|
|
<name>
|
|
<given>Michael</given>
|
|
<common>Lucas</common>
|
|
</name>
|
|
<email>mwlucas@michaelwlucas.com</email>
|
|
</person>
|
|
</contact>
|
|
|
|
<links>
|
|
<url href="http://blather.michaelwlucas.com/archives/2088">book announcement</url>
|
|
<url href="http://blather.michaelwlucas.com/archives/2119">pre-pub availability announcement</url>
|
|
<url href="https://www.tiltedwindmillpress.com/?product=freebsd-mastery-storage-essentials">in-progress draft</url>
|
|
</links>
|
|
|
|
<body>
|
|
<p>Lucas is working on a series of small &os; books. The
|
|
first one, FreeBSD Mastery: Storage Essentials, is underway,
|
|
and covers GEOM, gpart, MBR, UFS, GELI, GBDE, disk sector
|
|
alignment, and more. You can pre-order the book at a discount
|
|
from his web site, or wait for it to hit print and all major
|
|
ebook retailers.</p>
|
|
|
|
<p>Get status updates on his blog, or check @mwlauthor on
|
|
Twitter.</p>
|
|
</body>
|
|
|
|
<help>
|
|
<task>
|
|
<p>Lucas needs to write faster.</p>
|
|
</task>
|
|
</help>
|
|
</project>
|
|
|
|
<project cat='ports'>
|
|
<title>Xfce</title>
|
|
|
|
<contact>
|
|
<person>
|
|
<name>
|
|
<given>&os; Xfce Team</given>
|
|
</name>
|
|
<email>xfce@FreeBSD.org</email>
|
|
</person>
|
|
</contact>
|
|
|
|
<links>
|
|
<url href="https://wiki.freebsd.org/Xfce" />
|
|
<url href="http://www.redports.org/browser/olivierd/xfce4">devel repo</url>
|
|
<url href="https://people.freebsd.org/~olivierd/xfce4-4.11-screencast.webm">Video showing significant changes</url>
|
|
</links>
|
|
|
|
<body>
|
|
<p>Xfce is a free software desktop environment for Unix and
|
|
Unix-like platforms including &os;. It aims to be fast and
|
|
lightweight while still being visually appealing and easy to
|
|
use.</p>
|
|
|
|
<p>There were no major updates in the ports tree except cosmetic
|
|
changes (fix pkg-plist, switch to USES= libtool, and so
|
|
on).</p>
|
|
|
|
<p>Still, the Xfce team continues to keep each piece of the Xfce
|
|
Desktop up to date. That is why we are working on the next
|
|
stable release (no date scheduled).</p>
|
|
|
|
<p>Major changes will be:</p>
|
|
|
|
<ul>
|
|
<li>Switch to USES</li>
|
|
|
|
<li>Support of GTK2 (default toolkits) and GTK3
|
|
(optional)</li>
|
|
|
|
<li>GNOME like default icons theme</li>
|
|
|
|
<li>Enhance documentation (handbooks, FAQ)</li>
|
|
</ul>
|
|
|
|
<p>Below is a list of current ports in the devel repository (see
|
|
link).</p>
|
|
|
|
<ul>
|
|
<li>deskutils/xfce4-xkb-plugin 0.7.0</li>
|
|
|
|
<li>devel/xfce4-dev-tools 4.11.0</li>
|
|
|
|
<li>misc/xfce4-appfinder 4.11.0</li>
|
|
|
|
<li>multimedia/xfce4-parole 0.6.1 and 0.7.0</li>
|
|
|
|
<li>sysutils/garcon 0.3.0</li>
|
|
|
|
<li>sysutils/xfce4-settings 4.11.3</li>
|
|
|
|
<li>x11/libxfce4menu 4.11.1</li>
|
|
|
|
<li>x11/libxfce4util 4.11.0</li>
|
|
|
|
<li>x11-wm/xfce4-desktop 4.11.8</li>
|
|
|
|
<li>x11-wm/xfce4-panel 4.11.1</li>
|
|
|
|
<li>x11-wm/xfce4-session 4.11.0</li>
|
|
</ul>
|
|
|
|
<p>There are also two new ports</p>
|
|
|
|
<ul>
|
|
<li>deskutils/xfce4-volumed-pulse 0.2.0</li>
|
|
|
|
<li>x11/xfce4-dashboard 0.2.3 and 0.3.2</li>
|
|
</ul>
|
|
|
|
<p>For more details, please see our wiki page in the Links
|
|
section.</p>
|
|
</body>
|
|
|
|
<help>
|
|
<task>
|
|
<p>Finish to patch ACPI helper (xfce4-power-manager).</p>
|
|
</task>
|
|
|
|
<task>
|
|
<p>Continue to work on documentation, especially the Porter's
|
|
Handbook and creating a FAQ).</p>
|
|
</task>
|
|
</help>
|
|
</project>
|
|
|
|
<project cat='docs'>
|
|
<title>ZFS Chapter of the Handbook</title>
|
|
|
|
<contact>
|
|
<person>
|
|
<name>
|
|
<given>Allan</given>
|
|
<common>Jude</common>
|
|
</name>
|
|
|
|
<email>allanjude@FreeBSD.org</email>
|
|
</person>
|
|
|
|
<person>
|
|
<name>
|
|
<given>Benedict</given>
|
|
<common>Reuschling</common>
|
|
</name>
|
|
|
|
<email>bcr@FreeBSD.org</email>
|
|
</person>
|
|
|
|
<person>
|
|
<name>
|
|
<given>Warren</given>
|
|
<common>Block</common>
|
|
</name>
|
|
|
|
<email>wblock@FreeBSD.org</email>
|
|
</person>
|
|
</contact>
|
|
|
|
<links>
|
|
<url href="&base;/doc/en_US.ISO8859-1/books/handbook/zfs.html">ZFS Section of the FreeBSD Handbook</url>
|
|
</links>
|
|
|
|
<body>
|
|
<p>ZFS is one of the premier features of &os; and the quality
|
|
of the documentation should match that of other important
|
|
features. Much of the original documentation from Sun and
|
|
Oracle has disappeared, moved, or is about the proprietary
|
|
version of ZFS. The OpenZFS project does not provide much
|
|
documentation and instead provides users with a few links,
|
|
including the &os; Handbook. New users have many questions
|
|
about ZFS and yet there exists a great deal more bad advice
|
|
about ZFS than proper documentation.</p>
|
|
|
|
<p>After over a year of work, a new ZFS chapter has been added
|
|
to the &os; Handbook. Over 20,000 words describing the
|
|
basics of creating, managing and maintaining a ZFS pool, as
|
|
well as using some of the advanced features like compression,
|
|
deduplication, and delegation. The chapter also contains a
|
|
glossary of terms, explaining a number of the concepts unique
|
|
to ZFS. The chapter also includes documentation of some of
|
|
the many sysctl variables that can be used to tune ZFS.</p>
|
|
|
|
<p>The remaining work is the FAQ section. To help users address
|
|
the most common questions or problems they might face 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 docs mailing list.</p>
|
|
</body>
|
|
|
|
<sponsor>ScaleEngine Inc.</sponsor>
|
|
|
|
<help>
|
|
<task>
|
|
<p>Technical review by Matt Ahrens (co-creator of
|
|
ZFS)</p>
|
|
</task>
|
|
|
|
<task>
|
|
<p>Improve delegation section</p>
|
|
</task>
|
|
|
|
<task>
|
|
<p>Improve tuning section, add recently added sysctls</p>
|
|
</task>
|
|
|
|
<task>
|
|
<p>Add section on jails and the jailed property</p>
|
|
</task>
|
|
|
|
<task>
|
|
<p>Add FAQ section</p>
|
|
</task>
|
|
|
|
<task>
|
|
<p>Add Use Cases section</p>
|
|
</task>
|
|
|
|
<task>
|
|
<p>General editing and review</p>
|
|
</task>
|
|
</help>
|
|
</project>
|
|
|
|
<project cat='proj'>
|
|
<title>Jenkins Continuous Integration for &os;</title>
|
|
|
|
<contact>
|
|
<person>
|
|
<name>
|
|
<given>Craig</given>
|
|
<common>Rodrigues</common>
|
|
</name>
|
|
<email>rodrigc@FreeBSD.org</email>
|
|
</person>
|
|
|
|
<person>
|
|
<name>Jenkins Administrators</name>
|
|
<email>jenkins-admin@FreeBSD.org</email>
|
|
</person>
|
|
|
|
<person>
|
|
<name>&os; Testing</name>
|
|
<email>freebsd-testing@FreeBSD.org</email>
|
|
</person>
|
|
</contact>
|
|
|
|
<links>
|
|
<url href="https://jenkins.freebsd.org">Jenkins CI server in &os; cluster</url>
|
|
<url href="https://wiki.freebsd.org/201405DevSummit/Jenkins">Jenkins working group at DevSummit</url>
|
|
<url href="http://www.bsdcan.org/2014/schedule/events/445.en.html">Jenkins presentation at BSDCan</url>
|
|
<url href="http://clang-analyzer.llvm.org/scan-build.html">clang static analyzer</url>
|
|
<url href="http://scan.freebsd.org">FreeBSD static analysis results</url>
|
|
<url href="http://www.bsdnow.tv/episodes/2014_07_02-base_iso_100">BSD Now episode 44</url>
|
|
<url href="http://www.slideshare.net/CraigRodrigues1/libvirt-bhyve">livirt and bhyve"</url>
|
|
<url href="https://github.com/jmmv/kyua">Kyua testing framework</url>
|
|
<url href="https://issues.jenkins-ci.org/browse/JENKINS-24521">Issue to update Jenkins to JNA 4.1.0 for FreeBSD</url>
|
|
<url href="https://github.com/jenkinsci/jenkins/pull/1387">Pull request #1 to upgrade JNA in Jenkins</url>
|
|
<url href="https://github.com/jenkinsci/jenkins/pull/1410">Pull request #2 to upgrade JNA in Jenkins</url>
|
|
<url href="http://jenkins.mouf.net/job/pkg/">Jenkins job for testing pkg</url>
|
|
<url href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193499">yacc bug found by kyua</url>
|
|
<url href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193246">IPv6 multicast join() problem found by Jenkins</url>
|
|
<url href="https://github.com/rodrigc/kyua/wiki/Quickstart-Guide">Kyua Quickstart Guide</url>
|
|
</links>
|
|
|
|
<body>
|
|
<p>In May, &a.rodrigc; led a working group <em>Continuous
|
|
Integration and Testing with Jenkins for &os;</em> at the
|
|
&os; Devsummit in Ottawa. &a.rodrigc; also gave a Jenkins
|
|
presentation at BSDCan.</p>
|
|
|
|
<p>At BSDCan, &a.rodrigc; had some discussions with &a.jmmv;
|
|
about how to better integrate &os; testing efforts with
|
|
Jenkins and kyua. As a result of this discussion, &a.jmmv;
|
|
enhanced the <tt>kyua</tt> testing framework with a
|
|
<tt>kyua report-junit</tt> command. This command takes kyua
|
|
test results and outputs a test report in JUnit XML format.
|
|
Jenkins can directly import JUnit XML test results and display
|
|
them nicely.</p>
|
|
|
|
<p>In June, &a.rodrigc; was interviewed for episode 44 of BSD
|
|
Now. The interview covered Jenkins and Continuous Integration
|
|
in the &os; project.</p>
|
|
|
|
<p>In July, &a.rodrigc; gave a presentation to the Bay Area &os;
|
|
Users Group (BAFUG), <em>Libvirt and bhyve</em>, based on
|
|
experience he had with those technologies when used with
|
|
Jenkins.</p>
|
|
|
|
<p>&a.lwhsu; set up a Jenkins job to run the LLVM scan-build
|
|
tool to perform static analysis of the &os; code, and make the
|
|
results availalble at <tt>scan.freebsd.org</tt>.</p>
|
|
|
|
<p>&a.swills; modified the Jenkins job which builds
|
|
<tt>pkg(8)</tt> to use the <tt>kyua report-junit</tt> command
|
|
to integrate <tt>pkg(8)</tt> test results in Jenkins.</p>
|
|
|
|
<p>Anthony Williams reported that the version of the Java
|
|
Native Access (JNA) library bundled with Jenkins has problems
|
|
on &os;. This causes problems with Jenkins using libpam and
|
|
other plugins which use JNA. Craig filed JENKINS-24521
|
|
against Jenkins. Craig submitted patches to Jenkins to update
|
|
Jenkins to use JNA 4.1.0, which has fixes for &os;. Github
|
|
pull request 1410 was accepted into Jenkins, while pull
|
|
request 1387 is pending.</p>
|
|
|
|
<p>&a.rodrigc; worked on automatically running the tests in the
|
|
&os; <tt>/usr/tests</tt> directory under Jenkins using the
|
|
<tt>kyua</tt> test framework. &a.rodrigc; provided feedback
|
|
to &a.jmmv; about <tt>kyua</tt> and &a.jmmv; incorporated some
|
|
of the feedback as bugfixes and feature enhancements to
|
|
<tt>kyua</tt>. &a.rodrigc; committed some fixes to &os; to
|
|
eliminate some test failures. One of the tests still results
|
|
in a crash in byacc. This is being tracked in PR 193499.
|
|
Thomas E. Dickey (byacc maintainer) submitted a patch to fix
|
|
the problem, and this has been committed to &os;.</p>
|
|
|
|
<p>&a.rodrigc; analyzed the cause of some startup errors in
|
|
Jenkins when opening a multicast socket. He had some
|
|
discussion with &a.bms; captured in PR 193246. The Java JDK
|
|
depends on functionality in Solaris where it is possible to
|
|
open an IPv4 multicast socket, but with an IPv4 multicast
|
|
address mapped to an IPv6 address. On Linux, there are
|
|
modifications to the JDK itself to work around this. &a.bms;
|
|
said that the work to make the &os; IPv6 stack behave like
|
|
Solaris would require some work.</p>
|
|
|
|
<p>&a.rodrigc; started writing a Kyua Quickstart Guide. This
|
|
guide is meant to help new kyua users who want to write tests
|
|
and run them under kyua. &a.rodrigc; is seeking feedback to
|
|
help improve this guide.</p>
|
|
</body>
|
|
|
|
<help>
|
|
<task>
|
|
<p>Upstream more fixes to Jenkins for &os;, such as JNA
|
|
fixes.</p>
|
|
</task>
|
|
|
|
<task>
|
|
<p>Automate the build of <tt>/usr/tests</tt>.</p>
|
|
</task>
|
|
|
|
<task>
|
|
<p>Set up more builds based on examples from the existing &os;
|
|
Tinderbox.</p>
|
|
</task>
|
|
|
|
<task>
|
|
<p>Get feedback for improving the Kyua Quickstart Guide.</p>
|
|
</task>
|
|
|
|
<task>
|
|
<p>We need more people to join us on
|
|
freebsd-testing@FreeBSD.org and help out. We especially
|
|
need people with devops and scripting experience to help us
|
|
set up more builds and tests. We would also like to
|
|
integrate with other parts of the project, such as
|
|
Phabricator.</p>
|
|
</task>
|
|
</help>
|
|
</project>
|
|
|
|
<project cat='bin'>
|
|
<title>LLVM Address Sanitizer (Asan)</title>
|
|
|
|
<contact>
|
|
<person>
|
|
<name>
|
|
<given>Viktor</given>
|
|
<common>Kuzutov</common>
|
|
</name>
|
|
<email>vkutuzov@accesssoftek.com</email>
|
|
</person>
|
|
</contact>
|
|
|
|
<links>
|
|
<url href="https://code.google.com/p/address-sanitizer/" />
|
|
<url href="http://clang.llvm.org/docs/AddressSanitizer.html" />
|
|
<url href="http://lab.llvm.org:8011/builders/sanitizer_x86_64-freebsd">Buildbot</url>
|
|
<url href="http://lists.freebsd.org/pipermail/svn-src-head/2014-July/060270.html" />
|
|
<url href="http://lists.freebsd.org/pipermail/svn-src-head/2014-July/060504.html" />
|
|
</links>
|
|
|
|
<body>
|
|
<p>The LLVM address sanitizer (Asan) has been ported to &os;.
|
|
The mainline version of LLVM is known to pass all unit and lit
|
|
Asan tests without unexpected failures on &os; 10.0.</p>
|
|
|
|
<p>A buildbot running sanitizers tests under &os; stable/10
|
|
has been established. See the Links section.</p>
|
|
|
|
<p>In order to make it possible to run programs with sanitizers
|
|
checks enabled on &os; a new kernel state named
|
|
<tt>kern.proc_vmmap_skip_resident_count</tt> has been added.
|
|
See the Links section.</p>
|
|
|
|
<p>Note that running Asan tests on stable/10 requires that state
|
|
to be set to 1.</p>
|
|
|
|
<p>A similar work dedicated to add &os; support to the thread
|
|
sanitizer (Tsan) is in progress.</p>
|
|
</body>
|
|
</project>
|
|
|
|
<project cat='soc'>
|
|
<title>&os; Preseed Installation (PXE)</title>
|
|
|
|
<contact>
|
|
<person>
|
|
<name>
|
|
<given>Kamil</given>
|
|
<common>Czekirda</common>
|
|
</name>
|
|
<email>kczekirda@FreeBSD.org</email>
|
|
</person>
|
|
</contact>
|
|
|
|
<links>
|
|
<url href="https://wiki.freebsd.org/SummerOfCode2014/FreeBSD_PXE_preseed" />
|
|
</links>
|
|
|
|
<body>
|
|
<p>This is a Google Summer of code project that aims to provide
|
|
a noninteractive &os; installation from the network. In
|
|
the first part, an implementation was added for scripted
|
|
<tt>bsdinstall(8)</tt>. It supports variables like: KEYMAP,
|
|
HOSTNAME, MIRROR, RELEASE, TIMEZONE, DAEMONS, ROOTPWHASH, and
|
|
USERS. Network configuration, ZFS options, and others are
|
|
also included.</p>
|
|
|
|
<p>Second part of project is about booting the fai (Fully
|
|
Automatic Installer) from network by PXE. Made installer
|
|
distro based on mfsbsd. After boot fai looks for
|
|
"bootfile-name" parameter from DHCP server which tell fai
|
|
where bsdinstall script located is. Fai supports mac-based
|
|
config or default, if mac-based file does not exist.</p>
|
|
</body>
|
|
|
|
<sponsor>
|
|
Google Summer of Code 2014
|
|
</sponsor>
|
|
|
|
<help>
|
|
<task>
|
|
<p>Documentation, including a howto and handbook. The project
|
|
needs more tests in different configurations. Support for
|
|
more than one network interface is planned.</p>
|
|
</task>
|
|
</help>
|
|
</project>
|
|
|
|
<project cat='ports'>
|
|
<title>GNOME/&os;</title>
|
|
|
|
<contact>
|
|
<person>
|
|
<name>
|
|
<common>&os; GNOME Team </common>
|
|
</name>
|
|
<email>gnome@FreeBSD.org</email>
|
|
</person>
|
|
</contact>
|
|
|
|
<links>
|
|
<url href="http://www.freebsd.org/gnome" />
|
|
<url href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" />
|
|
<url href="http://marcuscom.com/downloads/marcusmerge" />
|
|
</links>
|
|
|
|
<body>
|
|
<p>GNOME is a desktop environment and graphical user interface
|
|
that runs on top of a computer operating system. GNOME is
|
|
part of the GNU Project and can be used with various Unix-like
|
|
operating systems, including &os;.</p>
|
|
|
|
<p>The MATE ports were updated to the 1.8 versions.</p>
|
|
|
|
<p>Now that cairo was updated to 1.12 the merge of GNOME 3 has
|
|
started. Currently we are doing test builds to find ports
|
|
broken by the update and pruning ports that do not build
|
|
any more because of incompatible updates.</p>
|
|
|
|
<p>Gustau Perez started preliminary work on the next development
|
|
version of GNOME in MC, to be ready for GNOME 3.15. We will
|
|
skip 3.14 entirely.</p>
|
|
</body>
|
|
|
|
<help>
|
|
<task>
|
|
<p>Finish GNOME 3.12 merge, and start tracking GNOME 3.15
|
|
(development series).</p>
|
|
</task>
|
|
</help>
|
|
</project>
|
|
|
|
<project cat="ports">
|
|
<title>The Graphics Stack on &os;</title>
|
|
|
|
<contact>
|
|
<person>
|
|
<name>
|
|
<common>&os; Graphics team</common>
|
|
</name>
|
|
<email>x11@FreeBSD.org</email>
|
|
</person>
|
|
</contact>
|
|
|
|
<links>
|
|
<url href="https://wiki.freebsd.org/Graphics">Graphics stack roadmap and supported hardware matrix</url>
|
|
<url href="http://trillian.chruetertee.ch/ports/browser/trunk">Graphics stack ports-related development repository</url>
|
|
<url href="http://lists.freebsd.org/pipermail/freebsd-ports-announce/2014-October/000096.html">Removal of legacy X.Org announcement</url>
|
|
<url href="http://wiki.x.org/wiki/Events/XDC2014/">XDC 2014</url>
|
|
</links>
|
|
|
|
<body>
|
|
|
|
<p>The newest graphics stack (that is, ports behind the
|
|
WITH_NEW_XORG knob) was enabled on all architectures. The
|
|
only regression is for users of Intel GPUs and &os; 8.X or
|
|
9.0. Those releases lack the required kernel driver and
|
|
therefore <tt>xf86-video-intel</tt> will not work (the last
|
|
UMS-aware version does not work with xserver 1.12). Users can
|
|
still use <tt>xf86-video-vesa</tt> if they cannot or do not
|
|
want to update their &os; workstation. Owners of Radeon GPUs
|
|
can use <tt>xf86-video-ati-ums</tt> 6.14.6 with
|
|
<tt>xserver</tt> 1.12 if the KMS driver is not available (that
|
|
is, before &os; 9.3).</p>
|
|
|
|
<p>The old graphics stack will be removed with the next update
|
|
to these ports. See the announcement in the Links
|
|
section.</p>
|
|
|
|
<p>Hardware context support was added to the i915 driver in both
|
|
HEAD and 10.1-RELEASE. This will allow us to update libglapi,
|
|
libGL, dri, libEGL and libglesv2 ports to a newer version of
|
|
Mesa. The latest version is already available from our
|
|
development ports tree (see the links section).</p>
|
|
|
|
<p>Cairo was updated to 1.12. This will allow the &os; GNOME
|
|
team to upgrade pango and Gtk+ 3. Unfortunately, the update
|
|
also revealed that xf86-video-intel 2.7.1 was in a much worse
|
|
state than previously assumed.</p>
|
|
|
|
<p>We will attend XDC 2014 (X.Org Developer's Conference) from
|
|
October 8th through 10th in Bordeaux, France. The goal is to
|
|
reconnect with graphics stack developers, mostly working with
|
|
Linux these days. We will give a presentation on the current
|
|
state of this stack on &os;. See the XDC website in the Links
|
|
section for the program and live streaming.</p>
|
|
</body>
|
|
|
|
<help>
|
|
<task>
|
|
<p>See the "Graphics" wiki page for up-to-date
|
|
information.</p>
|
|
</task>
|
|
</help>
|
|
</project>
|
|
|
|
<project cat='proj'>
|
|
<title>ZFSguru</title>
|
|
|
|
<contact>
|
|
<person>
|
|
<name>
|
|
<given>Jason</given>
|
|
<common>Edwards</common>
|
|
</name>
|
|
<email>sub.mesa@gmail.com</email>
|
|
</person>
|
|
</contact>
|
|
|
|
<links>
|
|
<url href="http://zfsguru.com" />
|
|
<url href="http://zfsguru.com/news/stateoftheproject/2014" />
|
|
<url href="http://zfsguru.com/forum/zfsgurudevelopment/876" />
|
|
</links>
|
|
|
|
<body>
|
|
<p>ZFSguru is a multifunctional server appliance with a strong
|
|
emphasis on storage. ZFSguru began as simple web-interface
|
|
frontend to ZFS, but has since grown into a &os; derivative
|
|
with its own infrastructure. The scope of the project has
|
|
also grown with the inclusion of add-on packages that add
|
|
functionality beyond the traditional NAS functionality found
|
|
in similar product like FreeNAS and NAS4Free. ZFSguru aims to
|
|
be a true multifunctional server appliance that is extremely
|
|
easy to set up and can unite both novice and more experienced
|
|
users in a single user interface. The modular nature of the
|
|
project combats the danger of bloat, whilst still allowing
|
|
extended functionality to be easily deployed.</p>
|
|
|
|
<p>The development work in Q3 focused heavily on the new build
|
|
infrastructure. This allows the ZFSguru project to release
|
|
new system images together with addon services at much higher
|
|
frequency and with much less manual intervention. This should
|
|
free up a lot of development time to be spent on the core of
|
|
the project: the web-interface.</p>
|
|
|
|
<p>Furthermore, a new website and forum is being worked at,
|
|
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
|
|
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 have
|
|
been a good decision. The recent development where GitHub
|
|
removed projects after DCMA-takedowns being sent is
|
|
incompatible with the philosophy of free-flow-of-information,
|
|
of which the ZFSguru project is a strong proponent. By
|
|
hosting our own solution, we have avoided any dependency on
|
|
third party projects.</p>
|
|
|
|
<p>The next task will be to introduce a new remote database
|
|
structure, dubbed GuruDB. This will speed up the
|
|
web-interface as well as introduce Service Bulletins which
|
|
address important notifications to our users, as well as
|
|
announce new releases.</p>
|
|
|
|
<p>After GuruDB, the Migration Manager is one of the last
|
|
remaining features still missing in the 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 users 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 the 2014 development progress of the
|
|
ZFSguru project and information specific to the newly-released
|
|
10.1-002 system image can be found in the Links section.</p>
|
|
</body>
|
|
</project>
|
|
|
|
<project cat='ports'>
|
|
<title>&os; Python Ports</title>
|
|
|
|
<contact>
|
|
<person>
|
|
<name>
|
|
<given>&os;</given>
|
|
<common>Python Team</common>
|
|
</name>
|
|
<email>python@FreeBSD.org</email>
|
|
</person>
|
|
</contact>
|
|
|
|
<links>
|
|
<url href="https://wiki.FreeBSD.org/Python">The FreeBSD Python Team Page</url>
|
|
<url href="irc://freebsd-python@irc.freenode.net">IRC channel</url>
|
|
</links>
|
|
|
|
<body>
|
|
<p>The &os; Python team continued to improve the overall
|
|
experience with Python-based software on &os;.</p>
|
|
|
|
<p>During the last quarter, the <tt>bsd.python.mk</tt> bits of
|
|
the ports infrastructure were converted to the more modern
|
|
<tt>USES</tt> format. Several options, such as support for
|
|
<tt>easy_install</tt>, were deprecated or removed to make the
|
|
infrastructure easier to maintain and less complex for
|
|
maintainers.</p>
|
|
|
|
<p>The Python ports were refactored and simplified to improve
|
|
maintenance and to get rid of long-standing issues due to the
|
|
previously complex and error-prone build process.</p>
|
|
|
|
<p>The Python 2 branch was updated to Python 2.7.8 and
|
|
<tt>setuptools</tt> to 5.5.1.</p>
|
|
|
|
<p>With the availability of pkg 1.3, installing Python packages
|
|
and modules for different Python versions is now supported in
|
|
the package management infrastructure. This allows us to
|
|
remove the previously required port duplicates for Python 2
|
|
and Python 3.</p>
|
|
</body>
|
|
|
|
<help>
|
|
<task>
|
|
<p>Retire the Python 3 specific port duplicates</p>
|
|
</task>
|
|
|
|
<task>
|
|
<p>Convert ports to the new <tt>USES</tt> syntax</p>
|
|
</task>
|
|
|
|
<task>
|
|
<p>More tasks can be found on the team's wiki page (see
|
|
Links).</p>
|
|
</task>
|
|
|
|
<task>
|
|
<p>To get involved, interested people can say hello on IRC
|
|
and let us know their areas of interest!</p>
|
|
</task>
|
|
</help>
|
|
</project>
|
|
|
|
<project cat='kern'>
|
|
<title>Updating OpenCrypto</title>
|
|
|
|
<contact>
|
|
<person>
|
|
<name>
|
|
<given>John-Mark</given>
|
|
<common>Gurney</common>
|
|
</name>
|
|
<email>jmg@FreeBSD.org</email>
|
|
</person>
|
|
</contact>
|
|
|
|
<links>
|
|
<url href="https://p4db.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/opencrypto">Source in Perforce</url>
|
|
<url href="http://freebsdfoundation.blogspot.com/2014/08/freebsd-foundation-announces-ipsec.html">FreeBSD Foundation announces IPsec Enhancement Project</url>
|
|
</links>
|
|
|
|
<body>
|
|
<p>The project adds support for AES-GCM and AES-CTR mode to the
|
|
OpenCrypto framework. Both software and AES-NI accelerated
|
|
versions are functional and working. Ermal Luçi (eri@) is
|
|
working on adding support for the additional modes to
|
|
IPsec.</p>
|
|
</body>
|
|
|
|
<sponsor>
|
|
The FreeBSD Foundation
|
|
</sponsor>
|
|
|
|
<sponsor>
|
|
Netgate
|
|
</sponsor>
|
|
|
|
<help>
|
|
<task>
|
|
<p>Create test suite for the most common modes.</p>
|
|
</task>
|
|
</help>
|
|
</project>
|
|
|
|
<project cat='arch'>
|
|
<title>&os; on Newer ARM Boards</title>
|
|
|
|
<contact>
|
|
<person>
|
|
<name>
|
|
<given>Ganbold</given>
|
|
<common>Tsagaankhuu</common>
|
|
</name>
|
|
<email>ganbold@FreeBSD.org</email>
|
|
</person>
|
|
</contact>
|
|
|
|
<links>
|
|
<url href="https://github.com/tsgan/qualcomm">Some preliminary codes for Snapdragon board IFC6410</url>
|
|
</links>
|
|
|
|
<body>
|
|
<p>Work on initial support of the IFC6410 board,which was
|
|
stopped due to bricked bootloader, has been started again.
|
|
This board has the Qualcomm Snapdragon S4 SoC, featuring the
|
|
Krait CPU. This CPU is considered a "platform" for use in
|
|
smartphones, tablets, and smartbook devices. Krait has many
|
|
similarities with the ARM Cortex-A15 CPU and is also based on
|
|
the ARMv7 instruction set. These peripherals are working:</p>
|
|
|
|
<ul>
|
|
<li>Qualcomm High Speed UART driver for MSM 7000/8000 series
|
|
chips (included in <tt>src</tt> tree)</li>
|
|
|
|
<li>Krait Timer</li>
|
|
</ul>
|
|
</body>
|
|
|
|
<help>
|
|
<task>
|
|
<p>Get MMC driver working. May need more help from
|
|
experts.</p>
|
|
</task>
|
|
</help>
|
|
</project>
|
|
|
|
<project cat='team'>
|
|
<title>The &os; Core Team</title>
|
|
|
|
<contact>
|
|
<person>
|
|
<name>&os; Core Team</name>
|
|
<email>core@FreeBSD.org</email>
|
|
</person>
|
|
</contact>
|
|
|
|
<body>
|
|
<p>The &os; Core Team constitutes the project's "Board of
|
|
Directors", responsible for deciding the project's overall
|
|
goals and direction as well as managing specific areas of the
|
|
&os; project landscape.</p>
|
|
|
|
<p>Notable items dealt with by core during this period:</p>
|
|
|
|
<ul>
|
|
<li>Confirmed that DCTCP, although patented by Microsoft, was
|
|
permissible to commit to FreeBSD.</li>
|
|
|
|
<li>Promoted git-beta.freebsd.org out of beta-test to an
|
|
official service, consequently renaming it to
|
|
git.freebsd.org.</li>
|
|
|
|
<li>Mediated between groups of contributors and committers
|
|
adopting different positions on the on-going work to
|
|
introduce ASLR and associated technologies.</li>
|
|
|
|
<li>Worked with the &os; Foundation to obtain a license for
|
|
XenForo, and with the Forum administrators on plans to migrate
|
|
the FreeBSD forums onto the FreeBSD cluster and to switch to
|
|
XenForo.</li>
|
|
</ul>
|
|
|
|
<p>During this period, three commit bits were granted, and two
|
|
commit bits were taken in for safe keeping.</p>
|
|
</body>
|
|
</project>
|
|
</report>
|