Spell check in articles:
* outtakes -> out takes * themself -> themselves * manpages -> man pages * suprising -> surprising * Blinkenlights -> blinking lights * transmition -> transmission * coresponds -> corresponds * accessable -> accessible * disasserting -> dis-asserting (for lack of a better word) * harddisks -> hard disks * likelyhood -> likelihood * repeate -> repeat
This commit is contained in:
parent
25be68f882
commit
98698f4f5e
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=11091
7 changed files with 21 additions and 21 deletions
|
@ -522,11 +522,11 @@
|
|||
</itemizedlist>
|
||||
|
||||
<para>You will almost certainly get a conflict because
|
||||
of the <literal>$Id: article.sgml,v 1.87 2001-10-23 21:19:23 murray Exp $</literal> (or in FreeBSD's case,
|
||||
of the <literal>$Id: article.sgml,v 1.88 2001-10-31 23:10:30 chern Exp $</literal> (or in FreeBSD's case,
|
||||
<literal>$FreeBSD<!-- stop expansion -->$</literal>) lines, so you will have to edit
|
||||
the file to resolve the conflict (remove the marker lines and
|
||||
the second <literal>$Id: article.sgml,v 1.87 2001-10-23 21:19:23 murray Exp $</literal> line, leaving the original
|
||||
<literal>$Id: article.sgml,v 1.87 2001-10-23 21:19:23 murray Exp $</literal> line intact).</para>
|
||||
the second <literal>$Id: article.sgml,v 1.88 2001-10-31 23:10:30 chern Exp $</literal> line, leaving the original
|
||||
<literal>$Id: article.sgml,v 1.88 2001-10-31 23:10:30 chern Exp $</literal> line intact).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
@ -566,7 +566,7 @@
|
|||
file the differences are and how many lines they span. This
|
||||
is followed by a number of lines; some (preceded by a blank)
|
||||
are context; some (preceded by a <literal>-</literal> sign)
|
||||
are outtakes and some (preceded by a <literal>+</literal>) are
|
||||
are out takes and some (preceded by a <literal>+</literal>) are
|
||||
additions.</para>
|
||||
|
||||
<para>You can also diff against a different version
|
||||
|
@ -1097,7 +1097,7 @@ docs:Documentation Bug:nik:</programlisting>
|
|||
about these you are encouraged to send them via the
|
||||
<email>doc@FreeBSD.org</email> mailing list. Committers
|
||||
interested in contributing to the documentation should familiarise
|
||||
themself with the
|
||||
themselves with the
|
||||
<ulink url="../../books/fdp-primer/index.html">Documentation Project Primer</ulink>.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
@ -1618,7 +1618,7 @@ docs:Documentation Bug:nik:</programlisting>
|
|||
developers, so allow some time to elapse before merging
|
||||
unless the &os.stable; fix is critical,
|
||||
time sensitive or so obvious as to make further testing
|
||||
unnecessary (spelling fixes to manpages, obvious bug/typo
|
||||
unnecessary (spelling fixes to man pages, obvious bug/typo
|
||||
fixes, etc.) In other words, apply common sense.</para>
|
||||
</listitem>
|
||||
|
||||
|
|
|
@ -579,7 +579,7 @@ exit 0
|
|||
hardware, so we did it ourselves. But if you are not set up for
|
||||
this, or you have a large number of cables to make, then you
|
||||
might consider getting some cables custom made. Look in the
|
||||
yellow pages, there are a suprising number of places that do
|
||||
yellow pages, there are a surprising number of places that do
|
||||
this! Getting custom-made cabling is good, and you can get much
|
||||
more professional results, but can be expensive. For example,
|
||||
the RJ-45 to DB-25 adapter kits described below are about $10
|
||||
|
@ -1225,7 +1225,7 @@ conventions
|
|||
Last modified: Thu Jul 19 10:19:28 EST 2001
|
||||
<!-- hhmts end -->
|
||||
<br>
|
||||
$Id: article.sgml,v 1.4 2001-10-23 21:23:00 murray Exp $
|
||||
$Id: article.sgml,v 1.5 2001-10-31 23:10:30 chern Exp $
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
|
|
@ -29,7 +29,7 @@
|
|||
either have a software routing component (a PPP daemon, specifically)
|
||||
that can do some filtering or can be combined with a filter on the
|
||||
machine running the link. But with DSL you only get a little white
|
||||
box with some Blinkenlights on it and an Ethernet port that takes
|
||||
box with some blinking lights on it and an Ethernet port that takes
|
||||
your traffic back and forth from the Internet and nothing else (to
|
||||
some extent the same can be said of other mass-market high speed
|
||||
connectivity methods, like cable modems or high speed wireless links
|
||||
|
@ -74,7 +74,7 @@
|
|||
RELENG_4 and -current have had bridging support for all Ethernet
|
||||
interfaces. This does not mean that any Ethernet interface will work.
|
||||
For them to work, they have to support a working promiscuous mode for
|
||||
both reception and transmition -- that is, they have to be able to
|
||||
both reception and transmission -- that is, they have to be able to
|
||||
transmit Ethernet packets with any source address, not just their own.
|
||||
In order to get good throughput, the cards should also be PCI bus
|
||||
mastering cards. The best choices still are the Intel EtherExpress Pro
|
||||
|
@ -121,7 +121,7 @@ firewall_type="open"</programlisting>
|
|||
<para>There is one more thing that is necessary. When running IP over
|
||||
Ethernet, there are actually two Ethernet protocols in use. One
|
||||
is IP, the other is ARP. ARP is used when a machine must figure out
|
||||
what Ethernet address coresponds to a given IP address. ARP is not
|
||||
what Ethernet address corresponds to a given IP address. ARP is not
|
||||
a part of the IP layer, since it only applies to IP when run over
|
||||
Ethernet. The standard ipfirewall rule for the open firewall is</para>
|
||||
|
||||
|
|
|
@ -37,7 +37,7 @@
|
|||
<warning>
|
||||
<para>This procedure will make the 'Server' both insecure and dangerous,
|
||||
it is best to just keep the 'Server' on its own hub and not in any way
|
||||
accessable by any machines other than the 'Clients'.</para>
|
||||
accessible by any machines other than the 'Clients'.</para>
|
||||
</warning>
|
||||
|
||||
<para>Terminology : </para>
|
||||
|
@ -220,7 +220,7 @@
|
|||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Put the install files in an NFS accessable location on the
|
||||
<para>Put the install files in an NFS accessible location on the
|
||||
Server. Make a directory corresponding the 'nfs' directive in the
|
||||
<filename> install.cfg</filename> file and mirror the FreeBSD
|
||||
install files there, you will want it to look somewhat like
|
||||
|
@ -266,7 +266,7 @@ RELNOTES.TXT compat1x doc packages</screen>
|
|||
|
||||
<para>Inside your custom package dir you will want a file called
|
||||
<filename>PLIST</filename> which contains all the files that you wish to
|
||||
install and be incorperated into your package.</para>
|
||||
install and be incorporated into your package.</para>
|
||||
|
||||
<para>You will also want files called '<filename>pre</filename>' and
|
||||
'<filename>post</filename>' in the directory, these are shell scripts
|
||||
|
|
|
@ -179,7 +179,7 @@
|
|||
connected to the UART is a modem, the modem may report the
|
||||
presence of a carrier on the phone line while the computer
|
||||
may be able to instruct the modem to reset itself or to not
|
||||
take calls by asserting or disasserting one more of these
|
||||
take calls by asserting or dis-asserting one more of these
|
||||
extra signals. The function of each of these additional
|
||||
signals is defined in the EIA RS232-C standard.</para>
|
||||
</sect2>
|
||||
|
|
|
@ -1231,7 +1231,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen>
|
|||
<para>In some cases you come across devices that use multiple
|
||||
logical units (LUNs) on a single SCSI ID. In most cases FreeBSD
|
||||
only probes devices for LUN 0. An example are so called bridge
|
||||
boards that connect 2 non-SCSI harddisks to a SCSI bus (e.g. an
|
||||
boards that connect 2 non-SCSI hard disks to a SCSI bus (e.g. an
|
||||
Emulex MD21 found in old Sun systems).</para>
|
||||
|
||||
<para>This means that any devices with LUNs != 0 are not normally
|
||||
|
|
|
@ -20,8 +20,8 @@
|
|||
<year>2001</year>
|
||||
<holder>Robert A. Van Valzah</holder>
|
||||
</copyright>
|
||||
<pubdate>$Date: 2001-10-29 23:20:40 $ GMT</pubdate>
|
||||
<releaseinfo>$Id: article.sgml,v 1.2 2001-10-29 23:20:40 chern Exp $</releaseinfo>
|
||||
<pubdate>$Date: 2001-10-31 23:10:31 $ GMT</pubdate>
|
||||
<releaseinfo>$Id: article.sgml,v 1.3 2001-10-31 23:10:31 chern Exp $</releaseinfo>
|
||||
</articleinfo>
|
||||
|
||||
<abstract>
|
||||
|
@ -253,7 +253,7 @@
|
|||
and failure resilience--but this comes at a loss in capacity.</para>
|
||||
|
||||
<note><para>Both concatenation and striping bring their benefits over a
|
||||
single spindle at the cost of increased likelyhood of failure since
|
||||
single spindle at the cost of increased likelihood of failure since
|
||||
more than one spindle is now involved.</para></note>
|
||||
|
||||
<para>When three or more spindles are present,
|
||||
|
@ -1262,7 +1262,7 @@ ok <userinput>boot -s</userinput</screen>
|
|||
&prompt.root; <userinput>disklabel -R ad0s1 disklabel.ad0s1</userinput>
|
||||
&prompt.root; <userinput>disklabel -R ad2s1 disklabel.ad2s1</userinput></screen>
|
||||
|
||||
<note><para>If you have additional spindles, repeate the
|
||||
<note><para>If you have additional spindles, repeat the
|
||||
above commands as appropriate for them.</para></note>
|
||||
|
||||
</step>
|
||||
|
@ -2087,7 +2087,7 @@ ok <userinput>boot -s</userinput</screen>
|
|||
use strict;
|
||||
use FileHandle;
|
||||
|
||||
my $config_tag1 = '$Id: article.sgml,v 1.2 2001-10-29 23:20:40 chern Exp $';
|
||||
my $config_tag1 = '$Id: article.sgml,v 1.3 2001-10-31 23:10:31 chern Exp $';
|
||||
# Copyright (C) 2001 Robert A. Van Valzah
|
||||
#
|
||||
# Bootstrap Vinum
|
||||
|
|
Loading…
Reference in a new issue