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

o Expand some contractions.

Browse source 
This is the second and final part of:

PR:             docs/70954
Submitted by:   Jesus R. Camou <jcamou@cox.net>
This commit is contained in:
Ceri Davies 2004-08-26 20:16:31 +00:00
parent 3281116969
commit a80c9017b1
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=22130
1 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -4302,7 +4302,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<para>You must remove all power from the PC card slot to
fully reset the hardware. Completely power off the
laptop. (Don't suspend it, don't let it go into standby;
laptop. (Do not suspend it, do not let it go into standby;
the power needs to be completely off.) Wait a few
moments, and reboot. Your PC card should work now.</para>
@ -4402,7 +4402,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<para>The problem can be caused by many factors, although
perhaps the most common cause is faulty or incorrect
cabling. Check that the ATA cables are undamaged and rated
for the Ultra DMA mode in use. If you're using removable
for the Ultra DMA mode in use. If you are using removable
drive trays, they must also be compatible. Be sure that
all connections are making good contact. Problems have
also been noticed when an old drive is installed on the
@ -4444,10 +4444,10 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
using a combination of hard coded lock orders, and run-time
detected lock orders, and generates console warnings when lock
orders are violated. The intent of this is to detect the
potential for deadlocks due to lock order violations; it's worth
potential for deadlocks due to lock order violations; it is worth
observing that Witness is actually slightly conservative, and so
it's possible to get false positives. In the event that Witness
is accurately reporting a lock order problem, it's basically
it is possible to get false positives. In the event that Witness
is accurately reporting a lock order problem, it is basically
saying "If you were unlucky, a deadlock would have happened
here". There are a couple of "well known" false positives,
which we need to do a better job of documenting to prevent
@ -6340,7 +6340,7 @@ C:\="DOS"</programlisting>
<username>root</username> user.
&man.df.1; does not count that space when
calculating the <literal>Capacity</literal> column, so it can
exceed 100%. Also, you'll notice that the
exceed 100%. Also, you will notice that the
<literal>Blocks</literal> column is always greater than the
sum of the <literal>Used</literal> and
<literal>Avail</literal> columns, usually by a factor of
@ -8364,7 +8364,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
just a special case of the previous question and works
perfectly well.</para>
<para>If you're using dialup to connect to the Internet
<para>If you are using dialup to connect to the Internet
user-mode &man.ppp.8; contains a <option>-nat</option>
option. If you run &man.ppp.8; with the
<option>-nat</option> option, set
@ -8445,7 +8445,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
</question>
<answer>
<para>Because they aren't necessary. In the Berkeley
<para>Because they are not necessary. In the Berkeley
networking framework, network interfaces are only directly
accessible by kernel code. Please see the
<filename>/etc/rc.network</filename> file and the manual