BSD 4_3_Net_2 release

[unix-history] / usr / src / share / man / man4 / lo.4

diff --git a/usr/src/share/man/man4/lo.4 b/usr/src/share/man/man4/lo.4
index fce0127..8fcef27 100644 (file)
--- a/usr/src/share/man/man4/lo.4
+++ b/usr/src/share/man/man4/lo.4
@@ -1,49 +1,80 @@
-.\" Copyright (c) 1983 The Regents of the University of California.
+.\" Copyright (c) 1983, 1991 The Regents of the University of California.

 .\" All rights reserved.
 .\"
 .\" All rights reserved.
 .\"

-.\" Redistribution and use in source and binary forms are permitted provided
-.\" that: (1) source distributions retain this entire copyright notice and
-.\" comment, and (2) distributions including binaries display the following
-.\" acknowledgement:  ``This product includes software developed by the
-.\" University of California, Berkeley and its contributors'' in the
-.\" documentation or other materials provided with the distribution and in
-.\" all advertising materials mentioning features or use of this software.
-.\" Neither the name of the University nor the names of its contributors may
-.\" be used to endorse or promote products derived from this software without
-.\" specific prior written permission.
-.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
-.\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
-.\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"    This product includes software developed by the University of
+.\"    California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.

 .\"
 .\"

-.\"    @(#)lo.4        6.5 (Berkeley) 6/23/90
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.

 .\"
 .\"

-.TH LO 4 "June 23, 1990"
-.UC 5
-.SH NAME
-lo \- software loopback network interface
-.SH SYNOPSIS
-.B pseudo-device loop
-.SH DESCRIPTION
+.\"     @(#)lo.4       6.6 (Berkeley) 3/28/91
+.\"
+.Dd March 28, 1991
+.Dt LO 4
+.Os BSD 4.2
+.Sh NAME
+.Nm lo
+.Nd software loopback network interface
+.Sh SYNOPSIS
+.Sy pseudo-device
+.Nm loop
+.Sh DESCRIPTION

 The
 The

-.I loop
+.Nm loop

 interface is a software loopback mechanism which may be
 used for performance analysis, software testing, and/or local
 communication.
 As with other network interfaces, the loopback interface must have
 network addresses assigned for each address family with which it is to be used.
 These addresses
 interface is a software loopback mechanism which may be
 used for performance analysis, software testing, and/or local
 communication.
 As with other network interfaces, the loopback interface must have
 network addresses assigned for each address family with which it is to be used.
 These addresses

-may be set or changed with the SIOCSIFADDR ioctl.
+may be set or changed with the
+.Dv SIOCSIFADDR
+.Xr ioctl 2 .

 The loopback interface should be the last interface configured,
 as protocols may use the order of configuration as an indication of priority.
 The loopback interface should be the last interface configured,
 as protocols may use the order of configuration as an indication of priority.

-The loopback should \fBnever\fP be configured first unless no hardware
+The loopback should
+.Em never
+be configured first unless no hardware

 interfaces exist.
 interfaces exist.

-.SH DIAGNOSTICS
-\fBlo%d: can't handle af%d\fP.  The interface was handed
+.Sh DIAGNOSTICS
+.Bl -diag
+.It lo%d: can't handle af%d.
+The interface was handed

 a message with addresses formatted in an unsuitable address
 family; the packet was dropped.
 a message with addresses formatted in an unsuitable address
 family; the packet was dropped.

-.SH SEE ALSO
-intro(4), inet(4), ns(4)
-.SH BUGS
+.El
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr inet 4 ,
+.Xr ns 4
+.Sh HISTORY
+The
+.Nm
+device appeared in
+.Bx 4.2 .
+.Sh BUGS

 Previous versions of the system enabled the loopback interface
 automatically, using a nonstandard Internet address (127.1).
 Use of that address is now discouraged; a reserved host address
 Previous versions of the system enabled the loopback interface
 automatically, using a nonstandard Internet address (127.1).
 Use of that address is now discouraged; a reserved host address