os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Whitespace-only fixes, translators please ignore. URLs were converted to

Browse source 
single lines to prevent odd mouseover display.
This commit is contained in:
Warren Block 2014-07-18 12:55:50 +00:00
parent 9ee5e86b64
commit 0e0027c816
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=45338
1 changed files with 241 additions and 250 deletions
Download patch file Download diff file Expand all files Collapse all files

491
en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml
View file

@ -114,19 +114,18 @@
</contact>
<links>
<url
href="http://svnweb.freebsd.org/changeset/base/266581">Commit</url>
<url href="http://svnweb.freebsd.org/changeset/base/266581">Commit</url>
</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 <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 loaded separately as
a module. Follow the commit message link to get more
information.
userspace. 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
loaded separately as a module. Follow the commit message link
to get more information.
</p>
</body>
</project>
@ -145,33 +144,35 @@
</contact>
<body>
<p>The &os; RPC stack, used as a base for its NFS server, received
multiple optimizations to improve performance and SMP
scalability. Algorithmic optimizations reduced
processing overhead, while improved locking allowed it to
scale up to at least 40 processor cores without significant
lock congestion. Combined with some other kernel
optimizations, the peak NFS request rate increased
by many times, reaching up to 600K requests per second on
modern hardware.</p>
<p>The &os; RPC stack, used as a base for its NFS server,
received multiple optimizations to improve performance and SMP
scalability. Algorithmic optimizations reduced processing
overhead, while improved locking allowed it to scale up to at
least 40 processor cores without significant lock congestion.
Combined with some other kernel optimizations, the peak NFS
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
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 second.
That rate is sufficient to completely saturate 2x10Gbit
Ethernet links with 4KB requests. For comparison, the port of
net/istgt (user-level iSCSI server) on the same hardware with
an equivalent configuration showed only 100K IOPS.</p>
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
second. That rate is sufficient to completely saturate
2x10Gbit Ethernet links with 4KB requests. For comparison,
the port of net/istgt (user-level iSCSI server) on the same
hardware with an equivalent configuration showed only 100K
IOPS.</p>
<p>There is also ongoing work on improving CTL functionality.
It was already made to support three of four VMware VAAI storage
acceleration primitives (<tt>net/istgt</tt> supports 2), while the goal
is to reach full VAAI support during next months.</p>
It was already made to support three of four VMware VAAI
storage acceleration primitives (<tt>net/istgt</tt> supports
2), while the goal is to reach full VAAI support during next
months.</p>
<p>With all these improvements, and earlier improvements in CAM, GEOM, ZFS,
and a number of other kernel areas coming soon, FreeBSD 10.1 may
become the fastest storage release ever. ;)</p>
<p>With all these improvements, and earlier improvements in CAM,
GEOM, ZFS, and a number of other kernel areas coming soon,
FreeBSD 10.1 may become the fastest storage release ever.
;)</p>
<p>These projects are sponsored by iXsystems, Inc.</p>
</body>
@ -262,8 +263,7 @@
</contact>
<links>
<url href="https://wiki.freebsd.org/Newcons">Project wiki
page</url>
<url href="https://wiki.freebsd.org/Newcons">Project wiki page</url>
</links>
<body>
@ -275,23 +275,26 @@
<p>Since the last <a
href="http://www.freebsd.org/news/status/report-2014-01-2014-03.html#Updated-vt%284%29-System-Console">report</a>,
<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
<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
<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
variable. Users can select the virtual terminal system to use by setting <tt>kern.vty=sc</tt> or
<tt>kern.vty=vt</tt>.</p>
variable. Users can select the virtual terminal system to use
by setting <tt>kern.vty=sc</tt> or <tt>kern.vty=vt</tt>.</p>
<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;&nbsp;10.1-RELEASE.</p>
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;&nbsp;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 to its documentation. Great
thanks to &a.wblock; for that.</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
to its documentation. Great thanks to &a.wblock; for
that.</p>
<p>Major highlights:</p>
@ -395,31 +398,26 @@
</contact>
<links>
<url href="https://wiki.freebsd.org/QemuUserModeHowTo">Overview
of technology</url>
<url href="http://dirty.ysv.freebsd.org/">Status of ports
building</url>
<url href="https://github.com/seanbruno/qemu-bsd-user">Master
repository for collaboration</url>
<url href="https://wiki.freebsd.org/QemuUserModeHowTo">Overview of technology</url>
<url href="http://dirty.ysv.freebsd.org/">Status of ports building</url>
<url href="https://github.com/seanbruno/qemu-bsd-user">Master repository for collaboration</url>
</links>
<body>
<p>The <tt>ports-mgmt/poudriere-devel</tt> port is aware of how to build
ports via an emulator. Configuration of the miscellaneous
binary image activator is required prior to a poudriere-devel
run.</p>
<p>The <tt>ports-mgmt/poudriere-devel</tt> port is aware of how
to build ports via an emulator. Configuration of the
miscellaneous binary image activator is required prior to a
poudriere-devel run.</p>
<p>ARMV6, MIPS32 and MIPS64 packages can be produced via full
emulation. There are several packages that block a full run
of builds. They can be viewed on the "Status of ports building"
link.</p>
of builds. They can be viewed on the "Status of ports
building" link.</p>
<p>On current or latest stable/10:</p>
<p>Clone the github repository, and switch to the bsd-user branch. Then
run:</p>
<p>Clone the github repository, and switch to the bsd-user
branch. Then run:</p>
<p><tt>./configure --static \<br/>
--target-list="arm-bsd-user i386-bsd-user \<br/>
@ -429,8 +427,8 @@
<p><tt>gmake; gmake install</tt></p>
<p>Then set up the <tt>binmiscctl</tt> tools to do some evil hackery to
redirect execution of armv6 binaries to qemu:</p>
<p>Then set up the <tt>binmiscctl</tt> tools to do some evil
hackery to redirect execution of armv6 binaries to qemu:</p>
<p><tt>binmiscctl add armv6 --interpreter \
"/usr/local/bin/qemu-arm" --magic \
@ -463,9 +461,10 @@
</body>
<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 this.</task>
<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
this.</task>
<task>SPARC64 on AMD64 emulation is non-functional and instantly
segfaults. Looking for someone to poke at the bits
@ -474,9 +473,9 @@
<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>
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
failure that manifests itself when building
@ -503,11 +502,8 @@
</contact>
<links>
<url href="https://wiki.FreeBSD.org/Python">The &os; Python Team
Page</url>
<url href="irc://freebsd-python@irc.freenode.net">IRC
channel</url>
<url href="https://wiki.FreeBSD.org/Python">The &os; Python Team Page</url>
<url href="irc://freebsd-python@irc.freenode.net">IRC channel</url>
</links>
<body>
@ -587,8 +583,7 @@
</contact>
<links>
<url href="https://wiki.freebsd.org/UEFI">&os; UEFI wiki
page</url>
<url href="https://wiki.freebsd.org/UEFI">&os; UEFI wiki page</url>
<url href="http://www.freebsd.org/snapshots/">&os;&nbsp;snapshots</url>
</links>
@ -608,14 +603,15 @@
added UEFI support to the &os; installer and release image
creation script.</p>
<p>The EFI framebuffer requires the <tt>vt(4)</tt> system console &mdash;
a framebuffer driver is not implemented for the legacy
<tt>syscons(4)</tt> console. Ed added automatic <tt>vt(4)</tt> selection to the
UEFI boot path.</p>
<p>The EFI framebuffer requires the <tt>vt(4)</tt> system
console &mdash; a framebuffer driver is not implemented for
the legacy <tt>syscons(4)</tt> console. Ed added automatic
<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 <tt>vt(4)</tt>
work to stable/10 to appear in &os; 10.1-RELEASE.</p>
via 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>
<sponsor>The &os; Foundation</sponsor>
@ -658,8 +654,8 @@
<p>In May, a new release policy was published and
presented at the BSDCan developer conference by John Baldwin.
The idea is that each major release branch (for example, 10.X) is
guaranteed to be supported for at least five years, but
The idea is that each major release branch (for example, 10.X)
is guaranteed to be supported for at least five years, but
individual point releases on each branch, like 10.0-RELEASE,
will be issued at regular intervals and only the latest point
release will be supported.</p>
@ -754,7 +750,7 @@
<p>The goal of this work is to enable &os; as a fully supported
compute host for OpenStack using OpenContrail virtualized
networking. The main areas of development are:</p>
networking. The main areas of development are:</p>
<ul>
<li>Libvirt hypervisor driver for bhyve.</li>
@ -810,16 +806,16 @@
<body>
<p>The &os; Foundation is a 501(c)(3) non-profit organization
dedicated to supporting and promoting the &os;&nbsp;Project
and community worldwide. Most of the funding is used to
and community worldwide. Most of the funding is used to
support &os; development projects, conferences and developer
summits, purchase equipment to grow and improve the &os;
infrastructure, and provide legal support for the Project.</p>
<p>We published our third issue of the &os; Journal. We have
over 2700 subscriptions so far. We continued working on the
<p>We published our third issue of the &os; Journal. We have
over 2700 subscriptions so far. We continued working on the
digital edition, which will allow subscribers to read the
magazine in different web browsers, including those than run
on &os;. This will be available for the July/August issue of
on &os;. This will be available for the July/August issue of
the Journal.</p>
<p>We hired Anne Dickison, on a freelance basis, as our new
@ -828,22 +824,22 @@
<p>The annual board meeting was held in Ottawa, Canada, in May.
Directors and officers were elected, and 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
planning. We worked on our vision, core values, project road
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>
<p>We were a Gold+ sponsor for BSDCan, May 16-17 and provided
7 travel grants for developers to attend the conference. We
7 travel grants for developers to attend the conference. We
also were the sponsor for both the developer and vendor
summits.</p>
<p>Justin Gibbs gave a &os; presentation at a &os; user's
internal technology summit. Company visits like this help
internal technology summit. Company visits like this help
users understand the Project structure better and gives us
a chance to communicate what &os; people are working on as
well as learn what different companies are doing with &os;, as
well as what they'd like to see supported. We can then help
well as what they'd like to see supported. We can then help
facilitate collaboration between the companies and &os;
developers.</p>
@ -852,8 +848,8 @@
(texaslinuxfest.org), and SouthEast LinuxFest, June 20-22
(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
<p>Hardware was purchased to support an upgrade at Sentex. A
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>
@ -897,10 +893,10 @@
be included in &os;&nbsp;10.1.</p>
<p>Work continues on the Foundation-sponsored autofs automount
daemon, UEFI boot support, the updated <tt>vt(4)</tt> system video
console, virtual machine images, and the Intel graphics driver
update. Foundation-sponsored work resulted in
226 commits to &os; over the April to June period.</p>
daemon, UEFI boot support, the updated <tt>vt(4)</tt> system
video console, virtual machine images, and the Intel graphics
driver update. Foundation-sponsored work resulted in 226
commits to &os; over the April to June period.</p>
</body>
</project>
@ -918,23 +914,21 @@
</contact>
<links>
<url href="https://wiki.freebsd.org/SDIO">SDIO project page on
&os;&nbsp;Wiki</url>
<url href="https://github.com/kibab/freebsd/tree/mmccam">Source
code</url>
<url href="https://wiki.freebsd.org/SDIO">SDIO project page on &os;&nbsp;Wiki</url>
<url href="https://github.com/kibab/freebsd/tree/mmccam">Source code</url>
</links>
<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
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 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>
peripherals to the 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
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>
@ -942,17 +936,18 @@
<p>The WiFi driver is able to load firmware onto the card and
initialize it. A rewrite of the MMC stack as a transport
layer for the CAM framework is in progress. This will allow
utilization of the well-tested CAM locking model and debug features.</p>
utilization of the well-tested CAM locking model and debug
features.</p>
</body>
<help>
<task>SDIO stack: finish CAM migration. The initialization of
<task>SDIO stack: finish CAM migration. The initialization of
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 of
<tt>mmcsd(4)</tt> as a peripheral driver.</task>
MMC. The plan is to use a modified version of BeagleBone
Black SDHCI controller driver for 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,
write the code to implement required functions (such as
@ -973,11 +968,8 @@
</contact>
<links>
<url
href="http://www.freebsd.org/releases/9.3R/schedule.html">&os;&nbsp;9.3-RELEASE schedule</url>
<url
href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/">&os; development snapshots</url>
<url href="http://www.freebsd.org/releases/9.3R/schedule.html">&os;&nbsp;9.3-RELEASE schedule</url>
<url href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/">&os; development snapshots</url>
</links>
<body>
@ -1026,49 +1018,46 @@
</contact>
<links>
<url href="http://en.wikipedia.org/wiki/L4_microkernel_family">L4
microkernel family</url>
<url href="https://wiki.freebsd.org/201407DevSummit/BSDUserspace">A
brief description of the project on the &os; wiki (short talk
during &os; DevSummit in Cambridge)</url>
<url href="http://en.wikipedia.org/wiki/L4_microkernel_family">L4 microkernel family</url>
<url href="https://wiki.freebsd.org/201407DevSummit/BSDUserspace">A brief description of the project on the &os; wiki (short talk during &os; DevSummit in Cambridge)</url>
</links>
<body>
<p>Fiasco.OC belongs to the L4 microkernel family. A microkernel
provides a bare minimum of services to the applications
running on top of it, unlike traditional kernels that
incorporate complex code like IP stacks and device drivers.
This allows a dramatic decrease in the amount of code
running in the privileged mode of the CPU, achieving higher
security while still providing an acceptable level of
<p>Fiasco.OC belongs to the L4 microkernel family. A
microkernel provides a bare minimum of services to the
applications running on top of it, unlike traditional kernels
that incorporate complex code like IP stacks and device
drivers. This allows a dramatic decrease in the amount of
code running in the privileged mode of the CPU, achieving
higher security while still providing an acceptable level of
performance.</p>
<p>Running an operating system kernel on top of the microkernel
allows leveraging any software that was developed for that
operating system. The OS kernel runs in user-mode side-by-side
with other microkernel applications such as real-time
components. Multiple OSes, each with their userland
operating system. The OS kernel runs in user-mode
side-by-side with other microkernel applications such as
real-time components. Multiple OSes, each with their userland
applications, can even be run in parallel, thus allowing
construction of products where processing of corporate data is
strictly separated from the processing of private data.</p>
<p>The project aims to create a port of &os; to the Fiasco.OC
microkernel, a high performance L4 microkernel
developed by TU Dresden. Existing ports of OpenBSD and
Linux are used as a reference. This will allow the use of
developed by TU Dresden. Existing ports of OpenBSD and
Linux are used as a reference. This will allow the use of
unique &os; features like ZFS in L4-based projects.</p>
</body>
<help>
<task>Finish opensourcing the port of L4OpenBSD/amd64 made by
genua mbh. This is a work in progress.</task>
genua mbh. This is a work in progress.</task>
<task>Publish the sources of the L4&os; port that is largely based
on the L4OpenBSD code.</task>
<task>Publish the sources of the L4&os; port that is largely
based on the L4OpenBSD code.</task>
<task>Improve the port, the first task being adopting the
<tt>pmap(9)</tt> module to work with L4 microkernel memory allocation
services.</task>
<tt>pmap(9)</tt> module to work with L4 microkernel memory
allocation services.</task>
</help>
</project>
@ -1115,27 +1104,27 @@
</contact>
<links>
<url href="https://github.com/freebsd/pkg">The main <tt>pkg(8)</tt> git
repository.</url>
<url href="https://github.com/freebsd/pkg/issues">The preferred
place to raise bug reports concerning <tt>pkg(8)</tt>.</url>
<url href="https://github.com/freebsd/pkg">The main <tt>pkg(8)</tt> git repository.</url>
<url href="https://github.com/freebsd/pkg/issues">The preferred place to raise bug reports concerning <tt>pkg(8)</tt>.</url>
</links>
<body>
<p><tt>pkg(8)</tt> is the new package management tool for &os;. It
is now the only supported package management tool for &os;
<p><tt>pkg(8)</tt> is the new package management tool for &os;.
It is now the only supported package management tool for &os;
releases from 10.0-RELEASE, including the upcoming
9.3-RELEASE. <tt>pkg(8)</tt> is available on all currently supported
releases. Support for the legacy pkg_tools is due to be
discontinued at the beginning of September 2014.</p>
9.3-RELEASE. <tt>pkg(8)</tt> is available on all currently
supported releases. Support for the legacy pkg_tools is due
to be discontinued at the beginning of September 2014.</p>
<p>The release of <tt>pkg(8)</tt> 1.3 is imminent. This includes major
improvements in the dependency solver. Now we can:</p>
<p>The release of <tt>pkg(8)</tt> 1.3 is imminent. This
includes major improvements in the dependency solver. Now we
can:</p>
<ul>
<li>Switch versions of, for example, Perl or PHP and resolve all the
conflicts with packages that depend on them automatically.
No more need to manually switch package origins.</li>
<li>Switch versions of, for example, Perl or PHP and resolve
all the conflicts with packages that depend on them
automatically. No more need to manually switch package
origins.</li>
<li>Deal more gracefully with complex upgrade or install
scenarios.</li>
@ -1156,18 +1145,18 @@
a selection of "foreign" package repositories, such as CPAN or
CTAN or PyPi.</p>
<p>There are plans to use <tt>pkg(8)</tt> to package up the base system.
Along with other benefits, this will allow writing a universal
installer: download one installer image and from
<p>There are plans to use <tt>pkg(8)</tt> to package up the base
system. Along with other benefits, this will allow writing a
universal installer: download one installer image and from
there install any available version of &os;, including
snapshots.</p>
<p>We are also intending to use <tt>pkg(8)</tt> within the ports tree at
package-build time to handle fulfilling build dependencies.
This opens the possibility of installing build-dependencies by
downloading binary packages, which means you can install
a package with customized options with the minimum amount of
time spent compiling anything else.</p>
<p>We are also intending to use <tt>pkg(8)</tt> within the ports
tree at package-build time to handle fulfilling build
dependencies. This opens the possibility of installing
build-dependencies by downloading binary packages, which means
you can install a package with customized options with the
minimum amount of time spent compiling anything else.</p>
</body>
<help>
@ -1194,43 +1183,39 @@
</person>
</contact>
<links>
<url href="https://wiki.freebsd.org/Graphics">Graphics stack
roadmap and supported hardware matrix</url>
<url
href="http://lists.freebsd.org/pipermail/freebsd-announce/2014-July/001570.html">WITH_NEW_XORG
repository announce</url>
<url
href="http://trillian.chruetertee.ch/ports/browser/trunk">Ports-related
development repository</url>
<links>
<url href="https://wiki.freebsd.org/Graphics">Graphics stack roadmap and supported hardware matrix</url>
<url href="http://lists.freebsd.org/pipermail/freebsd-announce/2014-July/001570.html">WITH_NEW_XORG repository announce</url>
<url href="http://trillian.chruetertee.ch/ports/browser/trunk">Ports-related development repository</url>
</links>
<body>
<p>We were generally short on time this quarter. We made less
progress than expected on all fronts.</p>
<p>The alternate <tt>pkg(8)</tt> repository, built with WITH_NEW_XORG, is
now available. This alleviates the need for users to rebuild
their ports with WITH_NEW_XORG. See the announcement, linked
above for further information.</p>
<p>The alternate <tt>pkg(8)</tt> repository, built with
WITH_NEW_XORG, is now available. This alleviates the need for
users to rebuild their ports with WITH_NEW_XORG. See the
announcement, linked above for further information.</p>
<p>Thanks to a contribution from Jan Kokemüller, Radeon 32bit
ioctls are now working on 64bit hosts. This was tested
ioctls are now working on 64bit hosts. This was tested
successfully with Wine and StarCraft II on &os; 9.x and 11.
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
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
everything, so this still requires manual steps.</p>
<p>The DRM generic code update is ready, but it breaks the
current i915 driver. Therefore, the i915 driver must be
current i915 driver. Therefore, the i915 driver must be
updated before anything is committed.</p>
<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 ports
tree, unfortunately.</p>
<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
ports tree, unfortunately.</p>
</body>
<help>
@ -1302,11 +1287,12 @@
</contact>
<body>
<p>Extensive testing of <tt>tmpfs(5)</tt> using the stress2 kernel test
suite was done. The issues found were debugged and fixed.</p>
<p>Extensive testing of <tt>tmpfs(5)</tt> using the stress2
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.
interaction of vnode and node lifetime, culminating in e.g.,
unmount races and dotdot lookup bugs.</p>
<p>This project is sponsored by the FreeBSD Foundation.</p>
@ -1367,7 +1353,7 @@
<body>
<p>ZFSguru is a multifunctional server appliance with a strong
emphasis on storage. ZFSguru began as simple web-interface
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
@ -1375,53 +1361,54 @@
in similar product like FreeNAS and NAS4Free. ZFSguru aims to
be a true multifunctional server appliance that is extremely
easy to setup and can unite both novice and more experienced
users in a single user interface. The modular nature of the
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>Where development in the first quarter of this year brought
drag-and-drop permissions for Samba and NFS, development in
the second quarter focused on strengthening the infrastructure
of the project. A new library and toolkit solution dubbed
of the project. A new library and toolkit solution dubbed
'Mesa' is in the works, providing a cleaner foundation to the
project. A new master server providing secure remote services
is being setup, to be located in a high-speed datacenter. But
project. A new master server providing secure remote services
is being setup, to be located in a high-speed datacenter. But
most importantly, a new system build infrastructure has shown
great progress and will soon be able to provide automated
system builds to our users. This not only improves the
system builds to our users. This not only improves the
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,
replacing the old-fashioned website that offers only limited
functionality. The new website will be linked to the server
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
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 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 projects.</p>
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
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
projects.</p>
<p>It is expected that after the infrastructure of the project
<p>It is expected that after the infrastructure of the project
has been revamped, work on the web-interface itself can
continue. New functionality such as GuruDB and Service
continue. New functionality such as GuruDB and Service
Bulletins provide a tighter connection between the server
infrastructure and the web-interface. The Migration Manager
is one of the last remaining features still missing in the
web-interface. This functionality provides an easy way to
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
<p>A longer version of this status report giving a wider
perspective on the project, can be found at the
<quote>stateoftheproject</quote> link.</p>
</body>
@ -1438,7 +1425,7 @@
</name>
<email>gavin@FreeBSD.org</email>
</person>
<person>
<name>
<given>Glen</given>
@ -1446,7 +1433,7 @@
</name>
<email>gjb@FreeBSD.org</email>
</person>
<person>
<name>
<given>Wojciech</given>
@ -1468,16 +1455,16 @@
been allocated, a total of 16 projects were selected to
participate in Google Summer of Code 2014 with FreeBSD.</p>
<p>Projects selected cover a wide range of areas within FreeBSD,
<p>Projects selected cover a wide range of areas within FreeBSD,
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 allocated time this
year, and are very much looking forward to integrating code
produced by these projects into FreeBSD.</p>
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
allocated time this year, and are very much looking forward to
integrating code produced by these projects into FreeBSD.</p>
<p>This is the tenth time FreeBSD has taken part in Google's
Summer of Code, and we are grateful to Google to have accepted
us as a participating organisation.</p>
@ -1486,17 +1473,19 @@
<project cat='team'>
<title>&os; Port Management Team</title>
<contact>
<person>
<name>
<given>Frederic</given>
<common>Culot</common>
</name>
<email>portmgr-secretary@FreeBSD.org</email>
<name>
<given>Frederic</given>
<common>Culot</common>
</name>
<email>portmgr-secretary@FreeBSD.org</email>
</person>
<person>
<name>&os; Port Management Team</name>
<email>portmgr@FreeBSD.org</email>
<name>&os; Port Management Team</name>
<email>portmgr@FreeBSD.org</email>
</person>
</contact>
@ -1512,29 +1501,30 @@
</links>
<body>
<p>The ports tree slowly approaches the 25,000 ports threshold, while the
PR count is slightly below 1800.</p>
<p>The ports tree slowly approaches the 25,000 ports threshold,
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>
<p>In Q2 we added three new committers, took in one commit bit
for safe keeping, 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 team.</p>
secretary, and &a.swills; became a member of the portmgr
team.</p>
<p>Commencing July 1, the third intake of <tt>portmgr-lurkers</tt>
started active duty on <tt>portmgr</tt> for a four month
duration. The next two candidates are &a.wg; and &a.nivit;.</p>
<p>This quarter also saw the release of the second quarterly branch,
namely 2014Q2. This branch was not only built for 10 (as 2014Q1) but
for 9 as well (both i386 and amd64).</p>
<p>Commencing July 1, the third intake of
<tt>portmgr-lurkers</tt> started active duty on
<tt>portmgr</tt> for a four month duration. The next two
candidates are &a.wg; and &a.nivit;.</p>
<p>This quarter also saw the release of the second quarterly
branch, namely 2014Q2. This branch was not only built for 10
(as 2014Q1) but for 9 as well (both i386 and amd64).</p>
</body>
<help>
<task>As previously noted, many PRs continue to languish, we would
like to see committers dedicate themselves to closing as many
as possible.</task>
<task>As previously noted, many PRs continue to languish, we
would like to see committers dedicate themselves to closing as
many as possible.</task>
</help>
</project>
@ -1556,14 +1546,15 @@
are all welcome additions to the status reports.</p>
<p>The Monthly team has been busy since the last report, with
longtime organizer &a.pgj; having stepped down from the team &mdash;
thank you G&aacute;bor for all your hard work! This has left
something of a void in the preparation of this report, for which
the call for items was issued quite late. To help fill the void,
&a.wblock; and &a.bjk; have been added to the monthly@ team,
joining &a.gjb;, &a.gavin;, &a.emaste;, and the rest of the team
in preparing this report. Special thanks to Glen for doing most
of the work while simultaneously getting 9.3-RELEASE out the door!</p>
longtime organizer &a.pgj; having stepped down from the team
&mdash; thank you G&aacute;bor for all your hard work! This
has left something of a void in the preparation of this
report, for which the call for items was issued quite late.
To help fill the void, &a.wblock; and &a.bjk; have been added
to the monthly@ team, joining &a.gjb;, &a.gavin;, &a.emaste;,
and the rest of the team in preparing this report. Special
thanks to Glen for doing most of the work while simultaneously
getting 9.3-RELEASE out the door!</p>
<p>The next cycle is sooner than you think! The deadline for
submitting entries for the Q3 report is October 7th, 2014.</p>