LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

RFC references are now always writen as "RFC\ nnn" (not "RFC nnn" or 

"RFCnnn").
This commit is contained in:
Michael Kerrisk 2005-07-20 07:50:45 +00:00
parent 3dbef8d0ef
commit 331da7c3a0
24 changed files with 43 additions and 38 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Changes
View File

@ -17,6 +17,9 @@ Apologies if I missed anyone!
Global changes
--------------
RFC references are now always writen as "RFC\ nnn" (not "RFC nnn" or
"RFCnnn").
Typographical or grammatical errors have been corrected in several
places.

2
man2/adjtimex.2
View File

@ -34,7 +34,7 @@ adjtimex \- tune kernel clock
.sp
.BI "int adjtimex(struct timex *" "buf" );
.SH DESCRIPTION
Linux uses David L. Mills' clock adjustment algorithm (see RFC 1305).
Linux uses David L. Mills' clock adjustment algorithm (see RFC\ 1305).
The system call
.B adjtimex
reads and optionally sets adjustment parameters for this algorithm.

4
man3/cmsg.3
View File

@ -208,7 +208,7 @@ this could be used to declare the size of global
variables. This may be not portable, however.
.SH "CONFORMS TO"
This ancillary data model conforms to the POSIX.1003.1g draft, 4.4BSD-Lite,
the IPv6 advanced API described in RFC2292 and the Single Unix specification v2.
the IPv6 advanced API described in RFC\ 2292 and the Single Unix specification v2.
.B
CMSG_ALIGN
is a Linux extension.
@ -216,4 +216,4 @@ is a Linux extension.
.BR recvmsg (2),
.BR sendmsg (2)
.PP
RFC 2292
RFC\ 2292

2
man3/getaddrinfo.3
View File

@ -302,7 +302,7 @@ suitable for error reporting.
POSIX 1003.1-2003.
The
.B getaddrinfo()
function is documented in RFC 2553.
function is documented in RFC\ 2553.
.SH "SEE ALSO"
.BR getipnodebyaddr (3),
.BR getipnodebyname (3)

2
man3/gethostbyname.3
View File

@ -88,7 +88,7 @@ Here
.I name
is either a host name, or an IPv4 address in standard dot notation,
or an IPv6 address in colon (and possibly dot) notation.
(See RFC 1884 for the description of IPv6 addresses.)
(See RFC\ 1884 for the description of IPv6 addresses.)
If
.I name
is an IPv4 or IPv6 address, no lookup is performed and

2
man3/getipnodebyname.3
View File

@ -254,7 +254,7 @@ These functions have been present in glibc 2.1.91-95, but were
removed again. Several Unix-like systems support them, but all
call them deprecated.
.SH "CONFORMING TO"
RFC 2553.
RFC\ 2553.
.SH "SEE ALSO"
.BR getaddrinfo (3),
.BR getnameinfo (3),

4
man3/getnameinfo.3
View File

@ -184,7 +184,7 @@ reverse address mapping.
.fi
.RE
.SH "CONFORMING TO"
RFC 2553. (See also XNS, issue 5.2.)
RFC\ 2553. (See also XNS, issue 5.2.)
.SH "SEE ALSO"
.BR getaddrinfo (3),
.BR gethostbyaddr (3),
@ -199,7 +199,7 @@ RFC 2553. (See also XNS, issue 5.2.)
.LP
R. Gilligan, S. Thomson, J. Bound and W. Stevens,
.IR "Basic Socket Interface Extensions for IPv6" ,
RFC 2553, March 1999.
RFC\ 2553, March 1999.
.LP
Tatsuya Jinmei and Atsushi Onoe,
.IR "An Extension of Format for IPv6 Scoped Addresses" ,

2
man3/getnetent.3
View File

@ -108,4 +108,4 @@ networks database file
.BR getservent (3),
.BR networks (5)
.br
RFC 1101
RFC\ 1101

4
man3/inet_ntop.3
View File

@ -97,11 +97,11 @@ given by the
argument.
.SH "CONFORMING TO"
POSIX 1003.1-2001.
Note that RFC 2553 defines a prototype where the last parameter
Note that RFC\ 2553 defines a prototype where the last parameter
.I cnt
is of type
.BR size_t .
Many systems follow RFC 2553.
Many systems follow RFC\ 2553.
Glibc 2.0 and 2.1 have size_t, but 2.2 has socklen_t.
.\" 2.1.3: size_t, 2.1.91: socklen_t
.SH "SEE ALSO"

2
man3/rpc.3
View File

