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

Update Question 5.1:

Browse source 
- Put non-breakable spaces between quantities and units

Approved by:	gabor (mentor)
This commit is contained in:
Gabor Pali 2008-06-14 10:16:57 +00:00
parent cd820d796b
commit e0f19aeafa
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=32234
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -2829,26 +2829,26 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
and virtual addresses.</para>
<para>The convention for most PC hardware is to use the memory area
between 3.5G and 4G for a special purpose (usually for PCI). This
between 3.5&nbsp;GB and 4&nbsp;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 appear in 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 500M of RAM is entirely
nothing and the ability to use that last 500&nbsp;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>
<para>On a 32 bit version of &os;, the memory appears lost, since it
will be remapped above 4G, which a 32 bit kernel is unable to
<para>On a 32&nbsp;bit version of &os;, the memory appears lost, since it
will be remapped above 4&nbsp;GB, which a 32&nbsp;bit kernel is unable to
access. In this case, the solution is to build a PAE enabled
kernel. See <link linkend="memory-limits">this FAQ entry</link>
for more information.</para>
<para>On a 64 bit version of &os;, or when running a PAE-enabled
<para>On a 64&nbsp;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. This is normal and the