Fix a variety of whitespace issues in the FAQ
Translators may ignore Approved by: bcr (mentor) Partial commit of approved changes
This commit is contained in:
parent
6cfeec6095
commit
0f8ec17371
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=40635
1 changed files with 21 additions and 21 deletions
|
@ -1052,7 +1052,7 @@
|
|||
</question>
|
||||
<answer>
|
||||
<para>The official &os; forums are located at <ulink
|
||||
url="http://forums.FreeBSD.org/">http://forums.FreeBSD.org/</ulink>.</para>
|
||||
url="http://forums.FreeBSD.org/">http://forums.FreeBSD.org/</ulink>.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
@ -1123,8 +1123,8 @@
|
|||
|
||||
<answer>
|
||||
<para>On the
|
||||
<ulink url="http://www.freebsd.org/where.html">Getting &os;</ulink>
|
||||
page select <literal>[iso]</literal> next to the
|
||||
<ulink url="http://www.freebsd.org/where.html">Getting &os;</ulink>
|
||||
page select <literal>[iso]</literal> next to the
|
||||
architecture you want to use.</para>
|
||||
|
||||
<para>Any of the following can be used:</para>
|
||||
|
@ -1152,7 +1152,7 @@
|
|||
</row>
|
||||
|
||||
<row>
|
||||
<entry><filename>memstick.img</filename></entry>
|
||||
<entry><filename>memstick.img</filename></entry>
|
||||
<entry>A bootable image sufficient for copying to a
|
||||
USB stick.</entry>
|
||||
</row>
|
||||
|
@ -3218,8 +3218,8 @@ kern.timecounter.hardware: TSC -> i8254</screen>
|
|||
<para>The open-source <application><ulink
|
||||
url="http://www.openoffice.org">Apache OpenOffice</ulink></application>
|
||||
and <application><ulink
|
||||
url="http://www.libreoffice.org">LibreOffice</ulink></application>
|
||||
office suites work natively on &os;.</para>
|
||||
url="http://www.libreoffice.org">LibreOffice</ulink></application>
|
||||
office suites work natively on &os;.</para>
|
||||
|
||||
<para>&os; also includes a variety of text editors,
|
||||
spreadsheets, and drawing programs in the Ports
|
||||
|
@ -4482,22 +4482,22 @@ C:\="DOS"</programlisting>
|
|||
</question>
|
||||
|
||||
<answer>
|
||||
<para>This could happen because the pool is 100% full.
|
||||
ZFS requires space on the disk in order to write
|
||||
transaction metadata. In order to restore the pool
|
||||
to a usable state, truncate a file you want to
|
||||
delete.</para>
|
||||
<para>This could happen because the pool is 100% full.
|
||||
ZFS requires space on the disk in order to write
|
||||
transaction metadata. In order to restore the pool
|
||||
to a usable state, truncate a file you want to
|
||||
delete.</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>truncate -s 0 <replaceable>unimportant-file</replaceable></userinput></screen>
|
||||
<screen>&prompt.user; <userinput>truncate -s 0 <replaceable>unimportant-file</replaceable></userinput></screen>
|
||||
|
||||
<para>File truncation works because a new transaction is
|
||||
not started, new spare blocks are created instead.</para>
|
||||
<para>File truncation works because a new transaction is
|
||||
not started, new spare blocks are created instead.</para>
|
||||
|
||||
<note>
|
||||
<para>On systems with additional ZFS dataset tuning,
|
||||
such as deduplication, the space may not be immediately
|
||||
available</para>
|
||||
</note>
|
||||
<note>
|
||||
<para>On systems with additional ZFS dataset tuning,
|
||||
such as deduplication, the space may not be immediately
|
||||
available</para>
|
||||
</note>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
</qandaset>
|
||||
|
@ -4623,7 +4623,7 @@ C:\="DOS"</programlisting>
|
|||
|
||||
<para>To allow someone to <command>su</command> to
|
||||
<username>root</username>, simply put them in the
|
||||
<groupname>wheel</groupname> group. Use &man.pw.8;
|
||||
<groupname>wheel</groupname> group. Use &man.pw.8;
|
||||
for this purpose.</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>pw groupmod wheel -m <replaceable>lisa</replaceable></userinput></screen>
|
||||
|
@ -8913,7 +8913,7 @@ panic: page fault</programlisting>
|
|||
defined in an executable visible to the dynamic linker.
|
||||
Consequently <function>dlsym()</function> searches on
|
||||
handles obtained from calls to <function>dlopen(NULL,
|
||||
flags)</function> will fail to find such symbols.</para>
|
||||
flags)</function> will fail to find such symbols.</para>
|
||||
|
||||
<para>If you want to search, using
|
||||
<function>dlsym()</function>, for symbols present in the
|
||||
|
|
Loading…
Reference in a new issue