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.

1 files changed, 44 insertions, 20 deletions

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