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*`.
+You can easily see that you are using an NAMEI file server if there are files like `V0536871833.vol` in your `/vicep*`. (this is incorrect... transarc sun4x\_58 shows these files and is not NAMEI -- guest)
-- [[TinoSchwarze]] - 18 Nov 2002
</tr>
<tr>
<td> sun4x_5[789] </td>
- <td><code>ufs</code> w/o logging </td>
+ <td><code>ufs</code> w/o logging (client logging works OK for me) </td>
</tr>
<tr>
<td> aix_4[345] , aix_51 </td>