AFP3 change

[netatalk.git] / doc / README.ids

diff --git a/doc/README.ids b/doc/README.ids
index 414146f150ea3f2ffbaaa75750da065efa82d4b5..4f27aefe62d5ffa45c99a9935b6dabdb601b7654 100644 (file)
--- a/doc/README.ids
+++ b/doc/README.ids
@@ -62,7 +62,7 @@ their embeded documents.  These can break in the same way as aliases.
 
 So how does netatalk approach the problem?
 
-Netatalk has 4 different methods of allocating IDs: last, hash, mtab or cnid.
+Netatalk has two different methods of allocating IDs: last and cnid.
 
 DID = last.
 
@@ -73,22 +73,9 @@ lost.  This is the most simple method, but it is unreliable.  If you stick to
 the mac features which don't rely heavily on IDs it works fine.  If you try
 to use IDs much, things break.  
 
-DID = hash. 
-
-This uses inodes to identify files.  An inode is a unique number which
-is the equivalent to ID on ext2 (and 3) file systems.  However, an inode is
-significanlty bigger than an ID, so the number needs to be hashed to make it
-smaller.  Unfortunately this means it is nolonger unique, so you can get 2
-files with the same ID.  
-
-DID = mtab.
-
-This is similar to hash, but better.  This is not available on all operating 
-systems. See README.mtab for more details.
-
 DID = cnid. 
 
-This uses a Berkeley 3 database to store and maintain a directory of IDs
+This uses a Berkeley database to store and maintain a directory of IDs
 similar to that of a catalogue file on a mac.  Consequently it is the most
 reliable method.  Unfortunately there seem to be heavy multi user problems 
 that lead to database corruption.  These are being worked on, but cnid remains