none

diff --git a/AFSLore/SupportedConfigurations.mdwn b/AFSLore/SupportedConfigurations.mdwn
index 34499ef..a4edc60 100644 (file)
--- a/AFSLore/SupportedConfigurations.mdwn
+++ b/AFSLore/SupportedConfigurations.mdwn
@@ -1,3 +1,13 @@
+## <a name="NAMEI vs. inode based file serve"></a> NAMEI vs. inode based file server
+
+There are two different flavours of the AFS file server (the fs process): One uses inodes to store AFS data (volumes, files, metadata), the other uses real files.
+
+The inode-based server needs a file system which supports access by inode and usually a special fsck is required so that the AFS data is not corrupted (since the server does some behind-the-scenes stuff with the file system). The NAMEI file server does not pose any unusual constraints on the underlying filesystem - it's an ordinary userspace program working with (silly-named) files.
+
+You can easily see that you are using an NAMEI file server if there are files like `V0536871833.vol` in your `/vicep*`.
+
+-- [[TinoSchwarze]] - 18 Nov 2002
+
 ## <a name="Recommended Partition Types for"></a><a name="Recommended Partition Types for "></a> Recommended Partition Types for use with [[OpenAFS]]
 
 <table border="1" cellpadding="0" cellspacing="0">
@@ -45,7 +55,7 @@
   </tr>
   <tr>
     <td> i386_linux24 </td>
-    <td><code>ext2</code></td>
+    <td><code>ext2</code>, <code>ext3</code></td>
   </tr>
   <tr>
     <td> sun4x_5[789] </td>