X-Git-Url: http://git.openafs.org/?p=openafs-wiki.git;a=blobdiff_plain;f=SupportedConfigurations.mdwn;h=2425af791d1606199101fd6ad3899c05bbdf919c;hp=d55bd2192824aff7f2dadc9fd273819811836326;hb=02b8df541674329812924d504c5fd6e89f91a277;hpb=8cdb9c5451fe2214895f6df5181ab5d517c94215

diff --git a/SupportedConfigurations.mdwn b/SupportedConfigurations.mdwn
index d55bd21..2425af7 100644
--- a/SupportedConfigurations.mdwn
+++ b/SupportedConfigurations.mdwn
@@ -6,7 +6,7 @@ The inode-based server needs a file system which supports access by inode and us
 
 You can easily see that you are using an NAMEI file server if there is a directory named `AFSIDat` and with subdirectories like `+` and `+1` in your `/vicep*`.
 
--- [[TinoSchwarze]] - 25 Jul 2003
+-- Tino Schwarze - 25 Jul 2003
 
 ## <a name="Recommended Partition Types for"></a><a name="Recommended Partition Types for "></a> Recommended Partition Types for use with [[OpenAFS]]
 
@@ -83,8 +83,8 @@ Further, [[Tru64Unix]] 5.1 has only server support on ufs. The client is support
 
 - **Question:** Does this table imply that clients can't use the NAMEI backend and still need a specific filesystem? Will this ever change?
 
--- [[ToddLewis]] - 06 Nov 2002
+-- Todd Lewis - 06 Nov 2002
 
 - **Another Question:** Does this mean that you can use an NFS mount point as a /vicexx if you use a NAMEI fileserver?
 
--- [[ChrisMcClimans]] - 25 Jul 2003
+-- Chris McClimans - 25 Jul 2003