@ -1739,5 +1739,5 @@ rpcgen Programming Guide
.ft R
.RE
.IR "\s-1RPC\s0: Remote Procedure Call Protocol Specification" ,
.SM RFC1050, Sun Microsystems, Inc.,
.SM RFC\ 1050, Sun Microsystems, Inc.,
.SM USC-ISI\s0.

2
man3/rtime.3
View File

@ -18,7 +18,7 @@ rtime \- get time from a remote machine
.sp
.SH DESCRIPTION
This function uses the Time Server Protocol as described in
RFC 868 to obtain the time from a remote machine.
RFC\ 868 to obtain the time from a remote machine.
.LP
The Time Server Protocol gives the time in seconds since midnight 1900-01-01,
and this function subtracts the appropriate constant in order to

2
man3/strftime.3
View File

@ -196,7 +196,7 @@ The year as a decimal number including the century.
.TP
.B %z
The time-zone as hour offset from GMT.
Required to emit RFC822-conformant dates
Required to emit RFC\ 822-conformant dates
(using "%a, %d %b %Y %H:%M:%S %z"). (GNU)
.TP
.B %Z

2
man3/xdr.3
View File

@ -818,5 +818,5 @@ eXternal Data Representation: Sun Technical Notes
.ft R
.br
.IR "\s-1XDR\s0: External Data Representation Standard" ,
.SM RFC1014, Sun Microsystems, Inc.,
.SM RFC\ 1014, Sun Microsystems, Inc.,
.SM USC-ISI\s0.

2
man4/random.4
View File

@ -144,4 +144,4 @@ Theodore Ts'o (tytso@athena.mit.edu).
.SH "SEE ALSO"
mknod (1)
.br
RFC 1750, "Randomness Recommendations for Security"
RFC\ 1750, "Randomness Recommendations for Security"

4
man5/hosts.5
View File

@ -86,7 +86,7 @@ advantage.
Modifications to this file normally take effect immediately,
except in cases where the file is cached by applications.
.SH "HISTORICAL NOTES"
RFC 952 gave the original format for the host table, though it has
RFC\ 952 gave the original format for the host table, though it has
since changed.
Before the advent of DNS, the host table was the only way of resolving
@ -106,7 +106,7 @@ historical hosts.txt files on the WWW. I just found three, from 92,
.BR resolver (5),
.BR hostname (7),
.BR named (8),
Internet RFC 952
Internet RFC\ 952
.SH AUTHOR
This manual page was written by Manoj Srivastava <srivasta@debian.org>,
for the Debian GNU/Linux system.

3
man5/proc.5
View File

@ -614,7 +614,8 @@ IP address HW type Flags HW address Mask Device
.in
Here 'IP address' is the IPv4 address of the machine and the 'HW type'
is the hardware type of the address from RFC 826. The flags are the internal
is the hardware type of the address from RFC\ 826.
The flags are the internal
flags of the ARP structure (as defined in /usr/include/linux/if_arp.h) and
the 'HW address' is the data link layer mapping for that IP address if
it is known.

2
man5/services.5
View File

@ -200,7 +200,7 @@ Definition of
.BR protocols (5),
.BR inetd (8)
Assigned Numbers RFC, most recently RFC 1700, (AKA STD0002)
Assigned Numbers RFC, most recently RFC\ 1700, (AKA STD0002)
Guide to Yellow Pages Service

2
man7/arp.7
View File

@ -11,7 +11,7 @@
arp \- Linux ARP kernel module.
.SH DESCRIPTION
This kernel protocol module implements the Address Resolution
Protocol defined in RFC 826.
Protocol defined in RFC\ 826.
It is used to convert between Layer2 hardware addresses
and IPv4 protocol addresses on directly connected networks.
The user normally doesn't interact directly with this module except to

4
man7/koi8-r.7
View File

