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

Expand most contractions.

Browse source
This commit is contained in:
Giorgos Keramidas 2001-12-08 12:15:43 +00:00
parent 96e9fe2ad3
commit 4f6cf10151
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=11374
1 changed files with 51 additions and 51 deletions

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

@ -1438,7 +1438,7 @@ File: +DESC (ignored)</screen>
<qandaentry>
<question id="bad144-3x-4x">
<para>I've just upgraded from 3.X to 4.X, and my first boot
<para>I have just upgraded from 3.X to 4.X, and my first boot
failed with <errorname>bad sector table not
supported</errorname></para>
</question>
@ -1532,7 +1532,7 @@ sectors/track: 63</screen>
<listitem>
<para>If you are using Windows95 or Win98 did you run
<command>fdimage</command> or <command>rawrite</command> in
pure DOS mode? These OS's can interfere with programs that
pure DOS mode? These operating systems can interfere with programs that
write directly to hardware, which the disk creation program
does; even running it inside a DOS shell in the GUI can
cause this problem.</para>
@ -2429,10 +2429,10 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on
<ulink URL="http://www.freebsd.org/search/#mailinglists">
archives</ulink> before asking about the latest and
greatest hardware. Chances are a discussion about the
type of hardware you're looking for took place just last
type of hardware you are looking for took place just last
week.</para>
<para>If you're looking for a laptop, check the
<para>If you are looking for a laptop, check the
FreeBSD-mobile mailing list archives. Otherwise, you
probably want the archives for FreeBSD-questions, or
possibly a specific mailing list for a particular hardware
@ -3207,7 +3207,7 @@ diff -u -r1.60.2.1 -r1.60.2.2
<answer>
<para>The newer AIC789x series Adaptec chips are supported under
the CAM SCSI framework which made it's debut in 3.0. Patches
the CAM SCSI framework which made its debut in 3.0. Patches
against 2.2-STABLE are in <ulink
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/development/cam/">
ftp://ftp.FreeBSD.org/pub/FreeBSD/development/cam/</ulink>.
@ -3278,7 +3278,7 @@ diff -u -r1.60.2.1 -r1.60.2.2
<qandaentry>
<question id="micron-3comnic-failure">
<para>Why doesn't my 3Com PCI network card work with my Micron
<para>Why does my 3Com PCI network card not work with my Micron
computer?</para>
</question>
@ -3535,7 +3535,7 @@ quit</programlisting>
<para>It is broken. It cannot handle commands on both channels
simultaneously.</para>
<para>There's a workaround available now and it is enabled
<para>There is a workaround available now and it is enabled
automatically if your system uses this chip. For the details
refer to the manual page of the disk driver (man 4 wd).</para>
@ -4057,7 +4057,7 @@ quit</programlisting>
<question id="aci0-illegal-cable">
<para>When I boot my system, I get the error
<errorname>ahc0: illegal cable configuration</errorname>.
My cabling is correct. What's going on?</para>
My cabling is correct. What is going on?</para>
</question>
<answer>
@ -4095,7 +4095,7 @@ quit</programlisting>
You have asked mail to the domain (e.g., domain.net) to be
forwarded to a specific host (in this case, relay.domain.net)
by using an MX record, but the relay machine doesn't recognize
by using an MX record, but the relay machine does not recognize
itself as domain.net. Add domain.net to /etc/sendmail.cw
(if you are using FEATURE(use_cw_file)) or add "Cw domain.net"
to /etc/sendmail.cf.
@ -4323,7 +4323,7 @@ IO range check 0x00 activate 0x01</screen>
<para>You should first make a backup of <filename>sio.c</filename>
just in case things go wrong. You will also need it to make the
patch to submit with your PR (you are going to submit a PR,
aren't you?) then edit <filename>sio.c</filename> and search
are you not?) then edit <filename>sio.c</filename> and search
for the line</para>
<programlisting>static struct isa_pnp_id sio_ids[] = {</programlisting>
@ -5192,7 +5192,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
<qandaentry>
<question id="ports-3x">
<para>Why can't I build this port on my 3.X-STABLE machine?</para>
<para>Why can I not build this port on my 3.X-STABLE machine?</para>
</question>
<answer>
@ -5277,7 +5277,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
<port>sysutils/portupgrade</port>.
Since it is written in Ruby,
<command>portupgrade</command> is an unlikely candidate for
integration with the main FreeBSD tree. That shouldn't
integration with the main FreeBSD tree. That should not
stop anyone from using it, however.</para>
<para>If your system is up full time, the &man.periodic.8 system
@ -5290,8 +5290,8 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
<qandaentry>
<question id="minimal-sh">
<para>Why is <command>/bin/sh</command> so minimal? Why doesn't
FreeBSD use <command>bash</command> or another shell?</para>
<para>Why is <command>/bin/sh</command> so minimal? Why does
FreeBSD not use <command>bash</command> or another shell?</para>
</question>
<answer>
@ -6092,7 +6092,7 @@ C:\="DOS"</programlisting>
over, and with no need for <quote>DD</quote> mode at all. If,
however, you are still greeted with the dreaded <errorname>read
error</errorname> message when you try to boot, it is time to cross
your fingers and go for it - there's nothing left to
your fingers and go for it - there is nothing left to
lose.</para>
<para>To return a <quote>dangerously dedicated</quote> disk
@ -6117,7 +6117,7 @@ C:\="DOS"</programlisting>
<question id="du-vs-df">
<para>The <command>du</command> and <command>df</command>
commands show different amounts of disk space available.
What's going on?</para>
What is going on?</para>
</question>
<answer>
@ -6131,7 +6131,7 @@ C:\="DOS"</programlisting>
<command>du</command>.</para>
<para>When a program is using a file, and you delete the
file, the file isn't really removed from the filesystem
file, the file is not really removed from the filesystem
until the program stops using it. The file is immediately
deleted from the directory listing, however. You can see
this easily enough with a program such as
@ -6141,12 +6141,12 @@ C:\="DOS"</programlisting>
disks can be so large today, this might be a
<emphasis>very</emphasis> large file!) If you delete this
file while using <command>more</command> on it,
<command>more</command> doesn't immediately choke and
<command>more</command> does not immediately choke and
complain that it cannot view the file. The entry is
simply removed from the directory so no other program or
user can access it. <command>du</command> shows that it
is gone &mdash; it has walked the directory tree and the file
isn't listed. <command>df</command> shows that it is
is not listed. <command>df</command> shows that it is
still there, as the filesystem knows that
<command>more</command> is still using that space. Once
you end the <command>more</command> session,
@ -6170,7 +6170,7 @@ C:\="DOS"</programlisting>
<qandaentry>
<question id="safe-softupdates">
<para>Which partitions can safely use softupdates? I've
<para>Which partitions can safely use softupdates? I have
heard that softupdates on <filename>/</filename> can cause
problems.</para>
</question>
@ -6196,7 +6196,7 @@ C:\="DOS"</programlisting>
file. The first large file is not yet actually removed
from the physical disk, so the disk might not have enough
room for the second large file. You get an error that the
partition don't have enough space, although you know
partition does not have enough space, although you know
perfectly well that you just released a large chunk of
space! When you try again mere seconds later, the file
creation works as you expect. This has left more than one
@ -6223,7 +6223,7 @@ C:\="DOS"</programlisting>
possible that data could be lost. This risk is negligible
for most applications, but you should be aware that it
exists. If your system cannot tolerate this much risk,
don't use softupdates on the root filesystem!</para>
do not use softupdates on the root filesystem!</para>
<para><filename>/</filename> is traditionally one of the
smallest partitions. By default, FreeBSD puts the
@ -6595,7 +6595,7 @@ ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format</scr
<qandaentry>
<question id="ccd-disklabel">
<para>Why can't I edit the disklabel on my ccd?</para>
<para>Why can I not edit the disklabel on my ccd?</para>
</question>
<answer>
@ -6880,7 +6880,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<para>Refer to the previous section for details of how to turn
this <filename>.mc</filename> file into a
<filename>sendmail.cf</filename> file. Also, don't forget to
<filename>sendmail.cf</filename> file. Also, do not forget to
restart <application>sendmail</application> after updating <filename>sendmail.cf</filename>.</para>
</answer>
</qandaentry>
@ -7450,7 +7450,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<para>Rearranging your partitions with dump takes a bit more
work. To merge a partition like <filename>/var</filename>
into it's parent, create the new partition large enough
into its parent, create the new partition large enough
for both, move the parent partition as described above,
then move the child partition into the empty directory
that the first move created:</para>
@ -7462,8 +7462,8 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
&prompt.root; <userinput>cd var</userinput>
&prompt.root; <userinput>dump 0af - /var | restore xf -</userinput></screen>
<para>To split a directory from it's parent, say putting
<filename>/var</filename> on it's own partition when it wasn't
<para>To split a directory from its parent, say putting
<filename>/var</filename> on its own partition when it was not
before, create both partitions, then mount the child partition
on the appropriate directory in the temporary mount point, then
move the old single partition:</para>
@ -7603,7 +7603,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<qandaentry>
<question id="unsetting-schg">
<para>Why can't I unset the <literal>schg</literal> file
<para>Why can I not unset the <literal>schg</literal> file
flag?</para>
</question>
@ -7617,8 +7617,8 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<qandaentry>
<question id="ssh-shosts">
<para>Why doesn't SSH authentication through
<filename>.shosts</filename> work by default in recent
<para>Why does SSH authentication through
<filename>.shosts</filename> not work by default in recent
versions of FreeBSD?</para>
</question>
@ -7669,7 +7669,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
</question>
<answer>
<para>You can't do that with the standard boot manager without
<para>You can not do that with the standard boot manager without
rewriting it. There are a number of other boot managers
in the <filename>sysutils</filename> ports category that
provide this functionality.</para>
@ -7729,7 +7729,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<qandaentry>
<question id="x-and-moused">
<para>Why doesn't my mouse work with X?</para>
<para>Why doest my mouse not work with X?</para>
</question>
<answer>
@ -8136,7 +8136,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen>
<para>It is imperative that you completely shut down X Window if
it is running, before running this command. If you don't,
it is running, before running this command. If you do not,
your system will probably appear to hang/lock up after
executing the kill command.</para>
</answer>
@ -8894,7 +8894,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
<qandaentry>
<question id="nfs-linux">
<para>Why can't I NFS-mount from a Linux box?</para>
<para>Why can I not NFS-mount from a Linux box?</para>
</question>
<answer>
@ -8907,7 +8907,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
<qandaentry>
<question id="nfs-sun">
<para>Why can't I NFS-mount from a Sun box?</para>
<para>Why can I not NFS-mount from a Sun box?</para>
</question>
<answer>
@ -9482,7 +9482,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
using a MAC address in a format that FreeBSD does not
recognize. This is probably caused by someone
experimenting with an Ethernet card somewhere else on the
network. You'll see this most commonly on cable modem
network. You will see this most commonly on cable modem
networks. It is harmless, and should not affect the
performance of your FreeBSD machine.</para>
</answer>
@ -9561,7 +9561,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
<qandaentry>
<question id="ppp-nodial-auto">
<para>Why won't &man.ppp.8; dial in <literal>-auto</literal>
<para>Why will &man.ppp.8; not dial in <literal>-auto</literal>
mode?</para>
</question>
@ -9575,7 +9575,7 @@ default 10.0.0.2 UGSc 0 0 tun0
<para>This is assuming that you have used the addresses from the
handbook, the man page or from the ppp.conf.sample file.
If you haven't got a default route, it may be because you are
If you do not have a default route, it may be because you are
running an old version of &man.ppp.8;
that does not understand the word <literal>HISADDR</literal>
in the ppp.conf file. If your version of
@ -9890,7 +9890,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
<qandaentry>
<question id="ppp-lcp-constant">
<para>LCP negotiations continue 'till the connection is
<para>LCP negotiations continue until the connection is
closed. What is wrong?</para>
</question>
@ -9937,7 +9937,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
immediately receives the following ACK and enters
<acronym>OPENED</acronym>.</para>
<para>This goes on 'till one side figures out that they are
<para>This goes on until one side figures out that they are
getting nowhere and gives up.</para>
<para>The best way to avoid this is to configure one side to be
@ -10124,7 +10124,7 @@ CCP: Received Terminate Ack (1) state = Req-Sent (6)</programlisting>
<qandaentry>
<question id="ppp-connectionspeed">
<para>Why doesn't &man.ppp.8; log my connection speed?</para>
<para>Why does &man.ppp.8; not log my connection speed?</para>
</question>
<answer>
@ -10326,7 +10326,7 @@ ATDT1234567</programlisting>
<qandaentry>
<question id="ppp-nat-games">
<para>Why don't most games work with the -nat switch?</para>
<para>Why do most games not work with the -nat switch?</para>
</question>
<answer>
@ -10673,7 +10673,7 @@ sio1: type 16550A</programlisting>
<para>The <filename>GENERIC</filename> kernel includes support
for two serial ports using the same irq and port address
settings in the above example. If these settings are not
right for your system, or if you've added modem cards or have
right for your system, or if you have added modem cards or have
more serial ports than your kernel is configured for, just
reconfigure your kernel. See section
<link linkend="make-kernel">about building a kernel</link> for
@ -10938,7 +10938,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
<qandaentry>
<question id="cannot-tip">
<para>Why can't I run <command>tip</command> or
<para>Why can I not run <command>tip</command> or
<command>cu</command>?</para>
</question>
@ -11501,7 +11501,7 @@ raisechar=^^</programlisting>
<qandaentry>
<question id="chmod-symlinks">
<para>Why won't chmod change the permissions on symlinks?</para>
<para>Why will chmod not change the permissions on symlinks?</para>
</question>
<answer>
@ -11688,7 +11688,7 @@ raisechar=^^</programlisting>
too many volunteers were wandering out of the room during the
tests, thus skewing the results. We think most of the volunteers
are at Apple now, working on their new <quote>scratch and
sniff</quote> GUI. It's a funny old business we're in!</para>
sniff</quote> GUI. It is a funny old business we are in!</para>
<para>Seriously, both FreeBSD and Linux use the
<acronym>HLT</acronym> (halt) instruction when the system is
@ -11725,7 +11725,7 @@ raisechar=^^</programlisting>
but do not be surprised if they react adversely and try to stop
you. In fact, if at any point during the exercise you hear the
satanic voice of Bill Gates coming from the built-in speaker,
take off running and don't ever look back! Freed from the
take off running and do not ever look back! Freed from the
counterbalancing influence of the BSD daemons, the twin demons
of DOS and Windows are often able to re-assert total control
over your machine to the eternal damnation of your soul.
@ -11800,8 +11800,8 @@ raisechar=^^</programlisting>
<answer>
<para>The really, really short answer is that you should not.
The somewhat longer answer is that just because you are
capable of building a bikeshed doesn't mean you should stop
others from building one just because you don't like the
capable of building a bikeshed does not mean you should stop
others from building one just because you do not like the
color they plan to paint it. This is a metaphor indicating
that you need not argue about every little feature just
because you know enough to do so. Some people have
@ -12002,7 +12002,7 @@ raisechar=^^</programlisting>
network connection and <filename>/</filename> or angering
your ISP, as most of the data will end up getting
converted to heat by their equipment, but they generally
have good cooling, so if you don't overdo it you should be
have good cooling, so if you do not overdo it you should be
OK.</para>
<para><emphasis>Paul Robinson adds:</emphasis</para>
@ -12030,7 +12030,7 @@ raisechar=^^</programlisting>
<para>Incidentally, as an ex-admin of a large ISP who
experienced many problems attempting to maintain a stable
temperature in a server room, I would strongly discourage
people sending the data they don't want out to the
people sending the data they do not want out to the
network. The fairies who do the packet switching and
routing get annoyed by it as well.</para>
</answer>