Re: Any interest in an AFS interoperability problem solving CZAR?

[Peter Lister, Cranfield Computer Centre]

The real problem we find with 3rd party software is installation into
AFS. Patent "do everything" scripts usually make silly assumptions
about filesystems, the worst being that they assume that if it's not
local, it must be NFS.

We're wise to most of the problems now, and don't mention AFS unless
really necessary (every time we do, the vendor blames AFS; every time
it's been the vendor's fault). It would be nice to be able to give a
brain-dead vendor an authoritative list of do's and don'ts for
installations as well as the programs themselves.

E.g.
Don't assume that filenames can't exceed 32 characters. (Yes, really!)
Don't assume that the directories where I install the files will be one
>From which they're visible to the user.
Do tell me where files will be installed and how they're distributed,
so that I can set up volumes in advance.
Mr Software Vendor, don't tell me "we will only support OSF/DFS when it
arrives". AFS is sufficiently close that you plan supporting both of
them NOW, especially when I am trying to HELP you.

And finally, here's a couple of non-installation gripes:

Don't insist that some file must be world writeable (Yes, really!)
Don't try to list /afs in the file selection widget (e.g. Ghostscript)

Peter Lister                             Email: [EMAIL PROTECTED]
Computer Centre, Cranfield University    Voice: +44 234 754200 ext 2828
Cranfield, Bedfordshire MK43 0AL UK        Fax: +44 234 750875
--- Almost (but not quite) entirely unlike tea ---