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

Standardize:

Browse source 
TCL -> Tcl
ethernet -> Ethernet
ftp (noun) -> FTP

Approved by:	murray
This commit is contained in:
Chern Lee 2001-07-17 22:20:51 +00:00
parent 93321474e5
commit 3e8d98b70a
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9954
18 changed files with 94 additions and 94 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
en_US.ISO8859-1/articles/explaining-bsd/article.sgml
View file

@ -26,7 +26,7 @@
world's network connected machines run Linux. 14.6% run BSD UNIX.
Some of the world's largest web operations, such as <ulink
url="http://www.yahoo.com">Yahoo!</ulink>, run BSD. The world's
busiest ftp server, <ulink
busiest FTP server, <ulink
url="ftp://ftp.cdrom.com">ftp.cdrom.com</ulink>, uses BSD to
transfer 1.4 TB of data a day. Clearly this is not a niche
market: BSD is a well-kept secret.</para>
@ -352,7 +352,7 @@
<para>At regular intervals, between two and four times a year, the
projects bring out a <emphasis>RELEASE</emphasis> version of the
system, which is available on CD-ROM and for free download from
ftp sites, for example OpenBSD 2.6-RELEASE or NetBSD 1.4-RELEASE.
FTP sites, for example OpenBSD 2.6-RELEASE or NetBSD 1.4-RELEASE.
The RELEASE version is intended for end users and is the normal
version of the system. NetBSD also provides <emphasis>patch
releases</emphasis> with a third digit, for example NetBSD

10
en_US.ISO8859-1/articles/new-users/article.sgml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/new-users/article.sgml,v 1.20 2001/07/06 13:02:50 dd Exp $ -->
<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/new-users/article.sgml,v 1.21 2001/07/17 20:51:48 chern Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN">
@ -413,7 +413,7 @@
the long run the text editor <command>vi</command> is worth
learning. There's an excellent tutorial on vi in
<filename>/usr/src/contrib/nvi/docs/tutorial</filename> if you
have that installed; otherwise you can get it by ftp to
have that installed; otherwise you can get it by FTP to
<hostid>ftp.cdrom.com</hostid> in the directory
FreeBSD/FreeBSD-current/src/contrib/nvi/docs/tutorial.</para>
@ -830,7 +830,7 @@
<screen>&prompt.root; <userinput>make all install</></screen>
</informalexample>
<para>During this process the port will ftp to get any compressed
<para>During this process the port will FTP to get any compressed
files it needs that it didn't find on the CDROM or in
<filename>/usr/ports/distfiles</filename>. If you don't have
your network running yet and there was no file for the port in
@ -868,7 +868,7 @@
command to make it work; no space after the slash.)</para>
<para>You might want to get the most recent version of Netscape
from their <ulink URL="ftp://ftp.netscape.com">ftp site</ulink>.
from their <ulink URL="ftp://ftp.netscape.com">FTP site</ulink>.
(Netscape requires the X Window System.) There's now a FreeBSD
version, so look around carefully. Just use <command>gunzip
<replaceable>filename</replaceable></command> and <command>tar xvf
@ -890,7 +890,7 @@ setenv XNLSPATH /usr/X11R6/lib/X11/nls</programlisting>
them and put them there.</para>
<para>If you originally got Netscape as a port using the CDROM (or
ftp), don't replace <filename>/usr/local/bin/netscape</filename>
FTP), don't replace <filename>/usr/local/bin/netscape</filename>
with the new netscape binary; this is just a shell script that
sets up the environment variables for you. Instead rename the
new binary to <filename>netscape.bin</filename> and replace the

4
en_US.ISO8859-1/articles/pxe/article.sgml
View file

@ -22,7 +22,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/pxe/article.sgml,v 1.1 2001/06/25 14:51:37 nik Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/pxe/article.sgml,v 1.2 2001/07/13 22:03:55 billf Exp $</pubdate>
<abstract>
<para>This article details the method used to allow machines to install
@ -60,7 +60,7 @@
</informaltable>
<para>Requires:
Clients supporting the Intel PXE netboot option, an ethernet connection.
Clients supporting the Intel PXE netboot option, an Ethernet connection.
</para>
<para>Please let me know if you come across anything you have problems with

8
en_US.ISO8859-1/articles/solid-state/article.sgml
View file

@ -27,7 +27,7 @@
ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
$FreeBSD: doc/en_US.ISO8859-1/articles/solid-state/article.sgml,v 1.3 2001/07/10 14:00:14 dd Exp $
$FreeBSD: doc/en_US.ISO8859-1/articles/solid-state/article.sgml,v 1.4 2001/07/11 11:08:47 nik Exp $
-->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
@ -51,7 +51,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/solid-state/article.sgml,v 1.3 2001/07/10 14:00:14 dd Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/solid-state/article.sgml,v 1.4 2001/07/11 11:08:47 nik Exp $</pubdate>
<copyright>
<year>2001</year>
@ -403,8 +403,8 @@ pseudo-device md # memory disk</programlisting>
flash memory part is 128 megabytes, for instance, and your tar file
is larger than 64 megabytes, you cannot have your tar file on the
flash media at the same time as you explode it - you will run out of
space. One solution to this problem, if you are using ftp, is to
untar the file while it is transferred over ftp. If you perform
space. One solution to this problem, if you are using FTP, is to
untar the file while it is transferred over FTP. If you perform
your transfer in this manner, you will never have the tar file and
the tar contents on your disk at the same time:</para>

6
en_US.ISO8859-1/articles/storage-devices/article.sgml
View file

@ -20,7 +20,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD$</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/storage-devices/article.sgml,v 1.1 2001/07/13 22:30:40 murray Exp $</pubdate>
<abstract>
<para>This article talks about storage devices with FreeBSD.</para>
@ -1418,7 +1418,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen>
<para>Many X3T10 draft documents are available electronically on the
SCSI BBS (719-574-0424) and on the <hostid
role="fqdn">ncrinfo.ncr.com</hostid> anonymous ftp site.</para>
role="fqdn">ncrinfo.ncr.com</hostid> anonymous FTP site.</para>
<para>Latest X3T10 committee documents are:</para>
@ -1500,7 +1500,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen>
to look for more info. You can also find the SCSI-Faq there, which
is posted periodically.</para>
<para>Most major SCSI device and host adapter suppliers operate ftp
<para>Most major SCSI device and host adapter suppliers operate FTP
sites and/or BBS systems. They may be valuable sources of
information about the devices you own.</para>
</sect2>

6
en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.sgml,v 1.2 2001/07/06 13:02:53 dd Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.sgml,v 1.3 2001/07/17 20:51:49 chern Exp $
-->
<chapter id="ipv6">
@ -435,7 +435,7 @@
<title>Assignment of link-local, and special addresses</title>
<para>IPv6 link-local address is generated from IEEE802 address
(ethernet MAC address). Each of interface is assigned an IPv6
(Ethernet MAC address). Each of interface is assigned an IPv6
link-local address automatically, when the interface becomes up
(IFF_UP). Also, direct route for the link-local address is added
to routing table.</para>
@ -449,7 +449,7 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
<para>Interfaces that has no IEEE802 address (pseudo interfaces
like tunnel interfaces, or ppp interfaces) will borrow IEEE802
address from other interfaces, such as ethernet interfaces,
address from other interfaces, such as Ethernet interfaces,
whenever possible. If there is no IEEE802 hardware attached,
last-resort pseudorandom value, which is from MD5(hostname), will
be used as source of link-local address. If it is not suitable

4
en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/policies/chapter.sgml,v 1.19 2001/04/09 00:33:55 dd Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/policies/chapter.sgml,v 1.20 2001/07/13 22:21:27 chern Exp $
-->
<chapter id="policies">
@ -92,7 +92,7 @@
change can be rather dramatic.</para>
</note>
<para>The <application>TCL</application> embedded programming
<para>The <application>Tcl</application> embedded programming
language will be used as example of how this model works:</para>
<para><filename>src/contrib/tcl</filename> contains the source as

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

@ -17,7 +17,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.244 2001/07/10 14:39:25 nik Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.245 2001/07/17 20:51:50 chern Exp $</pubdate>
<copyright>
<year>1995</year>
@ -396,7 +396,7 @@
<answer>
<para>Every significant release of FreeBSD is available via
anonymous ftp from the <ulink
anonymous FTP from the <ulink
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/">
FreeBSD FTP site</ulink>:</para>
@ -884,7 +884,7 @@ File: +DESC (ignored)</screen>
</listitem>
<listitem>
<para>Using ftp mirror: You can download the FTP server's
<para>Using FTP mirror: You can download the FTP server's
copy of the web site sources using your favorite ftp mirror
tool. Keep in mind that you have to build these sources before
publishing them. Simply start at
@ -1695,7 +1695,7 @@ BUSY</literallayout></entry>
<para>Alternatively, there is a freely available utility
distributed with FreeBSD called <filename>pfdisk.exe</filename>
(located in the <filename>tools</filename> subdirectory on the
FreeBSD CDROM or on the various FreeBSD ftp sites) which can be
FreeBSD CDROM or on the various FreeBSD FTP sites) which can be
used to work out what geometry the other operating systems on
the disk are using. You can then enter this geometry in the
partition editor.</para>
@ -8690,7 +8690,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
<answer>
<para>The answer to this depends mostly on your rule set and
processor speed. For most applications dealing with ethernet
processor speed. For most applications dealing with Ethernet
and small rule sets, the answer is, negligible. For those of
you that need actual measurements to satisfy your curiosity,
read on.</para>
@ -8725,13 +8725,13 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
approximately 2.703ms/packet, or roughly 2.7 microseconds per
rule. Thus the theoretical packet processing limit with these
rules is around 370 packets per second. Assuming 10Mbps
ethernet and a ~1500 byte packet size, we would only be able to
Ethernet and a ~1500 byte packet size, we would only be able to
achieve a 55.5% bandwidth utilization.</para>
<para>For the latter case each packet was processed in
approximately 1.172ms, or roughly 1.2 microseconds per rule.
The theoretical packet processing limit here would be about
853 packets per second, which could consume 10Mbps ethernet
853 packets per second, which could consume 10Mbps Ethernet
bandwidth.</para>
<para>The excessive number of rules tested and the nature of
@ -10013,7 +10013,7 @@ ATDT1234567</programlisting>
<para>This is due to what is called a <quote>Black Hole</quote>
router. MacOS and Windows 98 (and maybe other Microsoft OSs)
send TCP packets with a requested segment size too big to fit
into a PPPoE frame (MTU is 1500 by default for ethernet)
into a PPPoE frame (MTU is 1500 by default for Ethernet)
<emphasis>and</emphasis> have the <quote>do not
fragment</quote> bit set (default of TCP) and the Telco router
is not sending ICMP <quote>must fragment</quote> back to the
@ -11713,7 +11713,7 @@ ${RELEASEDIR}/tarballs/bindist/bin_tgz.)</programlisting>
different 32-bit vendor ids. The idea of needing 32 bits just
for unique manufacturers is a bit excessive.</para>
<para>The lower 32 bits are a serial #, ethernet address,
<para>The lower 32 bits are a serial #, Ethernet address,
something that makes this one board unique. The vendor must
never produce a second board that has the same lower 32 bits
unless the upper 32 bits are also different. So you can have

4
en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml
View file

@ -27,7 +27,7 @@
ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
$FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml,v 1.26 2001/07/15 11:17:05 nik Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml,v 1.27 2001/07/17 20:51:51 chern Exp $
-->
<chapter id="sgml-markup">
@ -1936,7 +1936,7 @@ This is the file called 'foo2'</screen>
<term><literal>role="mac"</literal></term>
<listitem>
<para>The text is an ethernet MAC address, expressed as a series
<para>The text is an Ethernet MAC address, expressed as a series
of 2 digit hexadecimal numbers separated by colons.</para>
</listitem>
</varlistentry>

36
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.57 2001/07/17 00:11:17 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.58 2001/07/17 20:51:51 chern Exp $
-->
<chapter id="advanced-networking">
@ -36,7 +36,7 @@
<quote>default route</quote> is used if none of the other routes apply.
We will talk a little bit more about default routes later on. There are
also three types of gateways: individual hosts, interfaces (also called
<quote>links</quote>), and ethernet hardware addresses.</para>
<quote>links</quote>), and Ethernet hardware addresses.</para>
<sect2>
<title>An example</title>
@ -74,10 +74,10 @@ host2.foobar.com link#1 UC 0 0
<secondary>MAC address</secondary>
</indexterm>
<para>The next thing that stands out are the <hostid
role="mac">0:e0:...</hostid> addresses. These are ethernet hardware
role="mac">0:e0:...</hostid> addresses. These are Ethernet hardware
addresses. FreeBSD will automatically identify any hosts
(<hostid>test0</hostid> in the example) on the local ethernet and add
a route for that host, directly to it over the ethernet interface,
(<hostid>test0</hostid> in the example) on the local Ethernet and add
a route for that host, directly to it over the Ethernet interface,
<devicename>ed0</devicename>. There is also a timeout
(<literal>Expire</literal> column) associated with this type of route,
which is used if we fail to hear from the host in a specific amount of
@ -92,7 +92,7 @@ host2.foobar.com link#1 UC 0 0
subnet <hostid role="ipaddr">10.20.30</hostid>, and <hostid
role="domainname">foobar.com</hostid> is the domain name associated
with that subnet). The designation <literal>link#1</literal> refers
to the first ethernet card in the machine. You will notice no
to the first Ethernet card in the machine. You will notice no
additional interface is specified for those.</para>
<para>Both of these groups (local network hosts and local subnets) have
@ -101,12 +101,12 @@ host2.foobar.com link#1 UC 0 0
are statically defined (ie. entered explicitly) will exist.</para>
<para>The <literal>host1</literal> line refers to our host, which it
knows by ethernet address. Since we are the sending host, FreeBSD
knows by Ethernet address. Since we are the sending host, FreeBSD
knows to use the loopback interface (<devicename>lo0</devicename>)
rather than sending it out over the ethernet interface.</para>
rather than sending it out over the Ethernet interface.</para>
<para>The two <literal>host2</literal> lines are an example of what
happens when we use an ifconfig alias (see the section of ethernet for
happens when we use an ifconfig alias (see the section of Ethernet for
reasons why we would do this). The <literal>=&gt;</literal> symbol
after the <devicename>lo0</devicename> interface says that not only
are we using the loopback (since this is address also refers to the
@ -164,7 +164,7 @@ host2.foobar.com link#1 UC 0 0
<row>
<entry>L</entry>
<entry>Link: Route involves references to ethernet
<entry>Link: Route involves references to Ethernet
hardware.</entry>
</row>
</tbody>
@ -224,7 +224,7 @@ host2.foobar.com link#1 UC 0 0
<row>
<entry>Local2</entry>
<entry>Local1</entry>
<entry>ethernet</entry>
<entry>Ethernet</entry>
</row>
<row>
@ -270,10 +270,10 @@ Local1 (10.20.30.1, 10.9.9.30) --&gt; T1-GW (10.9.9.1)
used to refer to a machine that sits on two local-area
networks.</para>
<para>In one case, the machine as two ethernet cards, each having an
<para>In one case, the machine as two Ethernet cards, each having an
address on the separate subnets. Alternately, the machine may only
have one ethernet card, and be using ifconfig aliasing. The former is
used if two physically separate ethernet networks are in use, the
have one Ethernet card, and be using ifconfig aliasing. The former is
used if two physically separate Ethernet networks are in use, the
latter if there is one physical network segment, but two logically
separate subnets.</para>
@ -1178,9 +1178,9 @@ hostname myclient.mydomain</programlisting>
<indexterm><primary>isdn4bsd</primary></indexterm>
<para>The latest isdn4bsd version is available from <ulink
url="ftp://isdn4bsd@ftp.consol.de/pub/">ftp://isdn4bsd@ftp.consol.de/pub/</ulink>,
the main isdn4bsd ftp site (you have to log in as user
the main isdn4bsd FTP site (you have to log in as user
<username>isdn4bsd</username> , give your mail address as the password
and change to the <filename>pub</filename> directory. Anonymous ftp
and change to the <filename>pub</filename> directory. Anonymous FTP
as user <username>ftp</username> or <username>anonymous</username>
will <emphasis>not</emphasis> give the desired result).</para>
@ -2873,7 +2873,7 @@ dhcp_flags=""</programlisting>
IPs, and vice versa. For example, a query for www.freebsd.org
will send back a reply for the IP address of The FreeBSD Project's
webpage, whereas, a query for ftp.freebsd.org will return the IP
of the corresponding ftp machine. Likewise, the opposite can
of the corresponding FTP machine. Likewise, the opposite can
happen. A query for an IP address can resolve its hostname.
</para>
@ -3095,7 +3095,7 @@ dhcp_flags=""</programlisting>
<sect3>
<title><filename>/etc/namedb/named.conf</filename></title>
<programlisting>// $FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.57 2001/07/17 00:11:17 chern Exp $
<programlisting>// $FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.58 2001/07/17 20:51:51 chern Exp $
//
// Refer to the named(8) man page for details. If you are ever going
// to setup a primary server, make sure you've understood the hairy

8
en_US.ISO8859-1/books/handbook/hw/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/hw/chapter.sgml,v 1.39 2001/06/23 07:04:37 dd Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/hw/chapter.sgml,v 1.40 2001/07/14 02:21:12 chern Exp $
-->
<appendix id="hw">
@ -463,7 +463,7 @@
<para>Both the Pentium Pro and Pentium II work fine with FreeBSD. In
fact, our main FTP site <ulink
url="ftp://ftp.FreeBSD.org/">ftp.FreeBSD.org</ulink> (also known
as "<filename>ftp.cdrom.com</filename>", world's largest ftp site)
as "<filename>ftp.cdrom.com</filename>", world's largest FTP site)
runs FreeBSD on a Pentium Pro. <ulink
url="ftp://ftp.cdrom.com/archive-info/wcarchive.txt">Configurations
details</ulink> are available for interested parties.</para>
@ -4616,7 +4616,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen>
<para>Many X3T10 draft documents are available electronically on the
SCSI BBS (719-574-0424) and on the <hostid
role="fqdn">ncrinfo.ncr.com</hostid> anonymous ftp site.</para>
role="fqdn">ncrinfo.ncr.com</hostid> anonymous FTP site.</para>
<para>Latest X3T10 committee documents are:</para>
@ -4698,7 +4698,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen>
to look for more info. You can also find the SCSI-Faq there, which
is posted periodically.</para>
<para>Most major SCSI device and host adapter suppliers operate ftp
<para>Most major SCSI device and host adapter suppliers operate FTP
sites and/or BBS systems. They may be valuable sources of
information about the devices you own.</para>
</sect3>

14
en_US.ISO8859-1/books/handbook/install/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v 1.74 2001/07/17 00:11:18 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v 1.75 2001/07/17 02:31:55 murray Exp $
-->
<chapter id="install">
@ -75,7 +75,7 @@
linkend="install-hw">supported hardware</link> should
come in handy here. ;-) It would also be a good idea to make a
list of any <quote>special</quote> cards you have installed,
such as SCSI controllers, ethernet cards, sound cards, etc..
such as SCSI controllers, Ethernet cards, sound cards, etc..
The list should include their IRQs and IO port addresses.</para>
<sect3 id="install-floppies">
@ -423,7 +423,7 @@
<indexterm><primary>installation</primary><secondary>network</secondary><tertiary>Ethernet</tertiary></indexterm>
<para>There are three types of network installations you can do.
Serial port (SLIP or PPP), Parallel port (PLIP (laplink cable)),
or Ethernet (a standard ethernet controller (includes some
or Ethernet (a standard Ethernet controller (includes some
PCMCIA)).</para>
<para>The SLIP support is rather primitive, and limited primarily
@ -461,11 +461,11 @@
in a quicker installation.</para>
<para>Finally, for the fastest possible network installation, an
ethernet adapter is always a good choice! FreeBSD supports most
common PC ethernet cards; a table of supported cards (and their
Ethernet adapter is always a good choice! FreeBSD supports most
common PC Ethernet cards; a table of supported cards (and their
required settings) is provided in the <link
linkend="install-hw">Supported Hardware</link> list. If you are
using one of the supported PCMCIA ethernet cards, also be sure
using one of the supported PCMCIA Ethernet cards, also be sure
that it is plugged in <emphasis>before</emphasis> the laptop is
powered on! FreeBSD does not, unfortunately, currently support
hot insertion of PCMCIA cards during installation.</para>
@ -499,7 +499,7 @@
need to set this option in the Options menu before
installation can proceed.</para>
<para>If you have a poor quality ethernet card which suffers
<para>If you have a poor quality Ethernet card which suffers
from very slow transfer rates, you may also wish to toggle the
appropriate Options flag.</para>

8
en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.50 2001/07/12 00:41:05 dd Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.51 2001/07/17 00:11:19 chern Exp $
-->
<chapter id="kernelconfig">
@ -904,7 +904,7 @@ device wx # Intel Gigabit Ethernet Card (<quote>Wiseman</quote>
<programlisting># PCI Ethernet NICs that use the common MII bus controller code.
device miibus # MII bus support</programlisting>
<para>MII bus support is required for some PCI 10/100 ethernet NICs,
<para>MII bus support is required for some PCI 10/100 Ethernet NICs,
namely those which use MII-compliant transceivers or implement
transceiver control interfaces that operate like an MII. Adding
<literal>device miibus</literal> to the kernel config pulls in
@ -948,7 +948,7 @@ device sn0 at isa? port 0x300 irq 10
# requires PCCARD (PCMCIA) support to be activated
#device xe0 at isa?</programlisting>
<para>ISA ethernet drivers. See
<para>ISA Ethernet drivers. See
<filename>/usr/src/sys/i386/conf/LINT</filename> for which cards are
supported by which driver.</para>
@ -1025,7 +1025,7 @@ pseudo-device bpf # Berkeley packet filter</programlisting>
<para>This is the Berkeley Packet Filter. This pseudo-device allows
network interfaces to be placed in promiscuous mode, capturing every
packet on a broadcast network (e.g., an ethernet). These packets
packet on a broadcast network (e.g., an Ethernet). These packets
can be captured to disk and or examined with the &man.tcpdump.1;
program.</para>

14
en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml,v 1.43 2001/07/14 23:40:28 murray Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml,v 1.44 2001/07/17 00:11:20 chern Exp $
-->
<chapter id="linuxemu">
@ -367,7 +367,7 @@ multi on</programlisting>
<quote>machine ID</quote> by running the program
<command>mathinfo</command> in the Install directory. This
machine ID is based solely on the MAC address of your first
ethernet card.</para>
Ethernet card.</para>
<screen>&prompt.root; <userinput>cd /localdir/Files/SystemFiles/Installation/Binaries/Linux</userinput>
&prompt.root; <userinput>mathinfo</userinput>
@ -469,7 +469,7 @@ disco.example.com 7115-70839-20412</screen>
5.2 of these packages.</para>
<para>If you want to run the intelligent agent, you'll
also need to install the Red Hat TCL package:
also need to install the Red Hat Tcl package:
<filename>tcl-8.0.3-20.i386.rpm</filename>. The general command
for installing packages with the official RPM port is :</para>
@ -875,7 +875,7 @@ export PATH</programlisting>
<title>Installation of FreeBSD 4.3 stable</title>
<para>First I installed FreeBSD 4.3 stable. I did the
default-installation via ftp.</para>
default-installation via FTP.</para>
<sect3 id="install-via-ftp">
<title>Installation via FTP</title> <para>Get the diskimages
@ -1104,7 +1104,7 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile</programlisting>
<para>For <application>Oracle</application> to run the
intelligent agent, I also had to install the following
RedHat TCL package (as is stated in the FreeBSD Handbook):
RedHat Tcl package (as is stated in the FreeBSD Handbook):
<filename>tcl-8.0.5-30.i386.rpm</filename> (otherwise the
relinking during <application>Oracle</application> install
won't work). There are some other issues regarding
@ -1335,7 +1335,7 @@ sapmsIDS 3600/tcp # SAP Message Server. 3600 + Instance-Number</programlisting>
<para>SAP requires at least two locales that aren't part of
the default RedHat installation. SAP offers the required
RPMs as download from their ftp-server (which is only
RPMs as download from their FTP-server (which is only
accessible if you are a customer with OSS-access). See note
0171356 for a list of RPMs you need.</para>
@ -1665,7 +1665,7 @@ options SEMUME=100 #number of UNDO keys</programlisting></para>
could use the original binaries, or use the relinked
binaries from an original RedHat System.</para>
<para>For compiling the intelligent agent, the RedHat TCL
<para>For compiling the intelligent agent, the RedHat Tcl
package must be installed. If you can't get
<filename>tcl-8.0.3-20.i386.rpm</filename>, a newer one like
<filename>tcl-8.0.5-30.i386.rpm</filename> for RedHat 6.1

4
en_US.ISO8859-1/books/handbook/policies/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/policies/chapter.sgml,v 1.19 2001/04/09 00:33:55 dd Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/policies/chapter.sgml,v 1.20 2001/07/13 22:21:27 chern Exp $
-->
<chapter id="policies">
@ -92,7 +92,7 @@
change can be rather dramatic.</para>
</note>
<para>The <application>TCL</application> embedded programming
<para>The <application>Tcl</application> embedded programming
language will be used as example of how this model works:</para>
<para><filename>src/contrib/tcl</filename> contains the source as

6
en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.37 2001/06/25 22:05:25 murray Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.38 2001/07/17 00:11:23 chern Exp $
-->
<chapter id="ppp-and-slip">
@ -1994,7 +1994,7 @@ ppp_profile="default" # or your provider</programlisting>
<programlisting>set device PPPoE:<replaceable>xl1</replaceable>:<replaceable>ISP</replaceable></programlisting>
<para>Do not forget to change <replaceable>xl1</replaceable>
to the proper device for your ethernet card.</para>
to the proper device for your Ethernet card.</para>
<para>Do not forget to change <replaceable>ISP</replaceable>
to the profile you have just found above.</para>
</step>
@ -2746,7 +2746,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
linkend="ports">ports collection</link> or retrieve and build
it yourself from <ulink
url="ftp://ftp.gated.merit.edu/research.and.development/gated/">the
GateD anonymous ftp site</ulink>; the current version
GateD anonymous FTP site</ulink>; the current version
as of this writing is
<filename>gated-R3_5Alpha_8.tar.Z</filename>, which includes
support for FreeBSD <quote>out-of-the-box</quote>. Complete

4
en_US.ISO8859-1/books/handbook/security/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/security/chapter.sgml,v 1.57 2001/07/14 01:47:38 murray Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/security/chapter.sgml,v 1.58 2001/07/17 00:11:24 chern Exp $
-->
<chapter id="security">
@ -2339,7 +2339,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<para>If you use the logging versions of the <command>accept</command>
command, it can generate <emphasis>large</emphasis> amounts of log
data as one log line will be generated for every packet that passes
through the firewall, so large ftp/http transfers, etc, will really
through the firewall, so large FTP/http transfers, etc, will really
slow the system down. It also increases the latencies on those
packets as it requires more work to be done by the kernel before the
packet can be passed on. syslogd with also start using up a lot

30
en_US.ISO8859-1/books/porters-handbook/book.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v 1.157 2001/07/14 20:56:36 tobez Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v 1.158 2001/07/17 20:51:52 chern Exp $
-->
<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
@ -343,7 +343,7 @@ lib/X11/oneko/mouse.xpm
<note>
<para>In the past, we asked you to upload new port submissions in
our ftp site (<hostid role="fqdn">ftp.FreeBSD.org</hostid>). This
our FTP site (<hostid role="fqdn">ftp.FreeBSD.org</hostid>). This
is no longer recommended as read access is turned off on the
<filename>incoming/</filename> directory of that site due to the
large amount of pirated software showing up there.</para>
@ -398,7 +398,7 @@ lib/X11/oneko/mouse.xpm
<makevar>DISTDIR</makevar>. If <maketarget>fetch</maketarget>
cannot find the required files in <makevar>DISTDIR</makevar> it
will look up the URL <makevar>MASTER_SITES</makevar>, which is
set in the Makefile, as well as our main ftp site at <ulink
set in the Makefile, as well as our main FTP site at <ulink
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/</ulink>,
where we put sanctioned distfiles as backup. It will then
attempt to fetch the named distribution file with
@ -515,9 +515,9 @@ lib/X11/oneko/mouse.xpm
<emphasis>mainstream</emphasis> sources when and where you
can.</para>
<para>If you cannot find a ftp/http site that is well-connected to the
<para>If you cannot find a FTP/http site that is well-connected to the
net, or can only find sites that have irritatingly non-standard
formats, you might want to put a copy on a reliable ftp or http
formats, you might want to put a copy on a reliable FTP or http
server that you control (e.g., your home page). Make sure you set
<makevar>MASTER_SITES</makevar> to reflect your choice.</para>
@ -538,7 +538,7 @@ lib/X11/oneko/mouse.xpm
consider putting the distfile in your home page and listing it as
the first <makevar>MASTER_SITES</makevar>. This will prevent users
from getting <errorname>checksum mismatch</errorname> errors, and
also reduce the workload of maintainers of our ftp site. Also, if
also reduce the workload of maintainers of our FTP site. Also, if
there is only one master site for the port, it is recommended that
you house a backup at your site and list it as the second
<makevar>MASTER_SITES</makevar>.</para>
@ -628,7 +628,7 @@ lib/X11/oneko/mouse.xpm
answers to the questions, you check the
<makevar>PACKAGE_BUILDING</makevar> variable and turn off the
interactive script when it is set. This will allow us to build the
packages for CDROMs and ftp.</para>
packages for CDROMs and FTP.</para>
</sect1>
</chapter>
@ -953,7 +953,7 @@ PORTEPOCH= 1</programlisting>
subdirectories are specified by the variable
<makevar>CATEGORIES</makevar>. It is intended to make life easier
for the user when he is wading through the pile of packages on the
ftp site or the CDROM. Please take a look at the existing <link
FTP site or the CDROM. Please take a look at the existing <link
linkend="porting-categories">categories</link> and pick the ones
that are suitable for your port.</para>
@ -973,7 +973,7 @@ PORTEPOCH= 1</programlisting>
<sect1>
<title><makevar>MASTER_SITES</makevar></title>
<para>Record the directory part of the ftp/http-URL pointing at the
<para>Record the directory part of the FTP/http-URL pointing at the
original tarball in <makevar>MASTER_SITES</makevar>. Do not forget
the trailing slash (<filename>/</filename>)!</para>
@ -1016,7 +1016,7 @@ MASTER_SITE_SUBDIR= applications</programlisting>
<title><makevar>PATCHFILES</makevar></title>
<para>If your port requires some additional patches that are available
by ftp or http, set <makevar>PATCHFILES</makevar> to the names of
by FTP or http, set <makevar>PATCHFILES</makevar> to the names of
the files and <makevar>PATCH_SITES</makevar> to the URL of the
directory that contains them (the format is the same as
<makevar>MASTER_SITES</makevar>).</para>
@ -2267,7 +2267,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
<para>It is your responsibility as a porter to read the licensing
terms of the software and make sure that the FreeBSD project will
not be held accountable for violating them by redistributing the
source or compiled binaries either via ftp or CDROM. If in doubt,
source or compiled binaries either via FTP or CDROM. If in doubt,
please contact the &a.ports;.</para>
</note>
@ -2280,7 +2280,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
license, set the variable <makevar>NO_CDROM</makevar> to a string
describing the reason why. We will make sure such ports will not go
into the CDROM come release time. The distfile and package will
still be available via ftp.</para>
still be available via FTP.</para>
</listitem>
<listitem>
@ -2288,7 +2288,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
site, or the resulting binary package cannot be distributed due to
licensing; set the variable <makevar>NO_PACKAGE</makevar> to a
string describing the reason why. We will make sure such packages
will not go on the ftp site, nor into the CDROM come release time.
will not go on the FTP site, nor into the CDROM come release time.
The distfile will still be included on both however.</para>
</listitem>
@ -2297,7 +2297,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
patented stuff) or has a &ldquo;no commercial use&rdquo; license,
set the variable <makevar>RESTRICTED</makevar> to be the string
describing the reason why. For such ports, the distfiles/packages
will not be available even from our ftp sites.</para>
will not be available even from our FTP sites.</para>
</listitem>
</orderedlist>
@ -2318,7 +2318,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
<para>When you notice that a port is out of date compared to the latest
version from the original authors, first make sure you have the latest
port. You can find them in the
<filename>ports/ports-current</filename> directory of the ftp mirror
<filename>ports/ports-current</filename> directory of the FTP mirror
sites. You may also use CVSup to keep your whole ports collection
up-to-date, as described in <ulink url="../handbook/synching.html#CVSUP-CONFIG">the Handbook</ulink>.</para>