o Grammar fixes
o Fix various incorrect uses of apostrophes o Fix an instance of uppercasing where emphasis tags are more appropriate
This commit is contained in:
Ceri Davies
parent
0549acd463
commit
a2f3dc1df9
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=22869
1 changed files with 26 additions and 26 deletions
|
|
@ -1759,7 +1759,7 @@ sectors/track: 63</screen>
|
|||
supplied this way to get around certain limitations in
|
||||
&ms-dos;) and the disk capacity is more than 1GB, use M
|
||||
cylinders, 63 sectors per track (<emphasis>not</emphasis>
|
||||
64), and 255 heads, where 'M' is the disk capacity in MB
|
||||
64), and 255 heads, where <literal>M</literal> is the disk capacity in MB
|
||||
divided by 7.844238 (!). So our example 2GB drive would
|
||||
have 261 cylinders, 63 sectors per track and 255
|
||||
heads.</para>
|
||||
|
|
@ -3221,10 +3221,10 @@ ARRE (Auto Read Reallocation Enbld): 1</programlisting>
|
|||
the disk drive controller card and BIOS handle the task of
|
||||
locking out bad sectors. This is fine for operating systems
|
||||
like DOS that use BIOS code to access the disk. However,
|
||||
FreeBSD's disk driver does not go through BIOS, therefore a
|
||||
FreeBSD's disk driver does not go through the BIOS, therefore a
|
||||
mechanism, bad144, exists that replaces this functionality.
|
||||
bad144 only works with the wd driver (which means it is not
|
||||
supported in FreeBSD 4.0), it is NOT able to be used with SCSI.
|
||||
supported in FreeBSD 4.0), it is <emphasis>not</emphasis> able to be used with SCSI.
|
||||
bad144 works by entering all bad sectors found into a special
|
||||
file.</para>
|
||||
|
||||
|
|
@ -4007,7 +4007,7 @@ quit</programlisting>
|
|||
match and then fail due to resource conflicts. So, it
|
||||
disables the programmable cards first so this double probing
|
||||
cannot happen. It also means that it needs to know the PnP
|
||||
id's for supported PnP hardware. Making this more user
|
||||
ids for supported PnP hardware. Making this more user
|
||||
tweakable is on the TODO list.</para>
|
||||
</blockquote>
|
||||
|
||||
|
|
@ -5069,7 +5069,7 @@ kern.timecounter.hardware: TSC -> i8254</screen>
|
|||
consumed by the FreeBSD sources and additional maintenance work.
|
||||
Thus, it is much easier for both the developers and users to
|
||||
keep CVSup as a separate port, which can be easily installed as
|
||||
a package bundled on the FreeBSD installation CD's.</para>
|
||||
a package bundled on the FreeBSD installation CDs.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
|
@ -5207,7 +5207,7 @@ kern.timecounter.hardware: TSC -> i8254</screen>
|
|||
A. Welsh, available at <ulink
|
||||
url="http://www.stardate.bc.ca/eawpatches/html/default.htm"></ulink>.
|
||||
After timidity++ has been installed properly, midi files may
|
||||
be converted to wav's with the following command
|
||||
be converted to wav files with the following command
|
||||
line:</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>timidity -Ow -s 44100 -o /tmp/juke/01.wav 01.mid</userinput></screen>
|
||||
|
|
@ -5410,11 +5410,11 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
|
|||
|
||||
<qandaentry>
|
||||
<question id="scheduler-kern-quantum">
|
||||
<para>What is 'kern.quantum'?</para>
|
||||
<para>What is <literal>kern.quantum</literal>?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para><quote>kern.quantum</quote> is the maximum number of
|
||||
<para><literal>kern.quantum</literal> is the maximum number of
|
||||
ticks a process can run without being preempted. It is
|
||||
specific to the 4BSD scheduler, so you can use its
|
||||
presence or absence to determine which scheduler is in
|
||||
|
|
@ -6624,7 +6624,7 @@ options SYSVMSG # enable for messaging</programlisting>
|
|||
|
||||
<qandaentry>
|
||||
<question id="sendmail-alternative">
|
||||
<para>What other mail-server software can I use, instead of
|
||||
<para>What other mail-server software can I use instead of
|
||||
Sendmail?</para>
|
||||
</question>
|
||||
|
||||
|
|
@ -6634,12 +6634,12 @@ options SYSVMSG # enable for messaging</programlisting>
|
|||
easily replace it with one of the other MTA (for instance,
|
||||
an MTA installed from the ports).</para>
|
||||
|
||||
<para>There are various alternative MTA's in the ports tree
|
||||
<para>There are various alternative MTAs in the ports tree
|
||||
already, with <filename
|
||||
role="package">mail/exim</filename>, <filename
|
||||
role="package">mail/postfix</filename>, <filename
|
||||
role="package">mail/qmail</filename>, <filename
|
||||
role="package">mail/zmailer</filename>, being some of the
|
||||
role="package">mail/qmail</filename>, and <filename
|
||||
role="package">mail/zmailer</filename> being some of the
|
||||
most popular choices.</para>
|
||||
|
||||
<para>Diversity is nice, and the fact that you have many
|
||||
|
|
@ -6649,7 +6649,7 @@ options SYSVMSG # enable for messaging</programlisting>
|
|||
Qmail?</quote> in the mailing lists. If you do feel like
|
||||
asking, first check the mailing list archives. The
|
||||
advantages and disadvantages of each and every one of the
|
||||
available MTA's have already been discussed a few
|
||||
available MTAs have already been discussed a few
|
||||
times.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
|
@ -6660,7 +6660,7 @@ options SYSVMSG # enable for messaging</programlisting>
|
|||
do I do?</para>
|
||||
</question><answer>
|
||||
|
||||
<para>Do not Panic! Simply restart the system, type
|
||||
<para>Do not panic! Simply restart the system, type
|
||||
<userinput>boot -s</userinput> at the Boot: prompt (just
|
||||
<userinput>-s</userinput> for FreeBSD releases before 3.2) to
|
||||
enter Single User mode. At the question about the shell to use,
|
||||
|
|
@ -6682,8 +6682,8 @@ options SYSVMSG # enable for messaging</programlisting>
|
|||
|
||||
<answer>
|
||||
<para>If you are using syscons (the default console driver)
|
||||
build and install a new kernel with the following
|
||||
option.</para>
|
||||
build and install a new kernel with the
|
||||
line</para>
|
||||
|
||||
<programlisting>options SC_DISABLE_REBOOT</programlisting>
|
||||
|
||||
|
|
@ -7099,7 +7099,7 @@ options SYSVMSG # enable for messaging</programlisting>
|
|||
where they maintain their data, but can often be
|
||||
immediately reused (either with their old association,
|
||||
or reused with a new association.) There can be certain
|
||||
immediate transition from active to 'cache' state if the
|
||||
immediate transitions from <literal>active</literal> to <literal>cache</literal> state if the
|
||||
page is known to be clean (unmodified), but that
|
||||
transition is a matter of policy, depending upon the
|
||||
algorithm choice of the VM system
|
||||
|
|
@ -7118,24 +7118,24 @@ options SYSVMSG # enable for messaging</programlisting>
|
|||
</itemizedlist>
|
||||
|
||||
<para>Pages are most often written to disk (sort of a VM
|
||||
sync) when they are in the 'inactive' state, but 'active'
|
||||
sync) when they are in the inactive state, but active
|
||||
pages can also be synced (but requires the
|
||||
availability of certain CPU features.) This depends upon
|
||||
the CPU tracking of the 'modified' bit being available,
|
||||
the CPU tracking of the modified bit being available,
|
||||
and in certain situations there can be an advantage for a
|
||||
block of VM pages to be synced, whether they are active or
|
||||
inactive. In most common cases, it is best to think of
|
||||
the 'inactive' queue to be a queue of relatively unused
|
||||
the inactive queue to be a queue of relatively unused
|
||||
pages that might or might not be in the process of being
|
||||
written to disk. 'Cached' pages are already 'synced', not
|
||||
written to disk. Cached pages are already synced, not
|
||||
mapped, but available for immediate process use with their
|
||||
old association or with a new association. Free pages are
|
||||
available at interrupt level, but cached or free pages can
|
||||
be used at process state for reuse. Cache pages aren't
|
||||
be used at process state for reuse. Cache pages are not
|
||||
adequately locked to be available at interrupt
|
||||
level.</para>
|
||||
|
||||
<para>There are some other flags (e.g. Busy flag or busy
|
||||
<para>There are some other flags (e.g., busy flag or busy
|
||||
count) that might modify some of the rules that I
|
||||
described.</para>
|
||||
</answer>
|
||||
|
|
@ -8340,7 +8340,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
|
|||
</question>
|
||||
|
||||
<answer>
|
||||
<para>Typically, people who ask this question have two PC's
|
||||
<para>Typically, people who ask this question have two PCs
|
||||
at home, one with FreeBSD and one with some version of
|
||||
&windows; the idea is to use the FreeBSD box to connect to
|
||||
the Internet and then be able to access the Internet from
|
||||
|
|
@ -8959,7 +8959,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
|
|||
|
||||
<qandaentry>
|
||||
<question id="cvsup-missing-libs">
|
||||
<para>I've just installed CVSup but trying to execute it
|
||||
<para>I have just installed CVSup but trying to execute it
|
||||
produces errors. What is wrong?</para>
|
||||
</question>
|
||||
|
||||
|
|
@ -11741,7 +11741,7 @@ raisechar=^^</programlisting>
|
|||
it is part of standard practise to send data to the screen
|
||||
of interesting variety to keep all the pixies that make up
|
||||
your picture happy. Screen pixies (commonly mis-typed or
|
||||
re-named as 'pixels') are categorised by the type of hat
|
||||
re-named as <quote>pixels</quote> are categorised by the type of hat
|
||||
they wear (red, green or blue) and will hide or appear
|
||||
(thereby showing the colour of their hat) whenever they
|
||||
receive a little piece of food. Video cards turn data into
|
||||
|
|
|
|||
Loading…
Reference in a new issue