@ -33,7 +33,7 @@ many Unix-like operation systems. KOI8-R is a successor for KOI-8, a
de-facto standard for Internet Mail, News, WWW and other interactive
services at least all over the ex-SU territory.
.PP
KOI8-R is defined by RFC1489 (Registration of a Cyrillic Character
KOI8-R is defined by RFC\ 1489 (Registration of a Cyrillic Character
Set).
.SH NOTE
@ -191,5 +191,5 @@ _
.BR ascii (7),
.BR iso-8859-7 (7)
(not yet written),
RFC1489,
RFC\ 1489,
http://koi8.pp.ru/

2
man7/mailaddr.7
View File

@ -111,4 +111,4 @@ addressed. The "postmaster" address is not case sensitive.
.BR sendmail (8),
.BR vrfy (8)
RFC2822 (Internet Message Format)
RFC\ 2822 (Internet Message Format)

4
man7/packet.7
View File

@ -397,9 +397,9 @@ is present since glibc2.1. Older systems need
.BR raw (7),
.BR socket (7)
RFC 894 for the standard IP Ethernet encapsulation.
RFC\ 894 for the standard IP Ethernet encapsulation.
RFC 1700 for the IEEE 802.3 IP encapsulation.
RFC\ 1700 for the IEEE 802.3 IP encapsulation.
The
.I <linux/if_ether.h>

2
man7/tcp.7
View File

@ -381,7 +381,7 @@ minimum limit of 100 seconds is typically deemed too
short.
.TP
.BR tcp_rfc1337 " (Boolean; default: disabled)"
Enable TCP behaviour conformant with RFC 1337.
Enable TCP behaviour conformant with RFC\ 1337.
When disabled,
if a RST is received in TIME_WAIT state, we close
the socket immediately without waiting for the end

21
man7/uri.7
View File

@ -227,7 +227,7 @@ A
.I message-id
corresponds to the Message-ID of
.UR http://www.ietf.org/rfc/rfc1036.txt
IETF RFC 1036,
IETF RFC\ 1036,
.UE
without the enclosing "<"
and ">"; it takes the form
@ -349,7 +349,7 @@ a set of servers for hierarchically-organized information
(such as people and computing resources).
More information on the LDAP URL scheme is available in
.UR http://www.ietf.org/rfc/rfc2255.txt
RFC 2255.
RFC\ 2255.
.UE
The components of this URL are:
.IP hostport 12
@ -361,12 +361,13 @@ If empty, the client determines which the LDAP server to use.
the LDAP Distinguished Name, which identifies
the base object of the LDAP search (see
.UR http://www.ietf.org/rfc/rfc2253.txt
RFC 2253
RFC\ 2253
.UE
section 3).
.IP attributes
a comma-separated list of attributes to be returned;
see RFC 2251 section 4.1.5. If omitted, all attributes should be returned.
see RFC\ 2251 section 4.1.5.
If omitted, all attributes should be returned.
.IP scope
specifies the scope of the search, which can be one of
"base" (for a base object search), "one" (for a one-level search),
@ -376,7 +377,7 @@ specifies the search filter (subset of entries
to return). If omitted, all entries should be returned.
See
.UR http://www.ietf.org/rfc/rfc2254.txt
RFC 2254
RFC\ 2254
.UE
section 4.
.IP extensions
@ -412,7 +413,7 @@ ldap://host.com:6666/o=University%20of%20Michigan,c=US??sub?(cn=Babs%20Jensen)
This scheme designates a WAIS database, search, or document
(see
.UR http://www.ietf.org/rfc/rfc1625.txt
IETF RFC 1625
IETF RFC\ 1625
.UE
for more information on WAIS).
Hostport is the hostname, optionally followed by a colon and port number
@ -482,9 +483,9 @@ path, but the two are equivalent for an http URL.
.PP
For URIs which must handle characters outside the US ASCII character set,
the HTML 4.01 specification (section B.2) and
IETF RFC 2718 (section 2.2.5) recommend the following approach:
IETF RFC\ 2718 (section 2.2.5) recommend the following approach:
.IP 1. 4
translate the character sequences into UTF-8 (IETF RFC 2279) \(em see
translate the character sequences into UTF-8 (IETF RFC\ 2279) \(em see
.BR utf-8 (7)
\(em and then
.IP 2.
@ -613,7 +614,7 @@ in those rare cases where the 'password' parameter is intended to be public.
.SH "CONFORMING TO"
.PP
.UR http://www.ietf.org/rfc/rfc2396.txt
IETF RFC 2396,
IETF RFC\ 2396,
.UE
.UR http://www.w3.org/TR/REC-html40
HTML 4.0.
@ -656,5 +657,5 @@ David A. Wheeler (dwheeler@dwheeler.com) wrote this man page.
.BR mailaddr (7),
.BR utf-8 (7)
.UR http://www.ietf.org/rfc/rfc2255.txt
IETF RFC 2255.
IETF RFC\ 2255.
.UE

2
man7/utf-8.7
View File

@ -275,7 +275,7 @@ ways to represent these things in a non-shortest
.B UTF-8
encoding.
.SH STANDARDS
ISO/IEC 10646-1:2000, Unicode 3.1, RFC 2279, Plan 9.
ISO/IEC 10646-1:2000, Unicode 3.1, RFC\ 2279, Plan 9.
.SH AUTHOR
Markus Kuhn <mgk25@cl.cam.ac.uk>
.SH "SEE ALSO"