| Component | Translated | Untranslated | Untranslated words | Checks | Suggestions | Comments | |
|---|---|---|---|---|---|---|---|
articles_leap-seconds
BSD-2-Clause-FreeBSD
|
|||||||
|
|
|||||||
|
articles_linux-users
BSD-2-Clause-FreeBSD
|
0% | 119 | 1,745 | ||||
|
|
|||||||
|
articles_nanobsd
BSD-2-Clause-FreeBSD
|
|||||||
|
|
|||||||
|
articles_rc-scripting
BSD-2-Clause-FreeBSD
|
3% | 151 | 6,124 | ||||
|
|
|||||||
|
articles_remote-install
BSD-2-Clause-FreeBSD
|
2% | 102 | 2,266 | ||||
|
|
|||||||
|
books_arch-handbook
BSD-2-Clause-FreeBSD
|
91% | 235 | 10,596 | 853 | 1 | 1 | |
|
|
|||||||
|
books_developers-handbook
BSD-2-Clause-FreeBSD
|
1% | 2,243 | 59,296 | ||||
|
|
|||||||
|
books_handbook
BSD-2-Clause-FreeBSD
|
98% | 126 | 4,902 | 3,629 | 9 | ||
|
|
|||||||
|
books_porters-handbook
BSD-2-Clause-FreeBSD
|
0% | 9,916 | 81,015 | ||||
|
|
|||||||
bhy
<emphasis><varname>vfs.zfs.txg.timeout</varname></emphasis> - Maximum number of seconds between <link linkend="zfs-term-txg">transaction group</link>s. The current transaction group will be written to the pool and a fresh transaction group started if this amount of time has elapsed since the previous transaction group. A transaction group my be triggered earlier if enough data is written. The default value is 5 seconds. A larger value may improve read performance by delaying asynchronous writes, but this may cause uneven performance when the transaction group is written. This value can be adjusted at any time with <citerefentry><refentrytitle>sysctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
<emphasis><varname>vfs.zfs.txg.timeout</varname></emphasis> - <link linkend="zfs-term-txg">事务组</link>之间的最大秒数。如果从上一个事务组到现在已经过了这个时间，那么当前的事务组将被写入存储池中，并启动一个新的事务组。如果有足够的数据写入，则会提前触发一个事务组。默认值是5秒。更大的值可能会通过延迟异步写入来提高读取性能，但这可能会在写入事务组时导致性能不均衡。这个值可以在任何时候用<citerefentry><refentrytitle>sysctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>调整。
<emphasis><varname>vfs.zfs.resilver_delay</varname></emphasis> - Number of milliseconds of delay inserted between each I/O during a <link linkend="zfs-term-resilver">resilver</link>. To ensure that a resilver does not interfere with the normal operation of the pool, if any other I/O is happening the resilver will delay between each command. This value controls the limit of total <acronym>IOPS</acronym> (I/Os Per Second) generated by the resilver. The granularity of the setting is determined by the value of <varname>kern.hz</varname> which defaults to 1000 ticks per second. This setting may be changed, resulting in a different effective <acronym>IOPS</acronym> limit. The default value is 2, resulting in a limit of: 1000 ticks/sec / 2 = 500 <acronym>IOPS</acronym>. Returning the pool to an <link linkend="zfs-term-online">Online</link> state may be more important if another device failing could <link linkend="zfs-term-faulted">Fault</link> the pool, causing data loss. A value of 0 will give the resilver operation the same priority as other operations, speeding the healing process. The speed of resilver is only limited when there has been other recent activity on the pool, as determined by <link linkend="zfs-advanced-tuning-scan_idle"><varname>vfs.zfs.scan_idle</varname></link>. This value can be adjusted at any time with <citerefentry><refentrytitle>sysctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
<emphasis><varname>vfs.zfs.resilver_delay</varname></emphasis> - 在<link linkend="zfs-term-resilver">resilver</link>期间，每个I/O之间插入的延迟的毫秒数。为了确保 resilver 不干扰池的正常运行，如果发生任何其他 I/O，resilver 将在每个命令之间进行延迟。此值控制 resilver 产生的总 <acronym>IOPS</acronym>（每秒 I/O）的限制。设置的粒度由<varname>kern.hz</varname>的值决定，默认值为每秒1000次。此设置可以更改，从而导致不同的有效<acronym>IOPS</acronym>限制。默认值为2，因此限制为：1000 ticks/sec / 2 = 500 <acronym>IOPS</acronym>。如果另一个设备发生故障可能会让存储池发生<link linkend="zfs-term-faulted">故障</link>，导致数据丢失，则将池返回到<link linkend="zfs-term-online">在线</link>状态可能更为重要。值为0时，将赋予resilver操作与其他操作相同的优先级，从而加快修复过程。只有当池上最近有其他活动时，resilver 的速度才会受到限制，这由 <link linkend="zfs-advanced-tuning-scan_idle"><varname>vfs.zfs.scan_idle</varname></link>决定。这个值可以在任何时候用<citerefentry><refentrytitle>sysctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>调整。
Dual-Booting: A straightforward option is to run desired <trademark class="registered">Windows</trademark> applications natively on that OS. This of course means existing FreeBSD in order to boot <trademark class="registered">Windows</trademark>, so this method is not feasible if access to programs in both systems is required simultaneously.
多系统：最直接的解决办法是直接在电脑上安装<trademark class="registered">Windows</trademark>应用程序所需的操作系统。因此如果同时需要访问两个系统中的程序，则此方法是不可行的。
In addition to proprietary offerings, other projects have released applications designed to work in tandem with the standard, open source version of WINE. The goals for these can range from making installation easier to offering easy ways to get popular software installed.
除了专有的产品，其他项目也发布了一些应用程序，旨在与标准的开放源码版本的WINE协同工作。这些项目使流行软件更易于安装。