* Thomas Klausner <wiz@danbala.ifoer.tuwien.ac.at>
November 21, 2000: lots of NetBSD fixes (many of which are generic).
+November 28, 2004: small fixes to typos in amd.conf(5) man page.
+
* Olaf Kirch <okir@caldera.de>
February 1, 2001: important Linux NFS error number mapping fixed
+2004-11-29 Erez Zadok <ezk@cs.sunysb.edu>
+
+ * scripts/amd.conf.5: Small fixes to typos in man page, from
+ Thomas Klausner <tk@giga.or.at>.
+
2004-09-15 Erez Zadok <ezk@cs.sunysb.edu>
* doc/am-utils.texi: fix old URLs.
.\"
.\" %W% (Berkeley) %G%
.\"
-.\" $Id: amd.conf.5,v 1.7.2.10 2004/01/21 04:04:58 ib42 Exp $
+.\" $Id: amd.conf.5,v 1.7.2.11 2004/11/29 16:32:13 ezk Exp $
.\"
.TH AMD.CONF 5 "7 August 1997"
.SH NAME
If "yes", then amd's top-level mount points will be browsable to
.BR readdir (3)
calls. This means you could run for example
-.BR ls (3)
+.BR ls (1)
and see what keys are available to mount in that directory. Not all entries
are made visible to readdir(3): the "/default" entry, wildcard
entries, and those with a "/" in them are not included. If you specify
the correct
.I karch
variable set (for example, sun4c, sun4m, sun4u, etc.) Note that if not
-specified, amd will use uname(2) to figure out the kernel architecture of
+specified, amd will use uname(3) to figure out the kernel architecture of
the machine.
.TP
poor interactive response; too short an interval causes excessive retries.
.TP
-.BR nfs_allow_insecure_port " (string, default=no).
+.BR nfs_allow_insecure_port " (string, default=no)"
Normally amd will refuse requests coming from unprivileged ports (i.e.
ports >= 1024 on Unix systems), so that only privileged users and the kernel
can send NFS requests to it. However, some kernels (certain versions of