Whitespace-only fixes, translators please ignore. URLs were converted to
single lines to prevent odd mouseover display.
This commit is contained in:
Warren Block
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
|
|
@ -114,19 +114,18 @@
|
||||||
</contact>
|
</contact>
|
||||||
|
|
||||||
<links>
|
<links>
|
||||||
<url
|
<url href="http://svnweb.freebsd.org/changeset/base/266581">Commit</url>
|
||||||
href="http://svnweb.freebsd.org/changeset/base/266581">Commit</url>
|
|
||||||
</links>
|
</links>
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
<p>The so-called "CUSE4BSD" has been imported into the base
|
<p>The so-called "CUSE4BSD" has been imported into the base
|
||||||
system of &os;-11. CUSE is short for character device in
|
system of &os;-11. CUSE is short for character device in
|
||||||
userspace. The CUSE library is a wrapper for the <tt>devfs(8)</tt>
|
userspace. The CUSE library is a wrapper for the
|
||||||
kernel functionality which is exposed through /dev/cuse. In
|
<tt>devfs(8)</tt> kernel functionality which is exposed
|
||||||
order to function, the CUSE kernel code must either be enabled
|
through /dev/cuse. In order to function, the CUSE kernel code
|
||||||
in the kernel configuration file or loaded separately as
|
must either be enabled in the kernel configuration file or
|
||||||
a module. Follow the commit message link to get more
|
loaded separately as a module. Follow the commit message link
|
||||||
information.
|
to get more information.
|
||||||
</p>
|
</p>
|
||||||
</body>
|
</body>
|
||||||
</project>
|
</project>
|
||||||
|
|
@ -145,33 +144,35 @@
|
||||||
</contact>
|
</contact>
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
<p>The &os; RPC stack, used as a base for its NFS server, received
|
<p>The &os; RPC stack, used as a base for its NFS server,
|
||||||
multiple optimizations to improve performance and SMP
|
received multiple optimizations to improve performance and SMP
|
||||||
scalability. Algorithmic optimizations reduced
|
scalability. Algorithmic optimizations reduced processing
|
||||||
processing overhead, while improved locking allowed it to
|
overhead, while improved locking allowed it to scale up to at
|
||||||
scale up to at least 40 processor cores without significant
|
least 40 processor cores without significant lock congestion.
|
||||||
lock congestion. Combined with some other kernel
|
Combined with some other kernel optimizations, the peak NFS
|
||||||
optimizations, the peak NFS request rate increased
|
request rate increased by many times, reaching up to 600K
|
||||||
by many times, reaching up to 600K requests per second on
|
requests per second on modern hardware.</p>
|
||||||
modern hardware.</p>
|
|
||||||
|
|
||||||
<p>The CAM Target Layer (CTL), used as base for new kernel iSCSI
|
<p>The CAM Target Layer (CTL), used as base for new kernel iSCSI
|
||||||
server, also received a series of locking optimizations which allowed
|
server, also received a series of locking optimizations which
|
||||||
its peak request rate to increase from ~200K to ~600K IOPS
|
allowed its peak request rate to increase from ~200K to ~600K
|
||||||
with the potential of reaching a rate of 1M requests per second.
|
IOPS with the potential of reaching a rate of 1M requests per
|
||||||
That rate is sufficient to completely saturate 2x10Gbit
|
second. That rate is sufficient to completely saturate
|
||||||
Ethernet links with 4KB requests. For comparison, the port of
|
2x10Gbit Ethernet links with 4KB requests. For comparison,
|
||||||
net/istgt (user-level iSCSI server) on the same hardware with
|
the port of net/istgt (user-level iSCSI server) on the same
|
||||||
an equivalent configuration showed only 100K IOPS.</p>
|
hardware with an equivalent configuration showed only 100K
|
||||||
|
IOPS.</p>
|
||||||
|
|
||||||
<p>There is also ongoing work on improving CTL functionality.
|
<p>There is also ongoing work on improving CTL functionality.
|
||||||
It was already made to support three of four VMware VAAI storage
|
It was already made to support three of four VMware VAAI
|
||||||
acceleration primitives (<tt>net/istgt</tt> supports 2), while the goal
|
storage acceleration primitives (<tt>net/istgt</tt> supports
|
||||||
is to reach full VAAI support during next months.</p>
|
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,
|
<p>With all these improvements, and earlier improvements in CAM,
|
||||||
and a number of other kernel areas coming soon, FreeBSD 10.1 may
|
GEOM, ZFS, and a number of other kernel areas coming soon,
|
||||||
become the fastest storage release ever. ;)</p>
|
FreeBSD 10.1 may become the fastest storage release ever.
|
||||||
|
;)</p>
|
||||||
|
|
||||||
<p>These projects are sponsored by iXsystems, Inc.</p>
|
<p>These projects are sponsored by iXsystems, Inc.</p>
|
||||||
</body>
|
</body>
|
||||||
|
|
@ -262,8 +263,7 @@
|
||||||
</contact>
|
</contact>
|
||||||
|
|
||||||
<links>
|
<links>
|
||||||
<url href="https://wiki.freebsd.org/Newcons">Project wiki
|
<url href="https://wiki.freebsd.org/Newcons">Project wiki page</url>
|
||||||
page</url>
|
|
||||||
</links>
|
</links>
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
|
|
@ -275,23 +275,26 @@
|
||||||
|
|
||||||
<p>Since the last <a
|
<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>,
|
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> gained the ability to make early driver
|
||||||
<tt>vt(4)</tt> selects the best successfully-probed driver before
|
selection. <tt>vt(4)</tt> selects the best
|
||||||
most other kernel subsystems. Also, to make easy migration from
|
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
|
<tt>syscons(4)</tt> to <tt>vt(4)</tt>, multiple virtual
|
||||||
terminal subsystems in the kernel are now supported. It is
|
terminal subsystems in the kernel are now supported. It is
|
||||||
controlled by a small module with just one kernel environment
|
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
|
variable. Users can select the virtual terminal system to use
|
||||||
<tt>kern.vty=vt</tt>.</p>
|
by setting <tt>kern.vty=sc</tt> or <tt>kern.vty=vt</tt>.</p>
|
||||||
|
|
||||||
<p>The GENERIC kernel configuration for the amd64 and i386
|
<p>The GENERIC kernel configuration for the amd64 and i386
|
||||||
platforms now includes both <tt>syscons(4)</tt> and <tt>vt(4)</tt>
|
platforms now includes both <tt>syscons(4)</tt> and
|
||||||
by default. This configuration is also planned to be in the
|
<tt>vt(4)</tt> by default. This configuration is also planned
|
||||||
next 10-STABLE release and &os; 10.1-RELEASE.</p>
|
to be in the next 10-STABLE release and
|
||||||
|
&os; 10.1-RELEASE.</p>
|
||||||
|
|
||||||
<p>The project finally received a man page, so now <tt>vt(4)</tt> is not
|
<p>The project finally received a man page, so now
|
||||||
only the project name, but also a link to its documentation. Great
|
<tt>vt(4)</tt> is not only the project name, but also a link
|
||||||
thanks to &a.wblock; for that.</p>
|
to its documentation. Great thanks to &a.wblock; for
|
||||||
|
that.</p>
|
||||||
|
|
||||||
<p>Major highlights:</p>
|
<p>Major highlights:</p>
|
||||||
|
|
||||||
|
|
@ -395,31 +398,26 @@
|
||||||
</contact>
|
</contact>
|
||||||
|
|
||||||
<links>
|
<links>
|
||||||
<url href="https://wiki.freebsd.org/QemuUserModeHowTo">Overview
|
<url href="https://wiki.freebsd.org/QemuUserModeHowTo">Overview of technology</url>
|
||||||
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="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>
|
</links>
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
<p>The <tt>ports-mgmt/poudriere-devel</tt> port is aware of how to build
|
<p>The <tt>ports-mgmt/poudriere-devel</tt> port is aware of how
|
||||||
ports via an emulator. Configuration of the miscellaneous
|
to build ports via an emulator. Configuration of the
|
||||||
binary image activator is required prior to a poudriere-devel
|
miscellaneous binary image activator is required prior to a
|
||||||
run.</p>
|
poudriere-devel run.</p>
|
||||||
|
|
||||||
<p>ARMV6, MIPS32 and MIPS64 packages can be produced via full
|
<p>ARMV6, MIPS32 and MIPS64 packages can be produced via full
|
||||||
emulation. There are several packages that block a full run
|
emulation. There are several packages that block a full run
|
||||||
of builds. They can be viewed on the "Status of ports building"
|
of builds. They can be viewed on the "Status of ports
|
||||||
link.</p>
|
building" link.</p>
|
||||||
|
|
||||||
<p>On current or latest stable/10:</p>
|
<p>On current or latest stable/10:</p>
|
||||||
|
|
||||||
<p>Clone the github repository, and switch to the bsd-user branch. Then
|
<p>Clone the github repository, and switch to the bsd-user
|
||||||
run:</p>
|
branch. Then run:</p>
|
||||||
|
|
||||||
<p><tt>./configure --static \<br/>
|
<p><tt>./configure --static \<br/>
|
||||||
--target-list="arm-bsd-user i386-bsd-user \<br/>
|
--target-list="arm-bsd-user i386-bsd-user \<br/>
|
||||||
|
|
@ -429,8 +427,8 @@
|
||||||
|
|
||||||
<p><tt>gmake; gmake install</tt></p>
|
<p><tt>gmake; gmake install</tt></p>
|
||||||
|
|
||||||
<p>Then set up the <tt>binmiscctl</tt> tools to do some evil hackery to
|
<p>Then set up the <tt>binmiscctl</tt> tools to do some evil
|
||||||
redirect execution of armv6 binaries to qemu:</p>
|
hackery to redirect execution of armv6 binaries to qemu:</p>
|
||||||
|
|
||||||
<p><tt>binmiscctl add armv6 --interpreter \
|
<p><tt>binmiscctl add armv6 --interpreter \
|
||||||
"/usr/local/bin/qemu-arm" --magic \
|
"/usr/local/bin/qemu-arm" --magic \
|
||||||
|
|
@ -463,9 +461,10 @@
|
||||||
</body>
|
</body>
|
||||||
|
|
||||||
<help>
|
<help>
|
||||||
<task>PPC on AMD64 emulation. This is a work in progress as there appear to be some
|
<task>PPC on AMD64 emulation. This is a work in progress as
|
||||||
serious issues running the bsd-user binary on big-endian
|
there appear to be some serious issues running the bsd-user
|
||||||
hardware. Justin Hibbits working on this.</task>
|
binary on big-endian hardware. Justin Hibbits working on
|
||||||
|
this.</task>
|
||||||
|
|
||||||
<task>SPARC64 on AMD64 emulation is non-functional and instantly
|
<task>SPARC64 on AMD64 emulation is non-functional and instantly
|
||||||
segfaults. Looking for someone to poke at the bits
|
segfaults. Looking for someone to poke at the bits
|
||||||
|
|
@ -474,9 +473,9 @@
|
||||||
<task>External Tool Chain, XDEV support. Partial support for
|
<task>External Tool Chain, XDEV support. Partial support for
|
||||||
using an AMD64 tool chain that can output other architecture
|
using an AMD64 tool chain that can output other architecture
|
||||||
(use AMD64 toolchain to build MIPS64 packages). Currently
|
(use AMD64 toolchain to build MIPS64 packages). Currently
|
||||||
tracking a linking issue with <tt>ports-mgmt/pkg</tt>. Thanks to
|
tracking a linking issue with <tt>ports-mgmt/pkg</tt>. Thanks
|
||||||
Warner Losh, Baptiste Daroussin, Dimitry Andric for poking at
|
to Warner Losh, Baptiste Daroussin, Dimitry Andric for poking
|
||||||
bits in here to make the XDEV target useful.</task>
|
at bits in here to make the XDEV target useful.</task>
|
||||||
|
|
||||||
<task>Signal handling, MIPS/ARMV6 target still displays a
|
<task>Signal handling, MIPS/ARMV6 target still displays a
|
||||||
failure that manifests itself when building
|
failure that manifests itself when building
|
||||||
|
|
@ -503,11 +502,8 @@
|
||||||
</contact>
|
</contact>
|
||||||
|
|
||||||
<links>
|
<links>
|
||||||
<url href="https://wiki.FreeBSD.org/Python">The &os; Python Team
|
<url href="https://wiki.FreeBSD.org/Python">The &os; Python Team Page</url>
|
||||||
Page</url>
|
<url href="irc://freebsd-python@irc.freenode.net">IRC channel</url>
|
||||||
|
|
||||||
<url href="irc://freebsd-python@irc.freenode.net">IRC
|
|
||||||
channel</url>
|
|
||||||
</links>
|
</links>
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
|
|
@ -587,8 +583,7 @@
|
||||||
</contact>
|
</contact>
|
||||||
|
|
||||||
<links>
|
<links>
|
||||||
<url href="https://wiki.freebsd.org/UEFI">&os; UEFI wiki
|
<url href="https://wiki.freebsd.org/UEFI">&os; UEFI wiki page</url>
|
||||||
page</url>
|
|
||||||
<url href="http://www.freebsd.org/snapshots/">&os; snapshots</url>
|
<url href="http://www.freebsd.org/snapshots/">&os; snapshots</url>
|
||||||
</links>
|
</links>
|
||||||
|
|
||||||
|
|
@ -608,14 +603,15 @@
|
||||||
added UEFI support to the &os; installer and release image
|
added UEFI support to the &os; installer and release image
|
||||||
creation script.</p>
|
creation script.</p>
|
||||||
|
|
||||||
<p>The EFI framebuffer requires the <tt>vt(4)</tt> system console —
|
<p>The EFI framebuffer requires the <tt>vt(4)</tt> system
|
||||||
a framebuffer driver is not implemented for the legacy
|
console — a framebuffer driver is not implemented for
|
||||||
<tt>syscons(4)</tt> console. Ed added automatic <tt>vt(4)</tt> selection to the
|
the legacy <tt>syscons(4)</tt> console. Ed added automatic
|
||||||
UEFI boot path.</p>
|
<tt>vt(4)</tt> selection to the UEFI boot path.</p>
|
||||||
|
|
||||||
<p>Snapshots are now built as dual-mode images, and should boot
|
<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>
|
via BIOS and UEFI. Our plan is to merge the UEFI and
|
||||||
work to stable/10 to appear in &os; 10.1-RELEASE.</p>
|
<tt>vt(4)</tt> work to stable/10 to appear in &os;
|
||||||
|
10.1-RELEASE.</p>
|
||||||
</body>
|
</body>
|
||||||
|
|
||||||
<sponsor>The &os; Foundation</sponsor>
|
<sponsor>The &os; Foundation</sponsor>
|
||||||
|
|
@ -658,8 +654,8 @@
|
||||||
|
|
||||||
<p>In May, a new release policy was published and
|
<p>In May, a new release policy was published and
|
||||||
presented at the BSDCan developer conference by John Baldwin.
|
presented at the BSDCan developer conference by John Baldwin.
|
||||||
The idea is that each major release branch (for example, 10.X) is
|
The idea is that each major release branch (for example, 10.X)
|
||||||
guaranteed to be supported for at least five years, but
|
is guaranteed to be supported for at least five years, but
|
||||||
individual point releases on each branch, like 10.0-RELEASE,
|
individual point releases on each branch, like 10.0-RELEASE,
|
||||||
will be issued at regular intervals and only the latest point
|
will be issued at regular intervals and only the latest point
|
||||||
release will be supported.</p>
|
release will be supported.</p>
|
||||||
|
|
@ -754,7 +750,7 @@
|
||||||
|
|
||||||
<p>The goal of this work is to enable &os; as a fully supported
|
<p>The goal of this work is to enable &os; as a fully supported
|
||||||
compute host for OpenStack using OpenContrail virtualized
|
compute host for OpenStack using OpenContrail virtualized
|
||||||
networking. The main areas of development are:</p>
|
networking. The main areas of development are:</p>
|
||||||
|
|
||||||
<ul>
|
<ul>
|
||||||
<li>Libvirt hypervisor driver for bhyve.</li>
|
<li>Libvirt hypervisor driver for bhyve.</li>
|
||||||
|
|
@ -810,16 +806,16 @@
|
||||||
<body>
|
<body>
|
||||||
<p>The &os; Foundation is a 501(c)(3) non-profit organization
|
<p>The &os; Foundation is a 501(c)(3) non-profit organization
|
||||||
dedicated to supporting and promoting the &os; Project
|
dedicated to supporting and promoting the &os; 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
|
support &os; development projects, conferences and developer
|
||||||
summits, purchase equipment to grow and improve the &os;
|
summits, purchase equipment to grow and improve the &os;
|
||||||
infrastructure, and provide legal support for the Project.</p>
|
infrastructure, and provide legal support for the Project.</p>
|
||||||
|
|
||||||
<p>We published our third issue of the &os; Journal. We have
|
<p>We published our third issue of the &os; Journal. We have
|
||||||
over 2700 subscriptions so far. We continued working on the
|
over 2700 subscriptions so far. We continued working on the
|
||||||
digital edition, which will allow subscribers to read the
|
digital edition, which will allow subscribers to read the
|
||||||
magazine in different web browsers, including those than run
|
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>
|
the Journal.</p>
|
||||||
|
|
||||||
<p>We hired Anne Dickison, on a freelance basis, as our new
|
<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.
|
<p>The annual board meeting was held in Ottawa, Canada, in May.
|
||||||
Directors and officers were elected, and did some long term
|
Directors and officers were elected, and did some long term
|
||||||
planning. We worked on our vision, core values, project road
|
planning. We worked on our vision, core values, project road
|
||||||
mapping, and our near term goals. We also met with the core
|
mapping, and our near term goals. We also met with the core
|
||||||
team to discuss roles and responsibilities, project
|
team to discuss roles and responsibilities, project
|
||||||
roadmapping, and what we can do to help the Project more.</p>
|
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
|
<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
|
also were the sponsor for both the developer and vendor
|
||||||
summits.</p>
|
summits.</p>
|
||||||
|
|
||||||
<p>Justin Gibbs gave a &os; presentation at a &os; user's
|
<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
|
users understand the Project structure better and gives us
|
||||||
a chance to communicate what &os; people are working on as
|
a chance to communicate what &os; people are working on as
|
||||||
well as learn what different companies are doing with &os;, 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;
|
facilitate collaboration between the companies and &os;
|
||||||
developers.</p>
|
developers.</p>
|
||||||
|
|
||||||
|
|
@ -852,8 +848,8 @@
|
||||||
(texaslinuxfest.org), and SouthEast LinuxFest, June 20-22
|
(texaslinuxfest.org), and SouthEast LinuxFest, June 20-22
|
||||||
(southeastlinuxfest.org).</p>
|
(southeastlinuxfest.org).</p>
|
||||||
|
|
||||||
<p>Hardware was purchased to support an upgrade at Sentex. A new
|
<p>Hardware was purchased to support an upgrade at Sentex. A
|
||||||
high capacity 1Gbps switch was deployed to allow for more
|
new high capacity 1Gbps switch was deployed to allow for more
|
||||||
systems to be added to the test lab. The main file server and
|
systems to be added to the test lab. The main file server and
|
||||||
development box was upgraded to allow more users in the lab
|
development box was upgraded to allow more users in the lab
|
||||||
simultaneously.</p>
|
simultaneously.</p>
|
||||||
|
|
@ -897,10 +893,10 @@
|
||||||
be included in &os; 10.1.</p>
|
be included in &os; 10.1.</p>
|
||||||
|
|
||||||
<p>Work continues on the Foundation-sponsored autofs automount
|
<p>Work continues on the Foundation-sponsored autofs automount
|
||||||
daemon, UEFI boot support, the updated <tt>vt(4)</tt> system video
|
daemon, UEFI boot support, the updated <tt>vt(4)</tt> system
|
||||||
console, virtual machine images, and the Intel graphics driver
|
video console, virtual machine images, and the Intel graphics
|
||||||
update. Foundation-sponsored work resulted in
|
driver update. Foundation-sponsored work resulted in 226
|
||||||
226 commits to &os; over the April to June period.</p>
|
commits to &os; over the April to June period.</p>
|
||||||
</body>
|
</body>
|
||||||
</project>
|
</project>
|
||||||
|
|
||||||
|
|
@ -918,23 +914,21 @@
|
||||||
</contact>
|
</contact>
|
||||||
|
|
||||||
<links>
|
<links>
|
||||||
<url href="https://wiki.freebsd.org/SDIO">SDIO project page on
|
<url href="https://wiki.freebsd.org/SDIO">SDIO project page on &os; Wiki</url>
|
||||||
&os; Wiki</url>
|
<url href="https://github.com/kibab/freebsd/tree/mmccam">Source code</url>
|
||||||
<url href="https://github.com/kibab/freebsd/tree/mmccam">Source
|
|
||||||
code</url>
|
|
||||||
</links>
|
</links>
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
<p>SDIO is an interface designed as an extension of the existing
|
<p>SDIO is an interface designed as an extension of the existing
|
||||||
SD card standard, which allows the connecting of different
|
SD card standard, which allows the connecting of different
|
||||||
peripherals to the host with a standard SD controller. Peripherals
|
peripherals to the host with a standard SD controller.
|
||||||
currently sold on the general market include WLAN/BT modules,
|
Peripherals currently sold on the general market include
|
||||||
cameras, fingerprint readers, and barcode scanners.
|
WLAN/BT modules, cameras, fingerprint readers, and barcode
|
||||||
Additionally, SDIO is used to connect some peripherals in
|
scanners. Additionally, SDIO is used to connect some
|
||||||
products like Chromebooks and Wandboard. A prototype of the
|
peripherals in products like Chromebooks and Wandboard. A
|
||||||
driver for the Marvell SDIO WLAN/BT (Avastar 88W8787) module
|
prototype of the driver for the Marvell SDIO WLAN/BT (Avastar
|
||||||
is also being developed, using the existing Linux driver as
|
88W8787) module is also being developed, using the existing
|
||||||
the reference.</p>
|
Linux driver as the reference.</p>
|
||||||
|
|
||||||
<p>SDIO card detection and initialization already work, most
|
<p>SDIO card detection and initialization already work, most
|
||||||
needed bus methods are implemented and tested.</p>
|
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
|
<p>The WiFi driver is able to load firmware onto the card and
|
||||||
initialize it. A rewrite of the MMC stack as a transport
|
initialize it. A rewrite of the MMC stack as a transport
|
||||||
layer for the CAM framework is in progress. This will allow
|
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>
|
</body>
|
||||||
|
|
||||||
<help>
|
<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
|
MMC/SD card is implemented in the XPT layer, but cannot be
|
||||||
tested with real hardware because of the lack of any device
|
tested with real hardware because of the lack of any device
|
||||||
drivers that implement peripheral drivers and SIMs for CAM
|
drivers that implement peripheral drivers and SIMs for CAM
|
||||||
MMC. The plan is to use a modified version of BeagleBone Black
|
MMC. The plan is to use a modified version of BeagleBone
|
||||||
SDHCI controller driver for SIM and a modified version of
|
Black SDHCI controller driver for SIM and a modified version
|
||||||
<tt>mmcsd(4)</tt> as a peripheral driver.</task>
|
of <tt>mmcsd(4)</tt> as a peripheral driver.</task>
|
||||||
|
|
||||||
<task>Marvell SDIO WiFi: connect to the &os; network stack,
|
<task>Marvell SDIO WiFi: connect to the &os; network stack,
|
||||||
write the code to implement required functions (such as
|
write the code to implement required functions (such as
|
||||||
|
|
@ -973,11 +968,8 @@
|
||||||
</contact>
|
</contact>
|
||||||
|
|
||||||
<links>
|
<links>
|
||||||
<url
|
<url href="http://www.freebsd.org/releases/9.3R/schedule.html">&os; 9.3-RELEASE schedule</url>
|
||||||
href="http://www.freebsd.org/releases/9.3R/schedule.html">&os; 9.3-RELEASE schedule</url>
|
<url href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/">&os; development snapshots</url>
|
||||||
|
|
||||||
<url
|
|
||||||
href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/">&os; development snapshots</url>
|
|
||||||
</links>
|
</links>
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
|
|
@ -1026,49 +1018,46 @@
|
||||||
</contact>
|
</contact>
|
||||||
|
|
||||||
<links>
|
<links>
|
||||||
<url href="http://en.wikipedia.org/wiki/L4_microkernel_family">L4
|
<url href="http://en.wikipedia.org/wiki/L4_microkernel_family">L4 microkernel family</url>
|
||||||
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="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>
|
</links>
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
<p>Fiasco.OC belongs to the L4 microkernel family. A microkernel
|
<p>Fiasco.OC belongs to the L4 microkernel family. A
|
||||||
provides a bare minimum of services to the applications
|
microkernel provides a bare minimum of services to the
|
||||||
running on top of it, unlike traditional kernels that
|
applications running on top of it, unlike traditional kernels
|
||||||
incorporate complex code like IP stacks and device drivers.
|
that incorporate complex code like IP stacks and device
|
||||||
This allows a dramatic decrease in the amount of code
|
drivers. This allows a dramatic decrease in the amount of
|
||||||
running in the privileged mode of the CPU, achieving higher
|
code running in the privileged mode of the CPU, achieving
|
||||||
security while still providing an acceptable level of
|
higher security while still providing an acceptable level of
|
||||||
performance.</p>
|
performance.</p>
|
||||||
|
|
||||||
<p>Running an operating system kernel on top of the microkernel
|
<p>Running an operating system kernel on top of the microkernel
|
||||||
allows leveraging any software that was developed for that
|
allows leveraging any software that was developed for that
|
||||||
operating system. The OS kernel runs in user-mode side-by-side
|
operating system. The OS kernel runs in user-mode
|
||||||
with other microkernel applications such as real-time
|
side-by-side with other microkernel applications such as
|
||||||
components. Multiple OSes, each with their userland
|
real-time components. Multiple OSes, each with their userland
|
||||||
applications, can even be run in parallel, thus allowing
|
applications, can even be run in parallel, thus allowing
|
||||||
construction of products where processing of corporate data is
|
construction of products where processing of corporate data is
|
||||||
strictly separated from the processing of private data.</p>
|
strictly separated from the processing of private data.</p>
|
||||||
|
|
||||||
<p>The project aims to create a port of &os; to the Fiasco.OC
|
<p>The project aims to create a port of &os; to the Fiasco.OC
|
||||||
microkernel, a high performance L4 microkernel
|
microkernel, a high performance L4 microkernel
|
||||||
developed by TU Dresden. Existing ports of OpenBSD and
|
developed by TU Dresden. Existing ports of OpenBSD and
|
||||||
Linux are used as a reference. This will allow the use of
|
Linux are used as a reference. This will allow the use of
|
||||||
unique &os; features like ZFS in L4-based projects.</p>
|
unique &os; features like ZFS in L4-based projects.</p>
|
||||||
</body>
|
</body>
|
||||||
|
|
||||||
<help>
|
<help>
|
||||||
<task>Finish opensourcing the port of L4OpenBSD/amd64 made by
|
<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
|
<task>Publish the sources of the L4&os; port that is largely
|
||||||
on the L4OpenBSD code.</task>
|
based on the L4OpenBSD code.</task>
|
||||||
|
|
||||||
<task>Improve the port, the first task being adopting the
|
<task>Improve the port, the first task being adopting the
|
||||||
<tt>pmap(9)</tt> module to work with L4 microkernel memory allocation
|
<tt>pmap(9)</tt> module to work with L4 microkernel memory
|
||||||
services.</task>
|
allocation services.</task>
|
||||||
</help>
|
</help>
|
||||||
</project>
|
</project>
|
||||||
|
|
||||||
|
|
@ -1115,27 +1104,27 @@
|
||||||
</contact>
|
</contact>
|
||||||
|
|
||||||
<links>
|
<links>
|
||||||
<url href="https://github.com/freebsd/pkg">The main <tt>pkg(8)</tt> git
|
<url href="https://github.com/freebsd/pkg">The main <tt>pkg(8)</tt> git repository.</url>
|
||||||
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/issues">The preferred
|
|
||||||
place to raise bug reports concerning <tt>pkg(8)</tt>.</url>
|
|
||||||
</links>
|
</links>
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
<p><tt>pkg(8)</tt> is the new package management tool for &os;. It
|
<p><tt>pkg(8)</tt> is the new package management tool for &os;.
|
||||||
is now the only supported package management tool for &os;
|
It is now the only supported package management tool for &os;
|
||||||
releases from 10.0-RELEASE, including the upcoming
|
releases from 10.0-RELEASE, including the upcoming
|
||||||
9.3-RELEASE. <tt>pkg(8)</tt> is available on all currently supported
|
9.3-RELEASE. <tt>pkg(8)</tt> is available on all currently
|
||||||
releases. Support for the legacy pkg_tools is due to be
|
supported releases. Support for the legacy pkg_tools is due
|
||||||
discontinued at the beginning of September 2014.</p>
|
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
|
<p>The release of <tt>pkg(8)</tt> 1.3 is imminent. This
|
||||||
improvements in the dependency solver. Now we can:</p>
|
includes major improvements in the dependency solver. Now we
|
||||||
|
can:</p>
|
||||||
|
|
||||||
<ul>
|
<ul>
|
||||||
<li>Switch versions of, for example, Perl or PHP and resolve all the
|
<li>Switch versions of, for example, Perl or PHP and resolve
|
||||||
conflicts with packages that depend on them automatically.
|
all the conflicts with packages that depend on them
|
||||||
No more need to manually switch package origins.</li>
|
automatically. No more need to manually switch package
|
||||||
|
origins.</li>
|
||||||
|
|
||||||
<li>Deal more gracefully with complex upgrade or install
|
<li>Deal more gracefully with complex upgrade or install
|
||||||
scenarios.</li>
|
scenarios.</li>
|
||||||
|
|
@ -1156,18 +1145,18 @@
|
||||||
a selection of "foreign" package repositories, such as CPAN or
|
a selection of "foreign" package repositories, such as CPAN or
|
||||||
CTAN or PyPi.</p>
|
CTAN or PyPi.</p>
|
||||||
|
|
||||||
<p>There are plans to use <tt>pkg(8)</tt> to package up the base system.
|
<p>There are plans to use <tt>pkg(8)</tt> to package up the base
|
||||||
Along with other benefits, this will allow writing a universal
|
system. Along with other benefits, this will allow writing a
|
||||||
installer: download one installer image and from
|
universal installer: download one installer image and from
|
||||||
there install any available version of &os;, including
|
there install any available version of &os;, including
|
||||||
snapshots.</p>
|
snapshots.</p>
|
||||||
|
|
||||||
<p>We are also intending to use <tt>pkg(8)</tt> within the ports tree at
|
<p>We are also intending to use <tt>pkg(8)</tt> within the ports
|
||||||
package-build time to handle fulfilling build dependencies.
|
tree at package-build time to handle fulfilling build
|
||||||
This opens the possibility of installing build-dependencies by
|
dependencies. This opens the possibility of installing
|
||||||
downloading binary packages, which means you can install
|
build-dependencies by downloading binary packages, which means
|
||||||
a package with customized options with the minimum amount of
|
you can install a package with customized options with the
|
||||||
time spent compiling anything else.</p>
|
minimum amount of time spent compiling anything else.</p>
|
||||||
</body>
|
</body>
|
||||||
|
|
||||||
<help>
|
<help>
|
||||||
|
|
@ -1194,43 +1183,39 @@
|
||||||
</person>
|
</person>
|
||||||
</contact>
|
</contact>
|
||||||
|
|
||||||
<links>
|
<links>
|
||||||
<url href="https://wiki.freebsd.org/Graphics">Graphics stack
|
<url href="https://wiki.freebsd.org/Graphics">Graphics stack roadmap and supported hardware matrix</url>
|
||||||
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
|
<url href="http://trillian.chruetertee.ch/ports/browser/trunk">Ports-related development repository</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>
|
</links>
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
<p>We were generally short on time this quarter. We made less
|
<p>We were generally short on time this quarter. We made less
|
||||||
progress than expected on all fronts.</p>
|
progress than expected on all fronts.</p>
|
||||||
|
|
||||||
<p>The alternate <tt>pkg(8)</tt> repository, built with WITH_NEW_XORG, is
|
<p>The alternate <tt>pkg(8)</tt> repository, built with
|
||||||
now available. This alleviates the need for users to rebuild
|
WITH_NEW_XORG, is now available. This alleviates the need for
|
||||||
their ports with WITH_NEW_XORG. See the announcement, linked
|
users to rebuild their ports with WITH_NEW_XORG. See the
|
||||||
above for further information.</p>
|
announcement, linked above for further information.</p>
|
||||||
|
|
||||||
<p>Thanks to a contribution from Jan Kokemüller, Radeon 32bit
|
<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.
|
successfully with Wine and StarCraft II on &os; 9.x and 11.
|
||||||
This required modifications to <tt>emulators/i386-wine-devel</tt> so
|
This required modifications to
|
||||||
that it works with WITH_NEW_XORG, and the creation of a new
|
<tt>emulators/i386-wine-devel</tt> so that it works with
|
||||||
port, <tt>libtxc_dxtn</tt>, to support texture compression required by
|
WITH_NEW_XORG, and the creation of a new port,
|
||||||
StarCraft II. We haven't yet had the time to polish
|
<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>
|
everything, so this still requires manual steps.</p>
|
||||||
|
|
||||||
<p>The DRM generic code update is ready, but it breaks the
|
<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>
|
updated before anything is committed.</p>
|
||||||
|
|
||||||
<p>Compared to the previous status report, OpenCL test programs are
|
<p>Compared to the previous status report, OpenCL test programs
|
||||||
running fine now, thanks to upgrades and fixes to libc++ and
|
are running fine now, thanks to upgrades and fixes to libc++
|
||||||
Clang. Relevant ports are still not ready to hit the ports
|
and Clang. Relevant ports are still not ready to hit the
|
||||||
tree, unfortunately.</p>
|
ports tree, unfortunately.</p>
|
||||||
</body>
|
</body>
|
||||||
|
|
||||||
<help>
|
<help>
|
||||||
|
|
@ -1302,11 +1287,12 @@
|
||||||
</contact>
|
</contact>
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
<p>Extensive testing of <tt>tmpfs(5)</tt> using the stress2 kernel test
|
<p>Extensive testing of <tt>tmpfs(5)</tt> using the stress2
|
||||||
suite was done. The issues found were debugged and fixed.</p>
|
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
|
<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>
|
unmount races and dotdot lookup bugs.</p>
|
||||||
|
|
||||||
<p>This project is sponsored by the FreeBSD Foundation.</p>
|
<p>This project is sponsored by the FreeBSD Foundation.</p>
|
||||||
|
|
@ -1367,7 +1353,7 @@
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
<p>ZFSguru is a multifunctional server appliance with a strong
|
<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
|
frontend to ZFS, but has since grown into a &os; derivative
|
||||||
with its own infrastructure. The scope of the project has
|
with its own infrastructure. The scope of the project has
|
||||||
also grown with the inclusion of add-on packages that add
|
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
|
in similar product like FreeNAS and NAS4Free. ZFSguru aims to
|
||||||
be a true multifunctional server appliance that is extremely
|
be a true multifunctional server appliance that is extremely
|
||||||
easy to setup and can unite both novice and more experienced
|
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
|
project combats the danger of bloat, whilst still allowing
|
||||||
extended functionality to be easily deployed.</p>
|
extended functionality to be easily deployed.</p>
|
||||||
|
|
||||||
<p>Where development in the first quarter of this year brought
|
<p>Where development in the first quarter of this year brought
|
||||||
drag-and-drop permissions for Samba and NFS, development in
|
drag-and-drop permissions for Samba and NFS, development in
|
||||||
the second quarter focused on strengthening the infrastructure
|
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
|
'Mesa' is in the works, providing a cleaner foundation to the
|
||||||
project. A new master server providing secure remote services
|
project. A new master server providing secure remote services
|
||||||
is being setup, to be located in a high-speed datacenter. But
|
is being setup, to be located in a high-speed datacenter. But
|
||||||
most importantly, a new system build infrastructure has shown
|
most importantly, a new system build infrastructure has shown
|
||||||
great progress and will soon be able to provide automated
|
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
|
frequency of system releases but also frees much developer
|
||||||
time to be spent on different areas of the project.</p>
|
time to be spent on different areas of the project.</p>
|
||||||
|
|
||||||
<p>Furthermore, a new website and forum is being worked at,
|
<p>Furthermore, a new website and forum is being worked at,
|
||||||
replacing the old-fashioned website that offers only limited
|
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>
|
database, providing real-time updates about the project.</p>
|
||||||
|
|
||||||
<p>In addition, a new platform for collaborated development is
|
<p>In addition, a new platform for 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
|
project, which is a drop-in replacement of the popular GitHub
|
||||||
website. The choice was made to host our own solution and not
|
website. The choice was made to host our own solution and not
|
||||||
rely on GitHub itself. In retrospect this appears to be a good
|
rely on GitHub itself. In retrospect this appears to be a
|
||||||
decision. The recent development where GitHub removed projects
|
good decision. The recent development where GitHub removed
|
||||||
after DCMA-takedowns being sent is incompatible with the
|
projects after DCMA-takedowns being sent is incompatible with
|
||||||
philosophy of free-flow-of-information, which the ZFSguru
|
the philosophy of free-flow-of-information, which the ZFSguru
|
||||||
project is a strong proponent of. By hosting our own solution,
|
project is a strong proponent of. By hosting our own
|
||||||
we have avoided any dependency on third party projects.</p>
|
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
|
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
|
Bulletins provide a tighter connection between the server
|
||||||
infrastructure and the web-interface. The Migration Manager
|
infrastructure and the web-interface. The Migration Manager
|
||||||
is one of the last remaining features still missing in the
|
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
|
upgrade the current system by performing a new clean
|
||||||
installation, but migrate all relevant configuration to the
|
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
|
configuration in a single file to be stored on a different
|
||||||
machine should things go awry.</p>
|
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
|
perspective on the project, can be found at the
|
||||||
<quote>stateoftheproject</quote> link.</p>
|
<quote>stateoftheproject</quote> link.</p>
|
||||||
</body>
|
</body>
|
||||||
|
|
@ -1438,7 +1425,7 @@
|
||||||
</name>
|
</name>
|
||||||
<email>gavin@FreeBSD.org</email>
|
<email>gavin@FreeBSD.org</email>
|
||||||
</person>
|
</person>
|
||||||
|
|
||||||
<person>
|
<person>
|
||||||
<name>
|
<name>
|
||||||
<given>Glen</given>
|
<given>Glen</given>
|
||||||
|
|
@ -1446,7 +1433,7 @@
|
||||||
</name>
|
</name>
|
||||||
<email>gjb@FreeBSD.org</email>
|
<email>gjb@FreeBSD.org</email>
|
||||||
</person>
|
</person>
|
||||||
|
|
||||||
<person>
|
<person>
|
||||||
<name>
|
<name>
|
||||||
<given>Wojciech</given>
|
<given>Wojciech</given>
|
||||||
|
|
@ -1468,16 +1455,16 @@
|
||||||
been allocated, a total of 16 projects were selected to
|
been allocated, a total of 16 projects were selected to
|
||||||
participate in Google Summer of Code 2014 with FreeBSD.</p>
|
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,
|
covering both the base system and ports infrastructure,
|
||||||
userland and kernel. We have students working on firewall
|
userland and kernel. We have students working on firewall
|
||||||
optimisation, ports packaging tools, embedded systems,
|
optimisation, ports packaging tools, embedded systems,
|
||||||
debugging infrastructure, improved Unicode support, enhancements
|
debugging infrastructure, improved Unicode support,
|
||||||
to the loader and to the installer, and several other areas of
|
enhancements to the loader and to the installer, and several
|
||||||
work. We are just over half way through the allocated time this
|
other areas of work. We are just over half way through the
|
||||||
year, and are very much looking forward to integrating code
|
allocated time this year, and are very much looking forward to
|
||||||
produced by these projects into FreeBSD.</p>
|
integrating code produced by these projects into FreeBSD.</p>
|
||||||
|
|
||||||
<p>This is the tenth time FreeBSD has taken part in Google's
|
<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
|
Summer of Code, and we are grateful to Google to have accepted
|
||||||
us as a participating organisation.</p>
|
us as a participating organisation.</p>
|
||||||
|
|
@ -1486,17 +1473,19 @@
|
||||||
|
|
||||||
<project cat='team'>
|
<project cat='team'>
|
||||||
<title>&os; Port Management Team</title>
|
<title>&os; Port Management Team</title>
|
||||||
|
|
||||||
<contact>
|
<contact>
|
||||||
<person>
|
<person>
|
||||||
<name>
|
<name>
|
||||||
<given>Frederic</given>
|
<given>Frederic</given>
|
||||||
<common>Culot</common>
|
<common>Culot</common>
|
||||||
</name>
|
</name>
|
||||||
<email>portmgr-secretary@FreeBSD.org</email>
|
<email>portmgr-secretary@FreeBSD.org</email>
|
||||||
</person>
|
</person>
|
||||||
|
|
||||||
<person>
|
<person>
|
||||||
<name>&os; Port Management Team</name>
|
<name>&os; Port Management Team</name>
|
||||||
<email>portmgr@FreeBSD.org</email>
|
<email>portmgr@FreeBSD.org</email>
|
||||||
</person>
|
</person>
|
||||||
</contact>
|
</contact>
|
||||||
|
|
||||||
|
|
@ -1512,29 +1501,30 @@
|
||||||
</links>
|
</links>
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
<p>The ports tree slowly approaches the 25,000 ports threshold, while the
|
<p>The ports tree slowly approaches the 25,000 ports threshold,
|
||||||
PR count is slightly below 1800.</p>
|
while the PR count is slightly below 1800.</p>
|
||||||
|
|
||||||
<p>In Q2 we added three new committers, took in one commit bit for
|
<p>In Q2 we added three new committers, took in one commit bit
|
||||||
safe keeping, and reinstated one commit bit.</p>
|
for safe keeping, and reinstated one commit bit.</p>
|
||||||
|
|
||||||
<p>In May, &a.tabthorpe; was replaced by &a.culot; as portmgr
|
<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>
|
<p>Commencing July 1, the third intake of
|
||||||
started active duty on <tt>portmgr</tt> for a four month
|
<tt>portmgr-lurkers</tt> started active duty on
|
||||||
duration. The next two candidates are &a.wg; and &a.nivit;.</p>
|
<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>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>
|
</body>
|
||||||
|
|
||||||
<help>
|
<help>
|
||||||
<task>As previously noted, many PRs continue to languish, we would
|
<task>As previously noted, many PRs continue to languish, we
|
||||||
like to see committers dedicate themselves to closing as many
|
would like to see committers dedicate themselves to closing as
|
||||||
as possible.</task>
|
many as possible.</task>
|
||||||
</help>
|
</help>
|
||||||
</project>
|
</project>
|
||||||
|
|
||||||
|
|
@ -1556,14 +1546,15 @@
|
||||||
are all welcome additions to the status reports.</p>
|
are all welcome additions to the status reports.</p>
|
||||||
|
|
||||||
<p>The Monthly team has been busy since the last report, with
|
<p>The Monthly team has been busy since the last report, with
|
||||||
longtime organizer &a.pgj; having stepped down from the team —
|
longtime organizer &a.pgj; having stepped down from the team
|
||||||
thank you Gábor for all your hard work! This has left
|
— thank you Gábor for all your hard work! This
|
||||||
something of a void in the preparation of this report, for which
|
has left something of a void in the preparation of this
|
||||||
the call for items was issued quite late. To help fill the void,
|
report, for which the call for items was issued quite late.
|
||||||
&a.wblock; and &a.bjk; have been added to the monthly@ team,
|
To help fill the void, &a.wblock; and &a.bjk; have been added
|
||||||
joining &a.gjb;, &a.gavin;, &a.emaste;, and the rest of the team
|
to the monthly@ team, joining &a.gjb;, &a.gavin;, &a.emaste;,
|
||||||
in preparing this report. Special thanks to Glen for doing most
|
and the rest of the team in preparing this report. Special
|
||||||
of the work while simultaneously getting 9.3-RELEASE out the door!</p>
|
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
|
<p>The next cycle is sooner than you think! The deadline for
|
||||||
submitting entries for the Q3 report is October 7th, 2014.</p>
|
submitting entries for the Q3 report is October 7th, 2014.</p>
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue