Attack of the spelling police, part II.
This commit is contained in:
Jim Mock
parent
aca13e8771
commit
370586999f
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=7357
12 changed files with 80 additions and 80 deletions
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kerneldebug/chapter.sgml,v 1.22 2000/04/03 02:15:41 chris Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kerneldebug/chapter.sgml,v 1.23 2000/06/08 01:56:10 jim Exp $
|
||||
-->
|
||||
|
||||
<chapter id="kerneldebug">
|
||||
|
|
@ -286,7 +286,7 @@ makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols</
|
|||
<sect1>
|
||||
<title>On-Line Kernel Debugging Using DDB</title>
|
||||
|
||||
<para>While <command>kgdb</command> as an offline debugger provides a very
|
||||
<para>While <command>kgdb</command> as an off-line debugger provides a very
|
||||
high level of user interface, there are some things it cannot do. The
|
||||
most important ones being breakpointing and single-stepping kernel
|
||||
code.</para>
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/install/chapter.sgml,v 1.42 2000/06/08 01:56:08 jim Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/install/chapter.sgml,v 1.43 2000/06/12 14:23:39 alex Exp $
|
||||
-->
|
||||
|
||||
<chapter id="install">
|
||||
|
|
@ -307,7 +307,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
|
|||
|
||||
<para>Installing from tape is probably the easiest method, short
|
||||
of an online FTP install or CDROM install. The installation
|
||||
program expects the files to be simply tar'ed onto the tape, so
|
||||
program expects the files to be simply tarred onto the tape, so
|
||||
after getting all of the distribution files you are interested
|
||||
in, simply tar them onto the tape like so:</para>
|
||||
|
||||
|
|
@ -575,7 +575,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
|
|||
<para>Select a Standard, Express, or Custom install, depending on
|
||||
whether or not you would like the installation to help you
|
||||
through a typical installation, give you a high degree of
|
||||
control over each step, or simply whizz through it (using
|
||||
control over each step, or simply whiz through it (using
|
||||
reasonable defaults when possible) as fast as possible. If
|
||||
you have never used FreeBSD before, the Standard installation
|
||||
method is most recommended.</para>
|
||||
|
|
@ -605,7 +605,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
|
|||
ESDI drive configurations, various SCSI controllers, and network and
|
||||
serial cards is also provided.</para>
|
||||
|
||||
<para>In order to run FreeBSD, a recommmended minimum of eight
|
||||
<para>In order to run FreeBSD, a recommended minimum of eight
|
||||
megabytes of RAM is suggested. Sixteen megabytes is the preferred
|
||||
amount of RAM as you may have some trouble with anything less than
|
||||
sixteen depending on your hardware.</para>
|
||||
|
|
@ -938,7 +938,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Winbond W89C840F fast ethernet nics including the
|
||||
<para>Winbond W89C840F fast ethernet NICs including the
|
||||
Trendware TE100-PCIE</para>
|
||||
</listitem>
|
||||
|
||||
|
|
@ -1437,7 +1437,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Various frame grabbers based ont he the Brooktree Bt848
|
||||
<para>Various frame grabbers based on the Brooktree Bt848
|
||||
and Bt878 chip</para>
|
||||
</listitem>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.26 2000/06/08 01:56:10 jim Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.27 2000/06/12 23:57:35 murray Exp $
|
||||
-->
|
||||
|
||||
<chapter id="kernelconfig">
|
||||
|
|
@ -245,7 +245,7 @@ cpu I686_CPU</programlisting>
|
|||
your CPU use, you can use the <command>dmesg</command> command to
|
||||
view your boot up messages.</para>
|
||||
|
||||
<para>The Alpha architechture has different values for
|
||||
<para>The Alpha architecture has different values for
|
||||
<literal>cpu_type</literal>. They include:</para>
|
||||
|
||||
<programlisting>
|
||||
|
|
@ -794,7 +794,7 @@ device miibus # MII bus support</programlisting>
|
|||
|
||||
<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 taht operate like an MII. Adding
|
||||
transceiver control interfaces that operate like an MII. Adding
|
||||
<literal>device miibus</literal> to the kernel config pulls in
|
||||
support for the generic miibus API and all of the PHY drivers,
|
||||
including a generic one for PHYs that are not specifically handled
|
||||
|
|
@ -819,14 +819,14 @@ device ed0 at isa? port 0x280 irq 10 iomem 0xd8000
|
|||
device ex
|
||||
device ep
|
||||
# WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really
|
||||
# exists only as a PCMCIA device, so there is no ISA attatement needed
|
||||
# exists only as a PCMCIA device, so there is no ISA attachment needed
|
||||
# and resources will always be dynamically assigned by the pccard code.
|
||||
device wi
|
||||
# Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will
|
||||
# work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP
|
||||
# mode (the factory default). If you set the switches on your ISA
|
||||
# card for a manually chosen I/O address and IRQ, you must specify
|
||||
# those paremeters here.
|
||||
# those parameters here.
|
||||
device an
|
||||
# The probe order of these is presently determined by i386/isa/isa_compat.c.
|
||||
device ie0 at isa? port 0x300 irq 10 iomem 0xd0000
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kerneldebug/chapter.sgml,v 1.22 2000/04/03 02:15:41 chris Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kerneldebug/chapter.sgml,v 1.23 2000/06/08 01:56:10 jim Exp $
|
||||
-->
|
||||
|
||||
<chapter id="kerneldebug">
|
||||
|
|
@ -286,7 +286,7 @@ makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols</
|
|||
<sect1>
|
||||
<title>On-Line Kernel Debugging Using DDB</title>
|
||||
|
||||
<para>While <command>kgdb</command> as an offline debugger provides a very
|
||||
<para>While <command>kgdb</command> as an off-line debugger provides a very
|
||||
high level of user interface, there are some things it cannot do. The
|
||||
most important ones being breakpointing and single-stepping kernel
|
||||
code.</para>
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kernelopts/chapter.sgml,v 1.14 1999/12/11 06:04:35 chris Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kernelopts/chapter.sgml,v 1.15 2000/06/08 01:56:11 jim Exp $
|
||||
-->
|
||||
|
||||
<chapter id="kernelopts">
|
||||
|
|
@ -34,7 +34,7 @@
|
|||
C preprocessor macro for the kernel compilation process. To make the
|
||||
build truly optional, the corresponding part of the kernel source (or
|
||||
kernel <filename>.h</filename> file) must be written with the option
|
||||
concept in mind, i.e. the default must have been made overridable by the
|
||||
concept in mind, i.e., the default can be overridden by the
|
||||
config option. This is usually done with something like:</para>
|
||||
|
||||
<programlisting>
|
||||
|
|
@ -107,7 +107,7 @@ options notyet,notdef</programlisting>
|
|||
|
||||
<para>If there is already something that comes close to the purpose of the
|
||||
new option, pick this. For example, options modifying the overall
|
||||
behaviour of the SCSI subsystem can go into
|
||||
behavior of the SCSI subsystem can go into
|
||||
<filename>opt_scsi.h</filename>. By default, simply mentioning an
|
||||
option in the appropriate option file, say <literal>FOO</literal>,
|
||||
implies its value will go into the corresponding file
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/l10n/chapter.sgml,v 1.35 2000/04/16 22:10:20 ache Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/l10n/chapter.sgml,v 1.36 2000/06/08 01:56:11 jim Exp $
|
||||
-->
|
||||
|
||||
<chapter id="l10n">
|
||||
|
|
@ -25,7 +25,7 @@
|
|||
|
||||
<para>The author realizes that he may have been incomplete in the
|
||||
description of the i18n process in FreeBSD. Due to the various
|
||||
levels of i18n implementation in both the system and applicational
|
||||
levels of i18n implementation in both the system and application
|
||||
levels, we advise you to refer to individual documentation, man
|
||||
pages, READMEs, and so forth.</para>
|
||||
|
||||
|
|
@ -91,7 +91,7 @@
|
|||
the codes for the specify country and language (country
|
||||
codes tell applications what variation of given
|
||||
language to use). In addition, web
|
||||
browsers, SMTP/POP servers, HTTPd's, etc. make decisions based on
|
||||
browsers, SMTP/POP servers, web servers, etc. make decisions based on
|
||||
them. The following are examples of language/country codes:</para>
|
||||
|
||||
<informaltable frame="none">
|
||||
|
|
@ -222,7 +222,7 @@
|
|||
each shell's startup file. <link linkend="usr-setup">User
|
||||
Level Setup</link> can be done by an user himself and <link
|
||||
linkend="adm-setup">Administrator Level Setup</link> require
|
||||
superuser priviledges.</para>
|
||||
superuser privileges.</para>
|
||||
|
||||
<sect5 id="usr-setup">
|
||||
<title>User Level Setup</title>
|
||||
|
|
@ -513,7 +513,7 @@ options SC_MOUSE_CHAR=0x03</programlisting>
|
|||
<para>Although X11 is not part of the FreeBSD Project, we have
|
||||
included some information here for FreeBSD users. For more
|
||||
details, refer to the <ulink url="http://www.xfree86.org/">XFree86
|
||||
website</ulink> or whichever X11 Server you use.</para>
|
||||
web site</ulink> or whichever X11 Server you use.</para>
|
||||
|
||||
<para>In <filename>~/.Xresources</filename>, you can additionally
|
||||
tune application specific i18n settings (e.g., fonts, menus,
|
||||
|
|
@ -561,11 +561,11 @@ options SC_MOUSE_CHAR=0x03</programlisting>
|
|||
wide or multibyte character sets have independent patches for FFS
|
||||
enabling such support. They are only temporary unportable
|
||||
solutions or hacks and we have decided to not include them in the
|
||||
source tree. Refer to respective languages' websites for more
|
||||
source tree. Refer to respective languages' web sites for more
|
||||
informations and the patch files.</para>
|
||||
|
||||
<para>The FreeBSD MSDOS filesystem has the configurable ability to
|
||||
convert between MSDOS, Unicode character sets and chosen
|
||||
<para>The FreeBSD MS-DOS filesystem has the configurable ability to
|
||||
convert between MS-DOS, Unicode character sets and chosen
|
||||
FreeBSD filesystem character sets. See &man.mount.msdos.8; for
|
||||
details.</para>
|
||||
</sect2>
|
||||
|
|
@ -615,7 +615,7 @@ options SC_MOUSE_CHAR=0x03</programlisting>
|
|||
efforts for each country has been repeating each others'
|
||||
efforts. Many of us have been reinventing the wheel repeatedly
|
||||
and inefficiently. We hope that the various major groups in
|
||||
i18n could congregate into a group effort similiar to the Core
|
||||
i18n could congregate into a group effort similar to the Core
|
||||
Team's responsibility.</para>
|
||||
|
||||
<para>Currently, we hope that, when you write or port i18n
|
||||
|
|
@ -738,10 +738,10 @@ lp|Russian local line printer:\
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>MSDOS FS and Russian Filenames</title>
|
||||
<title>MS-DOS FS and Russian Filenames</title>
|
||||
|
||||
<para>The following example &man.fstab.5; entry enables support
|
||||
for Russian filenames in mounted MSDOS filesystems:</para>
|
||||
for Russian filenames in mounted MS-DOS filesystems:</para>
|
||||
|
||||
<programlisting>
|
||||
/dev/ad0s2 /dos/c msdos rw,-W=koi2dos,-L=ru_RU.KOI8-R 0 0</programlisting>
|
||||
|
|
@ -873,7 +873,7 @@ XkbVariant "winkeys"</programlisting>
|
|||
|
||||
<row>
|
||||
<entry>zh-doc tag=.</entry>
|
||||
<entry>FreeBSD Documenation Translation to BIG-5 Traditional
|
||||
<entry>FreeBSD Documentation Translation to BIG-5 Traditional
|
||||
Chinese</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/install/chapter.sgml,v 1.42 2000/06/08 01:56:08 jim Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/install/chapter.sgml,v 1.43 2000/06/12 14:23:39 alex Exp $
|
||||
-->
|
||||
|
||||
<chapter id="install">
|
||||
|
|
@ -307,7 +307,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
|
|||
|
||||
<para>Installing from tape is probably the easiest method, short
|
||||
of an online FTP install or CDROM install. The installation
|
||||
program expects the files to be simply tar'ed onto the tape, so
|
||||
program expects the files to be simply tarred onto the tape, so
|
||||
after getting all of the distribution files you are interested
|
||||
in, simply tar them onto the tape like so:</para>
|
||||
|
||||
|
|
@ -575,7 +575,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
|
|||
<para>Select a Standard, Express, or Custom install, depending on
|
||||
whether or not you would like the installation to help you
|
||||
through a typical installation, give you a high degree of
|
||||
control over each step, or simply whizz through it (using
|
||||
control over each step, or simply whiz through it (using
|
||||
reasonable defaults when possible) as fast as possible. If
|
||||
you have never used FreeBSD before, the Standard installation
|
||||
method is most recommended.</para>
|
||||
|
|
@ -605,7 +605,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
|
|||
ESDI drive configurations, various SCSI controllers, and network and
|
||||
serial cards is also provided.</para>
|
||||
|
||||
<para>In order to run FreeBSD, a recommmended minimum of eight
|
||||
<para>In order to run FreeBSD, a recommended minimum of eight
|
||||
megabytes of RAM is suggested. Sixteen megabytes is the preferred
|
||||
amount of RAM as you may have some trouble with anything less than
|
||||
sixteen depending on your hardware.</para>
|
||||
|
|
@ -938,7 +938,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Winbond W89C840F fast ethernet nics including the
|
||||
<para>Winbond W89C840F fast ethernet NICs including the
|
||||
Trendware TE100-PCIE</para>
|
||||
</listitem>
|
||||
|
||||
|
|
@ -1437,7 +1437,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Various frame grabbers based ont he the Brooktree Bt848
|
||||
<para>Various frame grabbers based on the Brooktree Bt848
|
||||
and Bt878 chip</para>
|
||||
</listitem>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/internals/chapter.sgml,v 1.20 2000/04/30 22:30:44 nik Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/internals/chapter.sgml,v 1.21 2000/06/08 01:56:09 jim Exp $
|
||||
-->
|
||||
|
||||
<chapter id="internals">
|
||||
|
|
@ -1434,7 +1434,7 @@
|
|||
|
||||
<para>FreeBSD dynamically tunes its paging queues and attempts to
|
||||
maintain reasonable ratios of pages in the various queues as well as
|
||||
attempts to maintain a reasonable breakdown of clean vs dirty pages.
|
||||
attempts to maintain a reasonable breakdown of clean v.s. dirty pages.
|
||||
The amount of rebalancing that occurs depends on the system's memory
|
||||
load. This rebalancing is implemented by the pageout daemon and
|
||||
involves laundering dirty pages (syncing them with their backing
|
||||
|
|
@ -1761,7 +1761,7 @@ makeoptions COPTFLAGS="-O2 -pipe"</programlisting>
|
|||
<para>RFC2428: FTP Extensions for IPv6 and NATs</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>RFC2428 is preferred over RFC1639. ftp clients will
|
||||
<para>RFC2428 is preferred over RFC1639. FTP clients will
|
||||
first try RFC2428, then RFC1639 if failed.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
@ -1812,7 +1812,7 @@ makeoptions COPTFLAGS="-O2 -pipe"</programlisting>
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Necessary statistics are gathered by the kernel. Actual
|
||||
IPv6 MIB support is provided as patchkit for ucd-snmp.</para>
|
||||
IPv6 MIB support is provided as a patchkit for ucd-snmp.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
|
|
@ -2043,7 +2043,7 @@ makeoptions COPTFLAGS="-O2 -pipe"</programlisting>
|
|||
<sect3 id="ipv6-pnp">
|
||||
<title>Plug and Play</title>
|
||||
|
||||
<para>Most of the IPv6 stateless address autoconfiguration is implemeted
|
||||
<para>Most of the IPv6 stateless address autoconfiguration is implemented
|
||||
in the kernel. Neighbor Discovery functions are implemented in the
|
||||
kernel as a whole. Router Advertisement (RA) input for hosts is
|
||||
implemented in the kernel. Router Solicitation (RS) output for
|
||||
|
|
@ -2053,7 +2053,7 @@ makeoptions COPTFLAGS="-O2 -pipe"</programlisting>
|
|||
<sect4>
|
||||
<title>Assignment of link-local, and special addresses</title>
|
||||
|
||||
<para>IPv6 link-local address is generated from IEEE802 adddress
|
||||
<para>IPv6 link-local address is generated from IEEE802 address
|
||||
(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
|
||||
|
|
@ -2167,7 +2167,7 @@ fe80:2::%ep0/64 link#2 UC ep0
|
|||
<title>Generic tunnel interface</title>
|
||||
|
||||
<para>GIF (Generic InterFace) is a pseudo interface for configured
|
||||
tunnel. Details are described in &man.gif.4; manpage. Currently</para>
|
||||
tunnel. Details are described in &man.gif.4;. Currently</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
|
|
@ -2193,10 +2193,10 @@ fe80:2::%ep0/64 link#2 UC ep0
|
|||
|
||||
<para>gif can be configured to be ECN-friendly. See <link
|
||||
linkend="ipsec-ecn">23.5.4.5</link> for ECN-friendliness of
|
||||
tunnels, and &man.gif.4; manpage for how to configure.</para>
|
||||
tunnels, and &man.gif.4; for how to configure.</para>
|
||||
|
||||
<para>If you would like to configure an IPv4-in-IPv6 tunnel with gif
|
||||
interface, read &man.gif.4; manpage carefully. You will need to
|
||||
interface, read &man.gif.4; carefully. You will need to
|
||||
remove IPv6 link-local address automatically assigned to the gif
|
||||
interface.</para>
|
||||
</sect3>
|
||||
|
|
@ -2267,10 +2267,10 @@ fe80:2::%ep0/64 link#2 UC ep0
|
|||
|
||||
<para>For new connections (when rule 1 does not apply), deprecated
|
||||
addresses (addresses with preferred lifetime = 0) will not be chosen
|
||||
as source address if other choises are available. If no other choices
|
||||
as source address if other choices are available. If no other choices
|
||||
are available, deprecated address will be used as a last resort. If
|
||||
there are multiple choice of deprecated addresses, the above scope
|
||||
rule will be used to choose from those deprecated addreses. If you
|
||||
rule will be used to choose from those deprecated addresses. If you
|
||||
would like to prohibit the use of deprecated address for some reason,
|
||||
configure net.inet6.ip6.use_deprecated to 0. The issue related to
|
||||
deprecated address is described in RFC2462 5.5.4 (NOTE: there is
|
||||
|
|
@ -2493,14 +2493,14 @@ fe80:2::%ep0/64 link#2 UC ep0
|
|||
"listening side" and the latter one "initiating side", for
|
||||
reference purposes.</para>
|
||||
|
||||
<para>You can perform wildcard bind on both of the adderss families,
|
||||
<para>You can perform wildcard bind on both of the address families,
|
||||
on the same port.</para>
|
||||
|
||||
<para>The following table show the behavior of FreeBSD 4.x.</para>
|
||||
|
||||
<screen>
|
||||
listening side initiating side
|
||||
(AF_INET6 wildcard (connetion to ::ffff:10.1.1.1)
|
||||
(AF_INET6 wildcard (connection to ::ffff:10.1.1.1)
|
||||
socket gets IPv4 conn.)
|
||||
--- ---
|
||||
FreeBSD 4.x configurable supported
|
||||
|
|
@ -2595,8 +2595,8 @@ FreeBSD 4.x configurable supported
|
|||
|
||||
<para>If you would like to use AF_INET6 socket for both IPv4 and
|
||||
IPv6 outgoing connection, you will need to use &man.getipnodebyname.3;.
|
||||
When you would like to update your existing appication to be IPv6
|
||||
aware with minimal effort, this approach might be choosed. But please
|
||||
When you would like to update your existing application to be IPv6
|
||||
aware with minimal effort, this approach might be chosen. But please
|
||||
note that it is a temporal solution, because &man.getipnodebyname.3;
|
||||
itself is not recommended as it does not handle scoped IPv6 addresses
|
||||
at all. For IPv6 name resolution, &man.getaddrinfo.3; is the
|
||||
|
|
@ -2605,7 +2605,7 @@ FreeBSD 4.x configurable supported
|
|||
|
||||
<para>When writing applications that make outgoing connections,
|
||||
story goes much simpler if you treat AF_INET and AF_INET6 as totally
|
||||
seaprate address family. {set,get}sockopt issue goes simpler,
|
||||
separate address family. {set,get}sockopt issue goes simpler,
|
||||
DNS issue will be made simpler. We do not recommend you to rely
|
||||
upon IPv4 mapped address.</para>
|
||||
|
||||
|
|
@ -2613,7 +2613,7 @@ FreeBSD 4.x configurable supported
|
|||
<title>unified tcp and inpcb code</title>
|
||||
|
||||
<para>FreeBSD 4.x uses shared tcp code between IPv4 and IPv6
|
||||
(from sys/netinet/tcp*) and separete udp4/6 code. It uses
|
||||
(from sys/netinet/tcp*) and separate udp4/6 code. It uses
|
||||
unified inpcb structure.</para>
|
||||
|
||||
<para>The platform can be configured to support IPv4 mapped address.
|
||||
|
|
@ -2673,7 +2673,7 @@ FreeBSD 4.x configurable supported
|
|||
<sect5>
|
||||
<title>initiating side</title>
|
||||
|
||||
<para>FreeBSD 4.x supports outgoing connetion to IPv4 mapped
|
||||
<para>FreeBSD 4.x supports outgoing connection to IPv4 mapped
|
||||
address (::ffff:10.1.1.1), if the node is configured to support
|
||||
IPv4 mapped address.</para>
|
||||
</sect5>
|
||||
|
|
@ -2683,7 +2683,7 @@ FreeBSD 4.x configurable supported
|
|||
<sect3>
|
||||
<title>sockaddr_storage</title>
|
||||
|
||||
<para>When RFC2553 was about to be finalized, there was discusson on
|
||||
<para>When RFC2553 was about to be finalized, there was discussion on
|
||||
how struct sockaddr_storage members are named. One proposal is to
|
||||
prepend "__" to the members (like "__ss_len") as they should not be
|
||||
touched. The other proposal was that don't prepend it (like "ss_len")
|
||||
|
|
@ -2715,7 +2715,7 @@ FreeBSD 4.x configurable supported
|
|||
the latter (XNET) definition.</para>
|
||||
|
||||
<para>Current implementation conforms to XNET definition, based on
|
||||
RFC2553bis discusson.</para>
|
||||
RFC2553bis discussion.</para>
|
||||
|
||||
<para>If you look at multiple IPv6 implementations, you will be able
|
||||
to see both definitions. As an userland programmer, the most
|
||||
|
|
@ -2728,7 +2728,7 @@ FreeBSD 4.x configurable supported
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>have -Dss_family=__ss_family to unify all occurences
|
||||
<para>have -Dss_family=__ss_family to unify all occurrences
|
||||
(including header file) into __ss_family, or</para>
|
||||
</listitem>
|
||||
|
||||
|
|
@ -2770,7 +2770,7 @@ FreeBSD 4.x configurable supported
|
|||
you find any problem with your card using IPv6/IPsec, then, please
|
||||
report it to <email>freebsd-bugs@FreeBSD.org</email>.</para>
|
||||
|
||||
<para>(NOTE: In the past we required all pcmcia drivers to have a
|
||||
<para>(NOTE: In the past we required all PCMCIA drivers to have a
|
||||
call to in6_ifattach(). We have no such requirement any more)</para>
|
||||
</sect2>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.26 2000/06/08 01:56:10 jim Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.27 2000/06/12 23:57:35 murray Exp $
|
||||
-->
|
||||
|
||||
<chapter id="kernelconfig">
|
||||
|
|
@ -245,7 +245,7 @@ cpu I686_CPU</programlisting>
|
|||
your CPU use, you can use the <command>dmesg</command> command to
|
||||
view your boot up messages.</para>
|
||||
|
||||
<para>The Alpha architechture has different values for
|
||||
<para>The Alpha architecture has different values for
|
||||
<literal>cpu_type</literal>. They include:</para>
|
||||
|
||||
<programlisting>
|
||||
|
|
@ -794,7 +794,7 @@ device miibus # MII bus support</programlisting>
|
|||
|
||||
<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 taht operate like an MII. Adding
|
||||
transceiver control interfaces that operate like an MII. Adding
|
||||
<literal>device miibus</literal> to the kernel config pulls in
|
||||
support for the generic miibus API and all of the PHY drivers,
|
||||
including a generic one for PHYs that are not specifically handled
|
||||
|
|
@ -819,14 +819,14 @@ device ed0 at isa? port 0x280 irq 10 iomem 0xd8000
|
|||
device ex
|
||||
device ep
|
||||
# WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really
|
||||
# exists only as a PCMCIA device, so there is no ISA attatement needed
|
||||
# exists only as a PCMCIA device, so there is no ISA attachment needed
|
||||
# and resources will always be dynamically assigned by the pccard code.
|
||||
device wi
|
||||
# Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will
|
||||
# work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP
|
||||
# mode (the factory default). If you set the switches on your ISA
|
||||
# card for a manually chosen I/O address and IRQ, you must specify
|
||||
# those paremeters here.
|
||||
# those parameters here.
|
||||
device an
|
||||
# The probe order of these is presently determined by i386/isa/isa_compat.c.
|
||||
device ie0 at isa? port 0x300 irq 10 iomem 0xd0000
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kerneldebug/chapter.sgml,v 1.22 2000/04/03 02:15:41 chris Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kerneldebug/chapter.sgml,v 1.23 2000/06/08 01:56:10 jim Exp $
|
||||
-->
|
||||
|
||||
<chapter id="kerneldebug">
|
||||
|
|
@ -286,7 +286,7 @@ makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols</
|
|||
<sect1>
|
||||
<title>On-Line Kernel Debugging Using DDB</title>
|
||||
|
||||
<para>While <command>kgdb</command> as an offline debugger provides a very
|
||||
<para>While <command>kgdb</command> as an off-line debugger provides a very
|
||||
high level of user interface, there are some things it cannot do. The
|
||||
most important ones being breakpointing and single-stepping kernel
|
||||
code.</para>
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kernelopts/chapter.sgml,v 1.14 1999/12/11 06:04:35 chris Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kernelopts/chapter.sgml,v 1.15 2000/06/08 01:56:11 jim Exp $
|
||||
-->
|
||||
|
||||
<chapter id="kernelopts">
|
||||
|
|
@ -34,7 +34,7 @@
|
|||
C preprocessor macro for the kernel compilation process. To make the
|
||||
build truly optional, the corresponding part of the kernel source (or
|
||||
kernel <filename>.h</filename> file) must be written with the option
|
||||
concept in mind, i.e. the default must have been made overridable by the
|
||||
concept in mind, i.e., the default can be overridden by the
|
||||
config option. This is usually done with something like:</para>
|
||||
|
||||
<programlisting>
|
||||
|
|
@ -107,7 +107,7 @@ options notyet,notdef</programlisting>
|
|||
|
||||
<para>If there is already something that comes close to the purpose of the
|
||||
new option, pick this. For example, options modifying the overall
|
||||
behaviour of the SCSI subsystem can go into
|
||||
behavior of the SCSI subsystem can go into
|
||||
<filename>opt_scsi.h</filename>. By default, simply mentioning an
|
||||
option in the appropriate option file, say <literal>FOO</literal>,
|
||||
implies its value will go into the corresponding file
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/l10n/chapter.sgml,v 1.35 2000/04/16 22:10:20 ache Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/l10n/chapter.sgml,v 1.36 2000/06/08 01:56:11 jim Exp $
|
||||
-->
|
||||
|
||||
<chapter id="l10n">
|
||||
|
|
@ -25,7 +25,7 @@
|
|||
|
||||
<para>The author realizes that he may have been incomplete in the
|
||||
description of the i18n process in FreeBSD. Due to the various
|
||||
levels of i18n implementation in both the system and applicational
|
||||
levels of i18n implementation in both the system and application
|
||||
levels, we advise you to refer to individual documentation, man
|
||||
pages, READMEs, and so forth.</para>
|
||||
|
||||
|
|
@ -91,7 +91,7 @@
|
|||
the codes for the specify country and language (country
|
||||
codes tell applications what variation of given
|
||||
language to use). In addition, web
|
||||
browsers, SMTP/POP servers, HTTPd's, etc. make decisions based on
|
||||
browsers, SMTP/POP servers, web servers, etc. make decisions based on
|
||||
them. The following are examples of language/country codes:</para>
|
||||
|
||||
<informaltable frame="none">
|
||||
|
|
@ -222,7 +222,7 @@
|
|||
each shell's startup file. <link linkend="usr-setup">User
|
||||
Level Setup</link> can be done by an user himself and <link
|
||||
linkend="adm-setup">Administrator Level Setup</link> require
|
||||
superuser priviledges.</para>
|
||||
superuser privileges.</para>
|
||||
|
||||
<sect5 id="usr-setup">
|
||||
<title>User Level Setup</title>
|
||||
|
|
@ -513,7 +513,7 @@ options SC_MOUSE_CHAR=0x03</programlisting>
|
|||
<para>Although X11 is not part of the FreeBSD Project, we have
|
||||
included some information here for FreeBSD users. For more
|
||||
details, refer to the <ulink url="http://www.xfree86.org/">XFree86
|
||||
website</ulink> or whichever X11 Server you use.</para>
|
||||
web site</ulink> or whichever X11 Server you use.</para>
|
||||
|
||||
<para>In <filename>~/.Xresources</filename>, you can additionally
|
||||
tune application specific i18n settings (e.g., fonts, menus,
|
||||
|
|
@ -561,11 +561,11 @@ options SC_MOUSE_CHAR=0x03</programlisting>
|
|||
wide or multibyte character sets have independent patches for FFS
|
||||
enabling such support. They are only temporary unportable
|
||||
solutions or hacks and we have decided to not include them in the
|
||||
source tree. Refer to respective languages' websites for more
|
||||
source tree. Refer to respective languages' web sites for more
|
||||
informations and the patch files.</para>
|
||||
|
||||
<para>The FreeBSD MSDOS filesystem has the configurable ability to
|
||||
convert between MSDOS, Unicode character sets and chosen
|
||||
<para>The FreeBSD MS-DOS filesystem has the configurable ability to
|
||||
convert between MS-DOS, Unicode character sets and chosen
|
||||
FreeBSD filesystem character sets. See &man.mount.msdos.8; for
|
||||
details.</para>
|
||||
</sect2>
|
||||
|
|
@ -615,7 +615,7 @@ options SC_MOUSE_CHAR=0x03</programlisting>
|
|||
efforts for each country has been repeating each others'
|
||||
efforts. Many of us have been reinventing the wheel repeatedly
|
||||
and inefficiently. We hope that the various major groups in
|
||||
i18n could congregate into a group effort similiar to the Core
|
||||
i18n could congregate into a group effort similar to the Core
|
||||
Team's responsibility.</para>
|
||||
|
||||
<para>Currently, we hope that, when you write or port i18n
|
||||
|
|
@ -738,10 +738,10 @@ lp|Russian local line printer:\
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>MSDOS FS and Russian Filenames</title>
|
||||
<title>MS-DOS FS and Russian Filenames</title>
|
||||
|
||||
<para>The following example &man.fstab.5; entry enables support
|
||||
for Russian filenames in mounted MSDOS filesystems:</para>
|
||||
for Russian filenames in mounted MS-DOS filesystems:</para>
|
||||
|
||||
<programlisting>
|
||||
/dev/ad0s2 /dos/c msdos rw,-W=koi2dos,-L=ru_RU.KOI8-R 0 0</programlisting>
|
||||
|
|
@ -873,7 +873,7 @@ XkbVariant "winkeys"</programlisting>
|
|||
|
||||
<row>
|
||||
<entry>zh-doc tag=.</entry>
|
||||
<entry>FreeBSD Documenation Translation to BIG-5 Traditional
|
||||
<entry>FreeBSD Documentation Translation to BIG-5 Traditional
|
||||
Chinese</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
|
|
|
|||
Loading…
Reference in a new issue