svn commit: r44816 - head/en_US.ISO8859-1/books/faq
Dru Lavigne
dru at FreeBSD.org
Mon May 12 15:15:45 UTC 2014
Author: dru
Date: Mon May 12 15:15:44 2014
New Revision: 44816
URL: http://svnweb.freebsd.org/changeset/doc/44816
Log:
White space fix only. Translators can ignore.
Sponsored by: iXsystems
Modified:
head/en_US.ISO8859-1/books/faq/book.xml
Modified: head/en_US.ISO8859-1/books/faq/book.xml
==============================================================================
--- head/en_US.ISO8859-1/books/faq/book.xml Mon May 12 14:41:45 2014 (r44815)
+++ head/en_US.ISO8859-1/books/faq/book.xml Mon May 12 15:15:44 2014 (r44816)
@@ -1090,7 +1090,8 @@
</chapter>
<chapter xml:id="install">
- <info><title>Installation</title>
+ <info>
+ <title>Installation</title>
<author><personname><firstname>Nik</firstname><surname>Clayton</surname></personname><affiliation>
<address><email>nik at FreeBSD.org</email></address>
@@ -1409,12 +1410,14 @@
<answer>
<para>Memory limits depend on the platform used. On a
standard &i386; install, the limit is 4 GB but more
- memory can be supported through &man.pae.4;. See <link linkend="memory-i386-over-4gb">instructions for using 4 GB or more memory on &i386;</link>.</para>
+ memory can be supported through &man.pae.4;. See <link
+ linkend="memory-i386-over-4gb">instructions for using
+ 4 GB or more memory on &i386;</link>.</para>
<para>&os;/pc98 has a limit of 4 GB memory, and PAE can
- not be used with it. Other architectures supported by &os;
- have much higher theoretical limits on maximum memory (many
- terabytes).</para>
+ not be used with it. Other architectures supported by
+ &os; have much higher theoretical limits on maximum memory
+ (many terabytes).</para>
</answer>
</qandaentry>
@@ -1424,44 +1427,47 @@
</question>
<answer>
- <para>For FFS file systems, the largest file system is practically
- limited by the amount of memory required to &man.fsck.8; the file
- system. &man.fsck.8; requires one bit per fragment, which with
- the default fragment size of 4 KB equates to 32 MB
- of memory per TB of disk. This does mean that on architectures
- which limit userland processes to 2 GB (e.g., &i386;),
- the maximum &man.fsck.8;'able filesystem is ~60 TB.</para>
-
- <para>If there was not a &man.fsck.8; memory limit the maximum
- filesystem size would be 2 ^ 64 (blocks) * 32 KB
- => 16 Exa * 32 KB => 512 ZettaBytes.</para>
+ <para>For FFS file systems, the largest file system is
+ practically limited by the amount of memory required to
+ &man.fsck.8; the file system. &man.fsck.8; requires one
+ bit per fragment, which with the default fragment size of
+ 4 KB equates to 32 MB of memory per TB of disk.
+ This does mean that on architectures which limit userland
+ processes to 2 GB (e.g., &i386;), the maximum
+ &man.fsck.8;'able filesystem is ~60 TB.</para>
+
+ <para>If there was not a &man.fsck.8; memory limit the
+ maximum filesystem size would be 2 ^ 64 (blocks)
+ * 32 KB => 16 Exa * 32 KB => 512
+ ZettaBytes.</para>
<para>The maximum size of a single FFS file is approximately
2 PB with the default block size of 32 KB. Each
32 KB block can point to 4096 blocks. With triple
indirect blocks, the calculation is 32 KB * 12 +
32 KB * 4096 + 32 KB * 4096^2 + 32 KB *
- 4096^3. Increasing the block size to 64 KB will increase
- the max file size by a factor of 16.</para>
+ 4096^3. Increasing the block size to 64 KB will
+ increase the max file size by a factor of 16.</para>
</answer>
</qandaentry>
<qandaentry>
<question xml:id="archsw-readin-failed-error">
- <para>Why do I get an error message,
- <errorname>readin failed</errorname> after compiling
- and booting a new kernel?</para>
+ <para>Why do I get an error message, <errorname>readin
+ failed</errorname> after compiling and booting a new
+ kernel?</para>
</question>
<answer>
- <para>Because your world and kernel are out of sync. This is
- not supported. Be sure you use <command>make buildworld</command>
- and <command>make buildkernel</command>
- to update your kernel.</para>
+ <para>Because your world and kernel are out of sync. This
+ is not supported. Be sure you use <command>make
+ buildworld</command> and <command>make
+ buildkernel</command> to update your kernel.</para>
<para>You can boot by specifying the kernel directly at the
- second stage, pressing any key when the <literal>|</literal>
- shows up before loader is started.</para>
+ second stage, pressing any key when the
+ <literal>|</literal> shows up before loader is
+ started.</para>
</answer>
</qandaentry>
@@ -1491,8 +1497,8 @@
<qandaset>
<qandaentry>
<question xml:id="which-hardware-to-get">
- <para>I want to get a piece of hardware for my &os; system.
- Which model/brand/type is best?</para>
+ <para>I want to get a piece of hardware for my &os;
+ system. Which model/brand/type is best?</para>
</question>
<answer>
@@ -1500,36 +1506,41 @@
lists. Since hardware changes so quickly, however, we
expect this. We <emphasis>still</emphasis> strongly
recommend that you read through the Hardware Notes
- for &os; <link xlink:href="&rel.current.hardware;">&rel.current;</link> or
- <link xlink:href="&rel2.current.hardware;">&rel2.current;</link> and
- search the mailing list <link xlink:href="http://www.FreeBSD.org/search/#mailinglists">archives</link>
+ for &os; <link
+ xlink:href="&rel.current.hardware;">&rel.current;</link>
+ or <link
+ xlink:href="&rel2.current.hardware;">&rel2.current;</link>
+ and search the mailing list <link
+ xlink:href="http://www.FreeBSD.org/search/#mailinglists">archives</link>
before asking about the latest and greatest hardware.
Chances are a discussion about the type of hardware you
are looking for took place just last week.</para>
- <para>If you are looking for a laptop, check the &a.mobile;
- archives. Otherwise, you probably want the archives for
- the &a.questions;, or possibly a specific mailing list for
- a particular hardware type.</para>
+ <para>If you are looking for a laptop, check the
+ &a.mobile; archives. Otherwise, you probably want the
+ archives for the &a.questions;, or possibly a specific
+ mailing list for a particular hardware type.</para>
</answer>
</qandaentry>
<qandaentry>
<question xml:id="memory-upper-limitation">
- <para>Does &os; support more than 4 GB of memory (RAM)?
- More than 16 GB? More than 48 GB?</para>
+ <para>Does &os; support more than 4 GB of memory
+ (RAM)? More than 16 GB? More than
+ 48 GB?</para>
</question>
<answer>
<para>Yes. &os; as an operating system generally supports
- as much physical memory (RAM) as the platform it is running
- on does. Keep in mind that different platforms have
- different limits for memory; for example &i386; without
- <acronym>PAE</acronym> supports at most 4 GB of
- memory (and usually less than that because of PCI address
- space) and &i386; with PAE supports at most 64 GB
- memory. AMD64 platforms currently deployed support up to
- 1 TB of physical memory.</para>
+ as much physical memory (RAM) as the platform it is
+ running on does. Keep in mind that different platforms
+ have different limits for memory; for example &i386;
+ without <acronym>PAE</acronym> supports at most
+ 4 GB of memory (and usually less than that because
+ of PCI address space) and &i386; with PAE supports at
+ most 64 GB memory. AMD64 platforms currently
+ deployed support up to 1 TB of physical
+ memory.</para>
</answer>
</qandaentry>
@@ -1540,53 +1551,55 @@
</question>
<answer>
- <para>The total address space on &i386; machines is 32-bit,
- meaning that at most 4 GB of memory is addressable (can
- be accessed). Furthermore, some addresses in this range
- are reserved by hardware for different purposes, for
- example for using and controlling PCI devices, for
- accessing video memory, and so on. Therefore, the total
- amount of memory usable by the operating system for its
- kernel and applications is limited to significantly less
- than 4 GB. Usually, 3.2 GB to 3.7 GB is
- the maximum usable physical memory in this
- configuration.</para>
+ <para>The total address space on &i386; machines is
+ 32-bit, meaning that at most 4 GB of memory is
+ addressable (can be accessed). Furthermore, some
+ addresses in this range are reserved by hardware for
+ different purposes, for example for using and
+ controlling PCI devices, for accessing video memory, and
+ so on. Therefore, the total amount of memory usable by
+ the operating system for its kernel and applications is
+ limited to significantly less than 4 GB. Usually,
+ 3.2 GB to 3.7 GB is the maximum usable
+ physical memory in this configuration.</para>
<para>To access more than 3.2 GB to 3.7 GB of
- installed memory (meaning up to 4 GB but also more than
- 4 GB), a special tweak called <acronym>PAE</acronym>
- must be used. PAE stands for Physical Address Extension
- and is a way for 32-bit x86 CPUs to address more than
- 4 GB of memory. It remaps the memory that would
- otherwise be overlaid by address reservations for
- hardware devices above the 4 GB range and uses it as
- additional physical memory (see &man.pae.4;). Using PAE
- has some drawbacks; this mode of memory access is a little
- bit slower than the normal (without PAE) mode and loadable
- modules (see &man.kld.4;) are not supported. This means
- all drivers must be compiled into the kernel.</para>
+ installed memory (meaning up to 4 GB but also more
+ than 4 GB), a special tweak called
+ <acronym>PAE</acronym> must be used. PAE stands for
+ Physical Address Extension and is a way for 32-bit x86
+ CPUs to address more than 4 GB of memory. It
+ remaps the memory that would otherwise be overlaid by
+ address reservations for hardware devices above the
+ 4 GB range and uses it as additional physical
+ memory (see &man.pae.4;). Using PAE has some drawbacks;
+ this mode of memory access is a little bit slower than
+ the normal (without PAE) mode and loadable modules (see
+ &man.kld.4;) are not supported. This means all drivers
+ must be compiled into the kernel.</para>
<para>The most common way to enable PAE is to build a new
- kernel with the special ready-provided kernel configuration
- file called <filename>PAE</filename>, which is already
- configured to build a safe kernel. Note that some entries
- in this kernel configuration file are too conservative and
- some drivers marked as unready to be used with PAE are
- actually usable. A rule of thumb is that if the driver is
- usable on 64-bit architectures (like AMD64), it is also
- usable with PAE. If you wish to create your own kernel
- configuration file, you can enable PAE by adding the
- following line to your configuration:</para>
+ kernel with the special ready-provided kernel
+ configuration file called <filename>PAE</filename>,
+ which is already configured to build a safe kernel.
+ Note that some entries in this kernel configuration file
+ are too conservative and some drivers marked as unready
+ to be used with PAE are actually usable. A rule of
+ thumb is that if the driver is usable on 64-bit
+ architectures (like AMD64), it is also usable with PAE.
+ If you wish to create your own kernel configuration
+ file, you can enable PAE by adding the following line to
+ your configuration:</para>
<programlisting>options PAE</programlisting>
<para>PAE is not much used nowadays because most new x86
hardware also supports running in 64-bit mode, known as
AMD64 or &intel; 64. It has a much larger address
- space and does not need such tweaks. &os; supports AMD64
- and it is recommended that this version of &os; be used
- instead of the &i386; version if 4 GB or more memory
- is required.</para>
+ space and does not need such tweaks. &os; supports
+ AMD64 and it is recommended that this version of &os; be
+ used instead of the &i386; version if 4 GB or more
+ memory is required.</para>
</answer>
</qandaentry>
</qandaset>
@@ -1604,15 +1617,17 @@
<answer>
<para>Yes. &os; divides support into multiple tiers.
- Tier 1 architectures, such as i386 or amd64; are
- fully supported. Tiers 2 and 3 are supported on an
+ Tier 1 architectures, such as i386 or amd64; are fully
+ supported. Tiers 2 and 3 are supported on an
if-possible basis. A full explanation of the tier
- system is available in the
- <link xlink:href="&url.articles.committers-guide;/archs.html">Committer's Guide.</link></para>
+ system is available in the <link
+ xlink:href="&url.articles.committers-guide;/archs.html">Committer's
+ Guide.</link></para>
<para>A complete list of supported architectures can be
- found on the
- <link xlink:href="http://www.FreeBSD.org/platforms/">platforms page.</link></para>
+ found on the <link
+ xlink:href="http://www.FreeBSD.org/platforms/">platforms
+ page.</link></para>
</answer>
</qandaentry>
@@ -1625,11 +1640,11 @@
<answer>
<para>&os; supports symmetric multi-processor (SMP) on all
non-embedded platforms (e.g, &arch.i386;, &arch.amd64;,
- etc.). SMP is also
- supported in arm and MIPS kernels, although some CPUs
- may not support this. &os;'s SMP implementation uses
- fine-grained locking, and performance scales nearly
- linearly with number of CPUs.</para>
+ etc.). SMP is also supported in arm and MIPS kernels,
+ although some CPUs may not support this. &os;'s SMP
+ implementation uses fine-grained locking, and
+ performance scales nearly linearly with number of
+ CPUs.</para>
<para>&man.smp.4; has more details.</para>
</answer>
@@ -1644,10 +1659,12 @@
<answer>
<para>Microcode is a method of programmatically
implementing hardware level instructions. This allows
- for CPU bugs to be fixed without replacing the on board chip.</para>
+ for CPU bugs to be fixed without replacing the on board
+ chip.</para>
<para>Install <package>sysutils/devcpu-data</package>,
then add:</para>
+
<programlisting>microcode_update_enable="YES"</programlisting>
<para>to <filename>/etc/rc.conf</filename></para>
@@ -1666,12 +1683,13 @@
</question>
<answer>
- <para>&os; supports EIDE, SATA, SCSI, and SAS drives (with a
- compatible controller; see the next section), and all
+ <para>&os; supports EIDE, SATA, SCSI, and SAS drives (with
+ a compatible controller; see the next section), and all
drives using the original <quote>Western Digital</quote>
- interface (MFM, RLL, ESDI, and of course IDE). A few ESDI
- controllers that use proprietary interfaces may not work:
- stick to WD1002/3/6/7 interfaces and clones.</para>
+ interface (MFM, RLL, ESDI, and of course IDE). A few
+ ESDI controllers that use proprietary interfaces may not
+ work: stick to WD1002/3/6/7 interfaces and
+ clones.</para>
</answer>
</qandaentry>
@@ -1682,8 +1700,10 @@
<answer>
<para>See the complete list in the Hardware Notes for &os;
- <link xlink:href="&rel.current.hardware;">&rel.current;</link>
- or <link xlink:href="&rel2.current.hardware;">&rel2.current;</link>.</para>
+ <link
+ xlink:href="&rel.current.hardware;">&rel.current;</link>
+ or <link
+ xlink:href="&rel2.current.hardware;">&rel2.current;</link>.</para>
</answer>
</qandaentry>
@@ -1693,7 +1713,8 @@
</question>
<answer>
- <para>&os; supports all standard SCSI tape interfaces.</para>
+ <para>&os; supports all standard SCSI tape
+ interfaces.</para>
</answer>
</qandaentry>
@@ -1703,17 +1724,18 @@
</question>
<answer>
- <para>&os; supports SCSI changers using the &man.ch.4; device
- and the &man.chio.1; command. The details of how you
- actually control the changer can be found in the
+ <para>&os; supports SCSI changers using the &man.ch.4;
+ device and the &man.chio.1; command. The details of how
+ you actually control the changer can be found in the
&man.chio.1; manual page.</para>
- <para>If you are not using <application>AMANDA</application>
- or some other product that already understands changers,
- remember that they only know how to move a tape from one
- point to another, so you need to keep track of which slot a
- tape is in, and which slot the tape currently in the drive
- needs to go back to.</para>
+ <para>If you are not using
+ <application>AMANDA</application> or some other product
+ that already understands changers, remember that they
+ only know how to move a tape from one point to another,
+ so you need to keep track of which slot a tape is in,
+ and which slot the tape currently in the drive needs to
+ go back to.</para>
</answer>
</qandaentry>
@@ -1723,8 +1745,8 @@
</question>
<answer>
- <para>Any SCSI drive connected to a supported controller is
- supported. Most ATAPI compatible IDE CD-ROMs are
+ <para>Any SCSI drive connected to a supported controller
+ is supported. Most ATAPI compatible IDE CD-ROMs are
supported.</para>
</answer>
</qandaentry>
@@ -1739,10 +1761,10 @@
drive. See &man.burncd.8; for details.</para>
<para>&os; also supports any SCSI CD-R or CD-RW drives.
- Install and use <command>cdrecord</command>
- from the ports or packages system, and make sure that you
- have the <filename>pass</filename> device compiled in
- your kernel.</para>
+ Install and use <command>cdrecord</command> from the
+ ports or packages system, and make sure that you have
+ the <filename>pass</filename> device compiled in your
+ kernel.</para>
</answer>
</qandaentry>
</qandaset>
@@ -1754,8 +1776,8 @@
<qandaset>
<qandaentry>
<question xml:id="moused">
- <para>Is it possible to use a mouse in any way outside the X
- Window system?</para>
+ <para>Is it possible to use a mouse in any way outside the
+ X Window system?</para>
</question>
<answer>
@@ -1774,8 +1796,8 @@
automatically determine the protocol type of most mice,
except old serial mice. Specify the
<literal>auto</literal> protocol to invoke automatic
- detection. If automatic detection does not work, see the
- &man.moused.8; manual page for a list of supported
+ detection. If automatic detection does not work, see
+ the &man.moused.8; manual page for a list of supported
protocol types.</para>
<para>If you have a PS/2 mouse, just add
@@ -1783,14 +1805,15 @@
<filename>/etc/rc.conf</filename> to start the mouse
daemon at boot-time. Additionally, if you would like to
use the mouse daemon on all virtual terminals instead of
- just the console, add
- <literal>allscreens_flags="-m on"</literal> to
+ just the console, add <literal>allscreens_flags="-m
+ on"</literal> to
<filename>/etc/rc.conf</filename>.</para>
- <para>When the mouse daemon is running, access to the mouse
- must be coordinated between the mouse daemon and other
- programs such as X Windows. Refer to the FAQ <link linkend="x-and-moused">Why does my mouse not work with X?</link>
- for more details on this issue.</para>
+ <para>When the mouse daemon is running, access to the
+ mouse must be coordinated between the mouse daemon and
+ other programs such as X Windows. Refer to the FAQ
+ <link linkend="x-and-moused">Why does my mouse not work
+ with X?</link> for more details on this issue.</para>
</answer>
</qandaentry>
@@ -1804,14 +1827,13 @@
<para>It is not possible to remove data using the mouse.
However, it is possible to <quote>copy and
paste</quote>.
- Once you get the mouse daemon running (see the
- <link linkend="moused">previous question</link>)
- hold down
- button 1 (left button) and move the mouse to select a region
- of text. Then, press button 2 (middle button) to paste
- it at the text cursor. Pressing button 3 (right button)
- will <quote>extend</quote> the selected region of
- text.</para>
+ Once you get the mouse daemon running (see the <link
+ linkend="moused">previous question</link>) hold down
+ button 1 (left button) and move the mouse to select a
+ region of text. Then, press button 2 (middle button) to
+ paste it at the text cursor. Pressing button 3 (right
+ button) will <quote>extend</quote> the selected region
+ of text.</para>
<para>If your mouse does not have a middle button, you may
wish to emulate one or remap buttons using mouse daemon
@@ -1835,7 +1857,8 @@
two, or three button mouse.</para>
<para>For the possible usage of wheels in the X Window
- environment, refer to <link linkend="x-and-wheel">that section</link>.</para>
+ environment, refer to <link
+ linkend="x-and-wheel">that section</link>.</para>
</answer>
</qandaentry>
@@ -1847,20 +1870,22 @@
<answer>
<para>For the <application>Bourne Shell</application>, add
- the following lines to your <filename>.shrc</filename>. See
- &man.sh.1; and &man.editrc.5;.</para>
+ the following lines to your <filename>.shrc</filename>.
+ See &man.sh.1; and &man.editrc.5;.</para>
<programlisting>bind ^? ed-delete-next-char # for console
bind ^[[3~ ed-delete-next-char # for xterm</programlisting>
<para>For the <application>C Shell</application>, add the
- following lines to your <filename>.cshrc</filename>. See
- &man.csh.1;.</para>
+ following lines to your <filename>.cshrc</filename>.
+ See &man.csh.1;.</para>
<programlisting>bindkey ^? delete-char # for console
bindkey ^[[3~ delete-char # for xterm</programlisting>
- <para>For more information, see <link xlink:href="http://www.ibb.net/~anne/keyboard.html">this page</link>.</para>
+ <para>For more information, see <link
+ xlink:href="http://www.ibb.net/~anne/keyboard.html">this
+ page</link>.</para>
</answer>
</qandaentry>
</qandaset>
@@ -1877,9 +1902,9 @@ bindkey ^[[3~ delete-char # for xterm</p
</question>
<answer>
- <para>Some sound cards set their output volume to 0 at every
- boot. Run the following command every time the machine
- boots:</para>
+ <para>Some sound cards set their output volume to 0 at
+ every boot. Run the following command every time the
+ machine boots:</para>
<screen>&prompt.root; <userinput>mixer pcm 100 vol 100 cd 100</userinput></screen>
</answer>
@@ -1892,9 +1917,9 @@ bindkey ^[[3~ delete-char # for xterm</p
</question>
<answer>
- <para>&os; supports the <acronym>ACPI</acronym>
- features found in modern hardware. Further
- information can be found in &man.acpi.4;.</para>
+ <para>&os; supports the <acronym>ACPI</acronym> features
+ found in modern hardware. Further information can be
+ found in &man.acpi.4;.</para>
</answer>
</qandaentry>
</qandaset>
@@ -1907,44 +1932,47 @@ bindkey ^[[3~ delete-char # for xterm</p
<qandaset>
<qandaentry>
<question xml:id="pae">
- <para>Why is &os; finding the wrong amount of memory on &i386;
- hardware?</para>
+ <para>Why is &os; finding the wrong amount of memory on
+ &i386; hardware?</para>
</question>
<answer>
<para>The most likely reason is the difference between
physical memory addresses and virtual addresses.</para>
- <para>The convention for most PC hardware is to use the memory
- area between 3.5 GB and 4 GB for a special purpose
- (usually for PCI). This address space is used to access PCI
- hardware. As a result real, physical memory can not be
- accessed by that address space.</para>
+ <para>The convention for most PC hardware is to use the
+ memory area between 3.5 GB and 4 GB for a
+ special purpose (usually for PCI). This address space is
+ used to access PCI hardware. As a result real, physical
+ memory can not be accessed by that address space.</para>
<para>What happens to the memory that should appear in that
- location is dependent on your hardware. Unfortunately, some
- hardware does nothing and the ability to use that last
- 500 MB of RAM is entirely lost.</para>
+ location is dependent on your hardware. Unfortunately,
+ some hardware does nothing and the ability to use that
+ last 500 MB of RAM is entirely lost.</para>
<para>Luckily, most hardware remaps the memory to a higher
location so that it can still be used. However, this can
- cause some confusion if you watch the boot messages.</para>
+ cause some confusion if you watch the boot
+ messages.</para>
- <para>On a 32-bit version of &os;, the memory appears
- lost, since it will be remapped above 4 GB, which a
- 32-bit kernel is unable to access. In this case, the
- solution is to build a PAE enabled kernel. See <link linkend="memory-limits">the entry on memory limits</link>
- and <link linkend="memory-upper-limitation">about different
- memory limits on different platforms</link> for more
+ <para>On a 32-bit version of &os;, the memory appears lost,
+ since it will be remapped above 4 GB, which a 32-bit
+ kernel is unable to access. In this case, the solution is
+ to build a PAE enabled kernel. See <link
+ linkend="memory-limits">the entry on memory
+ limits</link> and <link
+ linkend="memory-upper-limitation">about different memory
+ limits on different platforms</link> for more
information.</para>
<para>On a 64-bit version of &os;, or when running a
- PAE-enabled kernel, &os; will correctly detect and remap the
- memory so it is usable. During boot, however, it may seem
- as if &os; is detecting more memory than the system really
- has, due to the described remapping. This is normal and the
- available memory will be corrected as the boot process
- completes.</para>
+ PAE-enabled kernel, &os; will correctly detect and remap
+ the memory so it is usable. During boot, however, it may
+ seem as if &os; is detecting more memory than the system
+ really has, due to the described remapping. This is
+ normal and the available memory will be corrected as the
+ boot process completes.</para>
</answer>
</qandaentry>
@@ -1956,10 +1984,10 @@ bindkey ^[[3~ delete-char # for xterm</p
<answer>
<para>Signal 11 errors are caused when your process has
- attempted to access memory which the operating system has not
- granted it access to. If something like this is happening
- at seemingly random intervals then you need to start
- investigating things very carefully.</para>
+ attempted to access memory which the operating system has
+ not granted it access to. If something like this is
+ happening at seemingly random intervals then you need to
+ start investigating things very carefully.</para>
<para>These problems can usually be attributed to
either:</para>
@@ -1973,34 +2001,34 @@ bindkey ^[[3~ delete-char # for xterm</p
<listitem>
<para>If it is a problem with part of the base &os;
- system, it may also be buggy code, but more often than not
- these problems are found and fixed long before us
- general FAQ readers get to use these bits of code (that
- is what -CURRENT is for).</para>
+ system, it may also be buggy code, but more often than
+ not these problems are found and fixed long before us
+ general FAQ readers get to use these bits of code
+ (that is what -CURRENT is for).</para>
</listitem>
</orderedlist>
<para>In particular, a dead giveaway that this is
<emphasis>not</emphasis> a &os; bug is if you see the
problem when you are compiling a program, but the activity
- that the compiler is carrying out changes each time.</para>
+ that the compiler is carrying out changes each
+ time.</para>
- <para>For example, suppose you are running
- <command>make buildworld</command>,
- and the compile fails while trying to compile
- <filename>ls.c</filename> into <filename>ls.o</filename>.
- If you then run
- <command>make buildworld</command>
- again, and the compile fails in the same place then this is
- a broken build — try updating your sources and try
- again. If the compile fails elsewhere then this is almost
- certainly hardware.</para>
+ <para>For example, suppose you are running <command>make
+ buildworld</command>, and the compile fails while trying
+ to compile <filename>ls.c</filename> into
+ <filename>ls.o</filename>. If you then run <command>make
+ buildworld</command> again, and the compile fails in the
+ same place then this is a broken build — try
+ updating your sources and try again. If the compile fails
+ elsewhere then this is almost certainly hardware.</para>
<para>What you should do:</para>
<para>In the first case you can use a debugger e.g.,
&man.gdb.1; to find the point in the program which is
- attempting to access a bogus address and then fix it.</para>
+ attempting to access a bogus address and then fix
+ it.</para>
<para>In the second case you need to verify that it is not
your hardware at fault.</para>
@@ -2009,76 +2037,81 @@ bindkey ^[[3~ delete-char # for xterm</p
<orderedlist>
<listitem>
- <para>Your hard disks might be overheating: Check the fans
- in your case are still working, as your disk (and perhaps
- other hardware might be overheating).</para>
+ <para>Your hard disks might be overheating: Check the
+ fans in your case are still working, as your disk (and
+ perhaps other hardware might be overheating).</para>
</listitem>
<listitem>
- <para>The processor running is overheating: This might be
- because the processor has been overclocked, or the fan
- on the processor might have died. In either case you
- need to ensure that you have hardware running at what it
- is specified to run at, at least while trying to solve
- this problem (in other words, clock it back to the default
- settings.)</para>
+ <para>The processor running is overheating: This might
+ be because the processor has been overclocked, or the
+ fan on the processor might have died. In either case
+ you need to ensure that you have hardware running at
+ what it is specified to run at, at least while trying
+ to solve this problem (in other words, clock it back
+ to the default settings.)</para>
<para>If you are overclocking then note that it is far
cheaper to have a slow system than a fried system that
- needs replacing! Also the wider community is not often
- sympathetic to problems on overclocked systems, whether
- you believe it is safe or not.</para>
+ needs replacing! Also the wider community is not
+ often sympathetic to problems on overclocked systems,
+ whether you believe it is safe or not.</para>
</listitem>
<listitem>
<para>Dodgy memory: If you have multiple memory
SIMMS/DIMMS installed then pull them all out and try
- running the machine with each SIMM or DIMM individually
- and narrow the problem down to either the problematic
- DIMM/SIMM or perhaps even a combination.</para>
+ running the machine with each SIMM or DIMM
+ individually and narrow the problem down to either the
+ problematic DIMM/SIMM or perhaps even a
+ combination.</para>
</listitem>
<listitem>
<para>Over-optimistic Motherboard settings: In your BIOS
- settings, and some motherboard jumpers you have options
- to set various timings, mostly the defaults will be
- sufficient, but sometimes, setting the wait states on
- RAM too low, or setting the <quote>RAM Speed:
- Turbo</quote> option, or similar in the BIOS will cause
- strange behavior. A possible idea is to set to BIOS
- defaults, but it might be worth noting down your
- settings first!</para>
+ settings, and some motherboard jumpers you have
+ options to set various timings, mostly the defaults
+ will be sufficient, but sometimes, setting the wait
+ states on RAM too low, or setting the <quote>RAM
+ Speed: Turbo</quote> option, or similar in the BIOS
+ will cause strange behavior. A possible idea is to
+ set to BIOS defaults, but it might be worth noting
+ down your settings first!</para>
</listitem>
<listitem>
<para>Unclean or insufficient power to the motherboard.
- If you have any unused I/O boards, hard disks, or CD-ROMs
- in your system, try temporarily removing them or
- disconnecting the power cable from them, to see if your
- power supply can manage a smaller load. Or try another
- power supply, preferably one with a little more power
- (for instance, if your current power supply is rated at
- 250 Watts try one rated at 300 Watts).</para>
+ If you have any unused I/O boards, hard disks, or
+ CD-ROMs in your system, try temporarily removing them
+ or disconnecting the power cable from them, to see if
+ your power supply can manage a smaller load. Or try
+ another power supply, preferably one with a little
+ more power (for instance, if your current power supply
+ is rated at 250 Watts try one rated at
+ 300 Watts).</para>
</listitem>
</orderedlist>
- <para>You should also read the SIG11 FAQ (listed below) which
- has excellent explanations of all these problems, albeit from
- a &linux; viewpoint. It also discusses how memory testing
- software or hardware can still pass faulty memory.</para>
-
- <para>Finally, if none of this has helped it is possible that
- you have just found a bug in &os;, and you should follow the
- instructions to send a problem report.</para>
-
- <para>There is an extensive FAQ on this at <link xlink:href="http://www.bitwizard.nl/sig11/">the SIG11 problem FAQ</link>.</para>
+ <para>You should also read the SIG11 FAQ (listed below)
+ which has excellent explanations of all these problems,
+ albeit from a &linux; viewpoint. It also discusses how
+ memory testing software or hardware can still pass faulty
+ memory.</para>
+
+ <para>Finally, if none of this has helped it is possible
+ that you have just found a bug in &os;, and you should
+ follow the instructions to send a problem report.</para>
+
+ <para>There is an extensive FAQ on this at <link
+ xlink:href="http://www.bitwizard.nl/sig11/">the SIG11
+ problem FAQ</link>.</para>
</answer>
</qandaentry>
<qandaentry>
<question xml:id="trap-12-panic">
- <para>My system crashes with either <errorname>Fatal trap 12:
- page fault in kernel mode</errorname>, or
+ <para>My system crashes with either <errorname>Fatal trap
+ 12: page fault in kernel mode</errorname>, or
<errorname>panic:</errorname>, and spits out a bunch of
information. What should I do?</para>
</question>
@@ -2087,10 +2120,12 @@ bindkey ^[[3~ delete-char # for xterm</p
<para>The &os; developers are very interested in these
errors, but need some more information than just the error
you see. Copy your full crash message. Then consult the
- FAQ section on <link linkend="kernel-panic-troubleshooting">kernel panics</link>,
- build a debugging kernel, and get a backtrace. This might
- sound difficult, but you do not need any programming skills;
- you just have to follow the instructions.</para>
+ FAQ section on <link
+ linkend="kernel-panic-troubleshooting">kernel
+ panics</link>, build a debugging kernel, and get a
+ backtrace. This might sound difficult, but you do not
+ need any programming skills; you just have to follow the
+ instructions.</para>
</answer>
</qandaentry>
@@ -2103,19 +2138,21 @@ bindkey ^[[3~ delete-char # for xterm</p
<answer>
<para>The &os; kernel will only allow a certain number of
- processes to exist at one time. The number is based on the
- <varname>kern.maxusers</varname> &man.sysctl.8; variable.
- <varname>kern.maxusers</varname> also affects various other
- in-kernel limits, such as network buffers.
- If your machine is heavily loaded, you probably
- want to increase <varname>kern.maxusers</varname>. This
- will increase these other system limits in addition to the
+ processes to exist at one time. The number is based on
+ the <varname>kern.maxusers</varname> &man.sysctl.8;
+ variable. <varname>kern.maxusers</varname> also affects
+ various other in-kernel limits, such as network buffers.
+ If your machine is heavily loaded, you probably want to
+ increase <varname>kern.maxusers</varname>. This will
+ increase these other system limits in addition to the
maximum number of processes.</para>
<para>To adjust your <varname>kern.maxusers</varname> value,
- see the <link xlink:href="&url.books.handbook;/configtuning-kernel-limits.html#kern-maxfiles">File/Process Limits</link>
- section of the Handbook. (While that section refers to open
- files, the same limits apply to processes.)</para>
+ see the <link
+ xlink:href="&url.books.handbook;/configtuning-kernel-limits.html#kern-maxfiles">File/Process
+ Limits</link> section of the Handbook. (While that
+ section refers to open files, the same limits apply to
+ processes.)</para>
<para>If your machine is lightly loaded, and you are simply
running a very large number of processes, you can adjust
@@ -2124,25 +2161,25 @@ bindkey ^[[3~ delete-char # for xterm</p
<filename>/boot/loader.conf</filename>. The tunable will
not get adjusted until the system is rebooted. For more
information about tuning tunables, see
- &man.loader.conf.5;.
- If these processes are being run by a single user, you will
- also need to adjust <varname>kern.maxprocperuid</varname> to
- be one less than your new <varname>kern.maxproc</varname>
- value. (It must be at least one less because one system
- program, &man.init.8;, must always be running.)</para>
+ &man.loader.conf.5;. If these processes are being run by
+ a single user, you will also need to adjust
+ <varname>kern.maxprocperuid</varname> to be one less than
+ your new <varname>kern.maxproc</varname> value. (It must
+ be at least one less because one system program,
+ &man.init.8;, must always be running.)</para>
</answer>
</qandaentry>
<qandaentry>
<question xml:id="mail-loopback">
- <para>Why does <application>sendmail</application> give me an
- error reading <errorname>mail loops back to
+ <para>Why does <application>sendmail</application> give me
+ an error reading <errorname>mail loops back to
myself</errorname>?</para>
</question>
<answer>
<para>This is answered in the <link
- xlink:href="http://www.sendmail.org/faq/">Sendmail
+ xlink:href="http://www.sendmail.org/faq/">Sendmail
FAQ</link> as follows. This FAQ is recommended reading
when <quote>tweaking</quote> the mail setup.</para>
@@ -2170,9 +2207,9 @@ to /etc/mail/sendmail.cf.</programlistin
</question>
<answer>
- <para>The remote machine may be setting your terminal type to
- something other than the <literal>cons25</literal> terminal
- type required by the &os; console.</para>
+ <para>The remote machine may be setting your terminal type
+ to something other than the <literal>cons25</literal>
+ terminal type required by the &os; console.</para>
<para>There are a number of possible work-arounds for this
problem:</para>
@@ -2207,11 +2244,12 @@ to /etc/mail/sendmail.cf.</programlistin
</listitem>
<listitem>
- <para>Fire up an X server at the &os; end and login to the
- remote machine using an X based terminal emulator such
- as <command>xterm</command> or <command>rxvt</command>.
- The <envar>TERM</envar> variable at the remote host
- should be set to <literal>xterm</literal> or
+ <para>Fire up an X server at the &os; end and login to
+ the remote machine using an X based terminal emulator
+ such as <command>xterm</command> or
+ <command>rxvt</command>. The <envar>TERM</envar>
+ variable at the remote host should be set to
+ <literal>xterm</literal> or
<literal>vt100</literal>.</para>
</listitem>
</itemizedlist>
@@ -2221,46 +2259,48 @@ to /etc/mail/sendmail.cf.</programlistin
<qandaentry>
<question xml:id="connection-delay">
<para>Why does it take so long to connect to my computer via
- <command>ssh</command> or <command>telnet</command>?</para>
+ <command>ssh</command> or
+ <command>telnet</command>?</para>
</question>
<answer>
- <para>The symptom: there is a long delay between the time the
- TCP connection is established and the time when the client
- software asks for a password (or, in &man.telnet.1;'s case,
- when a login prompt appears).</para>
+ <para>The symptom: there is a long delay between the time
+ the TCP connection is established and the time when the
+ client software asks for a password (or, in
+ &man.telnet.1;'s case, when a login prompt
+ appears).</para>
<para>The problem: more likely than not, the delay is caused
by the server software trying to resolve the client's IP
address into a hostname. Many servers, including the
<application>Telnet</application> and
- <application>SSH</application> servers that come with &os;,
- do this to store the hostname
- in a log file for future reference by the
- administrator.</para>
+ <application>SSH</application> servers that come with
+ &os;, do this to store the hostname in a log file for
+ future reference by the administrator.</para>
<para>The remedy: if the problem occurs whenever you connect
- from your computer (the client) to any server, the problem is
- with the client; likewise, if the problem only occurs when
- someone connects to your computer (the server) the problem
- is with the server.</para>
-
- <para>If the problem is with the client, the only remedy is to
- fix the DNS so the server can resolve it. If this is on a
- local network, consider it a server problem and keep
- reading; conversely, if this is on the global Internet, you
- will most likely need to contact your ISP and ask them to
- fix it for you.</para>
+ from your computer (the client) to any server, the problem
+ is with the client; likewise, if the problem only occurs
+ when someone connects to your computer (the server) the
+ problem is with the server.</para>
+
+ <para>If the problem is with the client, the only remedy is
+ to fix the DNS so the server can resolve it. If this is
+ on a local network, consider it a server problem and keep
+ reading; conversely, if this is on the global Internet,
+ you will most likely need to contact your ISP and ask them
+ to fix it for you.</para>
<para>If the problem is with the server, and this is on a
- local network, you need to configure the server to be able to
- resolve address-to-hostname queries for your local address
- range. See the &man.hosts.5; and &man.named.8; manual pages
- for more information. If this is on the global Internet,
- the problem may be that your server's resolver is not
- functioning correctly. To check, try to look up another
- host — say, <systemitem>www.yahoo.com</systemitem>. If it
- does not work, that is your problem.</para>
+ local network, you need to configure the server to be able
+ to resolve address-to-hostname queries for your local
+ address range. See the &man.hosts.5; and &man.named.8;
+ manual pages for more information. If this is on the
+ global Internet, the problem may be that your server's
+ resolver is not functioning correctly. To check, try to
+ look up another host — say,
+ <systemitem>www.yahoo.com</systemitem>. If it does not
+ work, that is your problem.</para>
<para>Following a fresh install of &os;, it is also possible
that domain and name server information is missing from
@@ -2268,10 +2308,10 @@ to /etc/mail/sendmail.cf.</programlistin
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
More information about the svn-doc-head
mailing list