upstream/bind9
1
0
Fork 0
mirror of https://github.com/isc-projects/bind9.git synced 2026-06-11 14:59:59 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

[v9_9] backport doc fixes from master

Browse source
This commit is contained in:
Evan Hunt 2014-08-18 14:08:19 -07:00
parent c4a8cecd96
commit c1989110d4
10 changed files with 30 additions and 28 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
bin/pkcs11/pkcs11-destroy.docbook
View file

@ -126,10 +126,10 @@
<title>SEE ALSO</title>
<para>
<citerefentry>
<refentrytitle>pkcs11-list</refentrytitle><manvolnum>3</manvolnum>
<refentrytitle>pkcs11-keygen</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
<citerefentry>
<refentrytitle>pkcs11-keygen</refentrytitle><manvolnum>3</manvolnum>
<refentrytitle>pkcs11-list</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>
</para>
</refsect1>

4
bin/pkcs11/pkcs11-list.docbook
View file

@ -130,10 +130,10 @@
<title>SEE ALSO</title>
<para>
<citerefentry>
<refentrytitle>pkcs11-keygen</refentrytitle><manvolnum>3</manvolnum>
<refentrytitle>pkcs11-destroy</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>,
<citerefentry>
<refentrytitle>pkcs11-destroy</refentrytitle><manvolnum>3</manvolnum>
<refentrytitle>pkcs11-keygen</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>
</para>
</refsect1>

4
bin/python/dnssec-coverage.docbook
View file

@ -130,7 +130,7 @@
<para>
This option is mandatory unless the <option>-f</option> has
been used to specify a zone file. (If <option>-f</option> has
been specified, this option may still be used; it will overrde
been specified, this option may still be used; it will override
the value found in the file.)
</para>
</listitem>
@ -159,7 +159,7 @@
been used to specify a zone file, or a default key TTL was
set with the <option>-L</option> to
<command>dnssec-keygen</command>. (If either of those is true,
this option may still be used; it will overrde the value found
this option may still be used; it will override the value found
in the zone or key file.)
</para>
</listitem>

23
doc/arm/Bv9ARM-book.xml
View file

@ -2871,12 +2871,14 @@ $ORIGIN 0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa.
<para>
Integers may take values
0 &lt;= value &lt;= 18446744073709551615, though
certain parameters may use a more limited range
within these extremes. In most cases, setting a
value to 0 does not literally mean zero; it means
"undefined" or "as big as psosible", depending on
the context. See the expalantions of particular
parameters that use <varname>size_spec</varname>
certain parameters
(such as <command>max-journal-size</command>) may
use a more limited range within these extremes.
In most cases, setting a value to 0 does not
literally mean zero; it means "undefined" or
"as big as possible", depending on the context.
See the explanations of particular parameters
that use <varname>size_spec</varname>
for details on how they interpret its use.
</para>
<para>
@ -7102,7 +7104,7 @@ options {
than matching the case of the records entered in
the zone file. This allows responses to exactly
match the query, which is required by some clients
due to incorrect use of case-sensitive comparisions.
due to incorrect use of case-sensitive comparisons.
</para>
<para>
Case-insensitive compression is <emphasis>always</emphasis>
@ -7110,12 +7112,12 @@ options {
the client matches this ACL.
</para>
<para>
There are circusmstances in which <command>named</command>
There are circumstances in which <command>named</command>
will not preserve the case of owner names of records:
if a zone file defines records of different types with
the same name, but the capitalization of the name is
different (e.g., "www.example.com/A" and
"WWW.EXAMPLE.COM/AAAA"), then all resposnes for that
"WWW.EXAMPLE.COM/AAAA"), then all responses for that
name will use the <emphasis>first</emphasis> version
of the name that was used in the zone file. This
limitation may be addressed in a future release. However,
@ -13305,8 +13307,7 @@ example.com. NS ns2.example.net.
<para>
Each RR can have a TTL as the second
field in the RR, which will control how long other
servers can cache
the it.
servers can cache it.
</para>
</entry>
</row>

2
doc/arm/libdns.xml
View file

@ -270,7 +270,7 @@ $ <userinput>make</userinput>
consists of a single domain name. Example:
<literallayout>
www.example.com
mx.examle.net
mx.example.net
ns.xxx.example
</literallayout>
</listitem>

13
doc/arm/pkcs11.xml
View file

@ -68,12 +68,13 @@
is an example of such a device.</para>
</listitem>
</itemizedlist>
<para>The modified OpenSSL code is included in the BIND 9 release,
in the form of a context diff against the latest verions of
OpenSSL. OpenSSL 0.9.8, 1.0.0 and 1.0.1 are supported; there are
separate diffs for each version. In the examples to follow,
we use OpenSSL 0.9.8, but the same methods work with OpenSSL 1.0.0
and 1.0.1.
<para>
The modified OpenSSL code is included in the BIND 9 release,
in the form of a context diff against the latest versions of
OpenSSL. OpenSSL 0.9.8, 1.0.0, and 1.0.1 are supported; there are
separate diffs for each version. In the examples to follow,
we use OpenSSL 0.9.8, but the same methods work with OpenSSL
1.0.0 and 1.0.1.
</para>
<note>
The latest OpenSSL versions at the time of the BIND release

2
lib/lwres/man/lwres.docbook
View file

@ -63,7 +63,7 @@
and address-to-hostname lookup services to applications by
transmitting lookup requests to a resolver daemon
<command>lwresd</command>
running on the local host. The resover daemon performs the
running on the local host. The resolver daemon performs the
lookup using the DNS or possibly other name service protocols,
and returns the results to the application through the library.
The library and resolver daemon communicate using a simple

2
lib/lwres/man/lwres_gabn.docbook
View file

@ -120,7 +120,7 @@ void
There are four main functions for the getaddrbyname opcode.
One render function converts a getaddrbyname request structure &mdash;
<type>lwres_gabnrequest_t</type> &mdash;
to the lighweight resolver's canonical format.
to the lightweight resolver's canonical format.
It is complemented by a parse function that converts a packet in this
canonical format to a getaddrbyname request structure.
Another render function converts the getaddrbyname response structure

2
lib/lwres/man/lwres_noop.docbook
View file

@ -127,7 +127,7 @@ void
There are four main functions for the no-op opcode.
One render function converts a no-op request structure &mdash;
<type>lwres_nooprequest_t</type> &mdash;
to the lighweight resolver's canonical format.
to the lightweight resolver's canonical format.
It is complemented by a parse function that converts a packet in this
canonical format to a no-op request structure.
Another render function converts the no-op response structure &mdash;

2
lib/lwres/man/lwres_resutil.docbook
View file

@ -153,7 +153,7 @@ typedef struct {
<para>
The lightweight resolver uses
<function>lwres_getaddrsbyname()</function> to perform
foward lookups.
forward lookups.
Hostname <parameter>name</parameter> is looked up using the
resolver
context <parameter>ctx</parameter> for memory allocation.