summaryrefslogtreecommitdiff
path: root/share/man/man4/netintro.4
diff options
context:
space:
mode:
authorAaron Campbell <aaron@cvs.openbsd.org>1999-07-09 13:36:00 +0000
committerAaron Campbell <aaron@cvs.openbsd.org>1999-07-09 13:36:00 +0000
commit078c2448197a826265f74828b3159d758f1f0ceb (patch)
treeef3b0d7b2b6fcf1328ac8953d9e2abf6431093ea /share/man/man4/netintro.4
parent3610cb2f5b1eeb5e599fcca418780b43c2f30b6d (diff)
- remove all trailing whitespace
* except when it is escaped with a `\' at the end of the line - fix remaining .Nm usage as well - this is from a patch I received from kwesterback@home.com, who has been working on some scripts for fixing formatting errors in mdoc'd man pages Ok, so there could be a cost/benefit debate with this commit, but since I have the patch we might as well commit it...
Diffstat (limited to 'share/man/man4/netintro.4')
-rw-r--r--share/man/man4/netintro.416
1 files changed, 8 insertions, 8 deletions
diff --git a/share/man/man4/netintro.4 b/share/man/man4/netintro.4
index d622cde32f1..aac58f3d305 100644
--- a/share/man/man4/netintro.4
+++ b/share/man/man4/netintro.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: netintro.4,v 1.14 1999/07/02 20:11:49 aaron Exp $
+.\" $OpenBSD: netintro.4,v 1.15 1999/07/09 13:35:47 aaron Exp $
.\" $NetBSD: netintro.4,v 1.4 1995/10/19 08:03:40 jtc Exp $
.\"
.\" Copyright (c) 1983, 1990, 1991, 1993
@@ -59,8 +59,8 @@ All network protocols are associated with a specific
.Em protocol family .
A protocol family provides basic services to the protocol
implementation to allow it to function within a specific
-network environment. These services may include
-packet fragmentation and reassembly, routing, addressing, and
+network environment. These services may include
+packet fragmentation and reassembly, routing, addressing, and
basic transport. A protocol family may support multiple
methods of addressing, though the current protocol implementations
do not. A protocol family is normally comprised of a number
@@ -68,7 +68,7 @@ of protocols, one per
.Xr socket 2
type. It is not required that a protocol family support
all socket types. A protocol family may contain multiple
-protocols supporting the same socket abstraction.
+protocols supporting the same socket abstraction.
.Pp
A protocol supports one of the socket abstractions detailed in
.Xr socket 2 .
@@ -180,7 +180,7 @@ certain interfaces such as the loopback interface,
.Xr lo 4 ,
do not.
.Pp
-The following
+The following
.Xr ioctl
calls may be used to manipulate network interfaces.
The
@@ -188,7 +188,7 @@ The
is made on a socket (typically of type
.Dv SOCK_DGRAM )
in the desired domain.
-Most of the requests supported in earlier releases
+Most of the requests supported in earlier releases
take an
.Ar ifreq
structure as its parameter. This structure has the form
@@ -294,10 +294,10 @@ the address family in which the original socket was opened.
.It Dv SIOCGIFCONF
Get interface configuration list. This request takes an
.Ar ifconf
-structure (see below) as a value-result parameter. The
+structure (see below) as a value-result parameter. The
.Ar ifc_len
field should be initially set to the size of the buffer
-pointed to by
+pointed to by
.Ar ifc_buf .
On return it will contain the length, in bytes, of the
configuration list. Alternately, if the