NFS directory heirarchy for very heterogeneous environment

[David Carmean <dlc@silcom.com>]

I'm configuring an NFS server to serve a large variety of
*n*x systems, and I'm not really happy with the way the
other servers around here have been configured previously.
I'm wondering if anyone has any tips/anecdotes/horror stories.

Hardware platforms include single and multi-processor x86,
sun4m, sun4u, even a couple of sun4c's, and Alpha CPUs.
OSes include Linux (various RedHat and Debian releases,
x86 only so far), Solaris 2.4-2.8 (x86 and Sparc),
OSF1/Ultix/True-flavor-of-the-week for the Alphas (about which
I know little or nothing; mostly just a place-holder for now),
and FreeBSD.

I'd like to create parallel /usr/local/bin directories for each,
at least; probably /usr/local/{src,build,lib,libexec,share}
also.

I'm wondering to what extent I can create a single
/export/sun4-sunos5 - type directory for each flavor.  I.e. am
I going to have to create an /export/sun4c-sunos5.4 as well
as an /export/sun4u-sunos5.8 tree?

Or maybe I do something like this:

    foo:~> mount
    blah
    blah
    /n/filer/sun4-sunos5 on filer:/export/sun4-sunos5
    /usr/local on filer:/export/sun4u-sunos5.7

where /export/sun4u-sunos5.7 is almost exclusively symlinks
back to /n/filer/sun4-sunos5 except for the few arch/release
specific utilities like top, lsof, etc???

Achhk!  This could grow into a monster.  Any ideas?

Thanks.

--