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

Whitespace-only fixes, translators please ignore.

Browse source
This commit is contained in:
Warren Block 2014-04-16 20:32:20 +00:00
parent d80aac63ac
commit eb29c0b12c
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=44588
1 changed files with 68 additions and 66 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

134
en_US.ISO8859-1/htdocs/news/status/report-2014-01-2014-03.xml
View file

@ -1182,18 +1182,18 @@
committed code to Subversion since the last successful
build.</p>
<p>As part of the Jenkins setup, &a.rodrigc; encountered problems
with running Java on &os;&nbsp;9.2 and &os;&nbsp;10.0. Both
problems stemmed from changes to the &os; Virtual Memory (VM)
subsystem. On &os; 9.2-RELEASE, running Jenkins under Java
would cause the kernel to panic. This was a known problem, and
fixed in 9.2.-RELEASE-p3. On &os; 10.0-RELEASE, Java processes
would randomly crash. Disabling the
<tt>vm.pmap.pcid_enabled</tt> <tt>sysctl(3)</tt> variable seemed
to fix the problem. In <tt>kern/187238</tt>, Henrik Gulbrandsen
submitted fixes to the &os; VM to address this problem. &a.kib;
committed the fixes to <tt>head</tt>, where they are being
tested now.</p>
<p>As part of the Jenkins setup, &a.rodrigc; encountered
problems with running Java on &os;&nbsp;9.2 and
&os;&nbsp;10.0. Both problems stemmed from changes to the
&os; Virtual Memory (VM) subsystem. On &os; 9.2-RELEASE,
running Jenkins under Java would cause the kernel to panic.
This was a known problem, and fixed in 9.2.-RELEASE-p3. On
&os; 10.0-RELEASE, Java processes would randomly crash.
Disabling the <tt>vm.pmap.pcid_enabled</tt> <tt>sysctl(3)</tt>
variable seemed to fix the problem. In <tt>kern/187238</tt>,
Henrik Gulbrandsen submitted fixes to the &os; VM to address
this problem. &a.kib; committed the fixes to <tt>head</tt>,
where they are being tested now.</p>
<p>During the setup of the bhyve VMs which run Jenkins
processes, &a.rodrigc; wrote scripts to start bhyve VMs from
@ -2418,49 +2418,49 @@ device vt_efifb</pre>
<body>
<p>ZFSguru is a multifunctional server appliance with a strong
emphasis on storage. It wants to deliver all the great BSD and
ZFS technology to a wider audience, while at the same time
emphasis on storage. It wants to deliver all the great BSD
and ZFS technology to a wider audience, while at the same time
pleasing more advanced users as well with unique features and
customization.</p>
<p>A <q>vanilla</q> ZFSguru installation comes with only Samba and
a web-interface setup, but can be extended easily by installing
addons called <q>services</q> to add functionality as desired.
This prevents users from running programs they do not need and
do not want. Advanced users can still use ZFSguru as they would
a normal &os; installation with a 100% ZFS setup
(<q>Root-on-ZFS</q>). ZFSguru does not strip away anything, and
uses a <tt>GENERIC</tt>-like kernel with only some additional
settings added like InfiniBand networking, Device Polling and
AltQ. This means you can use a ZFSguru installation as you
would use a &os; installation.</p>
<p>A <q>vanilla</q> ZFSguru installation comes with only Samba
and a web-interface setup, but can be extended easily by
installing addons called <q>services</q> to add functionality
as desired. This prevents users from running programs they do
not need and do not want. Advanced users can still use
ZFSguru as they would a normal &os; installation with a 100%
ZFS setup (<q>Root-on-ZFS</q>). ZFSguru does not strip away
anything, and uses a <tt>GENERIC</tt>-like kernel with only
some additional settings added like InfiniBand networking,
Device Polling and AltQ. This means you can use a ZFSguru
installation as you would use a &os; installation.</p>
<p>In the first month of 2014, ZFSguru has released beta9 version
of the web interface. This release brings vastly improved support
for Samba and NFS configuration. In particular, it adds a
convenient drag-and-drop interface for Samba permissions. This
allows novice users to configure access to shares in various
configurations. It allows both control and usability, with no
manual being necessary in order to operate it. This is the
ZFSguru-style.</p>
<p>In the first month of 2014, ZFSguru has released beta9
version of the web interface. This release brings vastly
improved support for Samba and NFS configuration. In
particular, it adds a convenient drag-and-drop interface for
Samba permissions. This allows novice users to configure
access to shares in various configurations. It allows both
control and usability, with no manual being necessary in order
to operate it. This is the ZFSguru-style.</p>
<p>New system versions have been released, based on &os; 9.2,
10.0, and <tt>head</tt>. The experimental <tt>head</tt> version
has <tt>vt(4)</tt> and X.org 7.12.4 and the Intel/Radeon KMS
graphics drivers. That is, the latest and greatest of &os;
graphics development. The ZFSguru project plans to release
<tt>stable/10</tt> builds in the near future which also have the
MFCed patches for <tt>vt(4)</tt>, the KMS-enabled system
console with Unicode support. Please see the <tt>vt(4)</tt>
entry for more information.</p>
10.0, and <tt>head</tt>. The experimental <tt>head</tt>
version has <tt>vt(4)</tt> and X.org 7.12.4 and the
Intel/Radeon KMS graphics drivers. That is, the latest and
greatest of &os; graphics development. The ZFSguru project
plans to release <tt>stable/10</tt> builds in the near future
which also have the MFCed patches for <tt>vt(4)</tt>, the
KMS-enabled system console with Unicode support. Please see
the <tt>vt(4)</tt> entry for more information.</p>
<p>Support for ZFS version 5000 is now universal across 9.2, 10.0
and <tt>head</tt> builds. LZ4 compression is the key feature for
ZFS version 5000. Otherwise users are advised to keep their
pool versions as is, to be as compatible as you can with as many
ZFS platforms as possible. Only upgrade the pool as you desire
its functionality, forfeiting the compatibility with older
storage platforms.</p>
<p>Support for ZFS version 5000 is now universal across 9.2,
10.0 and <tt>head</tt> builds. LZ4 compression is the key
feature for ZFS version 5000. Otherwise users are advised to
keep their pool versions as is, to be as compatible as you can
with as many ZFS platforms as possible. Only upgrade the pool
as you desire its functionality, forfeiting the compatibility
with older storage platforms.</p>
</body>
<help>
@ -2469,14 +2469,14 @@ device vt_efifb</pre>
some minor bugs as well as speed up some pages by having a
redesigned remote database system called GuruDB.</task>
<task>ZFSguru beta11 will add the one major feature still missing
in ZFSguru: the Migration Manager. This allows users to maintain
a file with all the configuration of their ZFSguru installation.
It can be used like a firmware &mdash; restoring the machine to
the exact state and configuration of the snapshot configuration.
It allows users to maintain a backup of their ZFSguru
configuration and allows upgrading to a newer ZFSguru system
version without any hassle.</task>
<task>ZFSguru beta11 will add the one major feature still
missing in ZFSguru: the Migration Manager. This allows users
to maintain a file with all the configuration of their ZFSguru
installation. It can be used like a firmware &mdash; restoring
the machine to the exact state and configuration of the
snapshot configuration. It allows users to maintain a backup
of their ZFSguru configuration and allows upgrading to a newer
ZFSguru system version without any hassle.</task>
<task>Automated system builds should bring more system image
releases.</task>
@ -2485,8 +2485,8 @@ device vt_efifb</pre>
<task>Developer website with GitLab setup, allowing bugreports,
code contributions, wiki, and wall messages. Note that GitLab
has also been provided as ZFSguru service, for those interested
in trying GitLab.</task>
has also been provided as ZFSguru service, for those
interested in trying GitLab.</task>
</help>
</project>
@ -2544,13 +2544,13 @@ device vt_efifb</pre>
<p>bhyve is a Type-1 hypervisor that runs on the &os; platform.
It currently only runs &os; (9.x or later) and Linux guests,
current development efforts aim at widening support for other
x86 64-bit operating systems. After a great deal of work by all
involved, bhyve was shipped as part of &os; 10.0-RELEASE.
x86 64-bit operating systems. After a great deal of work by
all involved, bhyve was shipped as part of &os; 10.0-RELEASE.
Increased interest in bhyve and the first usable versions have
provided great feedback and many bug reports.</p>
<p>A number of important improvements have been made to bhyve this
quarter:</p>
<p>A number of important improvements have been made to bhyve
this quarter:</p>
<ul>
<li>Optionally ignore accesses to unimplemented MSRs</li>
@ -2560,15 +2560,16 @@ device vt_efifb</pre>
<li>Graceful shutdown via ACPI on SIGTERM</li>
<li>Fix issue with virtio-blk devices on Linux guests with more
than 4GB of ram</li>
<li>Fix issue with virtio-blk devices on Linux guests with
more than 4GB of ram</li>
<li>Increase the block-layer backend maximum requests to match
AHCI command queue depth</li>
<li>Add SMBIOS support</li>
<li>Improve support for nmdm, opening the tty non-blocking</li>
<li>Improve support for nmdm, opening the tty
non-blocking</li>
<li>Add HPET device emulation</li>
@ -2589,7 +2590,8 @@ device vt_efifb</pre>
<task>Write Handbook chapter for bhyve.</task>
<task>Merge fixes and features back to <tt>stable/10</tt>.</task>
<task>Merge fixes and features back to
<tt>stable/10</tt>.</task>
<task>Support for booting with UEFI instead of userspace
loaders.</task>