Whitespace-only fixes, translators please ignore.
This commit is contained in:
parent
a1751fbcca
commit
669a6a6c0e
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=45803
1 changed files with 48 additions and 45 deletions
|
@ -29,11 +29,11 @@
|
|||
<p>The third quarter of 2014 was another productive quarter for
|
||||
the &os; 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. The various ports teams have also 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>
|
||||
&os; 11. The various ports teams have also 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>
|
||||
|
@ -160,9 +160,8 @@
|
|||
|
||||
|
||||
<body>
|
||||
<p>
|
||||
Building on the new in-kernel iSCSI target and initiator stack
|
||||
released in &os; 10.0, Chelsio Communications has begun
|
||||
<p>Building on the new in-kernel iSCSI target and initiator
|
||||
stack released in &os; 10.0, Chelsio Communications has begun
|
||||
developing an offload interface to take advantage of the
|
||||
hardware offload capabilities of Chelsio T4 and T5 10 and 40
|
||||
gigabit Ethernet adapters.</p>
|
||||
|
@ -256,9 +255,9 @@
|
|||
|
||||
<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). There were no major updates
|
||||
in the ports tree except for cosmetic changes this quarter.</p>
|
||||
|
||||
stable release (no date scheduled). There were no major
|
||||
updates in the ports tree except for cosmetic changes this
|
||||
quarter.</p>
|
||||
|
||||
<p>Major upcoming changes include:</p>
|
||||
|
||||
|
@ -372,21 +371,22 @@
|
|||
about ZFS than proper documentation.</p>
|
||||
|
||||
<p>After over a year of work, a new ZFS chapter has been added
|
||||
to the &os; Handbook. Over 20,000 words describe the
|
||||
basics of creating, managing, and maintaining a ZFS pool.
|
||||
Advanced features like compression,
|
||||
deduplication, and delegation are covered. The chapter also contains a
|
||||
glossary of terms, explaining a number of the concepts unique
|
||||
to ZFS, and documents some of
|
||||
the many <tt>sysctl</tt> variables that can be used for tuning.</p>
|
||||
to the &os; Handbook. Over 20,000 words describe the basics
|
||||
of creating, managing, and maintaining a ZFS pool. Advanced
|
||||
features like compression, deduplication, and delegation are
|
||||
covered. The chapter also contains a glossary of terms,
|
||||
explaining a number of the concepts unique to ZFS, and
|
||||
documents some of the many <tt>sysctl</tt> variables that can
|
||||
be used for tuning.</p>
|
||||
|
||||
<p>The remaining work to be done is in the FAQ section, which aims to help
|
||||
users address the most common questions or problems they might
|
||||
face with ZFS. We would like 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>The remaining work to be done is in the FAQ section, which
|
||||
aims to help users address the most common questions or
|
||||
problems they might face with ZFS. We would like 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>
|
||||
|
@ -601,8 +601,8 @@
|
|||
<p>Note that running Asan tests on stable/10 requires that state
|
||||
to be set to 1.</p>
|
||||
|
||||
<p>A similar work is in progress to add &os; support to the thread
|
||||
sanitizer (Tsan), which detects data races in parallel
|
||||
<p>A similar work is in progress to add &os; support to the
|
||||
thread sanitizer (Tsan), which detects data races in parallel
|
||||
programs.</p>
|
||||
</body>
|
||||
</project>
|
||||
|
@ -633,13 +633,14 @@
|
|||
USERS. Network configuration, ZFS options, and others are
|
||||
also included.</p>
|
||||
|
||||
<p>The Second part of the project is about booting the <tt>fai</tt> (Fully
|
||||
Automatic Installer) from the network by PXE. An installer
|
||||
distro was created based on mfsBSD. After boot, <tt>fai</tt> looks for the
|
||||
"bootfile-name" parameter from the DHCP server. This
|
||||
parameter tells <tt>fai</tt> where the <tt>bsdinstall</tt> script is
|
||||
located. <tt>fai</tt> supports MAC-based configuration, or a default if a
|
||||
MAC-based configuration file does not exist.</p>
|
||||
<p>The Second part of the project is about booting the
|
||||
<tt>fai</tt> (Fully Automatic Installer) from the network by
|
||||
PXE. An installer distro was created based on mfsBSD. After
|
||||
boot, <tt>fai</tt> looks for the "bootfile-name" parameter
|
||||
from the DHCP server. This parameter tells <tt>fai</tt> where
|
||||
the <tt>bsdinstall</tt> script is located. <tt>fai</tt>
|
||||
supports MAC-based configuration, or a default if a MAC-based
|
||||
configuration file does not exist.</p>
|
||||
</body>
|
||||
|
||||
<sponsor>
|
||||
|
@ -650,9 +651,11 @@
|
|||
<task>
|
||||
<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>
|
||||
|
@ -686,8 +689,8 @@
|
|||
<p>MATE is a fork of GNOME 2. The MATE ports were updated to
|
||||
the 1.8 versions.</p>
|
||||
|
||||
<p>Cairo, the vector graphics library used by GNOME,
|
||||
has been updated to 1.12. This allowed the merge of GNOME 3 to begin.
|
||||
<p>Cairo, the vector graphics library used by GNOME, has been
|
||||
updated to 1.12. This allowed the merge of GNOME 3 to begin.
|
||||
We are currently doing test builds to find ports broken by the
|
||||
update and pruning ports that do not build any more because of
|
||||
incompatible updates.</p>
|
||||
|
@ -727,8 +730,8 @@
|
|||
<body>
|
||||
|
||||
<p>The newest graphics stack (that is, ports behind the
|
||||
<tt>WITH_NEW_XORG</tt> knob) was enabled on all architectures. The
|
||||
only regression is for users of Intel GPUs and &os; 8.X or
|
||||
<tt>WITH_NEW_XORG</tt> knob) was enabled on all architectures.
|
||||
The only regression is for users of Intel GPUs and &os; 8.X or
|
||||
9.0. Those releases lack the required kernel driver and
|
||||
therefore <tt>xf86-video-intel</tt> will not work (the last
|
||||
UMS-aware version does not work with xserver 1.12). Users can
|
||||
|
@ -1830,6 +1833,7 @@
|
|||
</task>
|
||||
</help>
|
||||
</project>
|
||||
|
||||
<project cat='kern'>
|
||||
<title>Intel GPU Driver Update</title>
|
||||
|
||||
|
@ -1848,16 +1852,14 @@
|
|||
</links>
|
||||
|
||||
<body>
|
||||
<p>
|
||||
The project to update the Intel graphics chipset driver
|
||||
<p>The project to update the Intel graphics chipset driver
|
||||
(i915kms) to a recent snapshot of the Linux upstream code
|
||||
continues. A patch with a large chunk of updates has been
|
||||
made available to test for regressions against current
|
||||
functionality, but is not yet expected to provide working new functions.
|
||||
The GEM I/O ioctl code path
|
||||
has been modified to more closely resemble the Linux code
|
||||
structure (easing future imports).
|
||||
</p>
|
||||
functionality, but is not yet expected to provide working new
|
||||
functions. The GEM I/O ioctl code path has been modified to
|
||||
more closely resemble the Linux code structure (easing future
|
||||
imports).</p>
|
||||
</body>
|
||||
|
||||
<sponsor>
|
||||
|
@ -1868,6 +1870,7 @@
|
|||
<task>
|
||||
Fix any bugs reported against the latest versions of the patch.
|
||||
</task>
|
||||
|
||||
<task>
|
||||
Make Haswell graphics work with Mesa.
|
||||
</task>
|
||||
|
|
Loading…
Reference in a new issue