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

Editing pass through the report, added a summary.

Browse source
This commit is contained in:
David Chisnall 2014-10-12 12:44:51 +00:00
parent 66dee84cde
commit a43e88cf35
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=45795
1 changed files with 87 additions and 84 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

171
en_US.ISO8859-1/htdocs/news/status/report-2014-07-2014-09.xml
View file

@ -26,8 +26,14 @@
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>The third quarter of 2014 was another productive quarter for the
FreeBSD project. A lot of work has been done on various ARM
platforms, with the goal of bringing them to Tier 1 status in &os;
11 and the various ports teams have worked hard to improve the
state of &os; as a desktop operating system. As usual,
performance improvements feature in several places in this report
and many of these can benefit from user benchmarking to validate
our results.</p>
<p>Thanks to all the reporters for the excellent work! This
report contains 0 entries and we hope you enjoy reading it.</p>
@ -103,7 +109,7 @@
</links>
<body>
<p>Deficiencies in the current automounter, <tt>amd(8)</tt>, are
<p>Limitations of 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>
@ -118,7 +124,7 @@
to test the new automounter in existing LDAP-based environments,
including some with thousands of map entries.</p>
<p>The code is ready to use - it has been committed to
<p>The code is now 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>
@ -247,25 +253,22 @@
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
<p>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>
stable release (no date scheduled). There were no major updates
in the ports tree except for cosmetic changes this quarter.</p>
<p>Major changes will be:</p>
<p>Major upcoming changes include:</p>
<ul>
<li>Switch to USES</li>
<li>Switch to the to the <tt>USES</tt> framework</li>
<li>Support of GTK2 (default toolkits) and GTK3
(optional)</li>
<li>Support both GTK2 and GTK3, with GTK2 being the default.</li>
<li>GNOME like default icons theme</li>
<li>A GNOME-like default icons theme</li>
<li>Enhance documentation (handbooks, FAQ)</li>
<li>Enhanced documentation (handbooks, FAQ)</li>
</ul>
<p>Below is a list of current ports in the devel repository (see
@ -309,12 +312,12 @@
<help>
<task>
<p>Finish to patch ACPI helper (xfce4-power-manager).</p>
<p>Finish patching the ACPI helper (xfce4-power-manager).</p>
</task>
<task>
<p>Continue to work on documentation, especially the Porter's
Handbook and creating a FAQ).</p>
Handbook, and creata a FAQ).</p>
</task>
</help>
</project>
@ -373,15 +376,15 @@
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>
the many <tt>sysctl</tt> 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>The remaining work is the FAQ section, which aims 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. A use cases section that highlights some of the
cases where ZFS provides advantages over traditional file systems
is also planned.</p>
<p>Please send suggestions to the docs mailing list.</p>
</body>
@ -496,11 +499,9 @@
<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
other plugins that 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>
Jenkins to use JNA 4.1.0, which has fixes for &os;. </p>
<p>&a.rodrigc; worked on automatically running the tests in the
&os; <tt>/usr/tests</tt> directory under Jenkins using the
@ -581,14 +582,16 @@
</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>The LLVM address sanitizer (Asan) is a fast memory error
detector that can detect use-after-free errors and buffer
overflows. It has been ported to &os;. The mainline version of
LLVM is known to pass all of the tests in the LLVM and Asan test
suites 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
<p>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>
@ -597,7 +600,8 @@
to be set to 1.</p>
<p>A similar work dedicated to add &os; support to the thread
sanitizer (Tsan) is in progress.</p>
sanitizer (Tsan), which detects data races in parallel programs, is in
progress.</p>
</body>
</project>
@ -622,17 +626,18 @@
<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,
<tt>bsdinstall(8)</tt>. It supports variables such as 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>
Automatic Installer) from the network by PXE. Made installer
distro based on mfsbsd. After boot, fai looks for the
"bootfile-name" parameter from the DHCP server. This parameter
instructs fai where the bsdinstall script is located. Fai
supports mac-based config or a default, if a mac-based
configuration file does not exist.</p>
</body>
<sponsor>
@ -641,9 +646,13 @@
<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>
<p>Documentation, including a HOWTO and handbook</p>
</task>
<task>
<p>More tests in different configurations</p>
</task>
<task>
<p>Support for more than one network interface is planned</p>
</task>
</help>
</project>
@ -672,12 +681,14 @@
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>MATE is a fork of GNOME 2. 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>Now that cairo, the vector graphics library used by GNOME, has
been 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
@ -954,11 +965,11 @@
</contact>
<links>
<url href="https://github.com/tsgan/qualcomm">Some preliminary codes for Snapdragon board IFC6410</url>
<url href="https://github.com/tsgan/qualcomm">Some preliminary code for Snapdragon board IFC6410</url>
</links>
<body>
<p>Work on initial support of the IFC6410 board,which was
<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
@ -976,7 +987,7 @@
<help>
<task>
<p>Get MMC driver working. May need more help from
<p>Get the MMC driver working. May need more help from
experts.</p>
</task>
</help>
@ -1512,11 +1523,12 @@
</links>
<body>
<p>Arm64 is the name of the in-progress port of &os; to the
ARMv8 CPU when it is in AArch64 mode. Until recently, all ARM
CPU designs were 32-bit only. With the introduction of the
ARMv8 architecture, ARM has added a new 64-bit mode. This new
mode has been named AArch64.</p>
<p>Until recently, all ARM CPU designs were 32-bit only. With the
introduction of the ARMv8 architecture, ARM has added a new
64-bit mode. This new mode has been named AArch64. Arm64 is
the name of the in-progress port of &os; to ARMv8 CPUs when in
AArch64 mode.
</p>
<p>Since the last status report, &os; has started to execute
userland instructions. This includes implementing more of the
@ -2061,7 +2073,8 @@
</links>
<body>
<p>Add &os; kernel support for Xen Paravirtualised kernels.
<p>This project aims to add support to the &os; kernel for running
in Xen Paravirtualised mode on amd64 systems.
This project has finally reached a "Proof of Concept" stage
on the branch
<a href="http://svnweb.freebsd.org/base/projects/amd64_xen_pv/">
@ -2137,37 +2150,27 @@
<body>
<p>Address Space Layout Randomization (ASLR) is a computer
security technique that aids in mitigating low-level
vulnerabilities such as buffer overflows. In order to
prevent an attacker from knowing where a given
exploitable vulnerability lies in memory, ASLR randomizes
the memory layout of running applications.</p>
<p>&os; lacks behind the industry in exploit mitigation
technologies. ASLR is a great first step in implementing
such technologies. Future exploit mitigation technologies
will rely on ASLR.</p>
vulnerabilities such as buffer overflows. ASLR randomizes the
memory layout of running applications, to prevent an attacker
from knowing where a given exploitable vulnerability lies in
memory.</p>
<p>A lot has happened in the last few months. Shawn Webb gave
presentations at both BSDCan 2014 and EuroBSDCon 2014. The
presentations were met with a lot of support and backing.
At the end of EuroBSDCon, an awesome developer named Ilya
Bakulin fixed our ARM bug. Shawn Webb and Oliver Pinter
have submitted our patch to Phabricator, &os;'s new
code review utility. Shawn Webb added an API for allowing
a debugger to disable ASLR in order to support
deterministic debugging with applications such as lldb or
gdb. Oliver Pinter enhanced the performance of our ASLR
implementation. A package building exp-run was ran and came
out favorably in terms of performance. Shawn Webb bumped up
the maximum number of bits allowed to be randomized to 20
and set the default to 14.</p>
At the end of EuroBSDCon Ilya Bakulin fixed the known ARM bug.
Shawn Webb and Oliver Pinter have submitted our patch to
the Phabricator code review system. Shawn Webb added
an API for allowing a debugger to disable ASLR to
support deterministic debugging. Oliver Pinter enhanced the
performance of our ASLR implementation. A package building
exp-run was ran and came out favorably in terms of performance.
Shawn Webb bumped up the maximum number of bits allowed to be
randomized to 20 and set the default to 14.</p>
<p>To aid in the upstreaming process of the ASLR project and
other security-related projects, Shawn Webb and Oliver Pinter
founded The HardenedBSD project. It exists primarily to
serve as a staging area for bleeding-edge development of
security-related projects for &os; prior to being merged
upstream.</p>
<p>Shawn Webb and Oliver Pinter founded The HardenedBSD project to
serve as a staging area for their work on security-related
projects for &os.</p>
</body>