namespace.5, resolver.5:

- initial checkin
This commit is contained in:
gdr-ftp 1999-02-13 19:56:16 +00:00
parent ba2ef9169c
commit d9d4770f9f
2 changed files with 165 additions and 0 deletions

71 Normal file
View File

@ -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"
.BR namespace
\- map GS/OS partitions to GNO mount points
.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.
The format of the
.BR namespace
file is:
:mountpoint :path:to:real:directory
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.
In this abbreviated example, the /usr directory hierarchy exists on a
different physical partition than do /bin and /dev:
:bin :disk1:bin
:dev :disk1:dev
:usr :disk2:moreGNOstuff:usr
There is currently a limit of about 20 entries in the
.BR namespace
Whitespace can appear in the names of neither the mount point nor the
directory being mounted.
Only a single directory component can be specified for the mount point.
Therefore, the following would be an illegal entry:
:usr:local :disk3:local
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 / ).
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:
:root :hd3:root
.BR namespace
facility first appeared in GNO v2.0.

94 Normal file
View File

@ -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.
.\" @(#)resolver.5 5.9 (Berkeley) 12/14/89
.TH RESOLVER 5 "7 February 1999" GNO "File Formats"
resolver \- resolver configuration file
.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.
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.
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
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.
The search list is currently limited to six domains
with a total of 256 characters.
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.
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.
.I /etc/resolv.conf
gethostbyname(3N), resolver(3), hostname(7), named(8)
Name Server Operations Guide for BIND