X-Git-Url: https://git.openafs.org/?p=openafs-wiki.git;a=blobdiff_plain;f=AFSLore%2FSupportedConfigurations.mdwn;h=a0e56924bb6ac8c42daa5b4f3867272410489477;hp=e6974d27592541b464062beaca24054412c53166;hb=b217da850bffe150f58d4c368bb8349ebc6aec63;hpb=fc219c92befc7bdbba34f8538247c70737394353 diff --git a/AFSLore/SupportedConfigurations.mdwn b/AFSLore/SupportedConfigurations.mdwn index e6974d2..a0e5692 100644 --- a/AFSLore/SupportedConfigurations.mdwn +++ b/AFSLore/SupportedConfigurations.mdwn @@ -46,6 +46,12 @@ You can easily see that you are using an NAMEI file server if there is a directo ppc_darwin_14 ??? + + alpha_dux[40 + 50 + 51] + ufs , no AdvFS support + @@ -75,10 +81,12 @@ You can easily see that you are using an NAMEI file server if there is a directo - +
These Don't Work reiserfs, vxfs (HP-UX, Solaris) reiserfs, vxfs (HP-UX, Solaris), AdvFS (OSF1/DigitalUnix/CompaqUnix/Tru64Unix)
+Further, [[Tru64Unix]] 5.1 has only server support on ufs. The client is supported under Arla including `AdvFS` (but no server support as of Apr 2002). Server and client should work under DU4.0 and [[Tru64Unix]] 5.0. + - **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