summaryrefslogtreecommitdiffstats
path: root/share/man/man4
diff options
context:
space:
mode:
authormpp <mpp@FreeBSD.org>1997-03-21 20:14:15 +0000
committermpp <mpp@FreeBSD.org>1997-03-21 20:14:15 +0000
commit58cd3eaefb6de8e1689f65bd4c8d11d8e7bc1f1a (patch)
tree9674e601ac4c12570560ade3f15444e16aaa65b8 /share/man/man4
parent56d1eaec03ddf805b935ada9001511e3453d0246 (diff)
downloadFreeBSD-src-58cd3eaefb6de8e1689f65bd4c8d11d8e7bc1f1a.zip
FreeBSD-src-58cd3eaefb6de8e1689f65bd4c8d11d8e7bc1f1a.tar.gz
Use the .Fx macro for FreeBSD references for releases prior to 2.0.
Use the .Tn macro for generic FreeBSD references. Cleanup other formatting problems noticed while making the above changes.
Diffstat (limited to 'share/man/man4')
-rw-r--r--share/man/man4/cd.410
-rw-r--r--share/man/man4/cy.45
-rw-r--r--share/man/man4/ed.49
-rw-r--r--share/man/man4/fpa.45
-rw-r--r--share/man/man4/man4.i386/ar.46
-rw-r--r--share/man/man4/man4.i386/cy.45
-rw-r--r--share/man/man4/man4.i386/ed.49
-rw-r--r--share/man/man4/man4.i386/io.44
-rw-r--r--share/man/man4/man4.i386/mcd.45
-rw-r--r--share/man/man4/man4.i386/meteor.46
-rw-r--r--share/man/man4/man4.i386/pcvt.425
-rw-r--r--share/man/man4/man4.i386/spkr.48
-rw-r--r--share/man/man4/man4.i386/sr.46
-rw-r--r--share/man/man4/man4.i386/tw.44
-rw-r--r--share/man/man4/man4.i386/ze.49
-rw-r--r--share/man/man4/pcvt.425
-rw-r--r--share/man/man4/snp.45
-rw-r--r--share/man/man4/spkr.48
-rw-r--r--share/man/man4/uk.410
-rw-r--r--share/man/man4/yp.464
20 files changed, 151 insertions, 77 deletions
diff --git a/share/man/man4/cd.4 b/share/man/man4/cd.4
index 8f82c3c..84a188e 100644
--- a/share/man/man4/cd.4
+++ b/share/man/man4/cd.4
@@ -23,7 +23,7 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
-.\" $Id$
+.\" $Id: cd.4,v 1.10 1997/02/22 13:24:23 peter Exp $
.\"
.Dd January 16, 1996
.Dt CD 4
@@ -63,12 +63,16 @@ bus is scanned for devices. Any devices found which answer as `Read-only'
type devices will be `attached' to the
.Nm
driver.
-In FreeBSD releases prior to 2.1, the first found will be attached as
+Prior to
+.Fx 2.1 ,
+the first device found will be attached as
.Li cd0
the next,
.Li cd1 ,
etc.
-Beginning in 2.1 it is possible to specify what cd unit a device should
+Beginning in
+.Fx 2.1
+it is possible to specify what cd unit a device should
come on line as; refer to
.Xr scsi 4
for details on kernel configuration.
diff --git a/share/man/man4/cy.4 b/share/man/man4/cy.4
index 0b4c0a9..6fd1017 100644
--- a/share/man/man4/cy.4
+++ b/share/man/man4/cy.4
@@ -35,7 +35,7 @@
.\" from: @(#)dca.4 5.2 (Berkeley) 3/27/91
.\" from: com.4,v 1.1 1993/08/06 11:19:07 cgd Exp
.\" from: sio.4,v 1.16 1995/06/26 06:05:30 bde Exp $
-.\" $Id: cy.4,v 1.6 1997/02/22 13:25:15 peter Exp $
+.\" $Id: cy.4,v 1.7 1997/03/03 18:38:37 bde Exp $
.\"
.Dd October 10, 1995
.Dt CY 4 i386
@@ -223,7 +223,8 @@ changed for higher efficiency:
.Pp
RxFifoThreshold: default 6; on a 486DX-33, this works for 8 ports
talking to each other at 115200 bps; 11 works for 8 ports talking
-to each other at 57600 bps. The low threshold is not for FreeBSD,
+to each other at 57600 bps. The low threshold is not for
+.Tn FreeBSD ,
it's for the CD1400, which can't really keep up with 115200 bps.
.Pp
PollMode: required for Cyclom-16Y's; costs 10-20% relative efficiency
diff --git a/share/man/man4/ed.4 b/share/man/man4/ed.4
index 6545cfc..347164e 100644
--- a/share/man/man4/ed.4
+++ b/share/man/man4/ed.4
@@ -28,7 +28,7 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
-.\" $Id: ed.4,v 1.8 1997/02/22 13:25:18 peter Exp $
+.\" $Id: ed.4,v 1.9 1997/02/28 02:20:42 mpp Exp $
.\"
.Dd October 28, 1995
.Dt ED 4 i386
@@ -82,7 +82,9 @@ identify themselves as 8bit, even though they have a 16bit ISA interface.
Disable transmitter multi-buffering. This flag disables the use of multiple
transmit buffers and may be necessary in rare cases where packets are sent out
faster than a machine on the other end can handle (as evidenced by severe packet
-lossage). Some (non-FreeBSD :-)) machines have terrible ethernet performance
+lossage). Some
+.Pf ( No non- Ns Tn FreeBSD
+:-)) machines have terrible ethernet performance
and simply can't cope with 1100K+ data rates. Use of this flag also provides
one more packet worth of receiver buffering, and on 8bit cards, this may help
reduce receiver lossage.
@@ -164,7 +166,8 @@ have been received but not yet transfered from the card to main memory.
.Sh HISTORY
The
.Nm ed
-device driver first appeared in FreeBSD 1.0.
+device driver first appeared in
+.Fx 1.0 .
.Sh AUTHOR
The
.Nm
diff --git a/share/man/man4/fpa.4 b/share/man/man4/fpa.4
index 8af9217..cf1983fa 100644
--- a/share/man/man4/fpa.4
+++ b/share/man/man4/fpa.4
@@ -2,7 +2,7 @@
.\" Copyright (c) 1995, Matt Thomas
.\" All rights reserved.
.\"
-.\" $Id$
+.\" $Id: fpa.4,v 1.8 1997/02/22 13:24:29 peter Exp $
.\"
.Dd March 13, 1995
.Dt FPA 4 i386
@@ -15,7 +15,8 @@
.Cd "device fpa0"
.Cd "device fea0"
.Pp
-FreeBSD only:
+.Tn FreeBSD
+only:
.Cd "pseudo-device fddi"
.Sh DESCRIPTION
The
diff --git a/share/man/man4/man4.i386/ar.4 b/share/man/man4/man4.i386/ar.4
index d40503e..23cfb8d 100644
--- a/share/man/man4/man4.i386/ar.4
+++ b/share/man/man4/man4.i386/ar.4
@@ -28,7 +28,7 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
-.\" $Id$
+.\" $Id: ar.4,v 1.5 1997/02/22 13:25:12 peter Exp $
.\"
.Dd November 19, 1995
.Dt AR 4 i386
@@ -51,7 +51,9 @@ HD64570 chip. Both the 2 and 4 port cards is supported and auto detected.
Line speeds of up to 2Mbps is possible. At this speed about 85% of the
bandwidth is usable with 486DX processors.
.Pp
-The standard FreeBSD sppp code is used for the link level layer. The
+The standard
+.Tn FreeBSD
+sppp code is used for the link level layer. The
default protocol used is PPP. The Cisco HDLC protocol can be used by
adding
.Ar link2
diff --git a/share/man/man4/man4.i386/cy.4 b/share/man/man4/man4.i386/cy.4
index 0b4c0a9..6fd1017 100644
--- a/share/man/man4/man4.i386/cy.4
+++ b/share/man/man4/man4.i386/cy.4
@@ -35,7 +35,7 @@
.\" from: @(#)dca.4 5.2 (Berkeley) 3/27/91
.\" from: com.4,v 1.1 1993/08/06 11:19:07 cgd Exp
.\" from: sio.4,v 1.16 1995/06/26 06:05:30 bde Exp $
-.\" $Id: cy.4,v 1.6 1997/02/22 13:25:15 peter Exp $
+.\" $Id: cy.4,v 1.7 1997/03/03 18:38:37 bde Exp $
.\"
.Dd October 10, 1995
.Dt CY 4 i386
@@ -223,7 +223,8 @@ changed for higher efficiency:
.Pp
RxFifoThreshold: default 6; on a 486DX-33, this works for 8 ports
talking to each other at 115200 bps; 11 works for 8 ports talking
-to each other at 57600 bps. The low threshold is not for FreeBSD,
+to each other at 57600 bps. The low threshold is not for
+.Tn FreeBSD ,
it's for the CD1400, which can't really keep up with 115200 bps.
.Pp
PollMode: required for Cyclom-16Y's; costs 10-20% relative efficiency
diff --git a/share/man/man4/man4.i386/ed.4 b/share/man/man4/man4.i386/ed.4
index 6545cfc..347164e 100644
--- a/share/man/man4/man4.i386/ed.4
+++ b/share/man/man4/man4.i386/ed.4
@@ -28,7 +28,7 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
-.\" $Id: ed.4,v 1.8 1997/02/22 13:25:18 peter Exp $
+.\" $Id: ed.4,v 1.9 1997/02/28 02:20:42 mpp Exp $
.\"
.Dd October 28, 1995
.Dt ED 4 i386
@@ -82,7 +82,9 @@ identify themselves as 8bit, even though they have a 16bit ISA interface.
Disable transmitter multi-buffering. This flag disables the use of multiple
transmit buffers and may be necessary in rare cases where packets are sent out
faster than a machine on the other end can handle (as evidenced by severe packet
-lossage). Some (non-FreeBSD :-)) machines have terrible ethernet performance
+lossage). Some
+.Pf ( No non- Ns Tn FreeBSD
+:-)) machines have terrible ethernet performance
and simply can't cope with 1100K+ data rates. Use of this flag also provides
one more packet worth of receiver buffering, and on 8bit cards, this may help
reduce receiver lossage.
@@ -164,7 +166,8 @@ have been received but not yet transfered from the card to main memory.
.Sh HISTORY
The
.Nm ed
-device driver first appeared in FreeBSD 1.0.
+device driver first appeared in
+.Fx 1.0 .
.Sh AUTHOR
The
.Nm
diff --git a/share/man/man4/man4.i386/io.4 b/share/man/man4/man4.i386/io.4
index 5e78b5e..798e2b6 100644
--- a/share/man/man4/man4.i386/io.4
+++ b/share/man/man4/man4.i386/io.4
@@ -25,7 +25,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
-.\" $Id$
+.\" $Id: io.4,v 1.4 1997/02/22 13:25:31 peter Exp $
.\"
.Dd Jan 1, 1996
.Dt IO 4 i386
@@ -62,4 +62,4 @@ that even read/only access will grant the full I/O privileges.
The
.Nm io
file appeared in
-FreeBSD 1.0.
+.Fx 1.0 .
diff --git a/share/man/man4/man4.i386/mcd.4 b/share/man/man4/man4.i386/mcd.4
index 1072e80..16a3ba4 100644
--- a/share/man/man4/man4.i386/mcd.4
+++ b/share/man/man4/man4.i386/mcd.4
@@ -24,7 +24,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
-.\" $Id$
+.\" $Id: mcd.4,v 1.3 1997/03/07 02:49:51 jmg Exp $
.\"
.Dd December 8, 1994
.Dt MCD 4 i386
@@ -145,4 +145,5 @@ Andrew A. Chernov, and Jordan K. Hubbard.
.Sh HISTORY
An
.Nm mcd
-driver appeared in FreeBSD Release 1.0.
+driver appeared in
+.Fx 1.0.
diff --git a/share/man/man4/man4.i386/meteor.4 b/share/man/man4/man4.i386/meteor.4
index 1c64998..d8bc409 100644
--- a/share/man/man4/man4.i386/meteor.4
+++ b/share/man/man4/man4.i386/meteor.4
@@ -1,5 +1,5 @@
.\"
-.\" $Id$
+.\" $Id: meteor.4,v 1.5 1997/03/07 02:49:52 jmg Exp $
.\"
.Dd August 15, 1995
.br
@@ -35,7 +35,9 @@ The files required for Matrox Meteor card are:
/usr/include/machine/ioctl_meteor.h)
.br
.in -0.5i
-For FreeBSD release versions 2.1 and earlier, the following patch files are also required:
+For
+.Tn FreeBSD
+release versions 2.1 and earlier, the following patch files are also required:
.br
.in +0.5i
meteor/usr/sys/i386/i386/conf.patch
diff --git a/share/man/man4/man4.i386/pcvt.4 b/share/man/man4/man4.i386/pcvt.4
index 4152aae..372f15f 100644
--- a/share/man/man4/man4.i386/pcvt.4
+++ b/share/man/man4/man4.i386/pcvt.4
@@ -31,7 +31,7 @@
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" @(#)pcvt.4, 3.20, Last Edit-Date: [Sun Apr 2 18:23:39 1995]
-.\" $Id$
+.\" $Id: pcvt.4,v 1.7 1997/03/07 02:49:54 jmg Exp $
.\"
.\" Man page pcvt(4) created after pcvt_ioctl.h on 13-Jan-93
.\" by Joerg Wunsch
@@ -166,9 +166,11 @@ The
.Nm pcvt
console driver is currently available for the Intel-based BSD operating
systems
-.Em NetBSD/i386 Pq release 0.9 or higher,
+.Tn NetBSD/i386
+(release 0.9 or higher),
and
-.Em FreeBSD Pq release 1.0-GAMMA or higher .
+.Tn FreeBSD
+(release 1.0-GAMMA or higher) .
In order to get the appropriate system support, one of the options
.Em PCVT_NETBSD ,
or
@@ -176,13 +178,13 @@ or
must be defined in the system's config file
.Pq see Xr config 8 .
In addition, for the
-.Em FreeBSD
+.Tn FreeBSD
and
-.Em NetBSD
+.Tn NetBSD
operating systems, it is necessary to set this option to the operating
system's version number.
For
-.Em FreeBSD
+.Tn FreeBSD
this version number must be expressed as a 3-digit number.
E.\& g., if you are running the 1.0 release
.Pq which is actually version 1.0.2 ,
@@ -194,8 +196,15 @@ For
.Em NetBSD
this version number must be expressed as 9 if you are running NetBSD 0.9
and anything greater than 9 for NetBSD-current (pre 1.0). It is recommended
-to use (as with FreeBSD) 100 for NetBSD 1.0 and 999 for NetBSD-current.
-E.\& g., if you are running the NetBSD 1.0 release, you should define
+to use (as with
+.Tn FreeBSD )
+100 for
+.Nx 1.0
+and 999 for
+.Tn NetBSD-current.
+E.g., if you are running the
+.Nx 1.0
+release, you should define
.Em PCVT_NETBSD = 100
diff --git a/share/man/man4/man4.i386/spkr.4 b/share/man/man4/man4.i386/spkr.4
index e368d10..c999289 100644
--- a/share/man/man4/man4.i386/spkr.4
+++ b/share/man/man4/man4.i386/spkr.4
@@ -1,5 +1,5 @@
.\"
-.\" $Id$
+.\" $Id: spkr.4,v 1.8 1997/03/07 02:49:58 jmg Exp $
.\"
.Dd November 7, 1993
.Dt SPKR 4 i386
@@ -15,7 +15,8 @@
The speaker device driver allows applications to control the PC console
speaker on an
.Tn IBM-PC Ns --compatible
-machine running FreeBSD.
+machine running
+.Tn FreeBSD .
.Pp
Only one process may have this device open at any given time;
.Xr open 2
@@ -219,4 +220,5 @@ Andrew A. Chernov <ache@astral.msk.su>
.Sh HISTORY
The
.Nm
-device appeared in FreeBSD 1.0.
+device appeared in
+.Fx 1.0 .
diff --git a/share/man/man4/man4.i386/sr.4 b/share/man/man4/man4.i386/sr.4
index 71fba77..81c4689 100644
--- a/share/man/man4/man4.i386/sr.4
+++ b/share/man/man4/man4.i386/sr.4
@@ -28,7 +28,7 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
-.\" $Id$
+.\" $Id: sr.4,v 1.5 1997/02/22 13:25:43 peter Exp $
.\"
.Dd July 4, 1996
.Dt SR 4 i386
@@ -50,7 +50,9 @@ HD64570 chip.
Line speeds of up to 2Mbps is possible. At this speed about 95% of the
bandwidth is usable with 486DX processors.
.Pp
-The standard FreeBSD sppp code is used for the link level layer. The
+The standard
+.Tn FreeBSD
+sppp code is used for the link level layer. The
default protocol used is PPP. The Cisco HDLC protocol can be used by
adding
.Em link2
diff --git a/share/man/man4/man4.i386/tw.4 b/share/man/man4/man4.i386/tw.4
index f89267a..724a1bf 100644
--- a/share/man/man4/man4.i386/tw.4
+++ b/share/man/man4/man4.i386/tw.4
@@ -27,11 +27,11 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
-.\" $Id$
+.\" $Id: tw.4,v 1.6 1997/02/22 13:25:43 peter Exp $
.\"
.Dd Oct 30, 1993
.Dt TW 4 i386
-.Os BSD FreeBSD
+.Os FreeBSD
.Sh NAME
.Nm tw
.Nd TW-523 X-10 device driver
diff --git a/share/man/man4/man4.i386/ze.4 b/share/man/man4/man4.i386/ze.4
index d9c23c7..6125d3b 100644
--- a/share/man/man4/man4.i386/ze.4
+++ b/share/man/man4/man4.i386/ze.4
@@ -23,7 +23,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
-.\" $Id$
+.\" $Id: ze.4,v 1.3 1997/02/22 13:25:46 peter Exp $
.\"
.Dd January 19, 1997
.Dt ZE 4 i386
@@ -69,12 +69,15 @@ Currently the driver does not support multicast.
.Sh HISTORY
The
.Nm
-device driver first appeared in FreeBSD 1.1.5.
+device driver first appeared in
+.Fx 1.1.5 .
.Sh AUTHORS
The
.Nm
device driver was written by Keith Moore.
It is based on work originally by David Greenman, where
Keith made PCMCIA modifications and additions.
-It was adapted for FreeBSD 1.1.5 by Jordan Hubbard.
+It was adapted for
+.Fx 1.1.5
+by Jordan Hubbard.
This manual page was written by David E. O'Brien.
diff --git a/share/man/man4/pcvt.4 b/share/man/man4/pcvt.4
index 4152aae..372f15f 100644
--- a/share/man/man4/pcvt.4
+++ b/share/man/man4/pcvt.4
@@ -31,7 +31,7 @@
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" @(#)pcvt.4, 3.20, Last Edit-Date: [Sun Apr 2 18:23:39 1995]
-.\" $Id$
+.\" $Id: pcvt.4,v 1.7 1997/03/07 02:49:54 jmg Exp $
.\"
.\" Man page pcvt(4) created after pcvt_ioctl.h on 13-Jan-93
.\" by Joerg Wunsch
@@ -166,9 +166,11 @@ The
.Nm pcvt
console driver is currently available for the Intel-based BSD operating
systems
-.Em NetBSD/i386 Pq release 0.9 or higher,
+.Tn NetBSD/i386
+(release 0.9 or higher),
and
-.Em FreeBSD Pq release 1.0-GAMMA or higher .
+.Tn FreeBSD
+(release 1.0-GAMMA or higher) .
In order to get the appropriate system support, one of the options
.Em PCVT_NETBSD ,
or
@@ -176,13 +178,13 @@ or
must be defined in the system's config file
.Pq see Xr config 8 .
In addition, for the
-.Em FreeBSD
+.Tn FreeBSD
and
-.Em NetBSD
+.Tn NetBSD
operating systems, it is necessary to set this option to the operating
system's version number.
For
-.Em FreeBSD
+.Tn FreeBSD
this version number must be expressed as a 3-digit number.
E.\& g., if you are running the 1.0 release
.Pq which is actually version 1.0.2 ,
@@ -194,8 +196,15 @@ For
.Em NetBSD
this version number must be expressed as 9 if you are running NetBSD 0.9
and anything greater than 9 for NetBSD-current (pre 1.0). It is recommended
-to use (as with FreeBSD) 100 for NetBSD 1.0 and 999 for NetBSD-current.
-E.\& g., if you are running the NetBSD 1.0 release, you should define
+to use (as with
+.Tn FreeBSD )
+100 for
+.Nx 1.0
+and 999 for
+.Tn NetBSD-current.
+E.g., if you are running the
+.Nx 1.0
+release, you should define
.Em PCVT_NETBSD = 100
diff --git a/share/man/man4/snp.4 b/share/man/man4/snp.4
index 6ec3c2f..548ed3e 100644
--- a/share/man/man4/snp.4
+++ b/share/man/man4/snp.4
@@ -1,5 +1,5 @@
.\"
-.\" $Id: snp.4,v 1.11 1997/02/22 13:24:43 peter Exp $
+.\" $Id: snp.4,v 1.12 1997/03/19 04:58:33 bde Exp $
.\" $Source: /home/ncvs/src/share/man/man4/snp.4,v $
.\"
.Dd February 24, 1995
@@ -63,4 +63,5 @@ Ugen J.S. Antsilevich <ugen@NetVision.net.il>
.Sh HISTORY
The
.Nm snp
-device first appeared in FreeBSD 2.1.
+device first appeared in
+.Fx 2.1 .
diff --git a/share/man/man4/spkr.4 b/share/man/man4/spkr.4
index e368d10..c999289 100644
--- a/share/man/man4/spkr.4
+++ b/share/man/man4/spkr.4
@@ -1,5 +1,5 @@
.\"
-.\" $Id$
+.\" $Id: spkr.4,v 1.8 1997/03/07 02:49:58 jmg Exp $
.\"
.Dd November 7, 1993
.Dt SPKR 4 i386
@@ -15,7 +15,8 @@
The speaker device driver allows applications to control the PC console
speaker on an
.Tn IBM-PC Ns --compatible
-machine running FreeBSD.
+machine running
+.Tn FreeBSD .
.Pp
Only one process may have this device open at any given time;
.Xr open 2
@@ -219,4 +220,5 @@ Andrew A. Chernov <ache@astral.msk.su>
.Sh HISTORY
The
.Nm
-device appeared in FreeBSD 1.0.
+device appeared in
+.Fx 1.0 .
diff --git a/share/man/man4/uk.4 b/share/man/man4/uk.4
index e943b2c..06860e9 100644
--- a/share/man/man4/uk.4
+++ b/share/man/man4/uk.4
@@ -1,4 +1,4 @@
-.\" $Id$
+.\" $Id: uk.4,v 1.11 1997/02/22 13:24:52 peter Exp $
.\" Copyright (c) 1996
.\" Julian Elischer <julian@freebsd.org>. All rights reserved.
.\"
@@ -39,13 +39,17 @@ driver provides support for a
process to address devices on the scsi bus for which there is no configured
driver.
.Pp
-In FreeBSD releases prior to 2.1, the first unknown device
+Prior to
+.Fx 2.1 ,
+the first unknown device
found will be attached as
.Em uk0
and the next,
.Em uk1
etc.
-Beginning in 2.1 it is possible to specify what uk unit a device should
+Beginning in
+.Fx 2.1
+it is possible to specify what uk unit a device should
come on line as; refer to
.Xr scsi 4
for details on kernel configuration.
diff --git a/share/man/man4/yp.4 b/share/man/man4/yp.4
index 340e321..b9713f0 100644
--- a/share/man/man4/yp.4
+++ b/share/man/man4/yp.4
@@ -26,7 +26,7 @@
.\" SUCH DAMAGE.
.\"
.\" from: @(#)yp.8 1.0 (deraadt) 4/26/93
-.\" $Id$
+.\" $Id: yp.4,v 1.11 1997/02/22 13:24:55 peter Exp $
.\"
.Dd April 5, 1993
.Dt YP 4
@@ -89,7 +89,9 @@ called the
.Pa NIS master server .
The databases used to store the information are called
.Pa NIS maps.
-In FreeBSD, these maps are stored in
+In
+.Tn FreeBSD ,
+these maps are stored in
.Pa /var/yp/[domainname]
where
.Pa [domainname]
@@ -98,7 +100,9 @@ support several domains at once, therefore it is possible to have several
such directories, one for each supported domain. Each domain will have
its own independent set of maps.
.Pp
-In FreeBSD, the NIS maps are Berkeley DB hashed database files (the
+In
+.Tn FreeBSD ,
+the NIS maps are Berkeley DB hashed database files (the
same format used for the
.Xr passwd 5
database files). Other operating systems that support NIS use old-style
@@ -117,7 +121,9 @@ both pieces of information. This means that while you may have
and
.Pa passwd.byname.pag
files on other operating systems (both of which are really parts of the
-same map), FreeBSD will have only one file called
+same map),
+.Tn FreeBSD
+will have only one file called
.Pa passwd.byname .
The difference in format is not significant: only the
NIS server,
@@ -223,8 +229,8 @@ server. A slave server provides the exact same information as a master
server: whenever the maps on the master server are updated, the new
data should be propagated to the slave systems using the
.Xr yppush 8
-command. The NIS Makefile (
-.Pa /var/yp/Makefile )
+command. The NIS Makefile
+.Pf ( Pa /var/yp/Makefile )
will do this automatically if the administrator comments out the
line which says
.Em NOPUSH=true
@@ -265,11 +271,16 @@ but this is sometimes inconvenient. This problem can be avoided simply by
placing a slave server on the local network.)
.El
.Pp
-The FreeBSD
+The
+.Tn FreeBSD
.Xr ypserv 8
is specially designed to provided enhanced security (compared to
-other NIS implementations) when used exclusively with FreeBSD client
-systems. The FreeBSD password database system (which is derived directly
+other NIS implementations) when used exclusively with
+.Tn FreeBSD
+client
+systems. The
+.Tn FreeBSD
+password database system (which is derived directly
from
.Bx 4.4 )
includes support for
@@ -281,9 +292,11 @@ If the encrypted password database were made available as an NIS
map, this security feature would be totally disabled, since any user
is allowed to retrieve NIS data.
.Pp
-To help prevent this, FreeBSD's NIS server
-handles the shadow password maps (
-.Pa master.passwd.byname
+To help prevent this,
+.Tn FreeBSD Ns 's
+NIS server
+handles the shadow password maps
+.Pf ( Pa master.passwd.byname
and
.Pa master.passwd.byuid )
in a special way: the server will only provide access to these
@@ -292,7 +305,7 @@ Since only the super-user is allowed to bind to a privileged port,
the server assumes that all such requests come from privileged
users. All other requests are denied: requests from non-privileged
ports will receive only an error code from the server. Additionally,
-FreeBSD's
+.Tn FreeBSD Ns 's
.Xr ypserv 8
includes support for Wietse Venema's tcp wrapper package; with tcp
wrapper support enabled, the administrator can configure
@@ -304,7 +317,8 @@ they are by no means 100% effective. It is still possible for
someone with access to your network to spoof the server into disclosing
the shadow password maps.
.Pp
-On the client side, FreeBSD's
+On the client side,
+.Tn FreeBSD Ns 's
.Fn getpwent 3
functions will automatically search for the
.Pa master.passwd
@@ -325,16 +339,22 @@ a host that doesn't exist in its
.Pa hosts.byname
or
.Pa hosts.byaddr
-maps. FreeBSD's resolver uses DNS by default (it can be made to use
+maps.
+.Tn FreeBSD Ns 's
+resolver uses DNS by default (it can be made to use
NIS, if desired), therefore its NIS server doesn't do DNS lookups
by default. However,
.Xr ypserv 8
can be made to perform DNS lookups if it is started with a special
flag. It can also be made to register itself as an NIS v1 server
in order to placate certain systems that insist on the presence of
-a v1 server (FreeBSD uses only NIS v2, but many other systems,
-including SunOS 4.x, search for both a v1 and v2 server when binding).
-FreeBSD's
+a v1 server
+.Pf ( Tn FreeBSD
+uses only NIS v2, but many other systems,
+including
+.Tn SunOS
+4.x, search for both a v1 and v2 server when binding).
+.Tn FreeBSD Ns 's
.Xr ypserv 8
does not actually handle NIS v1 requests, but this ``kludge mode''
is useful for silencing stubborn systems that search for both
@@ -345,12 +365,16 @@ a v1 and v2 server.
manual page for a detailed description of these special features
and flags.)
.Sh BUGS
-While FreeBSD now has both NIS client and server capabilities,
+While
+.Tn FreeBSD
+now has both NIS client and server capabilities,
it does not yet have support for
.Xr ypupdated 8
or the
.Fn yp_update
-function. Both of these require secure RPC, which FreeBSD doesn't
+function. Both of these require secure RPC, which
+.Tn FreeBSD
+doesn't
support yet either.
.Pp
The
OpenPOWER on IntegriCloud