* Remove some more references to DB3, and mention exactly which versions of BDB

[netatalk.git] / doc / INSTALL

diff --git a/doc/INSTALL b/doc/INSTALL
index d650b5ae0ed5b2e894fccd2023880b8caf9d1068..2114c6d8d859f6838f38b350eacb16c7c74a6b1d 100644 (file)
--- a/doc/INSTALL
+++ b/doc/INSTALL
@@ -85,7 +85,7 @@ This step reads the options to the ./configure program and checks your
 system against the requirements of those options. It generally fails
 if your system doesn't meet the requirements. You should read the
 DEVELOPER file because some of these options require external sources
-to function correctly. (PAM, OpenSSL, Berkeley DB3, TCP Wrappers, etc).
+to function correctly. (PAM, OpenSSL, Berkeley DB, TCP Wrappers, etc).
 
 Netatalk options to the ./configure script: Use ./configure --help for
 a complete list.
@@ -99,18 +99,18 @@ a complete list.
 --enable-dropkludge: enable the experimental dropbox fix
        (INSECURE!),
 
---with-db3=PATH: specify path to Berkeley DB3 installation,
+--with-bdb=PATH: specify path to Berkeley DB installation,
+
+--with-did=[scheme]: set DID scheme (cnid,last),
+       CNID is a new scheme using Berkeley DB files to store a
+       per-volume cnid database persistently.
 
---with-did=[scheme]: set DID scheme (last,mtab,cnid),
        The last DID scheme recreates version 37b behaviour where
        directory id's are incrementally calculated versus the new
        hash method. Unfortunately for machines that have a lot of
        devices, and/or a lot of inodes the hash can fail with
        multiple directories resolving to the same DID.
 
-       cnid is a new and experimental scheme using Berkeley DB3 files
-       to store a per-volume cnid database persistently.
-
 --with-message-dir=path: path to message files [default is DISABLED],
 
 --enable-srvloc: Turn on Server Location Protocol support,