diff --git a/usr.man/man5/namespace.5 b/usr.man/man5/namespace.5
new file mode 100644
index 0000000..d0f93b8
--- /dev/null
+++ b/usr.man/man5/namespace.5
@@ -0,0 +1,71 @@
+.\"
+.\" $Id: namespace.5,v 1.1 1999/02/13 19:56:16 gdr-ftp Exp $
+.\"
+.TH NAMESPACE 5 "7 February 1999" GNO "File Formats"
+.SH NAME
+.BR namespace
+\- map GS/OS partitions to GNO mount points
+.SH SYNOPSIS
+/etc/namespace
+.SH DESCRIPTION
+The 
+.BR namespace
+file is parsed by the GNO kernel when the kernel is booting.  The mappings
+in this file allow the kernel to provide a continguous hierarchy of 
+directories without requiring those directories to be on the same physical
+disk partition.  This is similar to the UNIX concept of mount points.
+.LP
+The format of the
+.BR namespace 
+file is:
+.nf
+
+	:mountpoint	:path:to:real:directory
+
+.fi
+Comments are not currently allowed in the file.
+It is critical that only colons be used as pathname delimiters in this
+file, and that no trailing colons are specified.
+.SH EXAMPLE
+In this abbreviated example, the /usr directory hierarchy exists on a
+different physical partition than do /bin and /dev:
+.nf
+	:bin	:disk1:bin
+	:dev	:disk1:dev
+	:usr	:disk2:moreGNOstuff:usr
+.fi
+.SH BUGS
+There is currently a limit of about 20 entries in the 
+.BR namespace
+file.
+.LP
+Whitespace can appear in the names of neither the mount point nor the
+directory being mounted.
+.LP
+Only a single directory component can be specified for the mount point.
+Therefore, the following would be an illegal entry:
+.nf
+	:usr:local	:disk3:local
+.fi
+.LP
+One would expect that files existing in the same directory as the GNO
+kernel binary could be referenced relative to the root partition (for
+example, referencing the 
+.BR initrc
+file as
+.BR /initrc ).
+This is not permitted; such a reference will cause the relevent system
+call to fail with ENOENT.
+Similarily, one cannot refer to the directory in which the kernel resides as
+.BR / ).
+.LP
+The specified mount points cannot currently be used as home directories.
+For example, root's home directory cannot be /root, where /root is defined
+in /etc/namespace as:
+.nf
+        :root   :hd3:root
+.fi
+.SH HISTORY
+The 
+.BR namespace
+facility first appeared in GNO v2.0.
diff --git a/usr.man/man5/resolver.5 b/usr.man/man5/resolver.5
new file mode 100644
index 0000000..c41cee6
--- /dev/null
+++ b/usr.man/man5/resolver.5
@@ -0,0 +1,94 @@
+.\" Copyright (c) 1986 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms are permitted
+.\" provided that the above copyright notice and this paragraph are
+.\" duplicated in all such forms and that any documentation,
+.\" advertising materials, and other materials related to such
+.\" distribution and use acknowledge that the software was developed
+.\" by the University of California, Berkeley.  The name of the
+.\" University may not 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.
+.\"
+.\"	@(#)resolver.5	5.9 (Berkeley) 12/14/89
+.\"
+.TH RESOLVER 5 "7 February 1999" GNO "File Formats"
+.SH NAME
+resolver \- resolver configuration file
+.SH SYNOPSIS
+/etc/resolv.conf
+.SH DESCRIPTION
+.LP
+The
+.I resolver
+is a set of routines in the C library (\c
+.IR resolv (3))
+that provide access to the Internet Domain Name System.
+The resolver configuration file contains information that is read
+by the resolver routines the first time they are invoked by a process.
+The file is designed to be human readable and contains a list of
+keywords with values that provide various types of resolver information.
+.LP
+On a normally configured system this file should not be necessary.
+The only name server to be queried will be on the local machine,
+the domain name is determined from the host name,
+and the domain search path is constructed from the domain name.
+.LP
+The different configuration options are:
+.IP \fBnameserver\fP
+Internet address (in dot notation) of a name server
+that the resolver should query.
+Up to MAXNS (currently 3) name servers may be listed,
+one per keyword.
+If there are multiple servers,
+the resolver library queries them in the order listed.
+If no \fBnameserver\fP entries are present,
+the default is to use the name server on the local machine.
+(The algorithm used is to try a name server, and if the query times out,
+try the next, until out of name servers,
+then repeat trying all the name servers
+until a maximum number of retries are made).
+.IP \fBdomain\fP
+Local domain name.
+Most queries for names within this domain can use short names
+relative to the local domain.
+If no \fBdomain\fP entry is present, the domain is determined
+from the local host name returned by
+\fIgethostname\fP\|(2);
+the domain part is taken to be everything after the first `.'.
+Finally, if the host name does not contain a domain part, the root
+domain is assumed.
+.IP \fBsearch\fP
+Search list for host-name lookup.
+The search list is normally determined from the local domain name;
+by default, it begins with the local domain name, then successive
+parent domains that have at least two components in their names.
+This may be changed by listing the desired domain search path
+following the \fIsearch\fP keyword with spaces or tabs separating
+the names.
+Most resolver queries will be attempted using each component
+of the search path in turn until a match is found.
+Note that this process may be slow and will generate a lot of network
+traffic if the servers for the listed domains are not local,
+and that queries will time out if no server is available
+for one of the domains.
+.IP
+The search list is currently limited to six domains
+with a total of 256 characters.
+.LP
+The \fIdomain\fP and \fIsearch\fP keywords are mutually exclusive.
+If more than one instance of these keywords is present,
+the last instance will override.
+.LP
+The keyword and value must appear on a single line, and the keyword
+(e.g. \fBnameserver\fP) must start the line.  The value follows
+the keyword, separated by white space.
+.SH FILES
+.I /etc/resolv.conf
+.SH SEE ALSO
+gethostbyname(3N), resolver(3), hostname(7), named(8)
+.br
+Name Server Operations Guide for BIND