Thomas Klausner <tk@giga.or.at>.
* ldap.schema: add this file to distribution.
* Wolfram Klaus <klaus@physik.fu-berlin.de>.
November 21, 2000: recognize proplist mnttab flag.
-* Thomas Klausner <wiz@danbala.ifoer.tuwien.ac.at>
+* Thomas Klausner <tk@giga.or.at>
November 21, 2000: lots of NetBSD fixes (many of which are generic).
April 18, 2003: patch to reference am-utils info pages in man page.
+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-10-22 Erez Zadok <ezk@cs.sunysb.edu>
+
+ * ldap.schema: add this file to distribution.
+
2004-09-15 Erez Zadok <ezk@cs.sunysb.edu>
* doc/am-utils.texi: fix old URLs.
buildall \
config.guess.long \
depcomp \
+ ldap.schema \
ldap-id.ms \
ldap-id.txt \
stamp-h.in \
# Authored by Erez Zadok and/or source maintainers
# Definition by Tim Colles <timc@dai.ed.ac.uk>
-# OID Base is 1.3.6.1.4.1.aaa.bbb.ccc
+# OID Base is 1.3.6.1.4.1.10180
#
-# Syntaxes are under 1.3.6.1.4.1.aaa.bbb.ccc.3.175-199
-# Attribute types are under 1.3.6.1.4.1.aaa.bbb.ccc.2.175-199
-# Object classes are under 1.3.6.1.4.1.aaa.bbb.ccc.1.175-199
+# Syntaxes are under 1.3.6.1.4.1.10180.3.175-199
+# Attribute types are under 1.3.6.1.4.1.10180.2.175-199
+# Object classes are under 1.3.6.1.4.1.10180.1.175-199
# Atribute Type Definitions
-attributetype ( 1.3.6.1.4.1.aaa.bbb.ccc.2.175 NAME 'amdmapTimestamp'
+attributetype ( 1.3.6.1.4.1.10180.2.175 NAME 'amdmapTimestamp'
DESC 'Probably the time the map was last modified'
EQUALITY integerMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SINGLE-VALUE )
-attributetype ( 1.3.6.1.4.1.aaa.bbb.ccc.2.176 NAME 'amdmapName'
+attributetype ( 1.3.6.1.4.1.10180.2.176 NAME 'amdmapName'
DESC 'The symbolic name of the map, ie. map_name'
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE )
-attributetype ( 1.3.6.1.4.1.aaa.bbb.ccc.2.177 NAME 'amdmapKey'
+attributetype ( 1.3.6.1.4.1.10180.2.177 NAME 'amdmapKey'
DESC 'The key value for this entry'
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE )
-attributetype ( 1.3.6.1.4.1.aaa.bbb.ccc.2.178 NAME 'amdmapValue'
+attributetype ( 1.3.6.1.4.1.10180.2.178 NAME 'amdmapValue'
DESC 'The mount information for this entry'
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE )
# Object Class Definitions
-objectclass ( 1.3.6.1.4.1.aaa.bbb.ccc.1.175 NAME 'amdmapTimestamp'
+objectclass ( 1.3.6.1.4.1.10180.1.175 NAME 'amdmapTimestamp'
SUP top STRUCTURAL
DESC 'Timestamp for an AMD map'
MUST ( cn $ amdmapName $ amdmapTimestamp ) )
-objectclass ( 1.3.6.1.4.1.aaa.bbb.ccc.1.176 NAME 'amdmap'
+objectclass ( 1.3.6.1.4.1.10180.1.176 NAME 'amdmap'
SUP top STRUCTURAL
DESC 'Defines an AMD map entry'
MUST ( cn $ amdmapName $ amdmapKey $ amdmapValue ) )
.\"
.\" %W% (Berkeley) %G%
.\"
-.\" $Id: amd.conf.5,v 1.27 2004/01/22 05:01:06 ezk Exp $
+.\" $Id: amd.conf.5,v 1.28 2004/11/29 16:31:34 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
will reload only those maps that have changed.
.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